Leave, absence and time
Quinyx to Nmbrs integration: worked hours per hour code in the payroll period, schedules and leave back
With an integration between Quinyx and Nmbrs, approved hours, overtime and allowances from Quinyx arrive as variable hours on the right hour code and cost centre in the current Nmbrs payroll period. New employees, schedules and the leave balance from Nmbrs go back to Quinyx, so scheduling and payroll work from the same data.
What the integration does
Employers that plan in Quinyx and run payroll in Nmbrs, with a separate company per legal entity, enter the hours per company in Nmbrs every month. Someone who works at two locations then sometimes ends up at the wrong company, and hours on another cost centre disappear into the totals.
- HR records a new employee with a schedule at the right company in Nmbrs. KoppelHet creates the employee and the agreement in Quinyx.
- Employees clock in Quinyx and request leave there. Managers approve time and leave.
- After the transfer to payroll, KoppelHet retrieves the hours per employee, salary type and cost centre.
- The hours appear as variable hours in the current period of the right company in Nmbrs, on the hour code that belongs to the salary type and with the cost centre from Quinyx.
- Approved leave goes to Nmbrs as leave; the balance per leave type comes back to Quinyx.
Back: New employees and leavers · Schedule with hours per week · Leave balance per leave type
What to watch for with Quinyx and Nmbrs
- Nmbrs books variable hours in a company's period. Nmbrs only accepts a period the company has already passed if the submission is explicitly sent in unprotected mode; otherwise Nmbrs returns an error. KoppelHet therefore books late corrections from Quinyx in the current period by default.
- In Nmbrs hours are multiplied by the hourly wage through an hour code; fixed amounts go through wage components. Quinyx delivers allowances as hours per salary type, so they go to an hour code, and only allowances that Quinyx calculates as an amount go to a wage component.
- An hour line in Nmbrs has its own cost centre and cost unit. If someone works a shift at another location, those hours are also on that location's cost centre in Nmbrs, as Quinyx recorded them.
- One Nmbrs environment can contain several companies, while Quinyx thinks in stores or sites. KoppelHet records per Quinyx unit which Nmbrs company the hours belong to, so an employee in a second entity does not get hours in the first.
- Nmbrs can clear all extra hours of a period at once. That also affects hours payroll entered by hand. KoppelHet does not use it and only updates the lines it booked from Quinyx itself.
- Nmbrs has four leave types per employee, with a status from requested to approved. Leave approved in Quinyx arrives in Nmbrs as approved straight away, on the type that belongs to the Quinyx absence type.
- The Nmbrs schedule is stored as hours per day over two weeks. Quinyx works with hours per week and a distribution over the days in the agreement. KoppelHet converts the two-week schedule, so an employee with an even and an odd week keeps the right contract hours.
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
What if the period in Nmbrs has already been closed?
Then KoppelHet books the hours in the current period and reports that in the platform. Only if payroll wants that do we book in an earlier period.
Does this also work with several companies in Nmbrs?
Yes. Per store or site in Quinyx we record which company the hours belong to. Employees employed by two companies get the hours at the company of the unit where they worked.
Do fixed wage components go along too?
No. Fixed wage components such as salary and fixed allowances stay in Nmbrs. Quinyx only supplies what varies per period.
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; approvedSalaryStatus) after wsdlInitiateTransferToPayroll. The Nmbrs company per unit is recorded in the Quinyx Mapping API (mappingType EXTERNAL_COMPANY_CODE) or in our own table.
- Nmbrs is written with variable hours through HourComponentVar_Insert (EmployeeId, HourCode, Hours, CostCenterId, CostUnitId, Period, Year, UnprotectedMode) in the SOAP EmployeeService, or through the REST endpoint for variable hours. HourComponentVar_Clear clears all extra hours of a period and is not used. Leave with Leave_Insert (Type1 to Type4, Status), balance with LeaveBalance_GetPerType. The SOAP API stops on 1 March 2027.
- Employees go to Quinyx through wsdlUpdateEmployees or the Employees API v3, agreements through wsdlUpdateAgreementsV2 and balances through wsdlUpdateTimeTrackers.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Quinyx | Field in Nmbrs | Notes |
|---|---|---|
badgeNo | Personeelsnummer | Per company; unique together with the company |
salType | HourCode | Through a translation table from salary types to hour codes |
hours | Hours | |
costCentre | CostCenterId | Through a translation table from Quinyx cost centres to Nmbrs cost centres |
Overdrachtsperiode (fromDate, toDate) | Period en Year | |
Unit of EXTERNAL_COMPANY_CODE | Bedrijf in Nmbrs | Determines which company the hours land in |
Absence (goedgekeurd) | Leave (Status Approved, Type) | One Nmbrs type per leave type |
Time tracker | LeaveBalance per 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