VSAbsence reporting (SIVI)
Dayforce to the absence insurer via SIVI: sickness from Time Away From Work per policy
With an integration between Dayforce and the absence insurer, approved sickness of Dutch employees from Time Away From Work goes to the insurer automatically, as a SIVI employer-to-insurer message. A cancelled sickness request in Dayforce goes along as a cancelled report in the next period, and a sickness reason for an accident at work becomes the cause code work accident.
What the integration does
Organisations that record HR, schedules and absence in Dayforce and have covered continued pay during sickness in the Netherlands with an absence insurance policy now pass sickness and recovery to the insurer by hand. A cancellation or extension processed only in Dayforce makes the claim at the insurer incorrect.
- At the start we record the sickness reasons, which of them are an accident at work or in traffic, and which payroll tax number belongs to each Dutch legal entity.
- Per Dutch employee KoppelHet requests approved and cancelled absence over a look-back window.
- New sickness becomes a new report with cause code and percentage; a different end date or extent becomes a change.
- Per agreed period all reports go to the insurer together in one message.
What to watch for with Dayforce and Verzuimverzekeraar (SIVI)
- Every organisation sets up its own Time Away From Work reasons in Dayforce. KoppelHet translates the reason for an accident at work into cause code 10 and a traffic accident where someone else is liable into 11. All other sickness becomes 99, and the reason itself never goes along.
- Dayforce's response contains no status per request, and the status in the query is case-sensitive and can be changed per client. KoppelHet therefore requests approved and cancelled separately. If a reported sickness appears among the cancelled ones, it goes to the insurer as a cancelled report.
- Dayforce only returns absence per employee, within a mandatory date window. For the insurer KoppelHet turns that into one message per period, with all Dutch employers and their reports together.
- If the start time of an already reported request in Dayforce shifts, KoppelHet sends a correction with the old first day of absence, under the same absence number. The insurer then does not count two cases for one sickness.
- A request in Dayforce states whether it is a full day, half a day or a number of net hours. The absence percentage follows from that, so the insurer does not calculate a full day of continued pay for partial absence.
- Dayforce works with legal entities per work assignment, the insurer with the payroll tax number of the unit holding the policy. A fixed table holds that relation, so a move to another Dutch entity under the same policy does not break off the absence.
- Employee and manager comments on a request are not processed. They may contain medical details, and the insurer only needs dates, percentage and cause code.
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
Do we need to create new reasons in Dayforce?
Only if there is no separate reason yet for sickness caused by an accident at work or in traffic.
How often are reports sent to the insurer?
As often as you agree with the insurer, usually daily. All reports of that period then go together.
Can this run alongside our health service integration?
Yes. From the same request in Dayforce, health service and insurer each get their own message.
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 GET /V1/Employees/{xRefCode}/TimeAwayFromWork with filterTAFWStartDate, filterTAFWEndDate and status (mandatory, case-sensitive, for example APPROVED and CANCELED); response fields TAFWXRefCode, TimeStart, TimeEnd, NetHours, ReasonName, AllDay, HalfDay and DailyElapsedHours. Employees and legal entity through the Employees endpoint with WorkAssignments. ManagerComment and EmployeeComment are not processed.
- Message Verzuimmeldingen from employer to insurer (XML, targetNamespace VerzuimmeldingenWerkgeverVerzekeraar, file name prefixed WV-), processing codes 01 new, 02 changed, 03 cancelled, 04 for information and 05 correction, cause codes 10, 11 and 99. Transport to be agreed per insurer.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Dayforce | Field in Verzuimverzekeraar (SIVI) | Notes |
|---|---|---|
Legal entity van de work assignment (via tabel) | Werkgever: loonheffingennummer | |
Employee XRefCode | Identificatie werknemer | |
TAFWXRefCode | Verzuimgeval identificatie | |
TimeStart | Datum eerste verzuimdag | |
AllDay, HalfDay en NetHours | Percentage verzuim | |
TimeEnd + 1 dag | Datum hersteld en Einde verzuim J/N | |
ReasonName | Oorzaak verzuim (10, 11 of 99) | Only the code, never the reason itself |
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