ASAbsence reporting (SIVI)
Loket to occupational health service via SIVI: sick notification, absence progress and recovery from Loket to the health service
With an integration between Loket and the occupational health service, sick notifications, changes in absence progress and recovery notifications go from Loket to the health service automatically, in the SIVI format, per employer in Loket. Whoever records absence in Loket no longer has to enter it again in the health service portal, and a notification the health service rejects is noticed straight away.
What the integration does
Organisations that run payroll in Loket, themselves or through an accounting firm, record absence in Loket for continued pay and then report it again to the health service. If the percentage changes or a notification is reopened, the health service often only hears about it at the next contact.
- HR records a sick notification in Loket at the employee's employer; Loket immediately creates the first absence progress with it.
- KoppelHet sees the new absence in that employer's absence overview and fetches the notification with its progress.
- The health service receives the sick notification in the SIVI format, under the employer identifier and connection number of that Loket employer.
- A new absence progress is sent as a change of the percentage with the effective date; closing the absence is sent as a notification with the recovery date.
- The health service's confirmation shows in the KoppelHet platform; a rejected notification becomes a task for HR.
What to watch for with Loket and Arbodienst (SIVI)
- In Loket HR records through the absence reason whether it is sickness or a safety net situation, such as pregnancy, organ donation or adoption leave. KoppelHet derives the mandatory SIVI safety net field from it, so HR does not need to record anything extra for it.
- An absence in Loket consists of a chain of absence progress records; a new record closes the previous one on the day before. KoppelHet sends each new record as a SIVI change with the effective date and the percentage from 1 to 100, so the health service sees partial recovery on the right day.
- When an absence is closed, Loket records a date and a reason, and that date can also be the last day of employment. KoppelHet passes the reason on, so the health service does not process a departure during sickness as a recovery.
- Loket can reopen a closed absence; the end date and reason are then cleared. KoppelHet sends that as a correction to the recovery notification, so the absence case at the health service is open again instead of a second case being created.
- Loket's absence overview only shows employments that match the user's filter settings for that employer. KoppelHet uses its own API user without filters, so no sick notification stays out of view.
- An absence notification in Loket has a free comment field of up to 4,000 characters, and fields for the case manager and the nursing address. KoppelHet never sends the comment; the SIVI notification contains dates, percentages and codes, without a diagnosis.
- Changes through the API no longer create a separate notification in Loket; according to Loket that old mechanism does not return in the new version. KoppelHet therefore compares the state of each absence itself with what the health service has already received.
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
Our accounting firm works in Loket. Does it need to do anything differently?
No. It records absence as it does now; the notification to the health service then goes by itself. The firm sees in the platform whether the health service has received it.
Does medical data go to the health service?
No. Only dates, percentages and codes. Comments on the absence in Loket are not sent.
Do all our employers in Loket need the same health service?
No. Per Loket employer we record which health service receives the notifications and with which identifiers.
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-only rights. Per employer GetCalendarAbsencesByEmployerId (per employment with department, filtered on the user's settings), then GetAbsencesByEmployeeId and GetAbsenceByAbsenceId (causeOfAbsence, progress with startDate, incapacityPercentage and endOfAbsence with date and reason). Absence progress as a closed chain (PostAbsenceProgressByAbsenceId fills the end date of the previous record); closing and reopening through closeabsence and reopenabsence.
- 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. Employer identification and connection number per Loket employer. Transport under the SIVI 2025 interface specification, with a return and processing message back.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Loket | Field in Arbodienst (SIVI) | Notes |
|---|---|---|
Personeelsnummer | Identificatie werknemer | No citizen service number |
Dienstverband uit het verzuimoverzicht | Identificatie dienstverband | |
Absence id | Verzuimgeval identificatie | The same for all follow-up notifications |
causeOfAbsence (ziekte of vangnet) | Vangnet J/N | Derived from the reason for sickness |
progress.startDate en incapacityPercentage | Ingangsdatum mutatie en percentage verzuim | |
endOfAbsence.date | Datum hersteld en Einde verzuim J/N | |
endOfAbsence.reason | Reden einde verzuim | Recovered or end of employment |
Afdeling van het dienstverband | Organisatie-eenheid, code | |
Loket-werkgever | Werkgeverskenmerk en aansluitnummer | Issued per employer by the health service |
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