DyLeave, absence and time
ADP Workforce Now to Dyflexis integration: employees and contracts of the European sites in the schedule
With an integration between ADP Workforce Now and Dyflexis, employees of the sites that schedule in Dyflexis reach Dyflexis from ADP automatically, with a contract per position, the scheduled hours from ADP and an end date on departure. Dyflexis has its own ADP integration; KoppelHet covers what it does not, such as a selection by site and changes ADP does not send as a notification.
What the integration does
Organisations with ADP Workforce Now as the HR system at head office and European sites that schedule in Dyflexis enter new colleagues and hour changes in Dyflexis by hand. The hours there often go to local payroll, not back to ADP.
- ADP reports a hire or rehire; KoppelHet fetches the worker with their positions.
- Only positions at the work locations that schedule in Dyflexis become a contract in Dyflexis, at the office that belongs to that location.
- An hours change or different location produces a follow-up contract on the effective date.
- KoppelHet finds changes for which ADP sends no notification in the nightly comparison.
- On termination the contract gets the position's end date.
What to watch for with ADP Workforce Now and Dyflexis
- Dyflexis lists its own two-way integration with ADP Workforce and ADP iHCM, included in every subscription. If the hours from Dyflexis go to local payroll and not to ADP, only the flow of employees and contracts is needed. KoppelHet then only builds that side, so no hours flow to ADP is set up that nobody uses.
- ADP Workforce Now sends no notification for most position changes; only job title and FLSA status trigger one. Department, location and scheduled hours have their own notifications, but a department change only when it was made in the ADP screen. KoppelHet therefore compares all European workers every night, so no hours change is missed.
- In ADP Workforce Now an employee has one workerID and a separate positionID per position. Dyflexis allows several contracts per employee, each with its own reference. KoppelHet uses the positionID as contract reference, so someone with two positions at two sites gets two contracts.
- The ADP Workforce Now worker API can filter on work location and on payroll group. KoppelHet only requests the workers of the locations that schedule in Dyflexis, and sets the payroll group as employer in Dyflexis, so the hours later end up with the right payroll processing.
- ADP masks pay, date of birth and tax ID by default, and unmasking requires extra setup per project. A Dyflexis contract can contain an hourly wage. KoppelHet leaves out the hourly wage and requests no unmasked data, unless you want to see wage costs in Dyflexis; then we arrange the release for that field only.
- The worker status in ADP follows the position with the primary indicator. An employee can therefore be active while their second position has already ended. KoppelHet ends the contract per position in Dyflexis, not the whole employee, so they stay schedulable at the other site.
- ADP Workforce Now has a separate notification for rehires. An external employee in Dyflexis is updated on their reference. KoppelHet gives a returning colleague the same reference and a new contract, so the administrator does not have to link them again.
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
Dyflexis has its own ADP integration. Why KoppelHet?
Often it is enough. Choose KoppelHet when only some sites schedule in Dyflexis, when employees have several positions, or when hours do not go back to ADP.
Do the hours from Dyflexis go to ADP?
Not in this setup. Hours to local payroll or to ADP can be added later as an extension.
Does an administrator in Dyflexis still need to do anything?
Yes, once. Anyone arriving through the integration is first an external employee that an administrator links to a Dyflexis employee. Plan that at the start for existing employees.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- ADP Workforce Now through the Worker Management API: GET /hr/v2/workers with $top maximum 100 and $skip, and $filter on workAssignments/homeWorkLocation, payrollGroupCode, homeOrganizationalUnits or assignmentStatus; masked=false only after release. Notifications include worker.hire, worker.rehire, worker.terminate, worker.workAssignment.standardHours.change, worker.workAssignment.homeWorkLocation.change and worker.workAssignment.homeOrganizationalUnits.modify (only on a change in the screen). OAuth 2.0 client credentials with client certificate.
- Dyflexis is written through POST /api2/external-employees/{employeeReference} (firstName, lastNamePrefix, lastName, email, employmentStart, employmentEnd, personnelNumber, employerReferenceId) and POST /api2/external-employees/{employeeReference}/contracts (contractReference, office, type, start, end, hours, days); upserts with scope external_employees, token in the Authorization header with the Token prefix, rate limit per token with 429.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in ADP Workforce Now | Field in Dyflexis | Notes |
|---|---|---|
workerID | employeeReference en personnelNumber | Unique per employee within the client |
positionID | contractReference | Unique per position |
legalName | firstName, lastNamePrefix, lastName | |
standardHours | hours (uren per werkweek) | |
Werkdagen per contracttype (tabel) | days | |
homeWorkLocation | office | |
payrollGroupCode | employerReferenceId | |
Einddatum van de positie | end van het contract |
Related
ADP Workforce Now → 4PS Construct
ADP Workforce Now to 4PS Construct integration: employees with company, dimensions and statistics group in 4PS
ADP Workforce Now → Active Directory
ADP Workforce Now to Active Directory integration: accounts in your own domain, with expiry date and rehire from ADP
ADP Workforce Now → AFAS Profit
ADP Workforce Now to AFAS integration: Dutch employees from the US HR system in AFAS Profit
ADP Workforce Now → AllSolutions
ADP Workforce Now to AllSolutions integration: employees with department, cost centre and manager in AllSolutions