DyLeave, absence and time
ADP iHCM to Dyflexis integration: employees and contracts in scheduling, hours back to ADP
The integration between ADP iHCM and Dyflexis puts employees with position, contract type, contract hours and wage from ADP into Dyflexis, and sends worked hours, sick hours, overtime and allowances back to ADP per period. KoppelHet selects only the countries, employers and sites that schedule in Dyflexis.
What the integration does
Organisations that run HR and payroll in ADP iHCM and have their sites schedule in Dyflexis. The questions are mainly about scoping, such as employees in other countries who do not belong in Dutch scheduling.
- HR records a hire or change in ADP iHCM.
- KoppelHet puts the employee with contract into Dyflexis, only for the sites that schedule in Dyflexis.
- An administrator links the new employee to a Dyflexis employee the first time.
- Planners schedule, employees clock, managers approve the hours and close the period.
- The hours and allowances of the closed period go to ADP.
Back: Hours or days worked · Sick hours and waiting-day hours · Overtime, mileage allowance and custom allowances
What to watch for with ADP iHCM and Dyflexis
- Not only worked hours go back to ADP, but also sick hours and waiting-day hours, overtime, mileage allowance and custom allowances. Check with payroll that each of those types has a pay component in ADP iHCM, otherwise a line is left behind.
- ADP iHCM often serves several European countries in one environment, and the worker API cannot filter on workplace. If only part of the workforce should be in Dyflexis, KoppelHet fetches the population in parts and selects on country and location of the workplace itself.
- According to ADP not every worker in iHCM has the internal ADP key. KoppelHet therefore uses the workerID as the fixed reference of the employee in Dyflexis, so those workers can also be found again after a change.
- ADP sends the termination notification again when HR later changes the date or reason. Dyflexis contracts are updated on their reference. KoppelHet processes every new notification as a change to the end date, so an extended contract does not leave scheduling too early.
- Anyone arriving in Dyflexis through the integration is first an external employee that an administrator links once to a Dyflexis employee. Plan this for all existing employees at the start, otherwise they appear twice in scheduling.
- Dyflexis only releases hours from a locked payroll period. A planner sends that period from Dyflexis to a queue; KoppelHet picks it up there and sets the status back, so the payroll page in Dyflexis shows whether the hours are in ADP iHCM.
- Times in Dyflexis are in the time zone of the Dyflexis environment, not in UTC. Because ADP iHCM often serves countries in different time zones, KoppelHet records the time zone per Dyflexis environment, so a night shift lands on the right day 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
Does the wage also go to Dyflexis?
According to Dyflexis it does, for labour cost in scheduling. Decide in Dyflexis which roles may see the wage.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- KoppelHet reads ADP iHCM through the Worker Management API (GET /hr/v2/workers with $top at most 100 and $skip; per worker on associateOID or workerID) and the notifications worker.hire, worker.terminate and worker.workAssignment.modify. Access per canonical in the Consumer Application Registry.
- To Dyflexis through POST /api2/external-employees/{employeeReference} and POST /api2/external-employees/{employeeReference}/contracts (contractReference, office, type, start, end, hours, days); both upserts, scope external_employees.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in ADP iHCM | Field in Dyflexis | Notes |
|---|---|---|
workerID/idValue | employeeReference | Not every worker has an associateOID |
legalName (givenName, familyName1) | firstName, lastNamePrefix, lastName | |
workAssignments.homeWorkLocation | office | Through a translation table; filter by country |
workAssignments.jobTitle | jobDescription | |
Contracttype en contracturen | type, hours en days van het contract | |
Werkgever | employerReferenceId | |
hireDate en workerDates.terminationDate | employmentStart en employmentEnd |
Related
ADP iHCM → Active Directory
ADP iHCM to Active Directory integration: network accounts per country, with an expiry date for temporary contracts
ADP iHCM → Coupa
ADP iHCM to Coupa integration: approved Coupa expenses as a variable pay field in ADP iHCM NL
ADP iHCM → Microsoft Entra ID
ADP iHCM to Entra ID integration: accounts from ADP payroll, with the right licence in every European country
ADP iHCM → Google Workspace
ADP iHCM to Google Workspace integration: Google accounts from the ADP administration, with the address back in ADP