Payroll integration
Dayforce to YouForce integration: new hires and contract changes for Dutch payroll
With an integration between Dayforce and Visma Raet YouForce, every new hire and contract change of the Dutch entity in Dayforce becomes a request in YouForce, with the effective date from Dayforce. HR in the Netherlands completes that request with collective agreement scale and step, and a departure reaches payroll as a task with the last working day.
What the integration does
International employers that manage all staff in Dayforce and run Dutch payroll in YouForce, with its own collective agreement, have new employees passed on by email and retyped. Contract extensions and hours changes from Dayforce sometimes only reach YouForce after the run.
- HR records a new employee at the Dutch entity in Dayforce, often weeks before the first working day.
- KoppelHet fetches the employee with employment, job, organisation and hours as they apply on the start date.
- A hire request is waiting in YouForce. HR in the Netherlands adds collective agreement scale and step and completes the request.
- A later change in job, hours or salary becomes a contract change request, with the effective date from Dayforce.
- For a departure KoppelHet creates a task with the last working day, which payroll handles in YouForce.
What to watch for with Dayforce and Visma Raet YouForce
- YouForce does not let another system change an employment directly. Every hire and contract change from Dayforce therefore becomes a request that HR in the Netherlands completes, so grading in the collective agreement stays with payroll.
- Dayforce stores job, organisation and employment status with a start and end date. KoppelHet requests the state on the effective date, so a change that takes effect in three weeks carries that date in the request, not today's.
- The XRefCode is the fixed key of an employee in Dayforce. KoppelHet puts it in an extra field on the person in YouForce, because the employee numbers in the two systems almost always differ.
- If someone returns after an earlier departure, YouForce already knows the person. KoppelHet first searches on the Dayforce key and then starts a new contract on the existing person, so the history in YouForce stays together.
- A departure cannot be entered in YouForce from outside. The end date of the employment status in Dayforce becomes a task for payroll, with last working day and reason.
- Dayforce only returns a field when the integration's role has rights to it. If address or date of birth is missing, KoppelHet holds the request and notifies HR, instead of putting an incomplete request into YouForce.
- International organisations often record an annual salary with global job codes in Dayforce. KoppelHet converts the amount to a monthly figure and translates the job; HR picks scale and step in YouForce, because Dayforce does not know the Dutch collective agreement.
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
Is a new hire from Dayforce in YouForce straight away?
As a request yes, as an employee only after HR in the Netherlands has completed the request. Because Dayforce usually records new hires early, there is ample time for that before the first run.
What if HR rejects a request in YouForce?
The rejection shows in the KoppelHet platform next to the change from Dayforce. HR corrects Dayforce or queues the change again.
Do all employees from Dayforce go to YouForce?
No, only those of the Dutch entity. Which Dayforce organisation belongs to it is recorded at the start.
We already have an integration platform. Does this fit alongside it?
Yes. This integration runs on the KoppelHet platform and asks nothing of your existing integration platform. Every action is in the audit logging, so operations and audit know what happened.
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 and CompensationSummary, with contextDate and a date range for the state on the effective date. Fields are only returned with field-level access in the API user's role.
- YouForce through the Recruitment API (hires, persons/{PersonId}/contracts for rehires and contract adjustments), each starting a workflow in HR Core Self Service. The Recruitment API has no writable termination endpoint. The XRefCode in an extension field through the Extensions API.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Dayforce | Field in Visma Raet YouForce | Notes |
|---|---|---|
XRefCode | Extra veld op de persoon in YouForce | Fixed key; every later change finds the right person |
Voornaam, achternaam en geboortedatum | Voornaam, voorvoegsel, achternaam en geboortedatum | Split the name prefix from the surname |
Addresses | Adres | |
HireDate | Datum in dienst | |
EmploymentStatuses | Begin- en einddatum contract | An end date becomes a task, not an update |
WorkAssignments (functie) | Functie | Through a lookup table |
WorkAssignments (organisatie-eenheid) | Organisatie-eenheid | Through a lookup to the YouForce code |
Uren per week | Uren per week | |
CompensationSummary | Salaris in de aanvraag | Converted to a monthly amount; HR picks scale and step |
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