VSAbsence reporting (SIVI)
Unit4 HR to absence insurer via SIVI: completed sickness registrations from Unit4 to the insurer
With an integration between Unit4 HR and the absence insurer, sickness registrations from Unit4 go to the insurer automatically as the SIVI Verzuimmeldingen message, as soon as the workflow in Unit4 has completed them. A rejected or deleted registration becomes a cancelled report, and an open end stays open until HR records the recovery date.
What the integration does
Organisations that record absence in Unit4 HR and have placed their sickness risk with an insurer type every sick notification and recovery again in the insurer's portal. A registration that is later rejected or deleted often stays there.
- Every hour KoppelHet reads the absences with a sickness code updated since the previous run.
- Only registrations without draft status and with a completed workflow become a report.
- A new percentage becomes a change with the start date of that row; a confirmed end date the recovery.
- A rejected registration or a deletion request becomes a cancelled report.
- Per agreed period all reports per Unit4 company go to the insurer in one message.
What to watch for with Unit4 HR and Verzuimverzekeraar (SIVI)
- In Unit4 an absence is a transaction with an absence code, such as sickness or vacation. KoppelHet only reads the codes you mark as sickness, so vacation, study leave or special leave never reach the insurer.
- A sickness registration in Unit4 can still be a draft or be in the workflow. KoppelHet only reports registrations that are no longer drafts and whose workflow is finished or not required. If a reported registration is later rejected, KoppelHet sends the processing code cancelled.
- Unit4 lets an absence without a confirmed end date be recorded as open-ended. KoppelHet sends such a registration without a recovery date and with end of absence no. Only once the open end is cleared and the end date is fixed does the recovery date follow.
- The percentage on a Unit4 absence is the share of planned working time someone is absent. That fits SIVI's absence percentage. KoppelHet sends a new row with a different percentage as a change with that row's start date, within the same absence case.
- A deletion in Unit4 is first a request that goes through the workflow. KoppelHet reads that request and only sends the cancelled report once the deletion has gone through, so the insurer does not lose a case that stays in Unit4 after all.
- Every absence in Unit4 belongs to a position of the employee. SIVI allows several employments per employee. KoppelHet uses the position as the employment identification, so someone with two jobs is only reported sick for the job they drop out of.
- The insurer recognises an employer by the payroll tax number of the unit holding the policy. A Unit4 tenant often contains several companies. KoppelHet records the payroll tax number per company and skips companies not covered by the policy.
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 the reason or a comment go to the insurer?
Only as a cause code: work accident, traffic accident with recourse or other. Free text is not sent.
Can the same integration also go to the health service?
That can be added later as an extension, with the SIVI message for health services. We start with the insurer.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Unit4 ERPx through the ObjectAPI (GET /v1/objects/absences) with OAuth 2.0 client credentials, incremental with filter=lastUpdated/updatedAt ge and limit and offset. Fields including companyId, personId, positionId, sequenceNumber, absenceCode, absenceReason, percent, dateFrom, dateTo, isOpenEndedAbsence, isDraft, isDeleted and workflowState (No workflow, Workflow in progress, Finished, Rejected). Tenant limit 500 requests per minute.
- SIVI message Verzuimmeldingen from employer to insurer (XML under the XSD, file name prefixed WV-), processing codes 01 new, 02 changed, 03 cancelled, 04 for information and 05 correction, cause codes 10, 11 and 99. Employer by payroll tax number. Transport to be agreed per insurer.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Unit4 HR | Field in Verzuimverzekeraar (SIVI) | Notes |
|---|---|---|
companyId | Werkgever: loonheffingennummer | Table per Unit4 company |
personId | Identificatie werknemer | |
positionId | Identificatie dienstverband | |
personId met sequenceNumber | Verzuimgeval identificatie | |
dateFrom | Datum eerste verzuimdag | |
percent | Percentage verzuim | |
dateTo zonder open einde | Datum hersteld en Einde verzuim J/N | |
absenceReason | Oorzaak verzuim (10, 11 of 99) | Lookup table |
workflowState Rejected of isDeleted | Verwerkingscode 03 vervallen |
Related
Greenhouse → Unit4 HR
Greenhouse to Unit4 HR integration: accepted offer as an employee in the right Unit4 company
Recruitee → Unit4 HR
Recruitee to Unit4 HR integration: hired candidate as employee in Unit4, validated before it is saved
SmartRecruiters → Unit4 HR
SmartRecruiters to Unit4 HR integration: hire on the position from SmartRecruiters, with onboarding status back
Teamtailor → Unit4 HR
Teamtailor to Unit4 HR integration: hired candidates as employees in Unit4 ERPx, with company and position