ASAbsence reporting (SIVI)
Zoho People to the occupational health service via SIVI: sick leave records as absence reports
With an integration between Zoho People and the occupational health service, approved sick leave records of Dutch employees in Zoho People automatically become sick, change or recovery reports at the health service, in the SIVI format. A half or quarter day of sickness in the Leave Tracker becomes an absence percentage for that day at the health service.
What the integration does
Organisations that use Zoho People for HR and leave, and have a health service for their Dutch employees, enter every sickness report from the Leave Tracker by hand in the health service portal. A cancelled sickness report or a half day of recovery is usually not updated there.
- At the start we pick the leave types that are sickness, and the data centre and entity of the Dutch employees.
- Every hour KoppelHet requests the sick leave records of the current month, for all employees.
- An approved record becomes a sickness report; the number per day determines the percentage.
- When the number per day changes, a change with that date goes to the health service.
- After the last day the recovery report follows. A cancelled record that was already reported becomes a task for HR.
What to watch for with Zoho People and Arbodienst (SIVI)
- Zoho People returns an overview per date for each leave record, with the number of days taken. Half and quarter days show as 0.5 and 0.25. KoppelHet converts that per day into an absence percentage, so the health service sees when someone partly works again.
- The Zoho People leave API always requires a from and to date and has no change date. KoppelHet therefore reads the current month every hour and the past three months every night, and compares each record with what is already at the health service.
- Without an extra setting the API only returns the own leave of the user behind the integration. KoppelHet requests with the option for all employees, and filters straight away on the sick leave types, so holiday and other leave do not reach KoppelHet.
- A record in Zoho People has the status approved, pending, rejected or cancelled. Only approved sickness goes to the health service. If a reported sickness is cancelled, KoppelHet prepares a task for HR.
- Zoho People returns at most two hundred records per query and allows thirty queries per minute, with a five-minute wait after that. KoppelHet pages in blocks and stays below that limit, so the integration is not locked out.
- A record has a free text reason field that employees fill in themselves. KoppelHet never forwards that reason. The health service only gets dates, percentages and a cause code without diagnosis.
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 a separate leave type for sickness in Zoho People?
Yes. KoppelHet recognises sickness by the leave type. If you have several, for example sick with and without a note, we include all of them.
Does this also work with Zoho People on the European data centre?
Yes. We set up the integration on the data centre where your Zoho account is.
Does the health service see the reason the employee enters?
No. It stays in Zoho People.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Zoho People through the Leave Tracker API v2 (GET /api/v2/leavetracker/leaves/records on the customer's data centre, for example people.zoho.com or people.zoho.eu) with OAuth 2.0 and the header Authorization Zoho-oauthtoken. Parameters from, to, dateFormat, leavetype, approvalStatus (APPROVED, PENDING, CANCELLED, REJECTED), dataSelect ALL, startIndex and limit (up to 200). Fields per record Zoho.ID, From, To, Unit (Days or Hours), Days per date with LeaveCount and Session, Leavetype.ID, ApprovalStatus, Employee.ID and Reason. Limit of 30 requests per minute, then a 5-minute wait.
- 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) 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 Zoho People | Field in Arbodienst (SIVI) | Notes |
|---|---|---|
Employee.ID | Identificatie werknemer | No citizen service number |
Dienstverband uit het medewerkerformulier | Identificatie dienstverband | |
Zoho.ID van de registratie | Verzuimgeval identificatie | |
From | Datum eerste verzuimdag | |
Days.{datum}.LeaveCount | Percentage verzuim | 0.5 is fifty percent |
To + 1 dag | Datum hersteld en Einde verzuim J/N | |
Leavetype.ID | Filter op ziekte | Not sent itself |
Eigen veld in Zoho People | Vangnet J/N |
Related
Recruitee → Zoho People
Recruitee to Zoho People integration: hired candidates in the Zoho People employee form
Teamtailor → Zoho People
Teamtailor to Zoho People integration: hired candidates as a record in the Zoho People employee form
Zoho People → Active Directory
Zoho People to Active Directory integration: HR drives the domain account, not the other way round
Zoho People → AFAS Profit
Zoho People to AFAS integration: new hires and changes to Dutch payroll