ASAbsence reporting (SIVI)
AFAS to occupational health service via SIVI: when Profit's own delivery is enough, and when it is not
With an integration between AFAS Profit and the occupational health service, sick notifications, changes in the absence percentage and recovery notifications go from AFAS to the health service automatically, under the SIVI absence standard. AFAS itself delivers digitally to a number of large health services; KoppelHet comes in when a date changes afterwards, when your health service is not on that list, or when you want every confirmation and rejection in one place.
What the integration does
Organisations that record absence in AFAS Profit and work with a health service that receives SIVI messages but is not on AFAS's list currently export the absence file by hand. Without an integration a first sick day that is moved later does not reach the health service, and the file there runs behind.
- The manager or HR records an absence notification in AFAS, as now.
- KoppelHet fetches the notification with its progress lines, per employment.
- The health service receives a new notification or a change in the SIVI format, with the employer identifiers and the health service's connection number.
- If the start or end date changes afterwards, KoppelHet sends a correction including the old date.
- The health service confirms each notification. A rejection becomes a task for HR, with the reason.
What to watch for with AFAS Profit and Arbodienst (SIVI)
- According to its own documentation, AFAS does not automatically pass on a changed start or end date once the notification has been sent to the health service. KoppelHet detects such a change and sends a SIVI correction including the old date, so the file at the health service matches AFAS.
- Profit does not include the citizen service number in the absence file, following the Dutch Data Protection Authority's guidance; the health service links that number to the employee number through a conversion file. KoppelHet uses the same employee number, so a health service already working with AFAS needs no new conversion.
- AFAS's digital delivery goes through the communication service to health services Profit has a setup for, such as ArboNed, Arbo Unie, ArboVitale and Zorg van de Zaak. For a smaller health service Profit does create a file, but HR has to export and send it themselves. KoppelHet takes over that manual step.
- An absence notification in AFAS has progress lines, each with its own date and percentage. Every line becomes a SIVI change with its own effective date, so the health service sees the progress and not just the latest state.
- Under the new absence standard the health service needs a separate data exchange connection number, which AFAS records per employer on the health service record. If an AFAS environment has several employers, KoppelHet sends each notification with the number of that employment's employer.
- SIVI allows only one open absence case per employment. If an employee has two employments in AFAS, KoppelHet attaches the notification to the employment in the absence notification, and holds a second open notification on the same employment with a task for HR.
- If you switch from AFAS's own delivery to KoppelHet, we use the same identifiers for employee, employment and absence case. Open files at the health service continue and do not start again.
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
Can we use AFAS's delivery and KoppelHet side by side?
Not for the same health service, because it would then receive every notification twice. We choose one route per health service.
Is medical data included?
No. The notification contains dates, percentages and codes, no diagnosis.
Does anything need to change in AFAS?
An app connector with GetConnectors for absence and employments is added. The way people report sick stays the same.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- AFAS is read with GetConnectors on absence notifications with progress lines, employees, employments and organisational units, filtered on change date, under a dedicated app connector. Absence fields as in the HrIllness UpdateConnector - start date (DaBe), end date (DaEn), percentage (PsPc) and employment (EnSe).
- The message is Verzuimmeldingen from the SIVI absence standard for employers and health services, with processing code new, changed or correction, validated against the XML schema of the agreed version. Transport under the SIVI 2025 interface specification (REST endpoint at the health service, XML in Base64 inside JSON, OAuth 2.0), with a return and processing message back.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in AFAS Profit | Field in Arbodienst (SIVI) | Notes |
|---|---|---|
Medewerker | Identificatie werknemer | Employee number, no citizen service number |
Dienstverband (EnSe) | Identificatie dienstverband | |
Verzuimmelding | Verzuimgeval identificatie | Same as what AFAS's own delivery used, when switching |
Begindatum verzuim (DaBe) | Datum eerste verzuimdag | |
Verlooplijn: datum en percentage (PsPc) | Ingangsdatum mutatie verzuim en Percentage verzuim | |
Einddatum verzuim (DaEn) | Datum hersteld en Einde verzuim J/N | |
Organisatorische eenheid | Organisatie-eenheid, code | |
Werkgever | Werkgeverskenmerk en aansluitnummer gegevensuitwisseling |
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