Leave, absence and time
Deel to Quinyx integration: own employees and approved time off from Deel in Quinyx scheduling
With an integration between Deel and Quinyx, employees of the entities scheduled in Quinyx reach the right unit automatically, and time off approved in Deel appears as an absence in Quinyx straight away. If time off is changed or cancelled in Deel, KoppelHet adjusts the absence in Quinyx, including half days.
What the integration does
Organisations that run HR in Deel and schedule shops, warehouses or customer service in Quinyx enter new employees and approved time off into Quinyx by hand. Time off withdrawn in Deel stays in the schedule, and the planner only finds out when someone turns up to work unexpectedly.
- HR creates an employee in Deel at an entity scheduled in Quinyx.
- KoppelHet creates the employee in Quinyx, in the unit of the work location, with an agreement.
- A manager approves time off in Deel; Deel reports the review straight away.
- KoppelHet puts the time off in Quinyx as a full or partial absence.
- On a change or cancellation in Deel, KoppelHet removes the old absence and books the new one where needed.
What to watch for with Deel and Quinyx
- Deel reports the moment a manager reviews time off, with approved or rejected as the outcome. KoppelHet only books an absence in Quinyx when it is approved, so a request still in progress does not leave a gap in the schedule.
- For a half day Deel only says that the first or last day is half, not whether it is the morning or the afternoon. Quinyx wants to know whether the absence falls at the start or the end of the shift. KoppelHet books a half first day at the end of the shift and a half last day at the start, unless you choose another rule.
- Deel's time off notifications are tied to the contract, not to the person. An employee can have several contracts in Deel. KoppelHet looks up the Quinyx employee for each contract and ignores contracts at entities not scheduled in Quinyx.
- Deel has no field for contract hours in the people API. Quinyx schedules nobody without an agreement. KoppelHet takes the hours from a custom field in Deel, or picks a fixed agreement template per job, which we agree at the start.
- When time off is requested, Deel leaves out working away from the office by default, and deleted time off only when you ask for it. KoppelHet keeps working remotely out of Quinyx, because it is not an absence, and also requests deleted time off in the daily check, so a missed deletion does not block the schedule.
- A time off request in Deel can be in full days, half days, hours or a percentage per day, but all days of one request share the same kind. Quinyx has a full absence and a partial one with a percentage. KoppelHet converts hours and percentages per request to that percentage.
- Quinyx refuses absence for an employee whose employment has ended. Deel gives the last working day per contract. KoppelHet sets it as the leave date in Quinyx and no longer books time off that arrives after it, with an alert to HR.
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 EOR employees and contractors go to Quinyx too?
Only if you schedule them in Quinyx. We choose per hiring type and per entity who is included.
Do worked hours go back to Deel?
Not in this integration. A flow of hours to payroll can be added later as an extension.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Deel through the REST API (version 2026-01-01) with an API token or OAuth2 app (scopes people:read and time-off:read). Employees through GET /rest/people and /rest/people/{hris_profile_id} (hiring_type, work_location, client_legal_entity, employments with start_date, work_email and termination_last_day); version 2026-10-12 of this endpoint is in beta. Time off through the webhooks time-off.reviewed, time-off.updated and time-off.deleted (with start_date_is_half_day and end_date_is_half_day, per contract) and GET /rest/time_offs with updated_start_date, status and include_deleted_time_offs.
- Quinyx is written with employees through the Employees API v3 (POST /hr/v3/employees with badgeNumber, homeGroupId and employmentStartDate) and roles through /hr/v3/role-assignments. Absence through POST /v2/schedule/groups/{groupId}/absences and /absences/part-time (absenceRate, absenceRateDirection FROM_START or FROM_END); deleting with reassignBackShifts. INACTIVE_EMPLOYEE after leaving. Agreements through wsdlUpdateAgreementsV2, termination through wsdlUpdateEmployees (leaveDate).
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Deel | Field in Quinyx | Notes |
|---|---|---|
employments[].employee_number of worker_id | badgeNumber | Fixed key, chosen per customer |
first_name, last_name | personalInformation.firstName, lastName | |
employments[].work_email | email | |
work_location | employment.homeGroupId | Through a table from work locations to Quinyx units |
employments[].start_date | employment.employmentStartDate | |
Eigen veld contracturen | Agreement (contracturen) | Deel has no standard field for hours |
employments[].termination_last_day | leaveDate | |
Time off (APPROVED), time_off_type | Absence, absenceTypeId | |
start_date_is_half_day en end_date_is_half_day | Part-time absence (absenceRateDirection) |
Related
Ashby → Deel
Ashby to Deel integration: hires at the own entity as direct employee in Deel
Bullhorn → Deel
Bullhorn to Deel integration: first placement as a direct employee with a contract in Deel
Carerix → Deel
Carerix to Deel integration: successful placement as a person or contract in Deel
Deel → 4PS Construct
Deel to 4PS Construct integration: own employees of the construction entity in 4PS, with department and cost centre as dimensions