SDB logoVisma Verzuim logo

Absence reporting (SIVI)

SDB to Visma Verzuim integration: the full staff list and every sickness report from SDB in BlueVi

With an integration between SDB and Visma Verzuim, all employees, employments and sites from SDB appear in BlueVi automatically, and every sickness and recovery report from SDB goes to the right absence case. KoppelHet also supplies the full staff list and the structure of sites and teams the health service needs in BlueVi.

What the integration does

Care organisations that use SDB for HR and payroll and have absence managed in BlueVi by Visma Verzuim only see new employees in BlueVi when they first report sick. After a transfer a sickness report reaches the wrong case manager.

  1. KoppelHet creates the sites and teams from SDB as organisational units in BlueVi, each with the case manager and company doctor of that region.
  2. All employees appear in BlueVi with their employments, including those who have never been sick.
  3. A transfer in SDB moves the employee in BlueVi to the new site, with the effective date.
  4. A sickness or recovery report in SDB goes to the absence case in BlueVi, on the right employment.
SDB → KoppelHet → Visma VerzuimSOURCESDBTARGETVisma VerzuimKoppelHetmapping · logging · monitoringSDB → KoppelHet → Visma VerzuimSOURCESDBTARGETVisma VerzuimKoppelHetmapping · logging · monitoring
Out: Employee with address and contact details · Employments with hours and pay period · Sites and teams as organisational units · Sickness report, partial recovery and recovery · Safety net indicator, such as pregnancy-related sickness

What to watch for with SDB and Visma Verzuim

  • Besides absence reports, BlueVi also wants to know the employees without absence and the structure of sites. KoppelHet supplies that data.
  • In BlueVi each organisational unit can have its own company doctor and case owner. Because the sites come from SDB and a transfer takes the employee along, a sickness report always reaches the case manager of the site where someone works now.
  • BlueVi records a pay period per contract, from hour to month and also four weeks. For on-call care staff KoppelHet passes the pay period from SDB, so the health service sees that no fixed hours stand against the absence.
  • Pregnancy-related sickness falls under the UWV safety net. BlueVi has its own indicator for this on the absence report. If it is recorded as such in SDB, KoppelHet passes it on, so the employer does not miss the benefit.
  • SDB works with its own care suite in which HR, scheduling and the client record share data. The integration only requests staff and absence data, so no client data goes to the health service.
  • BlueVi works with a recovery percentage, where zero means fully sick. SDB records absence as a percentage sick. KoppelHet converts one into the other, also at every interim change.
  • A temporary care contract sometimes ends during sickness. With the end date from SDB, KoppelHet passes the reason leaving while sick to BlueVi, so the case stays open and moves to safety net support.

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, architecture and compliance

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.

Price indication · Basic

Leave your work email and you see the price indication right away.

We only use your address to follow up on your question about this integration.

Frequently asked questions

Is client data included?

No. The integration only reads staff and absence data from SDB.

What happens with a transfer during sickness?

The employee moves to the new site in BlueVi. Whether the open case moves to the new case manager, we agree with the health service beforehand.

Technical details for IT

For those who want to know how it works under the hood: APIs, fields and sources used.

  • SDB has no public API documentation. The source is an interface or export agreed per customer with SDB.
  • To BlueVi 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/contract (paymentPeriod hour, day, week, four-weeks, month, year; normHoursPerWeek; costCenterCode), /organizational-unit (dossierOfficerKey, companyDoctorKey) and /absence-course (employmentKey, dateStart, recoveryPercentage, safetyNet, recoveryReason). Contract types and absence reasons are configured per environment and fetched first through /configuration/employment/employment-type and /absence-reason.

Which fields are transferred

The key fields. The full mapping is agreed per customer.

Field in SDBField in Visma VerzuimNotes
Personeelsnummeremployee.externalKey en employeeNumber
Dienstverbandemployment.externalKey
Locatie of teamorganizational-unit (externalKey)With dossierOfficerKey and companyDoctorKey per region
Soort contractemploymentTypeCodeThrough a table of the contract types configured in BlueVi
BetaalperiodepaymentPeriod (hour, week, four-weeks, month)
Contracturen per weeknormHoursPerWeek
Eerste ziektedagabsence-course.dateStart
Verzuimpercentageabsence-course.recoveryPercentageConverted to recovery percentage
Vangnetindicatieabsence-course.safetyNetFor example sick-due-to-pregnancy

Related

Which systems do you want to connect?

Tell us which systems you use and what should happen automatically. Together we define the smallest working solution, with a clear design and a quote before building.