VSAbsence reporting (SIVI)
Deel to the absence insurer via SIVI: sickness of your own Dutch employees per policy
With an integration between Deel and the absence insurer, approved sickness of employees of your own Dutch entity in Deel goes to the insurer automatically, as a SIVI employer-to-insurer message. EOR employees and contractors fall outside your policy and are therefore not included.
What the integration does
Organisations that use Deel for HR in several countries and have absence insurance for their own Dutch entity now report sickness to the insurer by hand. Deel holds own employees, EOR employees and contractors side by side, and only the first group belongs under the policy.
- At the start we link the Dutch legal entity in Deel to the payroll tax number of the policy and add a question about an accident to the sickness policy.
- Deel sends a webhook on creation, review, change or deletion; KoppelHet fetches the request.
- Approved sickness of an own employee becomes a new report with percentage and cause code.
- Per agreed period all reports go to the insurer in one message.
What to watch for with Deel and Verzuimverzekeraar (SIVI)
- An EOR employee in Deel is employed by a Deel employer, and a contractor is not an employee. Your policy only covers continued pay of own employees. KoppelHet therefore only sends sickness of own employees of the Dutch entity to the insurer.
- A sickness policy in Deel can have its own questions. For the insurer we add the question whether the sickness comes from an accident at work or in traffic. The answer becomes cause code 10, 11 or 99; any explanation is not sent.
- If a request in Deel says the end date is an estimate, the insurer gets no recovery date yet. Only when the estimate is replaced by the real last day does the recovery go along in the next period.
- Deel can record a percentage per request. It goes to the insurer as the absence percentage, so that for partial sickness the full continued pay is not claimed.
- If an already reported request in Deel is cancelled or deleted, it goes to the insurer as a cancelled report in the next period, with everything beneath it. A rejected request is never reported.
- The insurer recognises the employer by the payroll tax number of the unit holding the policy, Deel by the legal entity. A fixed table holds that relation, so with several Dutch entities every report lands under the right employer.
- A request in Deel can have a reason and a description in free text. They may mention a complaint, so those fields are not passed on.
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 sickness of our EOR employees in the Netherlands included?
No. They are employed by a Deel employer and do not fall under your policy.
Do we need to change the sickness policy in Deel?
Only with one question about an accident, if you want to pass on the cause code.
Can this run alongside our health service integration?
Yes. From the same request in Deel, health service and insurer each get their own SIVI message.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Deel through the time off webhooks (created, reviewed, updated, deleted; payload with contract_id, start_date, end_date, half-day flags and status) and GET /rest/time_offs/profile/{hris_profile_id} with status (REQUESTED, APPROVED, REJECTED, USED, CANCELED). Fields include id, contract_oid, time_off_type_id, time_off_percentage, is_end_date_estimated and custom_field_values. Filter on own employees and the Dutch legal entity. Scope time-off:read.
- 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 Deel | Field in Verzuimverzekeraar (SIVI) | Notes |
|---|---|---|
Nederlandse legal entity (via tabel) | Werkgever: loonheffingennummer | |
hris_profile_id | Identificatie werknemer | |
Time off id | Verzuimgeval identificatie | |
start_date | Datum eerste verzuimdag | |
time_off_percentage of halve dagen | Percentage verzuim | |
end_date + 1 dag (niet als is_end_date_estimated) | Datum hersteld en Einde verzuim J/N | |
custom_field_values (vraag ongeval) | Oorzaak verzuim (10, 11 of 99) |
Related
Ashby → Deel
Ashby to Deel integration: hires at the own entity as direct employee in Deel
Bullhorn → Deel
Bullhorn to Deel integration: first placement as a direct employee with a contract in Deel
Carerix → Deel
Carerix to Deel integration: successful placement as a person or contract in Deel
Deel → 4PS Construct
Deel to 4PS Construct integration: own employees of the construction entity in 4PS, with department and cost centre as dimensions