Cezanne HR logoAS

Absence reporting (SIVI)

Cezanne HR to the occupational health service via SIVI: sickness absence events as absence reports

With an integration between Cezanne HR and the occupational health service, an approved sickness absence event of a Dutch employee in Cezanne HR automatically becomes a sick, change or recovery report at the health service, in the SIVI format. Sickness without a known end date, marked in Cezanne as open-ended sickness, stays open at the health service until HR fills in the end.

What the integration does

Organisations that use Cezanne HR for HR in several countries, with a Dutch branch that has a health service, record sickness as an absence event and then report it again in the health service portal. A sickness that HR deletes in Cezanne because it was on the wrong person stays at the health service.

  1. At the start we pick the absence types in the sickness category and the Dutch company.
  2. Every hour KoppelHet requests the absence events changed since the previous run, plus the deleted events.
  3. Approved sickness becomes a sickness report on the event's employment.
  4. From the hours per part of day KoppelHet determines the percentage; a different percentage becomes a change.
  5. As soon as the open-ended flag disappears and there is an end date, the recovery report follows. A deleted event that was already reported becomes a task for HR.
Cezanne HR → KoppelHet → Arbodienst (SIVI)SOURCECezanne HRTARGETArbodienst (SIVI)Arbodienst (SIVI)KoppelHetmapping · logging · monitoringCezanne HR → KoppelHet → Arbodienst (SIVI)SOURCECezanne HRTARGETArbodienst (SIVI)Arbodienst (SIVI)KoppelHetmapping · logging · monitoring
Out: Absence events in the sickness category · Hours per part of day from the absence event details · Open-ended sickness flag · Deleted absence events · Employment, company and organisational unit

What to watch for with Cezanne HR and Arbodienst (SIVI)

  • Cezanne HR has a separate flag on an absence event for sickness whose end is not yet known. While it is on, KoppelHet sends no recovery report, even if there is a provisional end date in the event. That fits the open absence case the health service expects.
  • For every day of an absence Cezanne records the hours for the morning and the afternoon, plus the total for that day. KoppelHet calculates the absence percentage per day from that, so an employee who only works mornings shows as half recovered at the health service.
  • A deleted absence event disappears from the normal list in Cezanne, but lands in a separate table of deleted events, with the dates and who deleted it. KoppelHet reads that table every hour, so a withdrawn sickness does not silently stay open at the health service.
  • Every absence event names the employment, the company and the organisational unit. KoppelHet only forwards events of the Dutch company and includes the organisational unit, so the occupational physician finds the employee in the right department.
  • The absence tables in the Cezanne API are only accessible to the HR Professional role. A restricted HR role cannot see the deleted events and day details. KoppelHet therefore asks for a dedicated API user with that role, and read rights only.
  • An absence event has notes, a reason and a sick pay checkbox. KoppelHet selects only the fields for dates, status, category and employment in the API, so notes with medical details do not reach KoppelHet or the health service.

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, architecture and compliance

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.

Price indication · Basic

Leave your work email and you see the price indication right away.

We only use your address to follow up on your question about this integration.

Frequently asked questions

Does HR need to use the open-ended sickness flag?

It is not required, but it helps. Without the flag KoppelHet treats a provisional end date as real recovery.

Do we need People PLUS+?

No. Webhooks require that package, but this integration reads the tables every hour through the API.

Are the notes on an absence sent along?

No. KoppelHet does not request them. The health service gets dates, a percentage and codes.

Technical details for IT

For those who want to know how it works under the hood: APIs, fields and sources used.

  • Cezanne HR through the OData API (dataservice.svc) with OAuth 2.0 and an API user with the HR Professional role. PersonAbsenceEvents with $filter on AbsenceCategory, AbsenceStatus, CompanyCode and AbsenceEventLastModifiedDate and $select on PersonAbsenceEventGUID, PersonCode, EmploymentID, CompanyCode, OrgUnitCode, AbsenceEventEffectiveFrom, AbsenceEventEffectiveTo, Commences, Finishes and OpenEndedSickness. PersonAbsenceEventDetails per ReferenceDate (AMWorkingHours, PMWorkingHours, DayTotalWorkingHours) and PersonAbsenceDeletedEvents (AbsenceEventGuid, ActionDate). AbsenceTypes with Category.
  • The SIVI messages Employments, Employee data and Absence reports go to the health service, with processing code new, changed or correction, 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 Cezanne HRField in Arbodienst (SIVI)Notes
PersonCodeIdentificatie werknemerNo citizen service number
EmploymentIDIdentificatie dienstverband
PersonAbsenceEventGUIDVerzuimgeval identificatie
AbsenceEventEffectiveFrom en CommencesDatum eerste verzuimdag
AM- en PMWorkingHours per ReferenceDatePercentage verzuim
AbsenceEventEffectiveTo + 1 dag, als OpenEndedSickness uit staatDatum hersteld en Einde verzuim J/N
OrgUnitCodeOrganisatie-eenheid, code
Eigen veld in CezanneVangnet J/N

Related

Which systems do you want to connect?

Tell us which systems you use and what should happen automatically. Together we define the smallest working solution, with a clear design and a quote before building.