ASAbsence reporting (SIVI)
BuddeeHR to occupational health service via SIVI: verified sickness registrations from Buddee to the health service
With an integration between BuddeeHR and the occupational health service, every verified sickness registration from Buddee goes to the health service automatically as a SIVI sick notification, and the end date as a recovery report. Employees and employments with their contract hours go along beforehand, per Buddee company under its own payroll tax number.
What the integration does
Organisations that record absence in BuddeeHR then enter sick employees by hand in the health service portal. Buddee lists no health service in its integration list, so recovery is entered by hand too.
- Every night KoppelHet prepares employees and employments per Buddee company at the health service.
- A few times a day KoppelHet reads the registrations that are still running or have ended since the previous run.
- A verified registration becomes a sick notification; an end date a recovery report.
- A deleted registration becomes a cancelled report.
- Return and processing messages from the health service show in the KoppelHet platform.
What to watch for with BuddeeHR and Arbodienst (SIVI)
- A sickness registration in Buddee has a start and end date and hours, but no percentage. KoppelHet therefore reports every registration as full absence. HR records a partial recovery in Buddee by closing the registration and starting a new one; the health service sees that switch as a recovery and a new report, and we discuss that with the health service beforehand.
- Buddee only accepts today or a date in the past as end date. An expected recovery date can therefore not be in Buddee. KoppelHet sends the recovery report the moment HR fills in the end date, and leaves the expected recovery field empty.
- A registration in Buddee has a verified flag. KoppelHet only reports verified registrations, so a mistake does not reach the health service. If a registration is still not verified after one working day, HR gets a reminder, because SIVI asks for absence to be reported as soon as possible.
- The Buddee API filters absence on id, employee, start and end date, not on modification date. KoppelHet therefore reads the registrations without an end date and those with a recent end date in every run, and compares them with what was already reported. A registration that is missing has been deleted in Buddee and becomes a cancelled report.
- SIVI only allows one open absence case per employment. Buddee allows two overlapping registrations for the same employee. KoppelHet checks for overlap and reports it to HR instead of sending a second case the health service would reject.
- The payroll tax number sits on the company in Buddee, and one Buddee environment can have several companies. KoppelHet takes the number of the employee's company into the employer data, and picks the connection number at the health service per company.
- SIVI asks for the contract hours per week on every employment. In Buddee they are on the contract, as part-time or full-time hours, next to the salary. KoppelHet only takes the hours field; the salary on the same contract does not go to the health service.
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 Buddee not have its own health service integration?
Buddee's integration list has no health service. Absence registration is a Buddee feature of its own; the report to the health service runs through this integration.
Does medical data or salary go to the health service?
No. The integration sends dates, contract hours and codes, no diagnosis and no salary.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Buddee REST API on api.buddee.nl with a dedicated Buddee user (JWT through /auth/token with refresh token) - GET /sick-leave-registrations (employee_id, start_date, end_date, hours, days, is_verified, updated_at; filters id, employee_id, start_date and end_date with gte), /employees (number, company with payroll_tax_number), /employments and /contracts (work_schedule_type, fulltime_hours, parttime_hours), pagination up to 200 per page.
- SIVI absence standard for employers and health services (XML with an XSD per message) - Werknemersgegevens (WN-), Dienstverbanden (DV-, contract hours per week required) and Verzuimmeldingen (VZ-), with processing code new, changed or cancelled, and return and processing messages back. One open absence case per employment. Version and transport to be agreed per health service.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in BuddeeHR | Field in Arbodienst (SIVI) | Notes |
|---|---|---|
company.payroll_tax_number | Werkgever: loonheffingennummer | Connection number per company in a table |
employees.number | Identificatie werknemer | |
employments (start_date, end_date) | Dienstverband ingangsdatum en einddatum | |
contracts.parttime_hours of fulltime_hours | Aantal contracturen per week | |
sick-leave-registrations.id | Verzuimgeval identificatie | |
start_date | Datum eerste verzuimdag | |
Vast 100 | Percentage verzuim | Buddee records no percentage |
end_date | Datum hersteld en Einde verzuim J/N |
Related
BuddeeHR → Active Directory
BuddeeHR to Active Directory integration: domain account from employment and position in Buddee
BuddeeHR → AllSolutions
Buddee to AllSolutions integration: employees, positions and schedules from BuddeeHR in AllSolutions
BuddeeHR → Microsoft Entra ID
BuddeeHR to Entra ID integration: Microsoft 365 account from the employment in Buddee
BuddeeHR → Exact Online
BuddeeHR to Exact Online integration: cost centres, cost units and employees from Buddee consistent in Exact