ASAbsence reporting (SIVI)
Dayforce to the occupational health service via SIVI: Time Away From Work as absence reports
With an integration between Dayforce and the occupational health service, approved sickness of Dutch employees in Time Away From Work automatically becomes a sick, change or recovery report at the health service, in the SIVI format. HR in the Netherlands no longer has to retype absence in the health service portal, and a cancelled sickness request in Dayforce lands with HR as a task.
What the integration does
Organisations that record HR, schedules and absence in Dayforce and have a Dutch occupational health service now report sickness in Dayforce and in the health service portal. If a recovery or cancellation only lands in Dayforce, the file at the health service falls behind.
- At the start we record which TAFW reasons in Dayforce mean sickness and which statuses your environment uses.
- KoppelHet fetches the list of Dutch employees and, per employee, requests approved and cancelled absence over a look-back window.
- New sickness goes to the health service as a sickness report, completed with employment, department and safety net.
- If the end date or the number of hours changes, a change or the recovery report follows.
- The health service's return notification shows in the KoppelHet platform; a rejection or a cancellation of reported sickness becomes a task for HR.
What to watch for with Dayforce and Arbodienst (SIVI)
- Dayforce only returns absence per employee, not for a whole organisation at once. KoppelHet therefore first fetches the Dutch employees and then requests sickness per person, within the API's limits.
- A status is mandatory when fetching absence, and it is case-sensitive. Organisations can change the values, such as APPROVED and CANCELED. At the start we record which statuses your Dayforce uses, so no approved sickness falls outside the integration.
- The Dayforce response contains no status per request. KoppelHet therefore requests approved and cancelled absence separately. If an already reported sickness shows up among the cancelled ones, HR gets a task instead of the health service silently receiving a withdrawal.
- A request in Dayforce states whether it is a full day, half a day or a number of net hours. From that KoppelHet calculates the absence percentage against the schedule, so an afternoon of sickness does not arrive at the health service as a full day.
- Absence in Dayforce is requested within a mandatory date window. So as not to miss sickness that is extended or shortened afterwards, the integration looks back a few weeks every time and compares with what the health service already has.
- A request can carry a comment from the employee and from the manager. These can contain medical details and never go to the health service. Only the reason decides whether it is sickness, and the reason itself is not sent either.
- An employee's XRefCode must match exactly in Dayforce, or the API refuses the request. KoppelHet also uses that code as the employee number at the health service, so a return notification always points back to the right person in Dayforce.
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 leave in Dayforce need a different setup?
Usually not. There must be a recognisable reason for sickness, and the API user must be allowed to read absence of Dutch employees.
How quickly does the health service know?
Within a few hours of approval in Dayforce. Dayforce sends no notification on a new absence, so the integration checks several times a day.
Do the comments on a request go along?
No. Employee and manager comments stay in Dayforce.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Dayforce through the REST API with the client name in the URL. Employees through the Employees endpoint (changed since the previous run, with WorkAssignments and EmploymentStatuses for the Dutch legal entity). Absence through GET /V1/Employees/{xRefCode}/TimeAwayFromWork with filterTAFWStartDate, filterTAFWEndDate and status (all mandatory); response fields include TAFWXRefCode, TimeStart, TimeEnd, NetHours, ReasonName, AllDay, HalfDay and DailyElapsedHours. Comment fields are not processed.
- The SIVI messages Employments, Employee data and Absence reports go to the health service, with Vangnet J/N (mandatory), organisational unit and a cause code without diagnosis. Transport under the SIVI 2025 interface specification (REST endpoint at the health service, XML in Base64 inside JSON, OAuth 2.0), with a return and processing message back.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Dayforce | Field in Arbodienst (SIVI) | Notes |
|---|---|---|
Employee XRefCode | Identificatie werknemer | No citizen service number |
Work assignment van de Nederlandse legal entity | Identificatie dienstverband | |
TAFWXRefCode | Verzuimgeval identificatie | |
TimeStart | Datum eerste verzuimdag | |
AllDay, HalfDay, NetHours en DailyElapsedHours | Percentage verzuim | Against the scheduled hours |
TimeEnd + 1 dag | Datum hersteld en Einde verzuim J/N | |
ReasonName | Filter op ziekte | Only reasons designated as sickness |
Eigen veld voor Nederland | Vangnet J/N | Dayforce has no safety net concept |
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