ASAbsence reporting (SIVI)
SAP SuccessFactors to the occupational health service via SIVI: sickness and recovery from Employee Central
With an integration between SAP SuccessFactors and the occupational health service, approved sickness reports, changes and recovery of Dutch employees go from Employee Central to the health service automatically, in the SIVI format health services process. New employments are also known to the health service in advance, so a first sickness report does not get stuck on an unknown employee.
What the integration does
Organisations with SAP SuccessFactors Employee Central as HR system and a Dutch occupational health service often keep absence twice, in Time Off and in the health service portal. If a new employee only appears at the first sickness report, sorting it out costs days of the statutory deadline.
- A new employment at the Dutch company goes to the health service as employment and employee, before anyone can fall sick.
- An employee or manager reports sickness in SuccessFactors; KoppelHet only picks it up after approval.
- If the absence lasts and HR converts it into a leave of absence, it stays the same absence case for the health service.
- On return the recovery date goes to the health service, also when the return is partial.
- The health service's return and processing notification comes back into the KoppelHet platform; a rejection becomes a task for HR in the Netherlands.
What to watch for with SAP SuccessFactors and Arbodienst (SIVI)
- In SuccessFactors a time off request has an approval status. The health service only receives approved sickness; a request that is pending or rejected is not sent.
- Long-term absence in SuccessFactors is often a leave of absence, with an expected and an actual return date. The actual return there is always one day after the end date, which is exactly the recovery date the health service wants.
- A leave of absence puts the employee on a different status in SuccessFactors, but for the health service it is not a departure. KoppelHet therefore does not report the employment as ended.
- With concurrent employment, one person in SuccessFactors has two employments, each with its own user. The health service wants one employee with two employments, so the person ID becomes the Employee ID and each user an employment.
- EmpJob is effective dated. KoppelHet reads the department and manager valid on the first sick day, so a transfer during the absence does not send the report to the wrong unit.
- The BSN sits in SuccessFactors among the national IDs with country NLD. Because health services may only use the BSN in limited ways, the integration does not read that field by default.
- SuccessFactors does not know the Dutch safety net scheme. We record it in a country-specific field for the Netherlands, so the rest of the group is not affected.
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
Does our global SuccessFactors team need to change anything?
Little: a technical user with read access and a country-specific field for the safety net. Reporting sick keeps working as it does now.
Is sickness that has not been approved yet sent to the health service?
No. If you want sickness to go straight away, we set up the sickness time type without an approval step.
What if the health service rejects a report?
The reason then shows in the KoppelHet platform and HR in the Netherlands gets a task. After the correction in SuccessFactors the report is sent again.
Can the same integration also report to an absence insurer?
Yes, as an extension. SIVI has a separate message from employer to insurer; the SuccessFactors side stays the same.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- SuccessFactors Employee Central is read through the OData API v2 with OAuth 2.0 (SAML bearer assertion), filtered on lastModifiedDateTime and the Dutch company. Sickness from EmployeeTime (timeType, approvalStatus, startDate, endDate, loaExpectedReturnDate, loaActualReturnDate); employments from EmpEmployment and EmpJob (department, managerId, standardHours) with fromDate and toDate.
- The SIVI messages Employments, Employee data and Absence reports (XML with an XSD per message) go to the health service; the health service sends return reports back. Version and transport are agreed with the health service, which supports the current and the two previous yearly versions.
- Technical user in SuccessFactors with read access to time off and the Dutch employees; no basic authentication.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in SAP SuccessFactors | Field in Arbodienst (SIVI) | Notes |
|---|---|---|
personIdExternal | Identificatie werknemer | The same across all employments of one person |
userId (EmpEmployment) | Identificatie dienstverband | With concurrent employment one per employment |
EmployeeTime.startDate | Datum eerste verzuimdag | |
EmployeeTime.loaActualReturnDate | Datum hersteld | In SuccessFactors already the day after the end date |
Afwezige uren ten opzichte van EmpJob.standardHours | Percentage verzuim | |
EmpJob.department op de eerste verzuimdag | Organisatie-eenheid, code | Through a lookup table to the units at the health service |
EmpJob.managerId | Contactpersoon (leidinggevende) | |
Country-specific field of extra veld | Vangnet J/N | |
PerNationalId (country NLD) | BSN | Only if the health service asks and you agree |
- SAP Business Accelerator Hub – Employee Central (OData v2)
- SAP KBA 2914686 – Leave of absence beëindigen via OData (loaActualReturnDate)
- SAP KBA 2836870 – Actual return date moet een dag na de einddatum liggen
- SAP KBA 2857820 – vaste goedkeuringsstatussen Employee Time
- SIVI – Verzuimstandaard Werkgevers – Arbodiensten
- SIVI – Toelichting Verzuimstandaard Werkgevers – Arbodiensten 2026 (concept)
Related
Ashby → SAP SuccessFactors
Ashby to SAP SuccessFactors integration: hire as a new employee in Employee Central
Bullhorn → SAP SuccessFactors
Bullhorn to SAP SuccessFactors integration: placements as employees or contingent workers in Employee Central
Carerix → SAP SuccessFactors
Carerix to SAP SuccessFactors integration: successful placement as a new employee in Employee Central
Greenhouse → SAP SuccessFactors
Greenhouse to SAP SuccessFactors integration: a hire as a new employee in Employee Central