VSAbsence reporting (SIVI)
Personio to the absence insurer via SIVI: sick leave periods per policy to the insurer
With an integration between Personio and the absence insurer, sick leave periods of employees of the Dutch legal entity go from Personio to the insurer automatically, as a SIVI employer-to-insurer message. A period without an end date stays open at the insurer, and a moved start or end in Personio goes as a correction including the old date.
What the integration does
Organisations that record HR and leave in Personio and have insured their Dutch absence risk with an absence insurer often enter sickness and recovery reports again in the insurer's portal. An extended or shortened sick leave period in Personio then arrives there late or not at all.
- At the start we link the Dutch legal entity in Personio to the payroll tax number the policy is held on, and pick the absence types of the sick leave category.
- HR or the employee records sickness in Personio, without an end date if the duration is still unknown.
- KoppelHet receives Personio's notification, fetches the period and its daily breakdown and works out the percentage.
- Per period all new reports, changes, corrections and cancelled reports go to the insurer in one message.
What to watch for with Personio and Verzuimverzekeraar (SIVI)
- A legal entity in Personio has a country and a registration number, but no payroll tax number. The insurer recognises the employer precisely by that number, and then the number of the unit with the policy. KoppelHet therefore records per Dutch legal entity under which number the absence arrives.
- Personio breaks an absence period down per day, with the actual duration of each day. If that duration changes halfway through the period, for example on partial recovery, KoppelHet sends the insurer a change with the new percentage and that day as the effective date.
- Personio only sends a notification when the start or end of a period changes. If the start date moves after the insurer already had the report, a correction goes along with the previous first day of absence and the previous absence number, so the insurer can find the report.
- A deleted sick leave period in Personio becomes a cancelled report at the insurer, including everything beneath it. If the sickness was recorded on the wrong employee, a new report follows on the right person.
- A new sick leave period shortly after recovery is a separate period in Personio. The insurer decides itself whether it is combined absence, so KoppelHet sends every period as its own absence with its own first day.
- If a temporary contract in Personio ends during an open sick leave period, the absence continues at the insurer. The end of the employment is not a recovery date.
- Personio has no fixed place for the cause of absence, while the insurer wants to know whether it is a work accident or a traffic accident with recourse. We add a custom attribute for that which the integration may read; the comment on a period stays outside the integration.
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 insurer see the comment on a sick leave period?
No. The integration does not read the comment. The insurer gets dates, percentages and a cause code.
What if we have several Dutch legal entities?
Each legal entity gets the payroll tax number of the policy it falls under. One message can contain several employers.
Can this run alongside the integration with the health service?
Yes. The health service gets its own SIVI message from the same sick leave periods in Personio.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Personio through the webhooks absence-period.created, absence-period.updated.timerange and absence-period.deleted, and the Personio API v2 (GET /v2/absence-periods filtered on updated_at, GET /v2/absence-periods/{id}/breakdowns with effective_duration per date, GET /v2/absence-types with category). Legal entities through GET /v2/legal-entities (country, registration_number). Read access only.
- 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, with old key values on a correction. Transport to be agreed per insurer.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Personio | Field in Verzuimverzekeraar (SIVI) | Notes |
|---|---|---|
Legal entity van het dienstverband | Werkgever: loonheffingennummer | Through a table; Personio does not store that number |
Person ID | Identificatie werknemer | |
Employment ID | Identificatie dienstverband | |
starts_from.date_time | Datum eerste verzuimdag | In the period's time zone |
effective_duration per dag uit de breakdowns | Percentage verzuim en ingangsdatum mutatie | |
ends_at + 1 dag | Datum hersteld en Einde verzuim J/N | Empty while ends_at is empty |
Eigen attribuut | Oorzaak verzuim (10, 11 of 99) |
Related
Ashby → Personio
Ashby to Personio integration: hires with hours and entity as new employees in Personio
Bullhorn → Personio
Bullhorn to Personio integration: placements as a person with employment in Personio
Carerix → Personio
Carerix to Personio integration: successful placement as a new employee in Personio
Greenhouse → Personio
Greenhouse to Personio integration: hired candidates as employees in Personio