VSAbsence reporting (SIVI)
SAP SuccessFactors to the absence insurer via SIVI: absence per policy from Employee Central
With an integration between SAP SuccessFactors and the absence insurer, approved absence of employees of the Dutch company goes from Employee Central to the insurer automatically, as a SIVI employer-to-insurer message. Every report arrives under the payroll tax number the policy is held on, and a moved date in SuccessFactors goes as a correction including the old values.
What the integration does
Organisations with SAP SuccessFactors Employee Central that have insured the absence risk of their Dutch employees with an absence insurer often still pass on sickness and recovery to that insurer by hand. A missed or late recovery report means the insurer calculates with the wrong days.
- At the start we record, for each Dutch company in SuccessFactors, under which payroll tax number the policy with the insurer is held.
- Sickness is reported and approved in SuccessFactors as now; KoppelHet only takes approved absence.
- Per period, new reports, changes, corrections and cancelled reports go to the insurer together in one message.
- On return the insurer receives the recovery date and the absence is closed.
What to watch for with SAP SuccessFactors and Verzuimverzekeraar (SIVI)
- The insurer recognises the employer by the payroll tax number of the unit that holds the policy. In SuccessFactors an employee belongs to a company, and that number is not stored there by default. KoppelHet keeps track of which policy each Dutch company falls under.
- A leave of absence in SuccessFactors has an actual return date one day after the end date. That is the first day work could have resumed, which the insurer asks for as the recovery date. The integration takes it over without conversion.
- Pregnancy and maternity leave is usually its own leave of absence in SuccessFactors. The message to the insurer has WAZO codes for that. Per time type we record which code applies, so pregnancy leave does not arrive at the insurer as ordinary sickness.
- If a temporary contract is ended in SuccessFactors while the employee is sick, the absence continues for the insurer. The standard explicitly asks not to report someone as recovered on the contract end date, so the termination in SuccessFactors closes nothing.
- Whether an absence comes from a work accident or a traffic accident with recourse determines who bears the cost. SuccessFactors has no fixed choice for it. We add a field to the sickness time type, and the integration converts it into the message's cause code.
- If HR moves the start date of an already reported absence in SuccessFactors, KoppelHet sends a correction with the previous first day of absence and the previous absence number. An absence withdrawn afterwards goes to the insurer as cancelled.
- With concurrent employment someone has several users in SuccessFactors. The insurer wants one employee number within one employer, even with several employments. The person ID therefore goes as the employee and each user as a separate employment.
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 also need an integration with the health service?
Often yes; that is a separate SIVI message. Both can come from the same absence in SuccessFactors.
What if we have several Dutch companies under one policy?
Then they all go under the payroll tax number of the unit that holds the policy. We record that per company at the start.
Is a diagnosis sent to the insurer?
No. Only dates, percentages, a cause code and, where needed, a WAZO code.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- SuccessFactors Employee Central through the OData API v2 with OAuth 2.0 (SAML bearer assertion), filtered on lastModifiedDateTime and the Dutch companies. Absence from EmployeeTime (timeType, approvalStatus, startDate, endDate, loaActualReturnDate); employments from EmpEmployment and EmpJob (company, standardHours) with fromDate and toDate.
- 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. Cause codes 10 work accident, 11 traffic accident with recourse and 99 other; WAZO codes 01, 02 and 03. Transport to be agreed per insurer.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in SAP SuccessFactors | Field in Verzuimverzekeraar (SIVI) | Notes |
|---|---|---|
Company (FOCompany) van EmpJob | Werkgever: loonheffingennummer | Through a table per company |
personIdExternal | Identificatie werknemer | |
userId (EmpEmployment) | Identificatie dienstverband | |
EmployeeTime.startDate | Datum eerste verzuimdag | |
loaActualReturnDate | Datum hersteld en Einde verzuim J/N | |
Afwezige uren ten opzichte van EmpJob.standardHours | Percentage verzuim | |
Time type voor zwangerschap of bevalling | WAZO-code | Set per time type |
Extra veld bij het time type | Oorzaak verzuim (10, 11 of 99) |
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