Payroll integration
Simployer to ADP iHCM integration: salary, bonuses and end of employment from Simployer One to ADP iHCM
An integration between Simployer and ADP iHCM passes salary changes, bonuses and the end date of Dutch employments from Simployer One to Dutch payroll in ADP iHCM. Payroll then no longer retypes those changes; first creating a new employee in ADP remains a payroll task.
What the integration does
Organisations that use Simployer One as their HR system for Scandinavian and Dutch sites, and run Dutch payroll in ADP iHCM, email payroll the new salaries and bonuses every month. Simployer has its own export to Visma Nmbrs, but not to ADP, so the retyping remains.
- HR records a new compensation, a bonus or an end date in Simployer One.
- KoppelHet reads the changed records hourly and keeps only employments with country Netherlands.
- A new compensation goes to ADP as a salary change; a bonus as a variable line in the period of the payout date.
- An end date on the employment starts the termination in ADP.
- Deviations and rejections are in an overview for payroll.
What to watch for with Simployer and ADP iHCM
- Simployer One records both the amount in the employee's currency and a base amount with exchange rate on a compensation. KoppelHet only sends an amount whose currency is EUR to ADP iHCM NL, and reports a salary in Norwegian or Swedish kroner to payroll instead of converting it itself.
- The payout period of a compensation in Simployer ranges from hourly to annual. ADP expects a salary code and an amount per period. KoppelHet translates the payout period to the salary code, and converts an annual salary to the period of the ADP pay group.
- A bonus is a separate record in Simployer with a name, an amount and a payout date. KoppelHet looks up the ADP pay period that date falls in and passes the exact start and end date, because ADP otherwise does not link the line to a run.
- Additional compensation in Simployer has its own salary code, an effective date and sometimes an end date: a fixed allowance that continues. ADP's Pay Data Input API only accepts variable data. KoppelHet puts such an allowance on the list for payroll in the first version; through the separate ADP API can be added later as an extension.
- Every employment in Simployer One has a country. KoppelHet only includes employments with country Netherlands, so an employee who also has a Swedish employment does not end up in ADP with two salaries.
- Simployer keeps an end date, an effective end date and a terminated flag on an employment. KoppelHet only starts the termination in ADP when the flag is set, and cancels it if HR reverses the termination in Simployer.
- Simployer has a standard export to Visma Nmbrs that HR starts itself. No such export exists for ADP iHCM. Anyone moving from Nmbrs to ADP switches off the Nmbrs export once this integration is live, so there are not two sources for the same pay data.
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 employees in ADP?
No. Payroll creates the employee in ADP, after which KoppelHet links them on employee number.
Do fixed allowances go along?
In the first version as a notification to payroll. Passing them on automatically through ADP's API for fixed pay components 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.
- Simployer One through the HRM One API (https://api.alexishr.com/v1, bearer access token): /compensation (amount, baseAmount, exchangeRate, currency, payoutPeriod HOURLY to ANNUAL, effectiveDate), /bonus-compensation (name, amount, payoutDate, currency), /additional-compensation (salaryCode, effectiveDate, endDate) and /employment (startDate, endDate, effectiveEndDate, terminated, country), with filters on updated.
- ADP iHCM through GET /hr/v2/workers, the Base Remuneration Change API (2416 and 2417), the Pay Data Input API for iHCM NL (.add and .replace with batch ID) and the Worker Terminate API (worker.terminate, worker-termination.cancel). Canonicals in the Consumer Application Registry (CAR).
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Simployer | Field in ADP iHCM | Notes |
|---|---|---|
employee.id | payrollfilenumber | Linked once and stored by KoppelHet |
employment.country = NL | payrollGroupCode | Fixed pay group per Dutch company |
compensation.amount en payoutPeriod | Salarisbedrag 2417 en salariscode 2416 | |
compensation.effectiveDate | effectiveDateTime van de salariswijziging | |
bonus-compensation.amount en payoutDate | Variabel veld (Vxxx) met payPeriodStartDate en payPeriodEndDate | |
employment.endDate | Beëindiging in worker.terminate |
Related
Recruitee → Simployer
Recruitee to Simployer integration: hired candidates with employment and salary in Simployer One
Simployer → Active Directory
Simployer to Active Directory integration: accounts in your own domain from Simployer
Simployer → AFAS Profit
Simployer to AFAS integration: Dutch employees from Simployer One in AFAS payroll
ASSimployer → Arbodienst (SIVI)
Simployer to the occupational health service via SIVI: approved sick leave as absence reports