VSAbsence reporting (SIVI)
Nmbrs to the absence insurer via SIVI: sick, partly recovered and recovered in one flow
With an integration between Nmbrs and the absence insurer, absence reports, partial recovery and recovery go from Nmbrs to the insurer automatically, as a SIVI employer-to-insurer message, per Nmbrs company under its own payroll tax number. Payroll reports absence only in Nmbrs and no longer has to keep the insurer's portal up to date.
What the integration does
Employers and accounting firms that keep payroll and absence in Nmbrs and have absence insurance often still report sickness and recovery to the insurer separately. With several companies in one Nmbrs environment, a report then easily ends up under the wrong policy.
- At the start we record for each Nmbrs company under which payroll tax number it is insured with the insurer, and which causes in Nmbrs belong to which SIVI code.
- Payroll records absence in Nmbrs, with partial recovery and recovery as follow-ups.
- KoppelHet fetches per company the absences that changed since the previous round, with the employee's current data.
- The insurer receives one message per period with all reports, grouped per employer.
What to watch for with Nmbrs and Verzuimverzekeraar (SIVI)
- One SIVI message can contain several employers, each with its own payroll tax number. KoppelHet bundles the reports of all Nmbrs companies insured with the same insurer into one message per period, and keeps companies with another insurer out.
- Besides the start date of an absence, Nmbrs also has a registration date. If a sickness report is entered a week late, KoppelHet sends the actual first day of sickness, because that is what the insurer uses for the waiting period and the payment.
- Nmbrs can store a cause per absence from its own list. The insurer only knows work accident, traffic accident with recourse and other. KoppelHet converts the cause through a fixed table, so a traffic accident the insurer can recover from does not arrive as ordinary sickness.
- For a new sickness report Nmbrs asks whether it belongs in a new file. For the insurer that makes no difference, because it determines combined absence within 28 days itself. KoppelHet therefore reports every sickness report as its own absence case, even if HR puts it in an existing file.
- Partial recovery is a separate message on the absence in Nmbrs, with a date and a new percentage. For the insurer it becomes a changed absence with that date as the effective date, not a new case.
- The SIVI message has its own place for an accounting firm that reports on behalf of the employer. If a firm processes the Nmbrs administration, we fill it in, so the insurer knows whom to contact with questions.
- An absence in Nmbrs comes with a free-text comment. It never goes to the insurer; the message only holds dates, percentages and a cause code.
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 this also work if our accounting firm manages Nmbrs?
Yes. The integration does need its own Nmbrs login, which you arrange together with the firm.
Is medical data included?
No. The comment on an absence stays in Nmbrs; the insurer only receives dates, percentages and a cause code.
What if our companies are with different insurers?
Then we create a separate message per insurer, with only the companies insured there.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Nmbrs SOAP EmployeeService (Netherlands only) - Absence_GetAll_AllEmployeesByCompany and Absence_GetList (AbsenceId, Comment, Percentage, Start, RegistrationStartDate, End, RegistrationEndDate, Dossier, Dossiernr) and Absence2_GetList for the cause (AbsenceCause with CauseId and Cause); partial recovery and recovery as separate messages. The SOAP API is retired from 1 March 2027; where the REST API (OAuth 2.0) provides the same, we switch over.
- Message Verzuimmeldingen from employer to insurer (XML, targetNamespace http://www.sivi.org/Verzuimmanagement/VerzuimmeldingenWerkgeverVerzekeraar/2022, file name starts with WV-), structure Bericht algemeen, Administratiekantoor (0..1), Werkgever (1..*), Werknemer, Dienstverband and Verzuim; processing codes 01 to 05; cause codes 10, 11 and 99.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Nmbrs | Field in Verzuimverzekeraar (SIVI) | Notes |
|---|---|---|
Nmbrs-bedrijf | Werkgever: loonheffingennummer | Through a table per company |
Personeelsnummer | Identificatie werknemer | |
AbsenceId | Verzuimgeval identificatie | |
Start | Datum eerste verzuimdag | Not RegistrationStartDate |
Percentage en gedeeltelijk herstel | Percentage verzuim met ingangsdatum mutatie | |
Herstel (laatste verzuimdag) | Datum hersteld en Einde verzuim J/N | |
AbsenceCause (CauseId, Cause) | Oorzaak verzuim (10, 11 of 99) | Through a code table |
Related
ADP Workforce Now → Nmbrs
ADP Workforce Now to Nmbrs integration: the Dutch payroll group from ADP in the right Nmbrs company
AlexisHR → Nmbrs
AlexisHR (Simployer One) to Nmbrs integration: Dutch employees into payroll
BambooHR → Nmbrs
BambooHR to Nmbrs integration: Dutch payroll next to a global HR system
Bullhorn → Nmbrs
Bullhorn to Nmbrs integration: placements with hourly pay and end date in payroll