ASAbsence reporting (SIVI)
Deel to the occupational health service via SIVI: sickness of your own Dutch employees reported automatically
With an integration between Deel and the occupational health service, approved sickness of employees directly employed by your Dutch company goes from Deel to the health service automatically, as a SIVI sick, change or recovery report. If the end date in Deel is still marked as estimated, the absence case stays open at the health service until that date is confirmed.
What the integration does
Organisations that use Deel as the HR system for their own employees, and have an occupational health service in the Netherlands, now report sickness in Deel and once more at the health service. Because the same Deel environment also holds contractors and EOR employees, HR keeps having to check who the health service actually covers.
- At the start we pick the time off policies in Deel that mean sickness, and add a question for the safety net to that policy.
- Deel sends a webhook on a new, reviewed, updated or deleted request. KoppelHet fetches the request and checks whether it concerns an own employee of the Dutch entity.
- After approval the health service receives the sickness report, with the absence percentage from Deel.
- Once the end date is final, the recovery report follows; a different percentage goes as a change.
- The health service's return notification shows in the KoppelHet platform. A deleted request or a rejection becomes a task for HR.
What to watch for with Deel and Arbodienst (SIVI)
- Deel holds own employees, EOR employees and contractors side by side. An EOR employee is employed by a Deel employer, and a contractor is not an employee. KoppelHet therefore only sends sickness of own employees of the Dutch entity to your health service.
- On a request Deel can indicate that the end date is an estimate. That is how long-term absence often starts. KoppelHet then sends the sickness report, but the recovery report only once the estimate flag is removed.
- Deel can record a percentage per request. That percentage goes straight to the health service as the absence percentage. Without a percentage KoppelHet calculates it from the half days and the work schedule in Deel.
- A request in Deel has the statuses requested, approved, rejected, used and cancelled. Approved and used go to the health service; a request that is still pending does not, unless you set sickness up without approval.
- A policy in Deel can have its own questions, whose answers are stored with the request. That is where we record the safety net and, where needed, whether it is a work accident. The safety net question thus sits with the sickness request itself, not in a separate field nobody maintains.
- Deel's time off webhooks refer to the contract, not to the person. Someone with two contracts at the Dutch entity therefore gets two employments under one employee number at the health service.
- A request in Deel can have a reason and a description in free text. These can mention a complaint, so those fields never go to the health service.
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 also apply to our EOR employees in the Netherlands?
No. They are employed by a Deel employer, which arranges their absence support. The integration covers employees employed by your own Dutch entity.
Does the reason from Deel go to the health service?
No. Reason and description stay in Deel. The health service gets dates, percentage and the safety net.
What if someone deletes a sickness request in Deel?
HR then gets a task. Withdrawing a report at the health service is better agreed with the health service than done silently by the integration.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Deel through the webhooks time-off.created, time-off.reviewed, time-off.updated and time-off.deleted (payload with contract_id, start_date, end_date, start_date_is_half_day, end_date_is_half_day and status), and GET /rest/time_offs/profile/{hris_profile_id} with status (REQUESTED, APPROVED, REJECTED, USED, CANCELED) and updated_start_date for the daily check. Fields include id, contract_oid, time_off_type_id, time_off_percentage, is_end_date_estimated and custom_field_values. Work schedule through GET /rest/time_offs/dailies. Filter on hiring type direct employee and the Dutch legal entity. Scope time-off:read.
- 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 Deel | Field in Arbodienst (SIVI) | Notes |
|---|---|---|
HRIS-profiel (worker ID) | Identificatie werknemer | No citizen service number |
contract_oid | Identificatie dienstverband | |
id (time off) | Verzuimgeval identificatie | |
start_date | Datum eerste verzuimdag | |
time_off_percentage, of halve dagen tegen het werkrooster | Percentage verzuim | |
end_date + 1 dag, alleen als is_end_date_estimated onwaar is | Datum hersteld en Einde verzuim J/N | |
custom_field_values van het ziektebeleid | Vangnet J/N | Question we add to the policy |
Afdeling in het HRIS-profiel | Organisatie-eenheid, code |
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