Leave, absence and time
Quinyx to YouForce integration: hours and allowances as pay components, employments and leave back
With an integration between Quinyx and Visma Raet YouForce, approved hours, overtime and allowances from Quinyx go to YouForce per employment as pay components, ready for payroll. The other way round, employments, planned contract changes, approved leave and sickness reports from YouForce reach Quinyx, so planning does not schedule anyone who is absent or has fewer hours.
What the integration does
Organisations that plan teams in Quinyx and process payroll in Visma Raet YouForce transfer worked hours and allowances monthly through an export that payroll processes by hand. A sickness report or leave in YouForce only reaches the planner when someone calls, and contract changes sometimes appear in Quinyx weeks later.
- HR records an employment or contract change in YouForce, even if it takes effect later. KoppelHet sets the employee and the agreement in Quinyx.
- Approved leave and sickness reports from YouForce appear as absence in the Quinyx schedule.
- Employees record their time in Quinyx and the team lead approves it. Quinyx calculates overtime and allowances.
- After the transfer to payroll, KoppelHet sends the hours per employment and pay component to YouForce.
- KoppelHet checks whether YouForce processed every submission and reports rejected lines in the platform.
Back: Employments and planned contract changes · Approved leave as absence · Sickness and recovery reports
What to watch for with Quinyx and Visma Raet YouForce
- YouForce accepts pay components per employment, not per employee. Someone who works on two agreements in Quinyx, for example a permanent contract and an on-call contract, gets the hours in YouForce on the employment on which they were worked.
- A submission to YouForce is queued first and processed later. KoppelHet requests the status per submission and shows a rejected line before the payroll run starts, instead of it only showing up on the payslip.
- Quinyx gives hours per cost centre, but a YouForce pay component only carries a code, a value and an effective date through this route. If hours must be charged to a cost centre other than the usual one, we handle that with a separate pay component per cost centre or in the YouForce cost allocation.
- Leave cannot reach YouForce as a leave entry through the API; YouForce only accepts pay components that way. Leave is therefore requested and approved in YouForce, and KoppelHet puts it in Quinyx as absence.
- Quinyx rejects a backdated sickness report over a period that has already been transferred to payroll in Quinyx. KoppelHet reports that to the planner, who reverses the transfer in Quinyx or handles the correction in YouForce directly.
- A change of hours that starts next month is in YouForce as a planned change. KoppelHet sets it in Quinyx with the right start date, so planning already sees the new contract when building the schedule for that month.
- Quinyx creates its own salary type for every allowance percentage; YouForce has its own pay components for those. Payroll manages the translation table, and a salary type without a pay component is not lost unnoticed.
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
Can employees request leave in the Quinyx app?
They can, but then the leave is not in YouForce, because YouForce does not accept leave entries through the API. We recommend requesting leave in YouForce; the planner then sees it in Quinyx.
What happens to hours corrected after closing?
The correction goes along in the next period, with that period's effective date. That way a closed payroll run in YouForce is left alone.
Do leave balances go to Quinyx too?
That can be added later as an extension. YouForce supplies leave entitlements and hours taken; which balance employees should see in Quinyx is then agreed per leave type.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Quinyx is read through wsdlGetPayrollV2 (salType, hours, costCentre, badgeNo) after a transfer with wsdlInitiateTransferToPayroll. Absence goes to Quinyx through the v2 Absences API (POST /v2/schedule/groups/{groupId}/absences); a period already transferred to payroll returns SALARY_PERIOD_LOCKED or SHIFT_ALREADY_TRANSFERRED_TO_PAYROLL.
- YouForce is written through the WFM API, POST /v1.0/PayComponents/{employment} with elementCode, value and effectiveDate per line (scope Youforce-WFM:Write_Basic). The status follows per ticket through /v1.0/payComponents/{TicketId}/status.
- YouForce is read through the WFM API (employments, employments/plannedChanges, leavePeriods, leaveHours and sickleaves) on latestSync, with OAuth 2.0 client credentials through Visma Connect.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Quinyx | Field in Visma Raet YouForce | Notes |
|---|---|---|
badgeNo | personCode | The YouForce person code is the badge number in Quinyx |
extAgreementId | employmentCode | Each employment its own agreement |
salType | elementCode | Through a translation table from salary types to pay components |
hours (opgeteld per periode) | value | |
Eerste dag van de salarisperiode | effectiveDate | |
Agreement fromDate | plannedChanges (ingangsdatum) | Planned changes become future agreements or dated entries |
Absence (absenceTypeId) | leavePeriods en sickleaves | One Quinyx absence type per leave and sickness type |
Related
ADP iHCM → Quinyx
ADP iHCM to Quinyx integration: employees and contract hours from ADP in scheduling, hours per pay period back to ADP
ADP Workforce Now → Quinyx
ADP Workforce Now to Quinyx integration: employees with agreements, positions and leave in hours in scheduling
BambooHR → Quinyx
BambooHR to Quinyx integration: employees, approved time off and balances from BambooHR in the schedule
Dayforce → Quinyx
Dayforce to Quinyx integration: employees, weekly hours and approved time away from work from Dayforce in scheduling