Payroll integration
Personio to Nmbrs integration: salaries and allowances per period into payroll
With an integration between Personio and Nmbrs, new Dutch employees and contract changes from Personio reach Nmbrs automatically, with schedule, salary and bank account. Each month's salaries, allowances and bonuses go to the right Nmbrs period by themselves, so the payroll bureau no longer retypes a monthly export.
What the integration does
Anyone who runs HR in Personio and has Dutch payroll run in Nmbrs, often through a payroll bureau, exports new people, changes and bonuses at the end of the month. The bureau enters that into Nmbrs by hand, and whatever changes after the export misses the payroll run.
- HR enters a new employee or change in Personio.
- KoppelHet checks whether the employee belongs to the Dutch entity and creates or updates them in Nmbrs.
- Before the payroll run KoppelHet fetches that month's salaries, allowances and bonuses.
- Fixed salary becomes the Nmbrs salary, recurring allowances fixed wage components, and one-off payments and bonuses variable wage components in that period.
- An end date in Personio sets the end date in Nmbrs. The payroll bureau sees notifications and differences in the KoppelHet platform.
What to watch for with Personio and Nmbrs
- Personio divides pay into fixed salary, hourly wage, recurring allowances, one-off payments and bonuses. That split matches the Nmbrs distinction between salary, fixed and variable wage components.
- Personio releases pay data per month. KoppelHet therefore requests it per Nmbrs period, and fetches a correction for an earlier month separately.
- Personio only reports that an employee changed, not what. KoppelHet compares the new state with Nmbrs and only writes what actually differs.
- Personio only reports a starting employee at midnight on the start date. For Nmbrs that is too late for the first period, so KoppelHet puts the employee in Nmbrs as soon as the contract is in Personio.
- BSN and IBAN sit in custom fields in Personio. The integration can only read them once the administrator opens them up; otherwise the field stays empty in Nmbrs and a notification follows.
- Nmbrs retires its old integration method on 1 March 2027. KoppelHet therefore connects Personio to 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
Does this work with an external payroll bureau?
Yes. The bureau works in Nmbrs as usual, but receives changes and pay data automatically and sees differences in the KoppelHet platform.
What happens to a bonus entered after the payroll run?
It goes to the next open period in Nmbrs. We agree per customer whether payroll gets a notification first.
Are employees from other countries included?
No. KoppelHet only includes employees of the Dutch entity in Personio.
Who keeps track of which allowance maps to which wage component?
KoppelHet. When a new kind of allowance is added in Personio, we update the translation to Nmbrs.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Personio is read through webhooks (only person or employment id; employment.started fires at midnight UTC on the start date) and the Personio API v2. The compensations endpoint accepts a period of at most one month, with categories FIXED_SALARY, HOURLY_SALARY, RECURRING, ONE_TIME and BONUS_PAYOUT.
- BSN and IBAN come from custom attributes that must be released for API access. Schedule from weekly_working_hours; a YEARLY amount is divided to monthly.
- Nmbrs is written through the Nmbrs REST API. The SOAP API is retired from 1 March 2027.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Personio | Field in Nmbrs | Notes |
|---|---|---|
Persoon-id | Personeelsnummer of vrij veld | |
Voornaam en achternaam | Voornaam, tussenvoegsel, achternaam | |
Adres | Adres | |
Startdatum dienstverband | Datum in dienst | |
weekly_working_hours | Rooster (uren per week) | |
FIXED_SALARY (amount, interval) | Bruto maandsalaris | A YEARLY amount divided to monthly |
HOURLY_SALARY | Uurloon | |
RECURRING | Vaste looncomponent | One Nmbrs wage component per compensation type |
ONE_TIME en BONUS_PAYOUT | Variabele looncomponent | |
Einddatum dienstverband | Datum uit dienst |
Related
Ashby → Personio
Ashby to Personio integration: hires with hours and entity as new employees in Personio
Bullhorn → Personio
Bullhorn to Personio integration: placements as a person with employment in Personio
Carerix → Personio
Carerix to Personio integration: successful placement as a new employee in Personio
Greenhouse → Personio
Greenhouse to Personio integration: hired candidates as employees in Personio