What we take care of

Payroll integration with multiple employers and employments

With several Dutch entities, the entity or company in the HR system, such as Workday, SuccessFactors or Deel, decides which Nmbrs company or which Loket or AFAS employer an employee lands in. A move between two entities becomes a termination at one employer and a hire at the other, on the same date.

Last updated: 9 November 2026

Discuss your integration All about Payroll integration

What it is

A group often has more than one Dutch entity, each with its own employer in payroll. In the HR system that is sometimes one field, and a move between entities an ordinary change on the same employee.

For payroll these are two employers, each with its own payroll tax return. Translate that badly and someone is paid by the wrong entity, or a returning former employee becomes a duplicate person.

How the integration handles it

For each entity in the HR system we record which Nmbrs company or which Loket or AFAS employer it belongs to, not based on country or workplace.
A move between entities becomes a termination at the old and a hire at the new company, on the same date.
Two employments with the same employer become two contracts under one employee. With two entities it becomes one employee per employer.
A rehire is recognised by the fixed key from the HR system, so a new employment is added to the existing person rather than a second person.
For the initial load KoppelHet compares all Dutch employees with payroll and matches existing employees on BSN, before daily changes are processed.

Edge cases we handle

Workday sometimes shows an employee with two jobs as two positions. We agree beforehand whether that becomes one or two employments.
If an organisation in Sympa has two entities, KoppelHet distributes the employees over the right companies in Nmbrs.
Someone working in the Netherlands on a temporary assignment appears in SuccessFactors as a global assignment. By default it does not go to payroll; we agree it per situation.
YouForce no longer returns terminations from long ago. The check therefore also compares active contracts in payroll with YouForce.

What KoppelHet does

Multiple entities is one of the reasons a payroll integration becomes custom work. KoppelHet records the split over employers on the platform, tests a move and a rehire before go-live, and reports an employee who fits no entity instead of guessing.

Common integrations

SAP SuccessFactors → Nmbrs

SuccessFactors to Nmbrs integration: HR changes straight into payroll

Workday → Loket

Workday to Loket integration: Workday changes straight into payroll

Deel → Nmbrs

Connect Deel to Nmbrs: payroll for your own Dutch BV next to EOR

SAP HCM → Nmbrs

SAP HCM to Nmbrs integration: SAP HR data to Dutch payroll

Sympa → Nmbrs

Sympa to Nmbrs integration: HR changes from Sympa to Dutch payroll

UKG Pro → AFAS Profit

UKG Pro to AFAS integration: Dutch employees of a US head office in AFAS Profit

Remote → Nmbrs

Remote to Nmbrs integration: your own Dutch employees from Remote HR into payroll

Customer case

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.

Read the customer story

Frequently asked questions

How does the integration know which entity someone belongs to?

From the entity, company or division in the HR system. For each value we record which payroll company or employer belongs to it.

What happens when someone changes entity?

Then KoppelHet closes the employment at the old employer and opens a new one at the other, on the same date.

Is a duplicate person created when a former employee returns?

No. KoppelHet first looks up the fixed key from the HR system and then starts a new employment for the existing person.