ASAbsence reporting (SIVI)
Remote to the occupational health service via SIVI: sick leave of your own Dutch employees
With an integration between Remote and the occupational health service, approved sick leave of employees of your own Dutch entity automatically becomes a sick, change or recovery report at your health service, in the SIVI format. Staff working through Remote as employer of record are left out, because Remote is their employer.
What the integration does
Organisations that use Remote as HR and payroll platform for their own Dutch entity handle sickness in Remote and then report it again to their health service. Because Remote also holds EOR employees and contractors, it is not always clear who belongs with which health service.
- At the start we record which employments belong to the own Dutch entity; EOR and contractors are not included.
- Remote sends a webhook on approval, date change, cancellation or taking; KoppelHet then fetches the time off.
- Approved sick leave goes to the health service as a sickness report, with employment and safety net.
- A new end date or fewer hours per day becomes a change or recovery report.
- Every day the integration compares ongoing sick leave with what the health service holds; a cancellation of reported sickness becomes a task for HR.
What to watch for with Remote and Arbodienst (SIVI)
- Remote is the employer of anyone working through Remote as employer of record, and then arranges Dutch absence support itself. KoppelHet therefore only sends sickness of employees of your own Dutch entity to your health service; EOR employees and contractors stay out.
- Remote has fixed types of time off, and sickness is called sick_leave there. A custom policy with another name, such as Self-Care, can still fall under sick_leave. The integration looks at the type behind the policy, not at the name employees see.
- An approved request in Remote automatically moves to taken once the date has passed. Nothing changes for the health service; KoppelHet only processes real changes in dates or hours.
- An employee can ask in Remote to cancel approved time off. While that request is open, the sickness report at the health service stays. Only once the cancellation is approved does HR get a task to correct the report at the health service.
- Remote records per day how many hours someone is off, up to eight hours a day. KoppelHet converts that into an absence percentage, so half a day of sickness arrives at the health service as fifty percent and not as a full day.
- A request in Remote can carry a document, such as a doctor's note, and a note from the employee. These never go to the health service; medical information should not pass through the employer.
- Remote creates public holidays automatically as approved time off. They are not absence. The integration ignores automatically created time off and everything that is not sick_leave.
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 work for staff through Remote as employer of record?
No. There Remote is the employer and arranges absence support. The integration is for employees of your own Dutch entity.
Does the doctor's note go along?
No. Documents and notes on the request stay in Remote.
How quickly does the health service know?
Within minutes of approval in Remote, thanks to the webhook.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Remote through the webhooks timeoff.approved, timeoff.date_changed, timeoff.canceled, timeoff.cancellation_requested, timeoff.updated and timeoff.taken, and GET /v1/timeoff with employment_id, timeoff_type, status, start_date and end_date (overlapping window), paged with page and page_size. Fields include id, employment_id, timeoff_type, status (requested, approved, taken, declined, cancel_requested, canceled), start_date, end_date, timeoff_days (day, hours, minutes), automatic, leave_policy, notes and document. Scope timeoff:read through a Customer API token or OAuth.
- 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 Remote | Field in Arbodienst (SIVI) | Notes |
|---|---|---|
employment_id | Identificatie dienstverband | |
Personeelsnummer in Remote | Identificatie werknemer | No citizen service number |
Time off id | Verzuimgeval identificatie | |
start_date | Datum eerste verzuimdag | |
timeoff_days (uren per dag) | Percentage verzuim | Against the contract hours |
end_date + 1 dag | Datum hersteld en Einde verzuim J/N | |
timeoff_type sick_leave | Filter op ziekte | |
Vaste waarde of eigen veld | Vangnet J/N | Remote has no safety net concept |
Related
Greenhouse → Remote
Greenhouse to Remote integration: foreign hires as EOR employment with the country's form
Recruitee → Remote
Recruitee to Remote integration: hires abroad straight into an employment at Remote
Remote → 4PS Construct
Remote to 4PS Construct integration: own employees of the construction entity from Remote in 4PS
Remote → Active Directory
Remote to Active Directory integration: accounts for colleagues in other countries