ASAbsence reporting (SIVI)
Simployer to the occupational health service via SIVI: approved sick leave as absence reports
With an integration between Simployer and the occupational health service, approved sick leave of Dutch employees in Simployer One automatically becomes a sick, change or recovery report at the health service, in the SIVI format. The sickness percentage HR records on the leave in Simployer is sent along as the absence percentage.
What the integration does
Organisations that use Simployer One for HR and leave, and have a health service with SIVI messages for their Dutch employees, now enter every sickness report twice. On partial recovery HR changes the percentage in Simployer, but at the health service the employee stays fully sick.
- At the start we pick the leave types of the kind sick leave and self-certified sickness, and decide which employees fall under the Dutch employer.
- HR or the employee records sickness in Simployer and the manager approves the leave.
- Every hour KoppelHet reads the leaves that are still running or have just ended, and compares them with what the health service already has.
- A newly approved leave becomes a sickness report; a different percentage becomes a change with the right effective date.
- After the last day of sickness the recovery report follows. A cancelled or archived leave that was already reported becomes a task for HR.
What to watch for with Simployer and Arbodienst (SIVI)
- Every leave type in Simployer has a fixed kind, such as sick_leave for sickness and self_certified for sickness without a doctor's note. For the health service both are absence. KoppelHet takes both kinds and leaves holiday, parental leave and childcare leave in Simployer.
- A leave in Simployer has its own sickness percentage, the gradePercentage field. Someone who is half sick shows fifty there. KoppelHet sends that number as the absence percentage, so the health service does not have to calculate with hours.
- Simployer requires a start and end date on every leave. For sickness of unknown duration, HR fills in an expected end date. KoppelHet only sends the recovery report once that date has passed and no new sick leave follows on; an extension is then not a new sickness report.
- A leave in Simployer has the status pending, approved, confirmed, denied or cancelled. Only approved and confirmed sickness goes to the health service. If an already reported sickness is cancelled later, HR gets a task, because withdrawing a sickness report is agreed with the health service.
- Simployer's webhooks cover employees, not leave. KoppelHet therefore requests leaves every hour with a filter on end date, and keeps track itself of what has been reported. A leave that HR archives does not disappear unnoticed.
- Besides the leave itself, Simployer records a leave transaction per day, with hours and extent. If someone falls sick halfway through the day, KoppelHet sees that in the first transaction and sends the health service the right first day of absence.
- The description on a leave is free text the employee fills in. KoppelHet uses the select parameter to request only dates, status, type and percentage, so a description of symptoms never reaches KoppelHet or 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 self-certified sickness without a doctor's note also go to the health service?
Yes. For the health service it is simply absence. We include the leave type of the kind self_certified, unless you want otherwise.
What if HR changes the sickness percentage?
Then KoppelHet sends a change with the new percentage. If you create a new leave for it that follows on from the previous one, it stays the same absence case.
Does the health service see the description the employee enters?
No. KoppelHet does not even request that description. The health service gets dates, a percentage and codes.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Simployer One through the HRM One API (api.alexishr.com/v1, sandbox at api.sandbox.alexishr.com/v1) with an access token as bearer. GET /leave with select=id,employeeId,typeId,status,duration,startDate,endDate,gradePercentage,archived and filters on endDate and status; GET /leave-type with kind (sick_leave, self_certified) and minimumDuration; GET /leave-transaction with date, hours and extent. Employees and employments through /employee and /employment.
- The SIVI messages Employments, Employee data and Absence reports go to the health service, with processing code new, changed or correction, Vangnet J/N (mandatory) 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 Simployer | Field in Arbodienst (SIVI) | Notes |
|---|---|---|
Employee id | Identificatie werknemer | No citizen service number |
Employment | Identificatie dienstverband | |
Leave id van het eerste verlof | Verzuimgeval identificatie | Adjoining leaves keep the same absence case |
startDate | Datum eerste verzuimdag | |
gradePercentage | Percentage verzuim | |
endDate + 1 dag, als er geen aansluitend ziekteverlof volgt | Datum hersteld en Einde verzuim J/N | |
Leave type (kind) | Filter op ziekte | Not sent itself |
Eigen veld in Simployer | Vangnet J/N |
Related
Recruitee → Simployer
Recruitee to Simployer integration: hired candidates with employment and salary in Simployer One
Simployer → Active Directory
Simployer to Active Directory integration: accounts in your own domain from Simployer
Simployer → ADP iHCM
Simployer to ADP iHCM integration: salary, bonuses and end of employment from Simployer One to ADP iHCM
Simployer → AFAS Profit
Simployer to AFAS integration: Dutch employees from Simployer One in AFAS payroll