VSAbsence reporting (SIVI)
Loket to absence insurer via SIVI: sick notifications, accidents and recovery from Loket to the insurer
With an integration between Loket and the absence insurer, sick notifications, changes in the percentage and recovery from Loket go to the absence insurer in the SIVI message for insurers, per wage tax number. An accident with a liable third party gets the right cause code, so the insurer can claim recourse.
What the integration does
Organisations that record absence in Loket and have insured the risk of continued pay during sickness now send the insurer an overview or fill in a portal. Especially the cause of an accident and the expiry of a temporary contract during sickness are then often lost.
- HR records the sick notification in Loket, with the accident type and whether a third party is liable in case of an accident.
- KoppelHet reads the new and changed absences with their progress per employer.
- At the end of the agreed period KoppelHet bundles all notifications per wage tax number into one SIVI message to the insurer.
- A recovery becomes an end of absence; a deleted absence a cancelled notification.
- Replies or rejections from the insurer arrive as a task for HR.
What to watch for with Loket and Verzuimverzekeraar (SIVI)
- For an accident Loket records the accident type and whether a third party is liable. The insurer only knows work accident, traffic accident with recourse and other. KoppelHet derives the SIVI cause from those two fields, so a collision caused by someone else arrives as recoverable.
- According to the SIVI guidance the employer does not end a sick temporary contract on its end date. Loket can close an absence on the last day of employment; KoppelHet then sends no end of absence, but leaves the case open at the insurer and notifies HR.
- Loket knows an absence as a safety net case for pregnancy, adoption or organ donation. In the SIVI message for insurers pregnancy and adoption each get their own WAZO code; KoppelHet sets it, so the insurer knows UWV pays the benefit.
- If HR deletes an absence in Loket, all its progress records disappear too. KoppelHet remembers which notifications the insurer already had and sends the processing code cancelled for such a case, instead of letting it disappear silently.
- The SIVI message identifies an employer by the wage tax number of the unit the contract was concluded with. Loket provides that number per payroll administration. KoppelHet bundles the employers covered by the same policy into one message and leaves out the rest.
- Loket fills in the employee number itself with the highest number plus one if it is empty at conversion. SIVI asks for a number that is never used for someone else. KoppelHet checks at the start whether the employer reuses numbers, and otherwise uses the fixed Loket id.
- An absence in Loket also has comments, a case manager and whether someone is in hospital. None of that goes to the insurer; the message contains dates, percentages and codes.
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
Our accounting firm works in Loket. Does it need to record anything differently?
Only for an accident: then the accident type and whether a third party is liable. The rest it records as it does now.
Can we connect a health service via SIVI at the same time?
Yes. That is a separate message with its own standard; KoppelHet sends both from the same absence in Loket.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Loket through the REST API with OAuth and read rights - GetCalendarAbsencesByEmployerId per employer, GetAbsenceByAbsenceId (causeOfAbsence, accidentType, isThirdPartyLiability, progress with startDate and incapacityPercentage, endOfAbsence) and wageTaxNumber of the payroll administration. DeleteAbsenceByAbsenceId also deletes the underlying progress records.
- Message Verzuimmeldingen from employer to insurer (XML, targetNamespace http://www.sivi.org/Verzuimmanagement/VerzuimmeldingenWerkgeverVerzekeraar/2022, file name starts with WV-, UTF-8), structure Bericht algemeen, Administratiekantoor, Werkgever (1..*), Werknemer, Dienstverband and Verzuim; processing codes 01 to 05; cause 10, 11 and 99; WAZO 01 pregnancy, 02 adoption, 03 foster care.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Loket | Field in Verzuimverzekeraar (SIVI) | Notes |
|---|---|---|
wageTaxNumber van de loonadministratie | Werkgever, loonheffingennummer | |
Personeelsnummer | Identificatie werknemer | |
Absence id | Identificatie verzuim | |
accidentType en isThirdPartyLiability | Oorzaak verzuim 10, 11 of 99 | |
causeOfAbsence (zwangerschap, adoptie) | Vangnet en WAZO-code | |
progress.startDate en incapacityPercentage | Ingangsdatum en percentage verzuim | |
endOfAbsence (date, reason) | Datum hersteld en Einde verzuim J/N | |
Verwijderd verzuim | Verwerkingscode 03 (vervallen) |
Related
ADP Workforce Now → Loket
ADP Workforce Now to Loket integration: hires, pay, hours and bonuses from ADP to the Dutch payroll run
AlexisHR → Loket
AlexisHR to Loket integration: employees of the Dutch company from AlexisHR into payroll
BambooHR → Loket
BambooHR to Loket integration: HR changes from BambooHR for Dutch payroll
Bullhorn → Loket
Bullhorn to Loket integration: placement as a concept employee in the right payroll administration