BambooHR to Nmbrs integration: Dutch payroll next to a global HR system
With an integration between BambooHR and Nmbrs, the Dutch employees in BambooHR reach Nmbrs automatically, with contract, schedule, salary and bank account. New hires, pay changes and terminations reach payroll with their effective date, without anyone retyping them.
Written by Marcel van Beek, founder and integration specialistLast updated:
What the integration does
International organisations that use BambooHR as their HR system and run Dutch payroll in Nmbrs have contracts and salaries copied by hand. Changes made in BambooHR between two runs are then missed.
HR outside the Netherlands enters a new employee in BambooHR, with start date, location Netherlands, job and salary.
KoppelHet picks up the change straight away and keeps only the employees of the Dutch entity.
The employee then appears in the right Nmbrs company, with address, contract, schedule and bank account.
A pay change in BambooHR becomes a salary change in Nmbrs with the same effective date.
An end date in BambooHR reaches Nmbrs. If a change fails, payroll sees the reason in the KoppelHet platform.
Out: Employee with personal and address data · Job title, department and location · Pay rate and frequency · Employment type and termination date · Bank account for salary payment
What to watch for with BambooHR and Nmbrs
BambooHR flags an employee as changed whenever anything in the record changes, including data that does not matter for payroll. KoppelHet compares the data Nmbrs needs and only passes on real differences.
Instant notifications from BambooHR do not cover custom tables. When Dutch data such as the payroll tax credit sits in such a table, KoppelHet fetches it in the scheduled round.
BambooHR has no standard IBAN field. For Nmbrs we capture the bank account in an extra field in BambooHR, or payroll completes it in Nmbrs.
In BambooHR a salary can be an hourly, monthly or annual amount. KoppelHet converts it to the gross monthly salary for the contracted hours, as Nmbrs expects.
Nmbrs retires its old integration method on 1 March 2027. For new customers this integration already uses the new one, so no migration is needed later.
The integration looks into BambooHR with the rights of one user. We ask for a separate user who only sees the data Nmbrs needs.
If the group has more than one Dutch entity, the division or location in BambooHR decides which Nmbrs company the employee goes to.
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.
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.
Price indication · Complex
€ 0.000 – € 00.000
€ 000 per month
Customer case
How it runs at Evondos Group
How these organisations use the integration. The configuration differs for each customer.
Evondos Group
Health tech
Evondos uses BambooHR as the group HR system and Nmbrs for Dutch payroll. New hires and changes move from BambooHR to Nmbrs automatically, and the cost centre decides which Nmbrs company they land in.
Do employees from other countries go to Nmbrs too?
No. The integration filters on the Dutch entity. Employees from other countries stay out of Nmbrs.
Who fills in the payroll tax credit and pension?
We agree that per field. Often it stays in Nmbrs and the integration does not overwrite it. If HR wants to keep it in BambooHR, we add an extra field.
What if someone enters a retroactive change?
KoppelHet takes the change with its effective date, not just the latest state. Nmbrs receives the original date and settles the difference.
Can payslips go back to BambooHR?
It is possible as an extra flow, but it is not part of this integration by default. We look at it per customer.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
BambooHR is read through the REST API, with webhooks on changed fields and the changed table data endpoint (jobInfo, compensation, employmentStatus) on timestamp. Webhooks do not cover custom tables.
Salary from payRate and paidPer, converted to gross per month; BSN from nationalId; termination from terminationDate.
Nmbrs is written through the Nmbrs REST API with OAuth 2.0. The Nmbrs SOAP API is retired from 1 March 2027.
The BambooHR API key belongs to a user and carries that user's permissions; entity through division or location.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
Field in BambooHR
Field in Nmbrs
Notes
employeeNumber
Personeelsnummer
firstName, lastName
Voornaam, tussenvoegsel, achternaam
Dutch name prefixes are often part of lastName in BambooHR and are split out
nationalId
BSN
dateOfBirth
Geboortedatum
address1, zipcode, city, country
Adres
hireDate
Datum in dienst
payRate + paidPer
Bruto salaris per maand
An annual or hourly amount is converted to the monthly amount
Tell us which systems you use and what should happen automatically. Together we define the smallest working solution, with a clear design and a quote before building.