ShLeave, absence and time
Nmbrs to Shiftbase integration: staff and contracts to the schedule, hours back on the right hour code
With an integration between Nmbrs and Shiftbase, new hires, contracts and departments from Nmbrs reach Shiftbase by themselves, and approved hours, surcharges, kilometres and meals go back to Nmbrs for the payroll run. KoppelHet keeps several Nmbrs companies with overlapping employee numbers apart, keeps leave balances aligned in both systems and sends the full state again on a correction.
What the integration does
Anyone who has payroll run in Nmbrs, with one Nmbrs company per entity, and schedules in Shiftbase gets stuck as soon as a second entity with the same employee numbers is added. Employees also sometimes see a different leave balance in Shiftbase than on their payslip, and a corrected period that is sent again can overwrite the first delivery in Nmbrs.
- Payroll creates the employee in the right Nmbrs company, with contract and department.
- KoppelHet puts the employee into Shiftbase in the site's team, with the contract type and hours from Nmbrs.
- After approval in Shiftbase the hours go to Nmbrs per hour code, and kilometres and meals as wage components.
- If a period is corrected after sending, KoppelHet sends the full state of those employees again, so the replacement in Nmbrs is right.
- Leave balances are compared between Nmbrs and Shiftbase; a difference goes to the place we agreed as leading.
Back: Approved hours per hour code · Kilometres and meals · Vacation hours to pay out
What to watch for with Nmbrs and Shiftbase
- Shiftbase requires employee numbers to be unique across the whole account. Two Nmbrs companies that both start at 1 would overwrite each other. KoppelHet builds the key from company and employee number, so payroll does not have to renumber in Nmbrs.
- When the same period reaches Nmbrs twice, the second delivery replaces the first for those employees, instead of adding to it. A correction must therefore contain the period's full hours. KoppelHet always sends the whole state on a correction, not just the difference.
- If the payslip shows the balance from Nmbrs and the app the one from Shiftbase, they drift apart. KoppelHet agrees per customer which system leads and keeps the other aligned.
- Nmbrs has two hour models and two wage models, and a company can use both. An hour type in Shiftbase linked to an empty component in the wrong model does not reach the payroll run. KoppelHet records per Nmbrs company which model applies and flags hours without an hour code.
- Shiftbase can add hours for hourly workers to their worked hours, so they count in Nmbrs as a surcharge on the hourly wage. For a permanent employee the same hour type goes separately. KoppelHet checks per contract type that a surcharge hour is not also paid as a worked hour.
- If absence counts as a worked day for social insurance, that can lead to wrong social insurance days for long-term sick employees in Nmbrs. KoppelHet decides per absence type whether it counts as a social insurance day.
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
Does this also work for an accounting firm with many clients in Nmbrs?
Yes. Per client we link the right Nmbrs companies to that client's Shiftbase account, with a separate key per company.
What happens to hours without an hour code in Nmbrs?
They are held back and appear as an alert in the platform. Payroll links an hour code, after which the next round delivers the hours.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Nmbrs through the REST API with OAuth 2.0. Employees, employments, contracts, schedules and departments are read per company; hours go as variable hours on one of the company's hour codes, allowances as a variable wage component. The SOAP API is retired from 1 March 2027.
- Shiftbase through the Shiftbase API with an API token for the Public API, for employees, contracts, teams, approved timesheets and absence.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Nmbrs | Field in Shiftbase | Notes |
|---|---|---|
Nmbrs-bedrijf + personeelsnummer | Personeelsnummer (Shiftbase) | Made unique across all companies |
Contracttype (Nmbrs) | Contracttype (uurloner of vaste uren) | Through a mapping table |
Afdeling of kostenplaats (Nmbrs) | Team | |
Rooster (Nmbrs) | Contracturen per week | |
Uursoort (Shiftbase) | Uurcode (Nmbrs) | Hour model 1 or 2, agreed per company |
Kilometers en maaltijden (Shiftbase) | Looncode (Nmbrs) | |
Team (Shiftbase) | Kostenplaats op de uren (Nmbrs) |
Related
ADP Workforce Now → Nmbrs
ADP Workforce Now to Nmbrs integration: the Dutch payroll group from ADP in the right Nmbrs company
AlexisHR → Nmbrs
AlexisHR (Simployer One) to Nmbrs integration: Dutch employees into payroll
BambooHR → Nmbrs
BambooHR to Nmbrs integration: Dutch payroll next to a global HR system
Bullhorn → Nmbrs
Bullhorn to Nmbrs integration: placements with hourly pay and end date in payroll