Payroll integration
Deel to ADP iHCM integration: employees of your own Dutch BV from Deel in ADP payroll
With an integration between Deel and ADP iHCM NL, the salary and last working day of employees of your own Dutch BV in Deel reach ADP automatically, at the pay group that belongs to the legal entity. Contractors and EOR workers in Deel stay out of ADP, because Deel pays them itself.
What the integration does
Employers that started in the Netherlands with EOR through Deel and now have their own BV paid by ADP iHCM keep employees in Deel and pass every pay rise and departure to ADP separately. When someone moves from EOR to the BV it is often unclear who pays the last month.
- ADP or payroll creates the employee in iHCM; KoppelHet links it once to the Deel employee.
- Deel reports a contract change; KoppelHet fetches the employee with employment and payment.
- A new salary goes to the employment in ADP with its effective date.
- A name change goes to the personal details in ADP.
- The last working day from Deel ends the employment in ADP.
What to watch for with Deel and ADP iHCM
- Besides employees of your own entity Deel also holds contractors, EOR, PEO and other kinds of workers. KoppelHet only requests the type for your own employees, so someone Deel pays itself never also ends up in ADP iHCM.
- Each Dutch BV is its own legal entity in Deel and its own pay group in ADP iHCM. KoppelHet determines the pay group from the entity of the employment, not from the employee's country or workplace.
- Deel stores payment as a rate with a scale such as per hour, week or month, and a currency. ADP iHCM wants an amount with a salary code. KoppelHet translates the scale to that code and holds back a payment in a currency other than euro.
- If someone moves from EOR to your own BV, that is a new employment in Deel. In ADP the employee only starts on the start date of that employment; the months under EOR stay with Deel, so nobody gets paid twice.
- Deel switches off a webhook subscription after ten failed deliveries in a row. KoppelHet therefore checks daily whether the subscription is still active and compares the employees in Deel with ADP, so a silenced notification is not only noticed after the run.
- If HR corrects the last working day in Deel, ADP cannot amend a termination. KoppelHet cancels it in ADP and starts it again with the new date, and only counts a termination as done once ADP confirms it itself.
- Deel lets an integration choose per request which fields come back. KoppelHet only requests name, entity, payment and end date; payroll records address and bank account in ADP.
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 EOR workers also go to ADP?
No. Deel pays them. Only employees of your own Dutch BV go to ADP iHCM.
Does the integration create new employees in ADP?
No. ADP's public iHCM guides have no API for that. ADP or payroll creates the employee, after which the integration keeps it up to date.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Deel through the REST API (GET people with hiring_types hris_direct_employee or direct_employee, hiring_statuses and fields with dot notation; employments with client_legal_entity, payment.rate, payment.scale, payment.currency and termination_last_day) and webhooks with x-deel-signature (HMAC-SHA256), response within 30 seconds, retries up to 16 hours and disabling after ten consecutive failures.
- ADP iHCM through event notifications (worker.hire), worker.legalName.change (associateOID required), the Base Remuneration Change API (2416 and 2417, one event per call) and the Worker Terminate API (worker.terminate and worker-termination.cancel; completion only through events). Every URI in the Consumer Application Registry (CAR).
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Deel | Field in ADP iHCM | Notes |
|---|---|---|
worker_id | payrollfilenumber (via de ADP-medewerker) | Linked once to the associateOID |
employments.client_legal_entity | payrollGroupCode | Lookup per entity |
employments.payment.rate | 2417 salarisbedrag | |
employments.payment.scale | 2416 salariscode | Hourly, weekly or monthly to the ADP code |
employments.payment.currency | Controle op euro | |
Naam | worker.legalName.change | |
employments.termination_last_day | worker.terminate |
Related
Ashby → Deel
Ashby to Deel integration: hires at the own entity as direct employee in Deel
Bullhorn → Deel
Bullhorn to Deel integration: first placement as a direct employee with a contract in Deel
Carerix → Deel
Carerix to Deel integration: successful placement as a person or contract in Deel
Deel → 4PS Construct
Deel to 4PS Construct integration: own employees of the construction entity in 4PS, with department and cost centre as dimensions