Payroll integration
Dayforce to Loket integration: Dutch employees from Dayforce as a concept in Loket
With an integration between Dayforce and Loket, a new employee at a Dutch location in Dayforce becomes a concept employee in Loket, with bank account, pay and working hours as they apply on the start date. Later changes follow with their effective date, and payroll only completes the Dutch payroll details.
What the integration does
International employers that manage all staff in Dayforce and have Dutch payroll processed in Loket send the payroll bureau a list every month. Employees on an hours contract therefore regularly get paid for the wrong number of hours.
- HR records a new employee at a Dutch location in Dayforce.
- KoppelHet fetches the employee with employment, work assignment, salary and bank account as they apply on the start date.
- In Loket a concept employee appears at the employer, with the new hire checklist started.
- Payroll completes collective agreement, payroll tax credit and pension and converts the concept.
- Changes in salary or hours go to pay and working hours in Loket with their effective date.
What to watch for with Dayforce and Loket
- Dayforce stores work assignment, salary and employment with a start and end date. KoppelHet requests the state on the effective date, so an hours increase from next month also lands in the Loket working hours with that date.
- Pay and working hours are separate parts in Loket. For staff on an hours contract often only the working hours change; KoppelHet then only adjusts that part and leaves the pay as it is.
- Dayforce holds the account an employee is paid into. KoppelHet puts it into the concept as payment details, so the first payment from Loket does not fail on a missing IBAN.
- Dayforce only returns a field when the integration's role has rights to it. An empty IBAN or salary for a new employee is therefore usually a missing right, and KoppelHet then does not create an incomplete concept.
- Loket calculates per month, per four weeks or per week. KoppelHet converts the salary from Dayforce to the employer's payroll period, and an hourly wage stays an hourly wage.
- Dayforce holds employees from every country of the organisation. Only employees with a work assignment at a Dutch location become a concept in Loket; the rest stays outside the integration.
- Loket has a date on which a leaver's self-service access expires. KoppelHet sets it after the end date from Dayforce to a period you choose, so the final payslip and annual statement can still be collected.
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 this work if a payroll bureau manages Loket for us?
Yes. The bureau gives the integration access to your employer in Loket; the bureau's other clients stay out of view.
Do hours worked also go along?
This integration takes the contract hours along. Hours worked and allowances from Dayforce time tracking are connected separately if needed.
What does Dayforce need to set up for the integration?
An API user with a role that may read the agreed fields, including salary and bank account. Your Dayforce administrator arranges this once.
What about the GDPR?
You are the controller and KoppelHet is the processor, under a data processing agreement. Only employees at Dutch locations go to Loket, and every action is in the audit logging.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Dayforce is read through the REST API with its own company name in the API URL. Changed employees through the update-date filters of the Employees endpoint; details with expand for EmploymentStatuses, WorkAssignments, Addresses, DirectDeposits and CompensationSummary, with contextDate. Fields only with field-level access in the API user's role.
- Loket is written through the Loket REST API with OAuth - concept employee, new hire checklist workflow, wages, working hours, payment information, end employment and the date on which ESS access is revoked.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Dayforce | Field in Loket | Notes |
|---|---|---|
XRefCode | Personeelsnummer of vrij veld | Fixed key |
Voornaam en achternaam | Voornaam, voorvoegsel en achternaam | |
Addresses | Adres | |
HireDate | Begindatum dienstverband | |
Locatie (WorkAssignments) | Werkgever | Only Dutch locations |
CompensationSummary | Loon per verloningsperiode | Converted to the employer's period |
Uren per week (work assignment) | Arbeidstijd | |
DirectDeposits | Betaalgegevens (SEPA) | |
EmploymentStatuses (einddatum) | Einde dienstverband |
Related
Ashby → Dayforce
Ashby to Dayforce integration: have Dayforce validate the hire first, then save it
Bullhorn → Dayforce
Bullhorn to Dayforce integration: first placement of an employee as an employee in Dayforce
Carerix → Dayforce
Carerix to Dayforce integration: successful placement as a validated new employee in Dayforce
Dayforce → 4PS Construct
Dayforce to 4PS Construct integration: technicians and site managers from Dayforce in 4PS, with cost centre and end date