Leave, absence and time
Factorial to Quinyx integration: employees of the Dutch entity in Quinyx, approved leave including half days
With an integration between Factorial and Quinyx, employees of the entities scheduled in Quinyx reach the right unit automatically, with a role from their first working day. Leave approved in Factorial then appears as an absence in Quinyx, with a half day at the start or end of the shift, and KoppelHet updates a change or deletion in Factorial.
What the integration does
Organisations that run HR in Factorial and schedule stores, hospitality or logistics in Quinyx enter new employees and approved leave into Quinyx by hand. Leave changed or deleted in Factorial stays in the schedule until the planner happens to notice.
- HR creates an employee with a contract in Factorial at an entity scheduled in Quinyx.
- KoppelHet creates the employee in Quinyx, in the unit of the workplace, with a role from the start date.
- A manager approves leave in Factorial; Factorial sends a notification straight away.
- KoppelHet puts the leave in Quinyx as a full or partial absence.
- On a change or deletion in Factorial KoppelHet removes the old absence and books the new one where needed.
What to watch for with Factorial and Quinyx
- For a half day Factorial says whether it is the beginning or the end of the day. Quinyx books a partial absence from the start or from the end of the shift. KoppelHet maps the two one-to-one, so a morning off in Factorial also frees the first half of the shift in Quinyx.
- Factorial gives hourly leave as a number of hours in hundredths. Quinyx wants a percentage of the shift for a partial absence. KoppelHet converts the hours to that percentage, based on that day's scheduled shift.
- Leave in Factorial can have no end date, for example for long-term sickness. Quinyx wants a start and an end for an absence. KoppelHet books such leave up to a fixed number of weeks ahead and extends it every night until Factorial gives an end date.
- In Factorial a leave type can count as worked time, such as a training day. That is not an absence in the schedule. KoppelHet only includes leave types that do not count as worked time, and agrees the exceptions with planning at the start.
- A webhook in Factorial only sees what the token that created it may see. With a user token the integration therefore misses leave of colleagues outside that user's reach. KoppelHet creates the subscriptions with a company token, so all leave of the entity comes in.
- Factorial disables a webhook subscription after twenty failed attempts or 48 hours, and reports this by email. Quinyx still has to be right in the meantime. KoppelHet therefore also requests deleted leave every day and compares it with the absences in Quinyx, so a missed notification does not block a shift.
- Quinyx only supports creating and deleting absences, while Factorial can update a leave. For an updated leave KoppelHet deletes the old absence, giving the shifts back, and books the new period.
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 contract hours go to Quinyx too?
Not in the smallest setup. Contract hours as an agreement in Quinyx can be added later as an extension.
Do worked hours go back to Factorial?
Not in this integration. A flow of hours for 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.
- Factorial through the Factorial API (version 2026-10-01 in the path) with OAuth 2.0 and a company token. Webhooks employees/employee/create_with_contract, employees/employee/update, employees/employee/terminate, timeoff/leave/approve, timeoff/leave/update, timeoff/leave/delete and timeoff/leave/bulk_delete (up to 20 attempts in 48 hours). Leave through GET /resources/timeoff/leaves (approved, include_deleted_leaves, type_is_workable, from and to; fields half_day, hours_amount_in_cents, start_on, finish_on, deleted_at).
- Quinyx through the Employees API v3 (POST /hr/v3/employees with badgeNumber and employment with homeGroupId and employmentStartDate) and /hr/v3/role-assignments. Absence through POST /v2/schedule/groups/{groupId}/absences and /absences/part-time (absenceRate, absenceRateDirection FROM_START or FROM_END), DELETE with reassignBackShifts.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Factorial | Field in Quinyx | Notes |
|---|---|---|
company_identifier | badgeNumber | Fixed key; the identifier field is the national ID number and stays out of the integration |
first_name, last_name | personalInformation.firstName, lastName | |
email | email | |
location_id (werkplek) | employment.homeGroupId | Through a table from workplaces to Quinyx units |
contract starts_on | employmentStartDate en role-assignment startDate | |
terminated_on | role-assignment endDate | |
Leave (approved true), leave_type_id | Absence, absenceTypeId | |
half_day (beginning_of_day of end_of_day) | Part-time absence, absenceRateDirection FROM_START of FROM_END | |
hours_amount_in_cents | Part-time absence, absenceRate |
Related
Factorial → 4PS Construct
Factorial to 4PS Construct integration: fitters and site managers with their cost centre as a dimension in 4PS
Factorial → Active Directory
Factorial to Active Directory integration: domain accounts from Factorial
Factorial → ADP iHCM
Factorial to ADP iHCM integration: contract versions and terminations of the Dutch entity to ADP
Factorial → AFAS Profit
Factorial to AFAS integration: employees and contracts from Factorial in AFAS Profit Payroll