Absence reporting (SIVI)
HR2day to Visma Verzuim integration: employees, employment relationships and sickness reports from HR2day in BlueVi
With an integration between HR2day and Visma Verzuim, all employees and employment relationships from HR2day appear in BlueVi automatically, and every sickness, partial recovery and recovery report from HR2day goes to the right absence case. The case manager and the company doctor thus work with the same data as payroll, and nobody reports a sick employee twice.
What the integration does
Employers with HR2day for staff and payroll and an occupational health service working in BlueVi from Visma Verzuim often enter a sickness report twice: the manager in HR2day, then someone from HR in BlueVi. If someone has a permanent and an on-call contract, BlueVi sometimes shows only one of the two, and the case is attached to the wrong contract.
- KoppelHet creates the HR2day departments as organisational units in BlueVi, with the manager.
- Every employee appears in BlueVi with all their employment relationships, each as its own employment with department, job and hours.
- A sickness report in HR2day goes to BlueVi, on the employment relationship on which the employee is sick.
- If the employee partly returns to work, BlueVi receives the new percentage with the effective date; on full recovery the recovery report follows.
- If an employment relationship ends during sickness, the integration reports the end of employment as leaving while sick.
What to watch for with HR2day and Visma Verzuim
- An employee in HR2day often has more than one employment relationship, for example a permanent contract and an on-call contract. BlueVi attaches an absence report to one employment. KoppelHet therefore turns each relationship into its own employment and passes the sickness report on for the relationship on which the employee drops out.
- HR2day records the percentage someone is sick, BlueVi asks for the percentage someone has recovered. Someone who is a quarter sick therefore goes to BlueVi as 75 percent recovered. KoppelHet converts this on every change.
- If someone drops out again within 28 days of recovery, BlueVi does not open a new case but adds the report to the previous one. In HR2day that is a new sickness report. KoppelHet lets BlueVi make that choice, so the statutory adding-up of sickness periods is right.
- On-call contracts in HR2day often end while the employee is still sick. BlueVi has a separate reason for that situation, leaving while sick. KoppelHet passes that reason with the end date, so the case manager sees that the UWV safety net comes into play.
- HR2day is listed by UWV as connected for sickness and recovery reports and the report after 42 weeks. If the occupational health service makes that report from BlueVi, we agree beforehand who does it, so UWV does not get a duplicate report.
- Besides contract hours, BlueVi also records the hours actually worked per week. For an on-call worker without fixed hours KoppelHet fills it with the average HR2day knows, so the health service sees how many hours of absence are involved.
- In BlueVi each organisational unit can have its own company doctor and case owner. Because the departments come from HR2day, a new employee in a department gets the right case manager straight away.
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 medical data go from HR2day to BlueVi?
No. HR2day holds no medical data, and the integration only sends what the report needs. The company doctor records medical information in BlueVi.
Are healthy employees in BlueVi too?
Yes. The full employee list is included, so the health service can also plan a preventive consultation without first adding someone by hand.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- HR2day is read through the Salesforce REST API on the HR2day objects for employee, employment relationship, department and absence, filtered on modification date, through a connected app with a read-only integration user.
- To BlueVi through the BlueVi Case Management API (REST, OpenAPI 3) with an access token from client ID and secret (POST /auth/token) and the Ocp-Apim-Subscription-Key header. Endpoints include /employee, /employment, /employment/contract and /organizational-unit, each with an externalKey (up to 191 characters) as our own key. Absence through POST /absence-course with employmentKey, dateStart and recoveryPercentage (0 to 100); a new report within 28 days of the previous one goes into the existing case. recoveryReason includes partial-recovery, recovered and ill-out-of-service.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in HR2day | Field in Visma Verzuim | Notes |
|---|---|---|
Personeelsnummer | employee.externalKey en employeeNumber | |
Arbeidsrelatie (nummer) | employment.externalKey | One employment per employment relationship |
Afdeling | organizational-unit (externalKey) | |
Leidinggevende | internalSupervisorId | |
Naamgebruik | person.namePreference (own, partner, own-partner, partner-own) | |
Contracturen en gewerkte uren | normHoursPerWeek en hoursPerWeek | |
Eerste ziektedag | absence-course.dateStart | |
Verzuimpercentage | absence-course.recoveryPercentage | Inverted: BlueVi asks for the recovery percentage (0 = fully sick) |
Einde arbeidsrelatie tijdens ziekte | recoveryReason ill-out-of-service en dateEmploymentEnd |
Related
Exact Online → HR2day
Exact Online to HR2day integration: cost centres and cost units to HR2day, payroll journal per division
HR2day → Active Directory
HR2day to Active Directory integration: accounts per school or location from HR
HR2day → Microsoft Entra ID
HR2day to Entra ID integration: Microsoft 365 accounts for care, education and childcare
HR2day → Google Workspace
HR2day to Google Workspace integration: one Google account per employee, also with several employment relationships