HR to ERP
Dayforce to Unit4 integration: Dayforce employees as resources in Unit4 ERP, per legal entity and on date
With an integration between Dayforce and Unit4 ERP, every new employee from Dayforce becomes an employee in the Unit4 company of their legal entity, with department and cost centre from their work assignment as relations from the effective date. A termination in Dayforce terminates the employee in Unit4, so no more hours are booked on them after the last working day.
What the integration does
Organisations that run HR, scheduling and time in Dayforce and projects and finance in Unit4 ERP create employees in Unit4 from a list out of Dayforce. A transfer to another department is in Dayforce ahead of time, but only reaches Unit4 when someone goes through the list again.
- KoppelHet asks Dayforce which employees were updated, hired or terminated since the previous run.
- Per employee KoppelHet reads the work assignments and the status, with their start and end dates.
- After a check without saving, a new employee goes into the Unit4 company of their legal entity.
- Department and cost centre go to Unit4 as relations with the effective date from Dayforce.
- After a termination in Dayforce KoppelHet sets the employee in Unit4 to terminated.
What to watch for with Dayforce and Unit4 ERP
- Work assignments in Dayforce have their own start and end date, and with a date range future rows can be requested too. KoppelHet sets each work assignment as a relation with dateFrom and dateTo in Unit4, so a transfer on the first of the month takes effect in Unit4 on that day.
- Org units in Dayforce can be requested with the legal entity they belong to. KoppelHet uses that to determine the Unit4 company, and processes per company, because Unit4 does not accept employees from different companies in one call.
- Dayforce groups statuses into Active, Inactive and Terminated. An employee on long-term leave is often Inactive; KoppelHet then does not terminate them in Unit4, so project postings and history stay with the same employee.
- Dayforce leaves out a field if the API user's role has no access to it or if it is empty. KoppelHet therefore does not read a missing department as the end of the relation in Unit4, but reports it, so a permissions problem does not close relations.
- Dayforce employee details are limited to 100 per minute, shared with all of the customer's other integrations, such as payroll. KoppelHet only requests employees updated since the previous run, and spreads the first load of Unit4 over several nights.
- If a start date in Dayforce is moved later, Unit4 does not let the employment start date be set later. KoppelHet then removes the employment in Unit4 and sets it up again with the new date, after Unit4 has checked it without saving first.
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
Do hours from Dayforce also go to Unit4?
Not in this integration. Booking hours on projects in Unit4 can be added later as an extension.
Which permissions does the API user need in Dayforce?
The role feature for RESTful Services and field-level access on name, work assignment, status and org unit. Pay and bank details are not needed.
Can Unit4 also be the source for cost centres in Dayforce?
That can be added later as an extension. In the first version only employees and their relations go from Dayforce to Unit4.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Dayforce RESTful Web Services at https://www.dayforcehcm.com/api/{CompanyName}/V1/Employees with filterUpdatedStartDate and filterUpdatedEndDate, filterHireStartDate and filterTerminationStartDate (XRefCodes only), then per XRefCode with expand for WorkAssignments, EmploymentStatuses and OrgUnitInfos, with contextDateRangeFrom and contextDateRangeTo. Org units through /V1/OrgUnits/{XRefCode} with expand OrgUnitLegalEntities. Role feature RESTful Services > Employee with field-level access; 100 employee details per minute per customer.
- Unit4 ERPx through the Employees API with client ID and secret - POST /v1/employees/validate, POST /v1/employees/batch (at most 200 per call, one companyId), PATCH with AddOrReplaceById and RemoveById on relatedValues and employments, DELETE /v1/employees/{personId} for the status Terminate. With an active workflow Unit4 answers with 202.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Dayforce | Field in Unit4 ERP | Notes |
|---|---|---|
XRefCode | personId | Automatic numbering in Unit4 off |
Legal entity van de org unit | companyId | Fixed table per legal entity |
FirstName, LastName | nameInformation.firstName, surname | |
HireDate, TerminationDate | employments (startDate, endDate) | |
WorkAssignments (Position.Department, EffectiveStart, EffectiveEnd) | relatedValues afdeling (dateFrom, dateTo) | |
Kostenplaats uit de werktoewijzing of org unit | relatedValues kostenplaats (dateFrom, dateTo) | Which relationId per Unit4 setup |
EmploymentStatuses | Status in Unit4 | Only Terminated ends the employment |
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