Time Clock Job and Cost Center Transfers Across HCMs

A time clock job or cost center transfer lets an employee switch the job, department, project or cost center they are working for at the moment they punch, so hours are charged to the right place and paid at the right rate. It matters for labor costing, overtime calculations and payroll accuracy, and it must sync cleanly with your HCM.

Disclosure: The author works at CloudApper, which makes CloudApper AI TimeClock, which is discussed in this article.

Key takeaways

• Transfers at the clock record where time was worked, not just how long.
• Different job rates in one week affect the FLSA regular rate used for overtime.
• Limit transfer choices to valid combinations for each employee to prevent errors.
• Offline punches and transfers must sync to the HCM without losing detail.
• Test transfers end to end through payroll before going live.

What is a job or cost center transfer at the time clock?

Many hourly employees work in more than one role or location in a shift: a cashier who covers the stockroom, a nurse aide who floats between units, a technician who charges hours to several projects. A transfer captures that change. At punch in, or mid-shift, the employee selects a different job, labor category, department, location or cost center. The system then splits the hours on the timecard.

Each HCM names these elements differently. UKG uses labor categories and job transfers, Workday uses worktags such as cost centers and projects, and Dayforce and Oracle Cloud HCM use their own job, department and costing structures. Your setup decides which values are transferable. Our guide to Workday org design with supervisory orgs and cost centers explains how those structures affect costing.

Why do transfers matter for pay compliance?

Under the Fair Labor Standards Act, employers must keep accurate records of hours worked and wages paid. When a nonexempt employee works two or more jobs at different rates in the same workweek, the Department of Labor explains that the regular rate for overtime is generally the weighted average of those rates: total straight-time earnings divided by total hours worked. If transfers are missed, hours land at the wrong rate and overtime can be miscalculated.

Transfers also drive labor cost reporting, grant or contract billing, and union rules that apply different rates to different work. Pay rules in the HCM must recognize transferred hours correctly; for UKG customers, our UKG Pro WFM pay rule and work rule checklist covers that side of the configuration.

How should transfers work at the clock?

Design choice	Good practice	Common mistake
Transfer options	Show only jobs and cost centers valid for that employee	A long list of every cost center
Timing	Allow transfer at punch in and mid-shift	Requiring a punch out and back in
Default values	Use the employee's primary job unless changed	No default, forcing a choice every punch
Validation	Catch invalid combinations before payroll	Fixing errors during payroll close
Offline handling	Store transfers with the punch and sync later	Dropping transfer detail when offline
Manager review	Flag unusual transfers for approval	No visibility until pay is wrong

Questions to ask any time clock vendor

• Which HCM objects (jobs, labor categories, worktags, cost centers) can the clock read and write?
• Are transfer lists filtered by employee, location or schedule?
• How are transfers stored and synced when the device is offline?
• Can managers correct a transfer, and is the change audited?
• Does the sync run in real time or in batches, and how are failures reported?

Where does CloudApper AI TimeClock fit?

CloudApper AI TimeClock runs on iPads, Android or iOS tablets, web browsers and desktops, and integrates with UKG, Workday, Ceridian Dayforce, Oracle Cloud HCM and other systems. Its configurable data capture forms and prompts can collect job transfers at the punch, and the product page states that job transfers, custom prompts and attestations work offline and sync later, and that incorrect job transfers can be caught before they reach payroll. The Workday version lists job transfer and pay code capture, custom timesheet allocations, project-based time tracking and labor transfers; the UKG version lists customizable data capture for job changes and pay codes. Punches can be made with facial recognition, QR code, barcode or NFC.

For Dayforce-specific setup, our post on an AI powered time clock for Ceridian Dayforce HCM covers that integration.

Frequently Asked Questions

Can an employee transfer jobs without punching out?

Most modern time clocks support a mid-shift transfer, where the employee selects a new job or cost center and the system ends one segment and starts another without a separate punch out. Whether this is available depends on your HCM configuration and clock vendor, so confirm it during setup and testing.

How does a job transfer affect overtime pay?

If an employee works jobs with different pay rates in the same workweek, overtime is generally based on a weighted average regular rate under the FLSA, unless another permitted method applies. Accurate transfers ensure each hour is recorded at the correct rate, so payroll can calculate the regular rate and overtime correctly.

What should we test before going live with transfers?

Test transfers at punch in and mid-shift, offline punches that sync later, invalid combinations, manager corrections and an overtime week with two rates. Then follow each test through to the timecard, the payroll results and labor cost reports in your HCM to confirm nothing is lost or misallocated.

Next steps

1. List every job, labor category and cost center employees actually transfer between.
2. Define which combinations are valid for each role and location.
3. Run an end-to-end payroll test before rolling transfers out to all sites.

Last reviewed: October 2026.

Sources

• Fact Sheet #23: Overtime Pay Requirements of the FLSA, U.S. Department of Labor
• Fact Sheet #21: Recordkeeping Requirements under the FLSA, U.S. Department of Labor
• Employee Time Clock Software, CloudApper