Absence reporting (SIVI)
Nmbrs to Visma Verzuim integration: employees per company and every absence course in BlueVi
With an integration between Nmbrs and Visma Verzuim, all employees of every Nmbrs company are in BlueVi, with department and contract hours, and every sick notification, partial recovery and recovery from Nmbrs goes to the absence file automatically. The case manager and health service then work with the same state as payroll.
What the integration does
Organisations that run the payroll of one or more companies in Nmbrs and handle absence management in Visma Verzuim now retype new employees and sick notifications in BlueVi. Without an integration a partial recovery reaches the absence application later than Nmbrs, and a new colleague is missing there until they fall ill.
- Every night KoppelHet prepares the employees, employments and departments of each Nmbrs company in BlueVi, including those who are not sick.
- HR records a sick notification in Nmbrs. KoppelHet passes it on as an absence course on the right employment.
- A partial recovery in Nmbrs becomes a new recovery percentage with the effective date in BlueVi.
- A recovery notification closes the absence in BlueVi with the last day of absence.
- If someone leaves while sick, the course gets the reason ill out of service and the file stays open.
What to watch for with Nmbrs and Visma Verzuim
- One Nmbrs environment often holds several companies. Each company becomes its own employer in BlueVi with its own organisational units, so the company doctor and file officer BlueVi keeps per unit belong to the right company.
- On a sick notification in Nmbrs HR chooses whether it is a new file. BlueVi itself applies the rule that a relapse within 28 days of recovery belongs to the previous file. KoppelHet leaves that choice to BlueVi, so the legal adding-up of sickness periods is right, and tells HR when Nmbrs and BlueVi differ.
- Nmbrs records partial recovery as a separate message with an effective date and percentage. BlueVi works with a recovery percentage, where zero means fully sick. KoppelHet converts the Nmbrs percentage on every interim recovery, so the case manager sees the right number of hours.
- BlueVi wants to know all employees, including those who are never sick, while an absence link from Nmbrs would only send notifications. KoppelHet therefore prepares the full list of employments with contract hours every night, so a first sick notification lands on an existing employee straight away.
- If a contract in Nmbrs ends while the employee is sick, KoppelHet passes the reason ill out of service to BlueVi. The file then stays open and the case manager sees that UWV safety net support comes into play.
- An absence notification in Nmbrs has a free comment field, which sometimes holds more than the case manager may know. That comment is not sent to BlueVi; the health service records any medical details itself.
- Today Nmbrs absence data is most complete in the SOAP interface, which disappears on 1 March 2027. For BlueVi this means that the recovery messages must arrive through REST before that date. KoppelHet switches over per part as soon as Nmbrs provides it through REST and checks this against the files in BlueVi.
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 salary data go to BlueVi?
No. Only what absence management needs, such as contract hours, department and the absence dates and percentages.
What if we already connect a health service through SIVI?
Then we agree which route the notifications take, so the health service does not receive them twice. The employee list to BlueVi can run separately.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Nmbrs is read through the Nmbrs REST API with OAuth 2.0 and read-only scopes, per company, for employees, employments, departments, schedule and absence (/employees/{employeeId}/absences). Where it does not yet provide everything, through the SOAP EmployeeService (Absence_GetAll_AllEmployeesByCompany; Absence with Start, Percentage, Dossier and Dossiernr; partial recovery and recovery as separate messages). The SOAP API stops on 1 March 2027.
- BlueVi is written through the BlueVi Case Management API (REST, OpenAPI 3) with an access token from client ID and secret and the Ocp-Apim-Subscription-Key header. Endpoints include /employee, /employment, /employment/contract (normHoursPerWeek) and /organizational-unit (dossierOfficerKey, companyDoctorKey), each with an externalKey. Absence through /absence-course with employmentKey, dateStart and recoveryPercentage (0 to 100); recoveryReason including partial-recovery, recovered and ill-out-of-service.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Nmbrs | Field in Visma Verzuim | Notes |
|---|---|---|
Bedrijf in Nmbrs | Werkgever in BlueVi | Each company its own employer |
Personeelsnummer met bedrijf | employee externalKey | |
Dienstverband | employment externalKey | |
Afdeling | organizational-unit | |
Contracturen per week | normHoursPerWeek (contract) | |
Startdatum verzuim | absence-course: dateStart | |
Percentage (ziekmelding en gedeeltelijk herstel) | recoveryPercentage | Converted to how many percent someone has recovered |
Herstel (laatste verzuimdag) | recoveryReason recovered | |
Einddatum dienstverband tijdens verzuim | recoveryReason ill-out-of-service |
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