Leave, absence and time
Dayforce to Quinyx integration: employees, weekly hours and approved time away from work from Dayforce in scheduling
With an integration between Dayforce and Quinyx, every employee from Dayforce appears automatically in Quinyx, in the unit of their primary assignment and with an agreement based on normal weekly hours and FTE. Approved time away from work from Dayforce appears as an absence in the schedule, with full and half days, and cancelled leave disappears again.
What the integration does
Organisations that run HR and pay in Dayforce and build schedules in Quinyx add every new employee to Quinyx by hand. Leave a manager approves in Dayforce is not visible to the planner, so shifts remain for people who are off.
- HR records a hire or change in Dayforce, with location, normal weekly hours and FTE.
- KoppelHet looks up changed employees by change date and fetches their employment status and assignments.
- Quinyx receives the employee in the unit of the primary assignment, with an agreement and an extra role per other assignment.
- For each employee in Quinyx, KoppelHet fetches approved time away from work for the coming period and enters it as an absence in the schedule.
- KoppelHet removes cancelled leave from Quinyx, and the shifts go back to the employee.
What to watch for with Dayforce and Quinyx
- Dayforce only returns time away from work per employee, with a mandatory date range and a mandatory status. There is no list for all employees at once. KoppelHet therefore only requests leave for employees who are scheduled in Quinyx, over a fixed window ahead, keeping the number of requests limited.
- The statuses of time away from work are case-sensitive and the customer can change them in Dayforce. KoppelHet reads at the start which status values the environment uses, so approved and cancelled leave are recognised even when the names differ from the default.
- For leave Dayforce indicates whether it is a full or half day, with net hours and start and end time. Quinyx books a full absence or a partial one with a percentage of the shift. KoppelHet turns a half day into a partial absence and uses the start time to decide whether the start or the end of the shift is off.
- Dayforce omits a field when it has no value. Missing normal weekly hours do not mean zero. KoppelHet then leaves the agreement in Quinyx as it is and reports the employee, instead of setting someone to zero contract hours.
- Which fields the integration sees in Dayforce depends on the web service user's field-level access, per element and per parent item. If a right is missing, the field disappears without an error. KoppelHet checks at the start that location, weekly hours, FTE and leave really come back.
- An employee can have several assignments in Dayforce, one of them primary. Quinyx allows several roles at the same time. KoppelHet makes the primary location the home unit and adds an extra role for the other locations, so someone who works at two sites can be scheduled at both.
- Dayforce counts an employee as changed as soon as a record starts or ends, not only when it is edited. A transfer HR records weeks ahead therefore comes by again on the effective date. KoppelHet already creates the new role in Quinyx with that start date on the first notice, and checks on the effective date that it still holds.
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 clocked hours from Quinyx go back to Dayforce?
Not in this integration. That can be added later as an extension, if payroll in Dayforce needs the hours from Quinyx.
Why not right after approval?
Dayforce's guide publishes no notification on leave approval. KoppelHet therefore checks several times a day what has changed.
What if a leave reason has no absence type in Quinyx?
Then the leave is not entered and an alert appears in the platform. The table is extended and the next round enters it.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Dayforce through the RESTful Web Services. Changed employees through GET /V1/Employees with filterUpdatedStartDate and filterUpdatedEndDate (optionally filterUpdatedEntities), details per XRefCode with Expand=EmploymentStatuses,WorkAssignments (NormalWeeklyHours, PayType, PayClass, Location, IsPrimary, FTE, EffectiveStart, EffectiveEnd). Leave through GET /V1/Employees/{xRefCode}/TimeAwayFromWork with filterTAFWStartDate, filterTAFWEndDate and status (APPROVED, PENDING, CANCELED, DENIED, CANCELPENDING). Role feature RESTful Services > Employee with field-level access per element.
- To Quinyx through the Employees API v3 (POST /hr/v3/employees) and /hr/v3/role-assignments with a future startDate; agreements through wsdlUpdateAgreementsV2. Absence through the v2 Absences API, POST /v2/schedule/groups/{groupId}/absences or /absences/part-time (absenceRate, absenceRateDirection FROM_START or FROM_END); deletion with reassignBackShifts.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Dayforce | Field in Quinyx | Notes |
|---|---|---|
XRefCode | badgeNumber | |
FirstName en LastName | personalInformation.firstName, lastName | |
WorkAssignments.Location (IsPrimary) | employment.homeGroupId | Through a table of Dayforce locations to Quinyx units |
WorkAssignments.Location (overige) | Extra role-assignment | |
EmploymentStatuses.NormalWeeklyHours | Contracturen (agreement) | |
NormalWeeklyHours en WorkAssignments.FTE | fullEmploymentHrs (agreement) | Weekly hours divided by FTE |
PayType en PayClass | extTemplateId (agreement-sjabloon) | |
HireDate en TerminationDate | employmentStartDate en leaveDate | |
TimeAwayFromWork (status APPROVED, AllDay, HalfDay, NetHours) | Absence of part-time absence | Through a table of ReasonName to absence types |
Related
Ashby → Dayforce
Ashby to Dayforce integration: have Dayforce validate the hire first, then save it
Bullhorn → Dayforce
Bullhorn to Dayforce integration: first placement of an employee as an employee in Dayforce
Carerix → Dayforce
Carerix to Dayforce integration: successful placement as a validated new employee in Dayforce
Dayforce → 4PS Construct
Dayforce to 4PS Construct integration: technicians and site managers from Dayforce in 4PS, with cost centre and end date