Payroll integration
Rippling to ADP iHCM integration: salary, signing bonus and leavers of your own Dutch entity
With an integration between Rippling and ADP iHCM NL, salary changes, signing bonuses and leavers of employees at your own Dutch entity in Rippling reach ADP iHCM automatically. Employees working through an EOR or PEO party stay out of ADP, and an amount not in euros never passes unseen.
What the integration does
Organisations that handle HR, IT and devices in Rippling but run Dutch payroll in ADP iHCM pass salary raises and leavers to payroll by hand. Anyone promised a signing bonus has to hope someone remembers it in the first month.
- Payroll creates the new worker in ADP iHCM; KoppelHet records once which Rippling worker belongs to it.
- KoppelHet requests workers changed since the previous round, including entity and compensation.
- Workers of an EOR or PEO entity and amounts in a currency other than euros stop here.
- A new salary goes to the work assignment in ADP with the effective date from Rippling.
- A signing bonus goes once as a variable amount to the ADP period of the start date.
- An end date in Rippling ends the work assignment in ADP.
What to watch for with Rippling and ADP iHCM
- Every legal entity in Rippling has a management type, such as PEO, EOR or COR. Someone working in the Netherlands through such a party is not on your ADP payroll. KoppelHet only sends workers of your own Dutch entity to ADP iHCM.
- Rippling converts monthly, weekly and hourly amounts on the basis of a forty-hour working week. ADP wants the amount that belongs to the Dutch employment contract. KoppelHet therefore takes the amount HR actually entered, never a converted one.
- Rippling gives the salary its own effective date. ADP iHCM rejects a salary change dated before the start of the work assignment. If the effective date in Rippling is before the first working day in ADP, KoppelHet uses that first working day and reports the difference.
- A signing bonus is stored in Rippling as an amount on the worker's compensation, with its own currency. ADP iHCM NL accepts such a one-off amount through a variable field of the pay group, in a period that must match exactly. KoppelHet sends the bonus once, in the period of the start date, and remembers it was sent.
- A termination in Rippling has a type, such as voluntary, but also a declined or rescinded offer. For the last two there is often no work assignment in ADP yet; KoppelHet then sends no termination but a notification to payroll.
- Fields the integration has no access to in Rippling come back as redacted, with a reason. KoppelHet checks per worker whether salary and dates are readable, so an empty amount never goes to ADP.
- ADP iHCM cannot change a termination date; the termination has to be cancelled and started again. If HR adjusts the end date in Rippling, KoppelHet takes those two steps in a row.
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
Rippling also runs payroll in the Netherlands. Why ADP?
If your Dutch payroll runs in ADP iHCM and stays there, the payroll run belongs there. The integration makes sure ADP knows the same amounts and dates as Rippling.
Does the integration create new workers in ADP?
No. ADP's public iHCM guides have no API to hire someone. A new worker from Rippling arrives as a task for payroll.
Do target bonus and commission come along too?
No. Rippling stores a target amount for those, not a payout. What is actually paid is recorded by payroll; that can be added later as an extension.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Rippling REST API (rest.ripplingapis.com) with a bearer token with workers.read and the scopes for nested objects. GET /workers filtered on updated_at and status, expand on legal_entity (management_type PEO, EOR or COR), employment_type and compensation (annual_compensation, hourly_wage, signing_bonus, salary_effective_date, currency_type per amount; monthly, weekly and hourly amounts assume forty hours). Fields number, start_date, original_start_date, end_date, termination_details.type (including VOLUNTARY, OFFER_DECLINED, RESCIND, RENEGE); redacted fields in __meta.redacted_fields. Cursor pagination, limit up to 100.
- ADP iHCM through the Base Remuneration Change API (2416 and 2417 per work assignment, one event per call), the Pay Data Input API for iHCM NL (.add with payrollGroupCode, payeeID equal to payrollfilenumber, period dates exactly matching the pay group, earnedPayPeriodStartDate not before the contract start) and the Worker Terminate API (worker.terminate and worker-termination.cancel). Canonical URIs in the Consumer Application Registry (CAR).
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Rippling | Field in ADP iHCM | Notes |
|---|---|---|
number | payrollfilenumber | Linked once to the associateOID |
legal_entity (management_type) | Wel of niet naar ADP | PEO, EOR and COR stay out of the integration |
compensation.annual_compensation of hourly_wage | 2417 salarisbedrag | The amount entered, not the derived one |
employment_type.compensation_time_period | 2416 salariscode | |
compensation.salary_effective_date | effectiveDateTime | |
compensation.signing_bonus | Variabel veld (Vxxx) in de paygroup | Once, in the period of start_date |
end_date en termination_details | worker.terminate |
Related
Carerix → Rippling
Carerix to Rippling integration: successful match as a hire for review in Rippling
Greenhouse → Rippling
Greenhouse to Rippling integration: every hire straight into Rippling for review
Recruitee → Rippling
Recruitee to Rippling integration: hired candidates ready to hire
Rippling → 4PS Construct
Rippling to 4PS Construct integration: own employees of the construction entity in 4PS, with department as a dimension