Leave, absence and time
Quinyx to Loket integration: hours and allowances as variable payroll data per period, leave back
With an integration between Quinyx and Loket, approved hours, overtime and allowances from Quinyx arrive as variable payroll data per employment and cost centre in the right Loket payroll period. Leave taken goes to Loket too, and the leave balance Loket calculates comes back to Quinyx.
What the integration does
Organisations that plan shifts and temporary workers in Quinyx and pay their own employees through Loket convert a Quinyx file into pay components by hand every period. If a period in Quinyx does not match the payroll period in Loket, hours slip to the wrong payslip.
- Employees clock in Quinyx and managers approve the time. Quinyx calculates allowances and overtime.
- After the transfer to payroll, KoppelHet retrieves the hours over exactly the dates of the Loket period.
- Per employment and cost centre the hours appear as variable payroll data in Loket, on the pay component that belongs to the salary type.
- Leave taken from Quinyx arrives as a leave record on the employment in Loket.
- Loket calculates the leave balance; KoppelHet sets it back in Quinyx per leave type.
Back: Leave balance per leave type
What to watch for with Quinyx and Loket
- Loket runs payroll per month, per four weeks or per week, with a period number per year. Quinyx transfers to payroll by start and end date. KoppelHet retrieves the hours over exactly the dates of the Loket period, so with four-weekly payroll no day falls in the wrong period.
- Loket identifies a record by the combination of period, shift, payslip type, distribution unit, cost centre and cost unit. Hours that Quinyx records on two cost centres therefore become two records in Loket, and a second submission for the same cost centre updates the existing record.
- When importing, Loket asks whether existing values are overwritten, skipped or added up. For hours from Quinyx KoppelHet chooses overwrite, so a corrected transfer replaces the first one and the hours do not appear twice on the payslip.
- Loket recommends retrieving an employment's default values first, such as cost centre and shift, and adding the pay components to them. KoppelHet does that per employment, so hours from Quinyx do not land on an empty cost centre.
- Loket calculates leave entitlement with its own leave policies, for example by age, wage or years of service. KoppelHet does not recalculate that in Quinyx, but puts the balance Loket returns per leave type on the tracker in Quinyx.
- An employee with two employments has two separate employments in Loket, each with its own variable payroll data. In Quinyx each agreement points to one employment, so hours are paid on the right contract.
- Agency workers are in Quinyx, but not in Loket. Their hours do not go to Loket; KoppelHet skips them based on the Quinyx staff category and reports hours of unknown employees separately.
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
We run payroll every four weeks. Does that work with Quinyx?
Yes. KoppelHet takes the employer's periods in Loket as the starting point and retrieves the hours in Quinyx over exactly those dates.
Our payroll office works in Loket. Does it need to do anything?
The payroll office gives the integration access to the employer and confirms the translation table from salary types to pay components. After that the hours are ready every period without a file.
Do new employees also go from Loket to Quinyx?
That can be added later as an extension. We start with hours and leave, because that is where most of the manual work is.
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 (fromDate, toDate, salType, hours, costCentre, badgeNo) after wsdlInitiateTransferToPayroll with a unique extTransferId. Balances go to Quinyx through wsdlUpdateTimeTrackers.
- Loket is written through the Loket REST API (OAuth 2.0) with PATCH /v2/providers/employers/employees/employments/{employmentId}/payrollperioddata, or the collective variant per employer. The key is payrollPeriod, shift, payslipType, distributionUnit, costCenter and costUnit; payrollComponent, value and attribute are inserted or overwritten. Defaults through /defaults. With the CSV import, processingMethod chooses between overwrite, do not overwrite and add up.
- Leave goes to Loket through POST .../employments/{employmentId}/leave; balances come from GET .../employments/{employmentId}/leavebalances (yearly balance per leave type).
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Quinyx | Field in Loket | Notes |
|---|---|---|
badgeNo | Personeelsnummer werknemer | |
extAgreementId | employmentId | The Quinyx agreement points to the employment in Loket |
salType | payrollComponent | Through a translation table from salary types to pay components |
hours | value | |
costCentre | costCenter | Each cost centre becomes its own record |
Overdrachtsperiode (fromDate, toDate) | payrollPeriod (year, periodNumber) | Month, four weeks or week, per employer |
Absence (goedgekeurd) | Leave bij het dienstverband | |
Time tracker | leavebalances per verlofsoort |
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