ASAbsence reporting (SIVI)
HiBob to occupational health service via SIVI: sick leave from Bob as absence notifications for Dutch employees
With an integration between HiBob and the occupational health service, sick leave of Dutch employees in Bob automatically becomes a sick, change or recovery notification at the health service, in the SIVI format health services use. A sick request without an end date becomes an open absence case, and as soon as HR sets the end date in Bob, the recovery notification follows.
What the integration does
Organisations that record HR and leave worldwide in HiBob and have a health service receiving SIVI notifications for their Dutch employees now report sickness twice, in Bob and in the health service portal. Without an integration the health service sometimes only hears about a recovery when Dutch HR remembers, and the file there runs behind.
- The employee or HR requests sick leave in Bob, open-ended if the duration is not yet known.
- KoppelHet receives HiBob's notification, fetches the request and checks whether it concerns the sick policy of a Dutch employee.
- The health service receives a sick notification in the SIVI format, completed with employment, department and safety net.
- When someone partly returns to work, the new percentage is sent as a change. When HR sets the end date, the recovery notification follows.
- The health service's confirmation shows in the KoppelHet platform; a rejected notification becomes a task for HR.
What to watch for with HiBob and Arbodienst (SIVI)
- Bob has an open-ended request, whose end date is decided later, and reports separately when that end date is set. That fits how an absence case runs at the health service. KoppelHet opens the absence case on the request and only sends the recovery notification on the end-date notification.
- When the date or time of a request changes in Bob, Bob replaces the request with a new one, referring to the first. KoppelHet uses that first request as the fixed number of the absence case, so the health service gets a correction and not a second sick notification.
- Bob can record a percentage of the day over a range of days per request. That percentage goes to the health service as the absence percentage; for half days or hours per day KoppelHet calculates it against the schedule.
- The sick policy in Bob can have reasons, such as headache or an accident at work. That is medical data. KoppelHet never passes that reason on; the SIVI notification only gets a cause code without a diagnosis, chosen in advance per situation.
- A sick policy in Bob can be hidden from colleagues or shown under another name, such as out of office. The integration's service user therefore needs explicit access to that policy; otherwise KoppelHet does not see the sick request and the health service misses it.
- If sick leave in Bob is approved automatically, Bob first sends a notification of the request and then of the approval. KoppelHet recognises this as one sick notification, so the health service does not receive it twice.
- Bob holds employees in every country. Only sick leave from the Dutch sites goes to the health service; sickness of colleagues elsewhere never leaves Bob.
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 our sick policy in Bob need a different setup?
Usually not. The policy for the Netherlands must be recognisable and the integration's service user must have rights on it. An extra field is often added for the safety net.
Do the reasons from Bob go to the health service?
No. Reasons such as headache stay in Bob. The health service only gets dates, a percentage and a code without a diagnosis.
What if someone cancels their sick request in Bob?
Then KoppelHet creates a task for HR. Withdrawing a notification at the health service is better agreed with the health service than done silently by an integration.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- HiBob is read through the time off webhooks (requested, approved, updated, cancelled, deleted and set end date for an open-ended request) and the Time Off API (fetching the request with requestRangeType such as days, portionOnRange, percentageOnRange and openEnded, and GET /timeoff/requests/changes for the daily check). On a hard update the notification contains originalRequestId and previousRequestId. A service user with rights on the sick policy.
- The message is Verzuimmeldingen from the SIVI absence standard for employers and health services, with processing code new, changed or correction, 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 HiBob | Field in Arbodienst (SIVI) | Notes |
|---|---|---|
root.id | Identificatie werknemer | No citizen service number |
Dienstverband (work) | Identificatie dienstverband | |
originalRequestId of het id van de eerste aanvraag | Verzuimgeval identificatie | Stays the same when Bob replaces the request on a date change |
Startdatum van de aanvraag | Datum eerste verzuimdag | |
percentageOnRange of uren per dag | Percentage verzuim | One hundred percent for full days |
Einddatum (ook achteraf gezet bij een open aanvraag) | Datum hersteld en Einde verzuim J/N | |
work.department | Organisatie-eenheid, code | |
Eigen veld vangnet | Vangnet J/N | Bob has no Dutch safety net concept |
Related
Ashby → HiBob
Ashby to HiBob integration: a hire from Ashby straight in as an employee in Bob
Bullhorn → HiBob
Bullhorn to HiBob integration: an approved placement as a new employee in Bob
Carerix → HiBob
Carerix to HiBob integration: successful match becomes a new employee in Bob
Greenhouse → HiBob
Greenhouse to HiBob integration: from a hire in Greenhouse to a new employee in Bob