Greenhouse logoNmbrs logo

Recruitment to HR

Greenhouse to Nmbrs integration: new hires from Greenhouse ready for the Dutch payroll run

With an integration between Greenhouse and Nmbrs, a candidate with an accepted offer in Greenhouse arrives as an employee in the right Nmbrs company, with employment, schedule and salary from the offer. The payroll bureau or payroll team only completes the Dutch payroll details, and an annual salary in dollars never ends up in Nmbrs as a monthly wage by mistake.

What the integration does

Employers that recruit through Greenhouse and have a payroll bureau run their Dutch entity in Nmbrs pass new employees on by email. Amounts then go wrong, such as an annual salary from the offer entered as a monthly salary.

  1. The recruiter marks the offer as accepted in Greenhouse.
  2. KoppelHet receives the hire with candidate, vacancy and offer.
  3. The vacancy's office determines the Nmbrs company; KoppelHet skips candidates for other countries.
  4. KoppelHet creates the employee and then employment, contract, schedule and salary, in that order.
  5. The payroll bureau adds BSN, collective agreement, payroll tax credit and pension in Nmbrs.
Greenhouse → KoppelHet → NmbrsSOURCEGreenhouseTARGETNmbrsKoppelHetmapping · logging · monitoringGreenhouse → KoppelHet → NmbrsSOURCEGreenhouseTARGETNmbrsKoppelHetmapping · logging · monitoring
Out: Employee with name, address and contact details · Nmbrs company from the vacancy's office · Employment and contract with start date · Schedule and salary from the offer · Department and job

What to watch for with Greenhouse and Nmbrs

  • The Greenhouse offer contains the salary with currency and unit. KoppelHet passes a monthly or hourly amount in euros straight through, and holds an annual amount or an amount in another currency with a notification, so the payroll bureau does not pay the wrong amount.
  • In Nmbrs the employee and then employment, contract, schedule and salary arrive in separate steps. If a later step fails, KoppelHet repeats only that step after correction, so no employee without a schedule ends up in the run.
  • Each BV belongs to its own company in Nmbrs, and Greenhouse has no BV but does have offices. Per office we record which Nmbrs company belongs to it; an office without a Nmbrs company falls outside the integration.
  • Departments and jobs exist per company in Nmbrs. If the Greenhouse department does not exist there, KoppelHet reports it, instead of creating a department in payroll itself.
  • Whoever grants consent in Nmbrs decides which companies the integration can access. A new BV must therefore also be opened up for the integration before Greenhouse hires can land there.
  • Greenhouse limits the number of requests per ten seconds. After a recruitment round with many hires at once, KoppelHet spreads the fetching, so every hire reaches Nmbrs.
  • Greenhouse retired its old API versions on 31 August 2026. This integration uses the new version with its own credentials and only the rights it needs.

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, architecture and compliance

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.

Price indication · Basic

Leave your work email and you see the price indication right away.

We only use your address to follow up on your question about this integration.

Frequently asked questions

What does our payroll bureau notice of the integration?

New employees are in Nmbrs with start date, schedule and salary. The bureau adds the Dutch details and runs payroll as usual.

What if the salary in the offer is an annual amount?

Then KoppelHet holds the salary and HR gets a notification, or we convert according to a fixed agreement on holiday pay. You choose at the start.

Does this work with several BVs?

Yes. Per Greenhouse office we record which Nmbrs company it belongs to.

What can be traced afterwards for an audit?

Every action of the integration is recorded in the audit logging of the KoppelHet platform. KoppelHet works with an ISO 27001 certified management system.

Technical details for IT

For those who want to know how it works under the hood: APIs, fields and sources used.

  • Greenhouse is read through the hire_candidate webhook (on Accept Offer, with application, candidate, job and offer with starts_at and custom fields; HMAC-SHA256 in the Signature header) and the Harvest API v3 with OAuth 2.0 client credentials and scopes. Rate limit per ten seconds (X-RateLimit-Limit), 429 with Retry-After.
  • Nmbrs is written through the Nmbrs REST API with OAuth; first the employee per company (the response contains the employee ID), then address, employment, contract, schedule, salary, department and job. 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 GreenhouseField in NmbrsNotes
candidate.idVrij veld bij de medewerkerTo recognise a second notification
candidate.first_name en last_nameVoornaam, tussenvoegsel en achternaam
candidate.addressesAdres
candidate.email_addresses en phone_numbersPrivé e-mail en telefoon
job.officesNmbrs-bedrijfThrough a lookup per office
offer.starts_atDatum in dienst en begindatum contract
Uren per week (offer custom field)Rooster
Salaris (offer custom field met valuta, bedrag en eenheid)Bruto maandsalaris of uurloon
job.departmentsAfdelingMust exist in the Nmbrs company

Related

Which systems do you want to connect?

Tell us which systems you use and what should happen automatically. Together we define the smallest working solution, with a clear design and a quote before building.