VSAbsence reporting (SIVI)
YouForce to the absence insurer via SIVI: sickness cases and sickness periods reported automatically
With an integration between Visma Raet YouForce and the absence insurer, sickness cases from YouForce go to the insurer automatically, as a SIVI employer-to-insurer message, with every new percentage and the recovery date as follow-up reports. HR records absence only in YouForce, and a sickness case changed afterwards goes to the insurer as a correction.
What the integration does
Employers that record absence in YouForce and have insured the risk of continued pay during sickness often still report sickness cases in the insurer's portal. YouForce has a SIVI route for occupational health services, but for the message to the insurer it is not in place by default.
- At the start we record which employers in YouForce are insured with the insurer under which payroll tax number.
- HR or the manager records sickness in YouForce, as now.
- After processing in YouForce, KoppelHet fetches the sickness case with the sickness periods and the current employee and employment data.
- Every sickness case becomes an absence in the SIVI message; every new sickness period a change with its own effective date.
- If a sickness case disappears from YouForce because it was entered in error, KoppelHet sends a cancellation.
What to watch for with Visma Raet YouForce and Verzuimverzekeraar (SIVI)
- YouForce records sickness as a sickness case with sickness periods beneath it, each with its own percentage. KoppelHet turns every period into a change dated from the start of that period, so the insurer sees when someone was back at work half-time and not just the latest state.
- Besides the first day of incapacity of the case, YouForce also keeps the first day of a series of sickness cases. The SIVI message does not ask for it, because the insurer derives combined absence itself. KoppelHet therefore sends each sickness case with its own first day and leaves the series date out.
- YouForce has both a recovery date and a recovery notification date. The insurer wants the day someone could have worked again, so KoppelHet uses the recovery date, even if the recovery notification was made a few days later.
- Sickness and pregnancy leave each have their own permission in the YouForce API. Both are needed, because for pregnancy leave the insurer asks for a WAZO code and a different safety net code applies than for ordinary sickness.
- A sickness case deleted in YouForce is still visible through the API as inactive for seven days and not afterwards. KoppelHet reads at least daily, so every deletion reaches the insurer as a cancellation in time.
- YouForce only shows what HR Core has already processed. A sickness report from this morning is therefore sent in the first round after processing, not at the moment of entry.
- In YouForce the reason for sickness is the organisation's own code list. The insurer only knows work accident, traffic accident with recourse and other. At the start we map your reasons to those three codes, and a reason without a mapping holds the report back.
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 YouForce not already have a SIVI integration?
YouForce mentions a SIVI route for occupational health services. The employer-to-insurer message is a different SIVI message; KoppelHet builds it from the YouForce data.
Is medical data included?
No. Only dates, percentages and a cause code; the reason from YouForce is converted to one of three codes.
Can the same integration also go to the occupational health service?
Yes, as a separate flow with the SIVI message for health services. The YouForce side is largely the same; the health service receives more data.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- YouForce through the Youforce WFM API (OAuth 2.0 through Visma Connect) with the scopes Youforce-WFM:Get_sickleave (GET /v1.0/sickleaves) and Youforce-WFM:Get_maternityLeave (GET /v1.0/maternityleaves), plus Get_Basic for persons and employments; filter on latestSync with from and to, paging with take (at most 1000), skip and nextLink; isActive for deleted records (visible for seven days). Fields according to the Data API tables sickness-case (ao_dag_dt, herst_dt, beterm_dt, zwvrlf_ind, vangnet_ind, rdn_zk, dpid110_sl) and sickness-case-detail (ztvk_vanaf, ztvk_tot, perc_ziek).
- Message Verzuimmeldingen from employer to insurer (XML, UTF-8, targetNamespace http://www.sivi.org/Verzuimmanagement/VerzuimmeldingenWerkgeverVerzekeraar/2022, file name starts with WV-), processing codes 01 to 05, employer by payroll tax number, cause codes 10, 11 and 99, WAZO codes 01 to 03. Transport to be agreed per insurer.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Visma Raet YouForce | Field in Verzuimverzekeraar (SIVI) | Notes |
|---|---|---|
Persoonsnummer | Identificatie werknemer | One number per employee, also with several employments |
Volgnummer dienstverband | Identificatie dienstverband | |
Technische sleutel ziektegeval | Verzuimgeval identificatie | |
Datum eerste ao-dag | Datum eerste verzuimdag | |
Ziektetijdvak vanaf en percentage ziek | Ingangsdatum mutatie verzuim en percentage | |
Datum herstel | Datum hersteld en Einde verzuim J/N | |
Indicatie zwangerschapsverlof | WAZO, code | Safety net then code 00 |
Reden ziek | Oorzaak verzuim (10, 11 of 99) | Through a code table |
Related
ADP Workforce Now → Visma Raet YouForce
ADP Workforce Now to YouForce integration: requests for new Dutch hires and contract changes
Bullhorn → Visma Raet YouForce
Bullhorn to YouForce integration: a placement becomes a hire request
Carerix → Visma Raet YouForce
Carerix to YouForce integration: a placed candidate starts the hire workflow in YouForce
Darwinbox → Visma Raet YouForce
Darwinbox to YouForce integration: hires and pay changes from Darwinbox as a request in YouForce