Absence reporting (SIVI)
Loket to Visma Verzuim integration: employees and absence progress from Loket in the BlueVi absence file
With an integration between Loket and Visma Verzuim, all employees of every Loket employer are in BlueVi, with department and hours, and every absence with its progress goes from Loket to the file as an absence course. Accident, safety net and leaving during sickness come along, so the case manager does not need to check with payroll.
What the integration does
Organisations that do payroll and absence registration in Loket and run absence management in Visma Verzuim now record a sick notification twice. The data the case manager needs, such as an accident with a liable third party or a safety net situation, is already on the absence in Loket and is asked again.
- Every night KoppelHet prepares employees, employments, departments and hours of every Loket employer in BlueVi.
- HR records an absence in Loket. KoppelHet creates an absence course in BlueVi on the right employment.
- Every new absence progress in Loket becomes a new absence course with the converted recovery percentage.
- Closing in Loket closes the absence in BlueVi, with the reason recovered or ill out of service.
- A difference between Loket and BlueVi arrives as a task for HR.
What to watch for with Loket and Visma Verzuim
- Loket records the percentage in which someone cannot work, BlueVi the recovery percentage, where zero is fully sick. KoppelHet converts every progress record, so 40 percent sick in Loket becomes 60 percent recovery in BlueVi.
- For an accident Loket records the accident type and whether a third party is liable. BlueVi knows four kinds, from private to work accident, each with or without a liable party. KoppelHet translates the Loket combination to one of them, so the case manager immediately sees that recourse is possible.
- A safety net absence in Loket due to pregnancy or organ donation gets the matching safety net value in BlueVi. BlueVi has no separate value for adoption; KoppelHet then leaves that field empty and notifies the case manager.
- For a new absence course BlueVi decides whether it belongs to an earlier file; within 28 days after recovery it becomes a compiled file. KoppelHet always passes the Loket absence on as new and leaves that rule to BlueVi, so the legal count happens in one place.
- Loket sometimes closes an absence on the last day of employment. KoppelHet recognises that reason and passes ill out of service to BlueVi with the employment end date, so the file stays open for safety net support.
- Loket records how many hours someone still worked on the first day of sickness. BlueVi has a field for it, but only in whole hours. KoppelHet rounds and puts the exact figure in the logging, so the case manager can check it.
- Loket also has a case manager and a free comment field on an absence. They do not go to BlueVi; there the file officer assigns support itself.
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 hours, department and the absence data that support needs.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Loket through the REST API with OAuth and read rights - employees, employments, departments and GetWorkingHoursByEmploymentId per employer; absence through GetCalendarAbsencesByEmployerId and GetAbsenceByAbsenceId (causeOfAbsence, accidentType, isThirdPartyLiability, hoursWorkedOnFirstDayOfAbsence, progress with incapacityPercentage, endOfAbsence).
- BlueVi through the Case Management API (REST, OpenAPI 3) with access token and Ocp-Apim-Subscription-Key - /employer, /employee, /employment, /employment/contract (normHoursPerWeek), /organizational-unit and /absence-course (employmentKey, dateStart, recoveryPercentage 0-100, newDossier, accidentType, safetyNet, workedHours as an integer, recoveryReason including partial-recovery, recovered, fully-sick-again and ill-out-of-service, dateEmploymentEnd).
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Loket | Field in Visma Verzuim | Notes |
|---|---|---|
Loket-werkgever | employer | Each employer separately |
Werknemer-id | employee externalKey | |
Dienstverband-id | employment externalKey | |
Afdeling | organizational-unit | |
Arbeidstijd (uren per week) | normHoursPerWeek | |
Absence id | absence-course externalKey | |
progress.incapacityPercentage | recoveryPercentage | 100 minus the percentage |
accidentType en isThirdPartyLiability | accidentType | |
causeOfAbsence vangnet | safetyNet | |
endOfAbsence (reden einde dienstverband) | recoveryReason ill-out-of-service met dateEmploymentEnd |
Related
ADP Workforce Now → Loket
ADP Workforce Now to Loket integration: hires, pay, hours and bonuses from ADP to the Dutch payroll run
AlexisHR → Loket
AlexisHR to Loket integration: employees of the Dutch company from AlexisHR into payroll
BambooHR → Loket
BambooHR to Loket integration: HR changes from BambooHR for Dutch payroll
Bullhorn → Loket
Bullhorn to Loket integration: placement as a concept employee in the right payroll administration