ASAbsence reporting (SIVI)
Lucca to the occupational health service via SIVI: confirmed sickness per half day as absence reports
With an integration between Lucca and the occupational health service, confirmed absence on the sick leave account of employees of the Dutch establishment in Lucca automatically becomes a sick, change or recovery report at your health service, in the SIVI format. For this KoppelHet regularly fetches the confirmed and cancelled absences since the previous run.
What the integration does
Organisations that use Lucca for leave and absence and have an occupational health service in the Netherlands now enter sickness in Lucca and then again in the health service portal. Lucca comes from France; the French sickness data it keeps does not apply to Dutch absence support.
- At the start we designate the leave accounts for sickness and the establishment that is the Dutch employer.
- Every hour KoppelHet fetches the absences confirmed or cancelled since the previous run.
- Consecutive half days of sickness become one sickness report at the health service, with employment and safety net.
- New days in the same period become a change, the end a recovery report.
- If reported sickness is cancelled, HR gets a task to inform the health service.
What to watch for with Lucca and Arbodienst (SIVI)
- Lucca splits an absence period into half days, each with a morning or afternoon flag and a leave account. KoppelHet merges the half days on the sickness account into one absence case, and passes on a single morning of sickness as fifty percent.
- A period in Lucca is only confirmed once the manager has approved it. Lucca advises treating unconfirmed absence as tentative. KoppelHet therefore only reports sickness to the health service after confirmation.
- Lucca sends no webhooks for absence; its events cover organisation, employees and employments. Every hour KoppelHet requests three things - newly confirmed, still unconfirmed and cancelled absence since the previous run - and applies replace or delete to every half day.
- The establishment filter in Lucca looks at the employee's current establishment, not the one at the time of the absence. If someone moves from the French to the Dutch establishment, KoppelHet records at the start from which date sickness goes to the Dutch health service.
- Timestamps in Lucca are precise to the minute. KoppelHet rounds the moment of the previous run down, so a confirmation in the same minute as the previous run does not fall between two runs.
- Lucca allows fifty requests per minute per environment, shared with all other integrations on Lucca. KoppelHet requests large pages per run and filters directly on the Dutch establishment, so the health service integration does not get in the way of other integrations.
- Lucca keeps additional data for some absences for French law, such as continued pay by the employer and waiting days. Those do not apply in the Netherlands and do not go to the health service, just like comments and attachments on the request.
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
Who creates the API key in Lucca?
According to Lucca, Lucca's Customer Success Manager creates that key with you, with access to the absence of the right employees.
Do the comment and attachment go along?
No. They stay in Lucca.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Lucca Absences API v3 (legacy) - GET /api/v3/leaves with required leavePeriod.ownerId and date, plus leavePeriod.owner.legalEntityId, leaveAccountId, leavePeriod.confirmationDate=since, leavePeriod.isconfirmed, cancellationDate=since and isActive, paging (start,count; default 1000, at most 10,000) and fields. Fields include id, date, isAM, leaveAccountId, leavePeriodId, value (hours), isActive, cancellationDate and comment; LeavePeriod with ownerId, isConfirmed, confirmationDate and attachmentId. Authorization lucca application={apiKey}; 50 requests per minute per tenant, timestamps per minute.
- The SIVI messages Employments, Employee data and Absence reports go to the health service, with Vangnet J/N (mandatory), organisational unit and a cause code without diagnosis. 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 Lucca | Field in Arbodienst (SIVI) | Notes |
|---|---|---|
leavePeriod.ownerId | Identificatie werknemer | No citizen service number |
leavePeriodId | Verzuimgeval identificatie | |
Eerste date in de periode | Datum eerste verzuimdag | |
isAM per date en value (uren) | Percentage verzuim | |
Laatste date + 1 dag | Datum hersteld en Einde verzuim J/N | |
leaveAccountId | Filter op ziekte | |
owner.legalEntityId | Filter op de Nederlandse vestiging | |
Vaste waarde of eigen veld | Vangnet J/N | Lucca has no safety net concept |
Related
Lucca → Active Directory
Lucca to Active Directory integration: accounts in your own domain based on Lucca
Lucca → ADP iHCM
Lucca to ADP iHCM integration: fixed and variable pay from Lucca Compensation to Dutch ADP payroll
Lucca → AFAS Profit
Lucca to AFAS integration: employees and pay of the Dutch entity from Lucca in AFAS
Lucca → DATEV
Lucca to DATEV integration: German joiners, leavers and master data from Lucca to DATEV