VSAbsence reporting (SIVI)
Oracle HCM Cloud to the absence insurer via SIVI: Dutch absences reported per policy
With an integration between Oracle HCM Cloud and the absence insurer, approved sickness of the Dutch legal employer goes to the insurer automatically, as a SIVI employer-to-insurer message. An absence recorded in Oracle as a Dutch work accident reaches the insurer as the cause code work accident, without disease code or comments.
What the integration does
Organisations that use Oracle HCM Cloud in several countries and have insured the absence risk in the Netherlands with an absence insurer now pass sickness and recovery on by hand in the insurer's portal. Whoever does it must also know which policy an employee falls under and whether the absence comes from a work accident.
- At the start we link each Dutch legal employer in Oracle to the payroll tax number the policy is held on, and designate the sickness absence types.
- Every hour KoppelHet fetches the absences changed since the previous run, with the Dutch context data.
- After approval KoppelHet turns it into a new report, with cause code and percentage.
- Per agreed period, new reports, changes, corrections and cancelled reports go to the insurer in one message.
What to watch for with Oracle HCM Cloud and Verzuimverzekeraar (SIVI)
- Oracle has its own Dutch contexts on an absence, including work accident. KoppelHet only uses the fact that this context was chosen and turns it into the cause code work accident. Whatever else the context holds does not go to the insurer.
- Oracle also has Dutch contexts for sickness due to pregnancy, sickness around childbirth and organ donation. A UWV safety net scheme often applies to those cases. KoppelHet marks them separately, and which code the insurer wants for them is agreed with the insurer at the start.
- An absence in Oracle has fields for a disease code and for the date the condition began. These are medical in nature and are not read. The insurer only gets dates, percentage and cause code.
- Every absence in Oracle belongs to a legal employer. The insurer wants the payroll tax number of the unit holding the policy. KoppelHet translates the legal employer with a fixed table, so two Dutch employers under one policy still arrive correctly.
- If the start date of a reported absence is moved in Oracle, KoppelHet sends a correction with the old first day of absence included. The insurer then replaces the case instead of adding a second one.
- An open-ended absence in Oracle gets no recovery date at the insurer yet. A contract ending during the sickness does not close the absence either. Only when the end date is in Oracle does the recovery go along.
- If someone withdraws a reported absence in Oracle, it goes to the insurer as a cancelled report in the next period. A linked relapse through a linkage rule is reported by KoppelHet as a case of its own, because the message has no separate notion of combined absence.
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
Do we need to use the Dutch contexts in Oracle?
For the cause code, yes. Without the work accident context all sickness goes to the insurer as other.
Can this run alongside our health service integration?
Yes. Health service and insurer each get their own SIVI message from the same absence in Oracle.
Does the disease code from Oracle go along?
No. The integration does not even request that field.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Oracle HCM Cloud through the absences REST resource (/hcmRestApi/resources/11.13.18.05/absences) with personNumber, legalEntityId (mandatory), absenceTypeId, absenceStatusCd, approvalStatusCd, openEndedFlag, startDate, endDate, startDateDuration, endDateDuration, duration, unitOfMeasure and lastUpdateDate; child absenceRecordingsDDF with the contexts ORA_HRX_NL_SICKNESS, ORA_HRX_NL_WORK_ACCIDENT, ORA_HRX_NL_SICK_PREG_REL, ORA_HRX_NL_SICK_CHILD_BIRTH and ORA_HRX_NL_ORGAN_DONOR. Fields diseaseCode, conditionStartDate, comments and absenceReason are not requested.
- Message Verzuimmeldingen from employer to insurer (XML, targetNamespace VerzuimmeldingenWerkgeverVerzekeraar, file name prefixed WV-), processing codes 01 new, 02 changed, 03 cancelled, 04 for information and 05 correction (with the old key values), cause codes 10, 11 and 99. Transport to be agreed per insurer.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Oracle HCM Cloud | Field in Verzuimverzekeraar (SIVI) | Notes |
|---|---|---|
legalEntityId (via tabel) | Werkgever: loonheffingennummer | The number of the unit holding the policy |
personNumber | Identificatie werknemer | |
Absence-id | Verzuimgeval identificatie | |
startDate | Datum eerste verzuimdag | |
startDateDuration, endDateDuration en duration | Percentage verzuim | |
endDate + 1 dag (niet bij openEndedFlag) | Datum hersteld en Einde verzuim J/N | |
Context ORA_HRX_NL_WORK_ACCIDENT | Oorzaak verzuim 10 (arbeidsongeval) | Otherwise 99, or 11 with recourse |
Related
Ashby → Oracle HCM Cloud
Ashby to Oracle HCM integration: an accepted offer on an opening becomes a pending worker
Bullhorn → Oracle HCM Cloud
Bullhorn to Oracle HCM integration: an approved placement of an employee becomes a pending worker
Carerix → Oracle HCM Cloud
Carerix to Oracle HCM integration: successful placement as a pending worker in Oracle HCM Cloud
Greenhouse → Oracle HCM Cloud
Greenhouse to Oracle HCM integration: accepted offer as a pending worker in Oracle HCM Cloud