VSAbsence reporting (SIVI)
Sage People to the absence insurer via SIVI: sickness from absence records per policy to the insurer
With an integration between Sage People and the absence insurer, approved sickness of employees of the Dutch employer goes from Sage People to the insurer automatically, as a SIVI employer-to-insurer message. A moved first day of sickness goes as a correction including the old date, and a withdrawn sickness as a cancelled report.
What the integration does
Organisations that use Sage People for HR in several countries and have insured the Dutch absence risk still pass sickness and recovery on by hand in the insurer's portal. When HR corrects a first day of sickness or withdraws a sickness in Sage People, the insurer calculates with old data.
- At the start we link every Dutch employer in Sage People to the payroll tax number the policy is held on, and choose the reasons that mean sickness.
- Every hour KoppelHet retrieves the absence records changed or deleted since the previous run.
- Approved sickness becomes a new report under the employment it was recorded on.
- A different duration per day becomes a change; a moved start date a correction with the old key.
- At the agreed frequency all reports per employer go to the insurer in one message.
What to watch for with Sage People and Verzuimverzekeraar (SIVI)
- An absence insurer recognises the employer by the payroll tax number of the policy. Sage People has no fixed field for it, because the system works for many countries. KoppelHet keeps track per Dutch employer of the number under which the sickness arrives at the insurer.
- An absence record in Sage People belongs to exactly one employment record. If someone has two contracts with the same Dutch employer, the absence reaches the insurer under the employment HR recorded the sickness on. That way continued pay per contract matches what the insurer reimburses.
- If HR moves the start date of an already reported sickness, that is a correction of a key value for the insurer. KoppelHet therefore sends the previous first day of absence along, so the insurer finds the existing report and does not open a second absence case.
- A deleted absence record stays in the recycle bin of the underlying Salesforce platform for a while. KoppelHet also requests those deleted records and sends the insurer a cancelled report, including the changes beneath it.
- Sage People can keep day records with the duration per day for each absence. A shorter working day halfway through the sickness produces a change at the insurer with that percentage and that day as the effective date, so the benefit calculation starts from the right moment of recovery.
- As long as the end date in Sage People is marked as provisional, the absence stays open at the insurer. Only when HR clears the checkbox does KoppelHet send a recovery date. An expected return thus does not become a recovery that later has to be reversed.
- Sage People has fields on an absence for a return-to-work interview, a return intention and medical certificates. Those stay outside the integration's permission set. The insurer gets dates, percentages and a cause code.
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
Can this run alongside the integration with the health service?
Yes. Both use the same absence records in Sage People, but each gets its own SIVI message.
What if we have several Dutch employers?
Each employer gets the payroll tax number of its policy. The insurer then sees the reports per employer.
Does the insurer see whether a return-to-work interview took place?
No. Those fields are not in the integration's rights and stay in Sage People.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Sage People through the Salesforce REST API with SOQL on the Absence object (fHCM2__Absence__c) and the Absence Day Record object (Day, Duration), filtered on LastModifiedDate, with fields including Employment Record, Start Date, End Date, End Date Provisional, Approved, Approval Date, Reason and Type. Deleted records through queryAll with IsDeleted. API user with a Salesforce Integration licence, OAuth 2.0 client credentials and a permission set without Notes, Is Private, certificate, Return Intent and Back To Work fields.
- Message Verzuimmeldingen from employer to insurer (XML, targetNamespace VerzuimmeldingenWerkgeverVerzekeraar), processing codes 01 new, 02 changed, 03 cancelled, 04 for information and 05 correction, with old key values on a correction; on cancellation the underlying entities are cancelled too. Transport to be agreed per insurer.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Sage People | Field in Verzuimverzekeraar (SIVI) | Notes |
|---|---|---|
Nederlandse werkgever (tabel in KoppelHet) | Werkgever: loonheffingennummer | Sage People does not store that number by default |
Team member | Identificatie werknemer | |
Employment Record | Identificatie dienstverband | |
Start Date | Datum eerste verzuimdag | |
Reason | Filter op ziekte | Not sent itself |
Absence Day Record (Duration per dag) | Percentage verzuim en ingangsdatum mutatie | |
End Date + 1 dag, alleen als End Date Provisional uit staat | Datum hersteld en Einde verzuim J/N | |
Eigen veld in Sage People | Oorzaak verzuim (10, 11 of 99) |
Related
Sage People → Active Directory
Sage People to Active Directory integration: domain accounts for the Dutch office
Sage People → ADP iHCM
Sage People to ADP iHCM integration: salary records, bonuses and leavers of the Dutch payroll company to ADP
Sage People → AFAS Profit
Sage People to AFAS integration: Dutch employees and salaries from Sage People in AFAS Profit
ASSage People → Arbodienst (SIVI)
Sage People to the occupational health service via SIVI: absence records as absence reports