Payroll integration
Rippling to Nmbrs integration: employees of the Dutch entity straight into payroll
With an integration between Rippling and Nmbrs, employees of your own Dutch entity move from Rippling into the right Nmbrs company automatically, with contract, hours and salary and the effective date from Rippling. Contractors stay out of Nmbrs, and a departure in Rippling sets the end date in Nmbrs.
What the integration does
Organisations that manage HR, devices and accounts in Rippling and process Dutch payroll in Nmbrs, often through an external payroll bureau, pass on new hires and pay rises by email without an integration. The bureau copies them from screenshots, and a contractor or a late pay rise only shows up when the payslip is wrong.
- HR hires someone at the Dutch entity in Rippling.
- KoppelHet picks up the new or changed worker and checks entity and employment type.
- The employee appears in that entity's Nmbrs company, with contract, schedule and salary.
- Payroll completes in Nmbrs what is not in Rippling, such as payroll tax credit and pension.
- A termination in Rippling sets the last working day as the end date in Nmbrs.
What to watch for with Rippling and Nmbrs
- Rippling records the legal entity per worker. Only workers of the Dutch entity go to Nmbrs, and with several Dutch entities that entity decides which Nmbrs company someone goes into.
- Rippling distinguishes employees and contractors. A contractor invoices and does not belong in payroll, so KoppelHet keeps them out of Nmbrs, even when they live in the Netherlands.
- Rippling has country fields for national numbers from the US and Canada among others, but not for the BSN. The BSN comes from a custom field in Rippling or is entered in Nmbrs; without a BSN KoppelHet does not create the employee but alerts HR.
- For hourly workers Rippling derives a monthly amount from a forty-hour week, and for salaried staff an hourly wage on the same basis. KoppelHet therefore takes the annual salary for salaried staff and the hourly wage for hourly staff, never the derived amount.
- Every amount in Rippling has its own currency. If a Dutch employee's salary is not in euro, KoppelHet does not pass it on but alerts payroll.
- A termination in Rippling has a type, including a declined or rescinded offer. If someone who is already in Nmbrs does not start after all, KoppelHet alerts payroll instead of sending a normal termination.
- Rippling releases breaking changes as a new dated API version. KoppelHet pins the version, so a change at Rippling does not alter the integration unnoticed.
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
Rippling also runs payroll in the Netherlands. Why Nmbrs?
Rippling does offer Dutch payroll. This integration is for organisations that keep Nmbrs, for example because a payroll bureau works in it or because payroll has run there for years.
Does the payslip come back to Rippling?
Not in this integration. That can follow later as an extension, if Rippling accepts documents through the API.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Rippling is read through the REST API (workers with expand on legal_entity, employment_type, compensation and department; filter on updated_at and status; termination_details with type and reason; custom_fields; country_fields), with a bearer token with only the required scopes and the Rippling-Api-Version header.
- Nmbrs calls the SOAP API deprecated (retiring in 2027) and wants new integrations on the REST API. The SOAP documentation includes Employee_InsertByEmployeeType, Contract_Insert, Salary_Update, Schedule_Update and Function_Update; the REST documentation only loads with JavaScript and has not been checked per operation.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Rippling | Field in Nmbrs | Notes |
|---|---|---|
number (worker) | Personeelsnummer | |
user (naam) | Voornaam en achternaam | |
legal_entity_id | Nmbrs-bedrijf (CompanyId) | Fixed mapping per entity; other entities are skipped |
start_date | Datum in dienst | |
title | Functie | |
department | Afdeling | |
compensation.annual_compensation | Bruto maandsalaris | Divided by twelve for salaried staff; hourly staff through hourly_wage |
custom_fields (BSN) | BSN | Rippling has no country field for the BSN |
end_date | Datum uit dienst |
Related
Carerix → Rippling
Carerix to Rippling integration: successful match as a hire for review in Rippling
Greenhouse → Rippling
Greenhouse to Rippling integration: every hire straight into Rippling for review
Recruitee → Rippling
Recruitee to Rippling integration: hired candidates ready to hire
Rippling → 4PS Construct
Rippling to 4PS Construct integration: own employees of the construction entity in 4PS, with department as a dimension