Payroll integration
Connect Deel to Nmbrs: payroll for your own Dutch BV next to EOR
With an integration between Deel and Nmbrs, the employees of your own Dutch BV move from Deel into the right Nmbrs company automatically, and a new employee or a departure is quickly ready for the payroll run. Contractors and employer of record (EOR) employees are left out, so nobody is paid twice.
What the integration does
Employers with contractors and EOR employees in Deel and, recently, a Dutch entity with its own staff in Nmbrs send the payroll bureau a list every month of who joined or left the entity. An EOR colleague who ends up on that list by mistake is only noticed when there are two payslips.
- HR adds a new employee in Deel or changes a contract at the Dutch BV.
- KoppelHet only fetches employees of your own BV; contractors and EOR employees never even enter the integration.
- The employee then appears in the Nmbrs company that belongs to that BV.
- What Deel does not hold, such as the Dutch tax data, the payroll bureau completes in Nmbrs.
- On a termination the last working day from Deel appears as the end date in Nmbrs.
What to watch for with Deel and Nmbrs
- KoppelHet only asks Deel for employees of your own entities. Contractors and EOR employees therefore never reach the integration, and cannot end up in Nmbrs by mistake.
- If the group has more than one Dutch BV, each has its own entity in Deel and its own company in Nmbrs. The integration picks the Nmbrs company based on that entity, not on country or workplace.
- A switch from EOR to your own BV is a new employment in Deel. For Nmbrs that is a new employee with its own start date; the EOR period belongs to Deel's payroll.
- KoppelHet only accepts notifications that verifiably come from Deel, and also compares the employees in Deel with Nmbrs at a fixed moment.
- If a payroll bureau runs the Nmbrs environment, the bureau only grants the integration access to your administration. The bureau's other clients stay out of sight.
- An international team rarely records BSN, payroll tax credit and pension scheme in Deel. That data stays in Nmbrs with the payroll bureau and the integration does not touch it.
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
Can Deel run the Dutch payroll itself?
Deel offers its own payroll and EOR. This integration is for organisations that deliberately run their own BV's payroll in Nmbrs, for example through a Dutch payroll bureau.
What if someone moves from EOR to our BV?
A new employee appears in Nmbrs from the new start date. The EOR contract ends at Deel.
Which data does the payroll bureau still enter itself?
The Dutch tax data and anything you do not record in Deel. Which data that is, we agree together at the start.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Deel is read through the Deel REST API (people list, filtered on hiring type hris_direct_employee, with employments and client_legal_entity) and through signed webhooks on contract events.
- Last working day from termination_last_day. The key is the Deel person id, in an employee number or free field in Nmbrs.
- Nmbrs is written through the Nmbrs REST API, which works per debtor.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Deel | Field in Nmbrs | Notes |
|---|---|---|
id (Deel person) | Personeelsnummer of vrij veld | Agreed at the start |
first_name en last_name | Voornaam, tussenvoegsel, achternaam | |
birth_date | Geboortedatum | |
country | Land (adres) | |
start_date (employment) | Datum in dienst | |
job_title | Functie | |
department | Afdeling | |
client_legal_entity | Nmbrs-bedrijf | Fixed table from legal entity to company |
termination_last_day | Datum uit dienst |
Related
Ashby → Deel
Ashby to Deel integration: hires at the own entity as direct employee in Deel
Bullhorn → Deel
Bullhorn to Deel integration: first placement as a direct employee with a contract in Deel
Carerix → Deel
Carerix to Deel integration: successful placement as a person or contract in Deel
Deel → 4PS Construct
Deel to 4PS Construct integration: own employees of the construction entity in 4PS, with department and cost centre as dimensions