Payroll integration
HiBob to Nmbrs integration: changes from Bob ready for the payroll run
With an integration between HiBob and Nmbrs, new Dutch employees, contracts, salaries and leavers from HiBob reach Nmbrs automatically, with the effective date HR chose in Bob. The payroll team or external bureau no longer gets a monthly change list and retypes nothing.
What the integration does
International employers with HiBob for HR in every country and Nmbrs for Dutch salaries often have Bob managed by an HR team in another country. Dutch payroll then receives a monthly list of changes, enters it in Nmbrs and calls back when a start date or salary is unclear.
- HR in another country enters a new Dutch colleague in HiBob, or a new contract or salary.
- KoppelHet picks up the change shortly afterwards and checks whether it belongs to the Dutch entity.
- A new employee then appears in Nmbrs with address, bank account, contract and schedule.
- A new salary arrives in Nmbrs as a salary change with the effective date from HiBob.
- A departure in HiBob sets the end date in Nmbrs. Before the payroll run the payroll team sees all differences between both systems in the platform.
What to watch for with HiBob and Nmbrs
- HiBob reports exactly which history entry changed. KoppelHet fetches that one entry, so Nmbrs gets the right effective date and not only the latest state.
- In HiBob only one entry per part can be effective at a time. If HR enters two salary entries in the same month, KoppelHet takes the entry effective on the Nmbrs period date.
- If something is missing in Nmbrs, with HiBob it is almost always down to the integration's permissions. It gets access per category, and for salaries also to the history.
- If the organisation has more Dutch entities, the entity in HiBob decides which Nmbrs company the employee goes to.
- HiBob has no payroll tax credit, no Dutch pension scheme and no BSN field. Nmbrs keeps that data itself, or HR records it in a custom HiBob table visible only for the Netherlands.
- Nmbrs retires its old integration method on 1 March 2027. New integrations with Nmbrs use the new one straight away.
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
How soon is a change from HiBob in Nmbrs?
Shortly after the change. Only a departure is reported by HiBob on the day itself; that is why the check before the payroll run also reads planned leaving dates in advance.
Does this work with an external payroll bureau?
Yes. The bureau gives KoppelHet access to the customer's Nmbrs company and sees the notifications in the KoppelHet platform.
What if the salary in HiBob is in dollars?
For Dutch employees the salary should be in euros. If it is not, payroll gets a notification instead of a converted amount.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- HiBob is read through employee data webhooks, which for historical tables (work, employment, salary, lifecycle) pass the entry key, such as the effectiveDate. KoppelHet then fetches that entry through the HiBob API.
- The service user has permissions per category; for salary history also the view-history permission.
- Nmbrs is written through the Nmbrs REST API with OAuth 2.0. The SOAP API is no longer supported from 1 March 2027.
- The key between both systems is root.id from HiBob.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in HiBob | Field in Nmbrs | Notes |
|---|---|---|
root.id | Personeelsnummer of vrij veld | |
root.firstName en achternaam | Voornaam, tussenvoegsel, achternaam | |
Geboortedatum | Geboortedatum | |
Adres (home address) | Adres | |
work.startDate | Datum in dienst | |
work.department | Afdeling | Through a lookup to Nmbrs departments |
Uren per week (employment-tabel) | Rooster | |
Salaris en valuta (salary-tabel) | Bruto maandsalaris | Convert an annual amount to the monthly amount in euros |
Bankrekening | Bankrekening (IBAN) | |
Vertrekdatum | Datum uit dienst |
Related
Ashby → HiBob
Ashby to HiBob integration: a hire from Ashby straight in as an employee in Bob
Bullhorn → HiBob
Bullhorn to HiBob integration: an approved placement as a new employee in Bob
Carerix → HiBob
Carerix to HiBob integration: successful match becomes a new employee in Bob
Greenhouse → HiBob
Greenhouse to HiBob integration: from a hire in Greenhouse to a new employee in Bob