Leave, absence and time
Dayforce to UKG Dimensions integration: employees and approved time away from work from Dayforce in UKG
With an integration between Dayforce and UKG Dimensions, every employee from Dayforce appears automatically in UKG, with their job, manager, pay rule and status. Approved time away from work from Dayforce arrives in UKG as a paycode edit, including half days.
What the integration does
Organisations that run HR and payroll in Dayforce but use UKG Dimensions for scheduling and timekeeping in part of the business, for example after an acquisition, maintain employees twice. Time off approved in Dayforce is not in the UKG schedule.
- Every hour KoppelHet asks Dayforce which employees changed since the previous run.
- Per employee KoppelHet reads status, work assignments and manager, and creates or updates the person in UKG.
- For employees scheduled in UKG, KoppelHet fetches time away from work over a fixed window ahead.
- Approved requests become paycode edits; cancelled ones are removed again.
- When an employment ends, KoppelHet sets the status in UKG on that date.
What to watch for with Dayforce and UKG Dimensions
- Dayforce only returns time away from work per employee, and only with a mandatory start, end and status. KoppelHet therefore only requests leave for employees who have a UKG absence license, over a window of a few months, so the number of calls stays limited.
- The status values of time away from work are case-sensitive and can differ per customer from APPROVED and CANCELED. UKG only has a paycode edit that is either there or not. KoppelHet records at the start which Dayforce value means approved and which means withdrawn, and reads both.
- Dayforce marks a request as a full day or half day and gives the net hours and start time. UKG can take the hours of a first or second half day from the schedule itself. KoppelHet uses the start time to decide whether it is the morning or the afternoon, and only sends the net hours when they differ.
- Dayforce lets you fetch a manager with the employee, but the default as-of date is today. UKG wants a manager who already exists or appears earlier in the same request. For a future team change KoppelHet requests the manager with the effective date as the as-of date and puts the new manager in UKG first.
- Dayforce omits a field without a value entirely, and a field without field rights too, without an error. For UKG that matters: a missing location would produce an employee without a job path, which UKG rejects. KoppelHet checks at the start whether location, job and pay type really come back, and skips an employee without a location with an alert.
- Dayforce has a pay type and pay class per employee with an effective date. In UKG the pay rule decides how overtime and premiums land on the timecard. KoppelHet chooses the pay rule from that combination and sets a change with the same effective date, so a switch from hourly to salaried starts in the right week.
How we build and run it
- The integration runs on the KoppelHet platform, hosted in a data centre in the EU.
- Every sync and every error is visible in the functional log; on an error your administrator is notified.
- A change that cannot go through is not half-applied but queued for another attempt.
- KoppelHet is ISO 27001 certified. Data travels encrypted and stays on the platform no longer than needed.
- After go-live we manage the integration and adjust it when your process changes.
- The integration fits next to your existing integration layer. Only the fields in the design are transferred; the platform keeps no register of its own.
Implementation and price
This is not an app you switch on. We build the integration for your organisation on our platform, with building blocks we reuse on every project. So it is custom work that does not start from scratch.
A consultant prepares the intake and analyses both systems. We then record the mapping and exceptions field by field, test in the test or acceptance environment and go live at a moment you choose. Costs are a one-off amount for the setup and a monthly amount for platform, monitoring and support.
Frequently asked questions
Why not schedule everything in Dayforce?
That is possible, and then this integration is not needed. It is meant for the period or part of the business in which UKG stays.
Do hours from UKG go back to Dayforce?
Not in this integration. Hours to payroll can be added later as an extension.
What if a Dayforce reason has no paycode in UKG?
Then KoppelHet does not enter the leave and an alert appears. HR links a paycode or confirms the reason is not needed in scheduling.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Dayforce through the RESTful Web Services with the role RESTful Services > Employee and field rights per element and parent item. Changed employees through GET /V1/Employees with filterUpdatedStartDate and filterUpdatedEndDate; details per XRefCode with Expand=EmploymentStatuses,WorkAssignments,EmployeeManagers and ContextDate as the as-of date.
- Leave through GET /V1/Employees/{xRefCode}/TimeAwayFromWork with filterTAFWStartDate, filterTAFWEndDate and status (case-sensitive, customer-configurable); fields TAFWXRefCode, TimeStart, TimeEnd, NetHours, AllDay, HalfDay and ReasonName.
- To UKG through the UKG Pro Workforce Management API: POST /v1/commons/persons or /multi_create (personNumber, employmentStatusList, primaryLaborAccounts.organizationPath, payRuleName, supervisorPersonNumber, personLicenseTypes). Leave through POST /v1/timekeeping/pay_code_edits/import with scheduleAmountType FULL_DAY_, FIRST_HALF_DAY_ or SECOND_HALF_DAY_AMOUNT_FROM_SCHEDULE, or durationInHours.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Dayforce | Field in UKG Dimensions | Notes |
|---|---|---|
XRefCode | personNumber | |
FirstName, LastName | person (firstName, lastName) | |
WorkAssignments (IsPrimary) met Location en Job | primaryLaborAccounts.organizationPath | Through a table to a job that exists in UKG |
EmployeeManagers | supervisorPersonNumber | |
EmploymentStatuses (PayType, PayClass) | payRuleName | |
EmploymentStatuses (EffectiveStart, EffectiveEnd) | employmentStatusList | |
TimeAwayFromWork (goedgekeurd, ReasonName) | Paycode edit met paycode per reden | |
AllDay, HalfDay, NetHours | scheduleAmountType of durationInHours |
Related
Ashby → Dayforce
Ashby to Dayforce integration: have Dayforce validate the hire first, then save it
Bullhorn → Dayforce
Bullhorn to Dayforce integration: first placement of an employee as an employee in Dayforce
Carerix → Dayforce
Carerix to Dayforce integration: successful placement as a validated new employee in Dayforce
Dayforce → 4PS Construct
Dayforce to 4PS Construct integration: technicians and site managers from Dayforce in 4PS, with cost centre and end date