Payroll integration
Dayforce to ADP iHCM integration: Dutch employees from Dayforce in ADP payroll
With an integration between Dayforce and ADP iHCM NL, salary, personal details and terminations of Dutch employees from Dayforce reach ADP automatically, with the effective date that applies in Dayforce. Dayforce remains the group's HR system, ADP runs payroll in the Netherlands, and payroll no longer enters anything twice.
What the integration does
Organisations that use Dayforce as their global HR system and run Dutch payroll in ADP iHCM email a list of changes to payroll every month. An address change or pay rise that arrives after sending waits until the next month.
- ADP or payroll creates the new worker in iHCM; ADP reports it.
- KoppelHet links the ADP worker once to the XRefCode in Dayforce.
- Every hour KoppelHet fetches the Dutch employees that were updated in Dayforce.
- Salary, address and contact details go to ADP with the applicable effective date.
- A termination in Dayforce ends the employment in ADP.
What to watch for with Dayforce and ADP iHCM
- Every organisation has its own Dayforce address with the company name in the URL. KoppelHet only looks up employees with a Dutch pay group there, so colleagues from other countries who are also in Dayforce never go to ADP.
- Dayforce leaves a field out of the response when it is empty, and also when the integration has no rights to it. KoppelHet therefore does not read a missing field as clearing it; otherwise a permissions issue in Dayforce would wipe an address in ADP.
- Dayforce stores status, pay group and hours with a start and end date, and returns the state at any chosen moment. KoppelHet requests the state on the effective date, so a pay rise from the first of next month does not land in the current ADP period.
- KoppelHet requests updated employees from Dayforce with both a start and an end date for the change; with only a start date Dayforce ignores the filter and returns all employees. The time window always follows on from the previous run, so nothing falls in between.
- ADP accepts one salary change per call, per employment. If an employee has two changes in Dayforce in the same hour, for example a correction straight after a raise, KoppelHet sends them one after the other in order of effective date.
- Dayforce passes a reason with a termination. ADP has its own list of leaving reasons, available through the termination metadata. KoppelHet translates the Dayforce reason to that list; a date that shifts later is cancelled and restarted in ADP.
- An employee can have more than one work assignment in Dayforce, with one as primary. ADP links salary to a specific employment with its own ID. KoppelHet records per Dayforce assignment which ADP employment belongs to it, and does not silently send a second assignment to the 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
Why not Dayforce's own payroll?
That is your choice. This integration is for organisations that keep running Dutch payroll in ADP iHCM.
Does the integration create new workers in ADP?
No. ADP's public iHCM guides have no API for it. ADP or payroll creates the worker, after which the integration takes over.
Do bonuses go along too?
Not in the first version. Variable amounts per period can follow later as an extension, if they are recorded per employee in Dayforce.
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 (https://www.dayforcehcm.com/api/{CompanyName}/V1/Employees) with filterUpdatedStartDate and filterUpdatedEndDate, details per XRefCode with expand EmploymentStatuses (PayGroup, PayType, PayClass, NormalWeeklyHours, EmploymentStatusReason, EffectiveStart, EffectiveEnd), Addresses and Contacts, and contextDate for the state on a date. Fields only with Web Services Field-Level Access in the API user's role; empty fields are missing from the response.
- ADP iHCM through event notifications (worker.hire), the Worker Management change events (personalAddress, personalCommunication; associateOID required), the Base Remuneration Change API (one event per call; 2416 and 2417) and the Worker Terminate API (worker.terminate, worker-termination.cancel, /meta for value lists). Every URI in the Consumer Application Registry (CAR).
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Dayforce | Field in ADP iHCM | Notes |
|---|---|---|
XRefCode | payrollfilenumber (via de ADP-medewerker) | Linked once to the associateOID |
EmploymentStatuses: PayGroup | payrollGroupCode | Lookup per pay group |
CompensationSummary (basisloon) | 2417 salarisbedrag | |
EmploymentStatuses: PayType | 2416 salariscode | Hourly or period pay |
EffectiveStart | effectiveDateTime | |
Addresses | worker.personalAddress.change | |
Contacts (privé e-mail en mobiel) | personalCommunication.email en mobile | |
EmploymentStatus beëindigd en EmploymentStatusReason | worker.terminate met reden |
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