VSAbsence reporting (SIVI)
AFAS Profit to the absence insurer via SIVI: absence reports and progress without a portal
With an integration between AFAS Profit and the absence insurer, absence reports from AFAS go to the insurer automatically, as a SIVI employer-to-insurer message, with every progress line as a change and the recovery date as the close. HR reports absence in AFAS as now, and the insurer receives it under the payroll tax number the policy is held on.
What the integration does
Employers that record absence in AFAS Profit and have absence insurance often enter sickness and recovery reports a second time in the insurer's portal. With several employers in one AFAS environment, HR also has to know which policy each employee falls under.
- An app connector is added in AFAS with GetConnectors for absence reports with progress lines, employees and employments.
- At the start we record for each AFAS employer under which payroll tax number the policy with the insurer is held.
- KoppelHet fetches the changed absence reports and compares them with what the insurer has already received.
- New reports, changes, corrections and cancelled reports go to the insurer in one message per period.
What to watch for with AFAS Profit and Verzuimverzekeraar (SIVI)
- AFAS ticks continuous absence itself when a new report falls within 28 days of the previous one. The SIVI message to the insurer has no field for it; the insurer determines combined absence itself. KoppelHet therefore sends the new report as its own absence with its own first day.
- If several AFAS employers fall under one policy, the standard asks for the payroll tax number of the unit that holds the policy, not that of each employer. KoppelHet records for each AFAS employer which policy it falls under, so an operating company does not arrive at the insurer under an unknown number.
- An absence report in AFAS has progress lines, each with a date and a percentage. Every line becomes a change with its own effective date. If a past line is corrected later, the standard says the later lines do not have to be sent again.
- If the start date of an absence report in AFAS is moved after the insurer has received it, KoppelHet sends a correction including the old first day of absence and the old absence number. Without those old values the insurer cannot find the report.
- An employee in AFAS keeps the same employee number for a second employment. That fits the insurer's requirement that an employee has one number within one employer, even with several employments. KoppelHet links the absence to the employment from the absence report.
- If a temporary employment ends in AFAS while the employee is sick, KoppelHet does not close the absence. The standard explicitly asks not to close sick employees on the contract end date; the absence continues until there is a recovery date.
- An absence report deleted in AFAS because it was on the wrong employee goes to the insurer as cancelled, with everything beneath it. A new report then follows on the right employee.
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 AFAS not have its own integration with absence insurers?
AFAS describes a digital delivery to occupational health services. We have not found a delivery of the SIVI message to insurers in the AFAS documentation. If your insurer has its own AFAS integration, we look at that first.
Is medical data included?
No. Only dates, percentages and, where needed, a cause code.
Can this run alongside the integration with the health service?
Yes. Health service and insurer each get their own SIVI message from the same absence reports in AFAS.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- AFAS Profit through GetConnectors on absence reports with progress lines, employees, employments and employers, filtered on change date, under a dedicated app connector with token. Fields as in the HrIllness UpdateConnector - employee (EmId), start date (DaBe), end date (DaEn) and the segment with progress lines.
- Message Verzuimmeldingen from employer to insurer (XML, UTF-8 or ISO-8859-1, targetNamespace http://www.sivi.org/Verzuimmanagement/VerzuimmeldingenWerkgeverVerzekeraar/2022, file name starts with WV-), processing codes 01 new, 02 changed, 03 cancelled, 04 for information and 05 correction, with old key values on a correction. Transport to be agreed per insurer.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in AFAS Profit | Field in Verzuimverzekeraar (SIVI) | Notes |
|---|---|---|
Werkgever in AFAS | Werkgever: loonheffingennummer | Number of the unit that holds the policy |
Medewerkernummer | Identificatie werknemer | |
Volgnummer dienstverband | Identificatie dienstverband | |
Begindatum verzuimmelding (DaBe) | Datum eerste verzuimdag | |
Verlooplijn (datum en percentage) | Ingangsdatum mutatie verzuim en percentage | |
Einddatum verzuimmelding (DaEn) | Datum hersteld en Einde verzuim J/N |
Related
ADP Workforce Now → AFAS Profit
ADP Workforce Now to AFAS integration: Dutch employees from the US HR system in AFAS Profit
AFAS Profit → 4PS Construct
AFAS to 4PS Construct integration: payroll journal per employer in the right 4PS company
AFAS Profit → Adobe Creative Cloud
AFAS to Adobe Creative Cloud integration: users and product profiles from AFAS Profit
AFAS Profit → AG5
AFAS to AG5 integration: employees, employments and absence from AFAS Profit in the skills matrix