X4HR to ITSM
Dayforce to Xurrent integration: people and requests on hire, transfer and termination
With an integration between Dayforce and Xurrent, every employee from Dayforce is a person in Xurrent, with organisation, site and manager, and a hire, transfer or departure in Dayforce sets up a request from the right template. KoppelHet reads the Dayforce REST API and writes through the Xurrent REST API.
What the integration does
Organisations with Dayforce as HR system and Xurrent for IT and facilities services often load people with a periodic import file. Between two imports new colleagues are missing, and a transfer to another location only reaches Xurrent after weeks.
- KoppelHet asks Dayforce for hires within the onboarding window and for changed work assignments.
- For each employee KoppelHet fetches work assignment, org unit, contact details and manager with the effective date as reference date.
- The manager becomes a person first if they are not one yet, then the employee, with the XRefCode as sourceID.
- A request from the right template is submitted for the employee, by the manager.
- After a completed offboarding request KoppelHet disables the person.
What to watch for with Dayforce and Xurrent (4me)
- KoppelHet reads the Dayforce REST API with a user that only reads and writes people and requests through the Xurrent API, with an OAuth token of its own integration user.
- A person in Xurrent cannot exist without a primary email address. Dayforce only returns the work email if the API user's role has field access to contact details; if it is missing, KoppelHet reports a permission problem instead of skipping the person.
- The work email is also the login name in Xurrent and changes with a change of name. KoppelHet sets the Dayforce XRefCode as sourceID, so the same person gets the new address.
- Dayforce can return employees as they are on a chosen date. On a transfer KoppelHet submits the access request straight away, but only sets the new organisation and site in Xurrent on the effective date, so approvals stay with the current department until that day.
- A request in Xurrent needs a submitter and a recipient. KoppelHet sets the manager from Dayforce as submitter; if they are new themselves, for example a location manager starting together with their team, KoppelHet creates them first.
- Org units in Dayforce become organisations in Xurrent with the parent unit as parent. Dayforce can filter by unit, so only the units of this Xurrent environment are included.
- A disabled person may no longer be linked to new records in Xurrent. Dayforce often reports a departure well ahead; KoppelHet submits the offboarding request straight away and only disables the person once that request is done.
This integration is also part of joiner, mover, leaver.
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
Can the periodic import file stay?
It is dropped, so that two sources do not update the same people. KoppelHet can deliver a large reorganisation as an import file.
Does pay data go to Xurrent?
No. KoppelHet only requests name, contact details, work assignment, organisation and manager.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Dayforce through the REST API at /api/{clientName}/v1/Employees with FilterHireStartDate, FilterTerminationStartDate, OrgUnitXRefCode and FilterUpdatedStartDate with filterUpdatedEntities; then Employees/{XRefCode} with expand (WorkAssignments, Contacts, EmployeeManagers) and ContextDate. Fields only with field access in the API user's role.
- Xurrent through the REST API with an OAuth token. People through /people (primary_email required, employeeID, job_title, organization, site, manager, disabled), organisations through /organizations, sites through /sites. Requests through POST /requests with subject, category, team, requested_for, requested_by, template and desired_completion_at. Rate limiting per user with HTTP 429.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Dayforce | Field in Xurrent (4me) | Notes |
|---|---|---|
XRefCode | source en sourceID | |
Werkadres uit Contacts | primary_email | Required in Xurrent |
FirstName, LastName | name | |
Job uit WorkAssignments | job_title | |
OrgUnit | organization | |
Location uit WorkAssignments | site | |
EmployeeManagers | manager en requested_by | |
Aannamedatum of laatste dag | desired_completion_at |
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