Payroll integration
Remote to Nmbrs integration: your own Dutch employees from Remote HR into payroll
With an integration between Remote and Nmbrs, employees employed by your own Dutch entity and managed in Remote reach the right Nmbrs company automatically. Staff employed through Remote as employer of record, contractors and employees whose payroll Remote runs itself stay out of Nmbrs, so nobody is paid twice.
What the integration does
Organisations that use Remote as the HR overview for everyone, including those employed by their own Dutch entity, and run that entity's payroll in Nmbrs copy new employees by hand without an integration. For every new name payroll has to find out whether someone works for the own entity, through Remote as employer or as a contractor.
- HR records an employee of your own Dutch entity in Remote.
- Remote reports the change; KoppelHet fetches the full employment and checks type and entity.
- The employee then appears in that entity's Nmbrs company, with start date, job and department.
- Payroll completes salary, schedule and tax data in Nmbrs.
- When the employment ends in Remote, KoppelHet sets the end date in Nmbrs.
What to watch for with Remote and Nmbrs
- Remote has four employment types - through Remote as employer of record, contractor, own employee, and employee of your own entity whose payroll Remote runs. Only the own employees of the Dutch entity belong in Nmbrs; KoppelHet filters on that.
- For own employees an integration can only read in Remote, not write. The Nmbrs employee number therefore does not go back to Remote; KoppelHet keeps track itself of which employment belongs to which Nmbrs employee.
- Remote recommends one full list as a start and then notifications per change, not a round past every employee. KoppelHet works that way, with a full comparison before the payroll run as a safety net for a missed notification.
- Remote's list is limited to name, job, status and type. Address and contract details differ per country and are only in the full employment; KoppelHet only fetches that for an employee who has changed.
- The entity that engaged an employment in Remote decides the Nmbrs company. An employee of a foreign entity does not go to Nmbrs, even when living in the Netherlands.
- When someone moves from Remote as employer to the own entity, Remote shows a new employment of a different type. KoppelHet creates a new hire in Nmbrs with the new start date; the period through Remote does not count in Nmbrs.
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
What happens to our staff employed through Remote?
They stay with Remote. Remote is their employer and pays them; Nmbrs only receives the employees of your own entity.
Why is the salary not in Nmbrs automatically?
We see no salary for own employees in Remote's documentation. Payroll therefore records it in Nmbrs; if it is in Remote for you, we include it.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Remote through the Remote API (GET /v1/employments filtered on employment_type=direct_employee for the initial load, GET /v1/employments/{employment_id} for the full employment) and webhooks through POST /v1/webhook-callbacks (including employment.updated and employment.details.updated). For direct_employee only List and Show employment are available.
- 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 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 Remote | Field in Nmbrs | Notes |
|---|---|---|
id (employment) | Vrij veld in Nmbrs | To find the employment again later |
full_name | Voornaam en achternaam | Split, checked by payroll |
type | Filter | Only direct_employee goes to Nmbrs |
engaged_by_legal_entity_id | Nmbrs-bedrijf | Fixed mapping per entity |
provisional_start_date | Datum in dienst | |
job_title | Functie | |
department | Afdeling | |
work_email | Zakelijk e-mailadres | |
termination_date | Datum uit dienst |
Related
Greenhouse → Remote
Greenhouse to Remote integration: foreign hires as EOR employment with the country's form
Recruitee → Remote
Recruitee to Remote integration: hires abroad straight into an employment at Remote
Remote → 4PS Construct
Remote to 4PS Construct integration: own employees of the construction entity from Remote in 4PS
Remote → Active Directory
Remote to Active Directory integration: accounts for colleagues in other countries