Payroll integration
Oracle HCM to ADP iHCM integration: salary, allowances and terminations to Dutch payroll
With an integration between Oracle HCM Cloud and ADP iHCM NL, salary changes, one-off allowances and terminations from Oracle reach ADP automatically, with the right effective date and in the pay period of the ADP pay group. Variable pay components and cancelled terminations come along too.
What the integration does
Organisations that run HR worldwide in Oracle HCM Cloud and have Dutch payroll processed in ADP iHCM send changes to payroll by spreadsheet or email. A back-dated pay rise or a termination that is reversed often only comes right a month later.
- ADP or payroll creates the new Dutch worker in iHCM; ADP reports it.
- KoppelHet links that ADP worker once to the Oracle person.
- A salary change in Oracle goes to the employment in ADP with its effective date.
- Allowances and one-off amounts go to the pay group's variable field, in the right period.
- A termination in Oracle ends the employment in ADP; if it is corrected, KoppelHet cancels and starts again.
What to watch for with Oracle HCM Cloud and ADP iHCM
- Oracle sends a new hire notification even when the hire lies in the future. ADP only accepts changes once the worker exists in iHCM; KoppelHet keeps the Oracle data until ADP reports the new worker and then sends it in one go.
- Oracle reports salary together with other assignment changes, such as manager or department. KoppelHet fetches the salary on the effective date for every notification and only sends it to ADP if amount or frequency really changed, because ADP accepts one salary change per call.
- Oracle records salary with a frequency such as annual, monthly or hourly, and can give the annual amount separately. ADP iHCM only knows an amount and a salary code for salary. KoppelHet translates the Oracle frequency to that code and rejects a currency other than euro with a notification.
- Element entries in Oracle can hold an amount, hours or a percentage. ADP has different entry points for these; variable amounts go through the per-period submission, hours and percentages through a separate route. KoppelHet picks the right route per Oracle element.
- Oracle has a separate notification for a cancelled work relationship, for example when someone does not show up on the first working day. In ADP the worker already exists by then. KoppelHet ends nothing automatically, but reports it to payroll, because ADP no longer wants a changed hire date after a processed run.
- If HR corrects a leaving date in Oracle, ADP cannot amend the termination. KoppelHet cancels the termination in ADP and starts it again with the new date, and waits for ADP's confirmation before the integration considers it done.
- Oracle only returns the fields an integration explicitly requests; without a field list only links come back. KoppelHet requests exactly the fields ADP needs per source, so no unnecessary personal data passes through the integration.
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
Does the integration create new workers in ADP?
ADP's public iHCM guides contain no API to create a worker. ADP or payroll does that; after that the integration keeps the data up to date.
Do workers from other countries also go to ADP?
No. Only workers of the Dutch legal employers in Oracle, who belong to a pay group in ADP.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Oracle HCM Cloud through the employee Atom feeds (newhire, empassignment, empupdate, payupdate, termination, cancelworkrelship and workrelshipupdate) and the REST resources salaries (finder findByAssignmentIdAndDate; SalaryAmount, AnnualSalary, SalaryFrequencyCode, CurrencyCode, DateFrom, DateTo; field list via fields required) and elementEntries (effectiveDate, child elementEntryValues).
- ADP iHCM through event notifications (worker.hire, also on rehire), the Base Remuneration Change API (one event per call; 2416 and 2417 per work assignment), the Pay Data Input API for iHCM NL (.add and .replace; payPeriodStartDate and payPeriodEndDate exactly equal to the pay group), Additional Remuneration Change for fields of type U, P, B, F, D and the Worker Terminate API (worker.terminate, 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 Oracle HCM Cloud | Field in ADP iHCM | Notes |
|---|---|---|
PersonNumber | payrollfilenumber (via de ADP-medewerker) | Linked once to the associateOID |
LegalEmployerName | payrollGroupCode | Translation per Dutch legal employer |
SalaryAmount en SalaryFrequencyCode | 2417 salarisbedrag en 2416 salariscode | |
DateFrom (salaris) | effectiveDateTime | |
Element entry (eenmalig) | earningCode Vxxx | Only fields enabled for the pay group |
Element entry met uren of percentage | Additional Remuneration-veld | Type U or P in iHCM |
Beëindigingsdatum en reden | worker.terminate | |
cancelworkrelship | Melding aan de salarisadministratie |
Related
Ashby → Oracle HCM Cloud
Ashby to Oracle HCM integration: an accepted offer on an opening becomes a pending worker
Bullhorn → Oracle HCM Cloud
Bullhorn to Oracle HCM integration: an approved placement of an employee becomes a pending worker
Carerix → Oracle HCM Cloud
Carerix to Oracle HCM integration: successful placement as a pending worker in Oracle HCM Cloud
Greenhouse → Oracle HCM Cloud
Greenhouse to Oracle HCM integration: accepted offer as a pending worker in Oracle HCM Cloud