VSAbsence reporting (SIVI)
Remote to the absence insurer via SIVI: sick leave of your own Dutch entity per period
With an integration between Remote and the absence insurer, approved sick leave of employees of your own Dutch entity in Remote goes to the insurer automatically, as a SIVI employer-to-insurer message. Anyone working through Remote as employer of record is not under your policy and is left out.
What the integration does
Organisations that use Remote for HR and payroll of their own Dutch entity and have insured continued pay during sickness now pass absence to the insurer by hand. Remote lists own employees, EOR employees and contractors together, and only own employees belong under the policy.
- At the start we link the own Dutch entity in Remote to the payroll tax number of the policy.
- Remote sends a webhook on approval, a new date or cancellation; KoppelHet fetches the time off.
- Approved sick leave of an own employee becomes a new report with first day of absence and percentage.
- A different end date or fewer hours per day becomes a changed report.
- Per agreed period all reports go to the insurer together in one message.
What to watch for with Remote and Verzuimverzekeraar (SIVI)
- For staff through employer of record, Remote itself is the employer and continued pay during sickness runs through Remote. Your absence insurance does not cover that pay. KoppelHet therefore checks per employment whether it belongs to the own Dutch entity, and only reports that sickness to the insurer.
- Remote records the number of hours off per day, with eight hours as the maximum. KoppelHet converts those hours into an absence percentage for the insurer. That way an employee who is sick for half days does not claim the full continued pay for that period.
- Remote has its own webhook for a new date on a request. When it arrives for reported sickness, the adjusted first or last day goes to the insurer in the next period as a changed report, under the same absence case.
- An employee can ask in Remote to withdraw approved time off. While that request is open, the report at the insurer simply stays. Only once the cancellation is approved in Remote does a cancelled report go to the insurer.
- After the last day Remote automatically marks approved time off as taken. For the insurer that is not a change; the integration ignores that status transition and reports recovery based only on the end date.
- The insurer recognises the employer by the payroll tax number of the policy. Remote has no such field on the employment. A fixed table records at the start which entity belongs to which payroll tax number, so every report falls under the right employer.
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 staff through Remote included?
No. Remote is their employer, and their continued pay does not fall under your policy.
Do the note and the doctor's note go along?
No. The insurer only gets dates, percentage and employer. Notes and documents stay in Remote.
Can this run alongside an integration with the health service?
Yes. From the same time off in Remote, 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.
- Remote through the webhooks timeoff.approved, timeoff.date_changed, timeoff.cancellation_requested and timeoff.canceled, and GET /v1/timeoff with employment_id, timeoff_type, status and a window on start_date and end_date, paged with page and page_size. Fields include id, employment_id, timeoff_type (sick_leave), status (requested, approved, taken, declined, cancel_requested, canceled), start_date, end_date and timeoff_days with hours per day. Employments with employment_type and employment_model (eor, peo, global_payroll) through GET /v1/employments. Scope timeoff: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 Remote | Field in Verzuimverzekeraar (SIVI) | Notes |
|---|---|---|
Eigen Nederlandse entiteit (via tabel) | Werkgever: loonheffingennummer | |
employment_id | Identificatie werknemer | No citizen service number |
Time off id | Verzuimgeval identificatie | |
start_date | Datum eerste verzuimdag | |
timeoff_days (hours per dag) | Percentage verzuim | Against eight hours |
end_date + 1 dag | Datum hersteld en Einde verzuim J/N | |
status canceled | Verwerkingscode 03 vervallen |
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