Recruitment to HR
Workable to Nmbrs integration: hired candidates with employment and salary in Nmbrs
With an integration between Workable and Nmbrs, a candidate hired in Workable arrives as an employee in the Nmbrs company of the legal entity, with employment, schedule and an hourly wage or monthly salary according to the offer. Payroll or the payroll bureau only completes the Dutch payroll details.
What the integration does
Anyone recruiting through Workable with payroll processed in Nmbrs by a payroll bureau, with a BV per location or brand, sends the offer to the bureau after a hire. New hourly-paid employees therefore sometimes end up in Nmbrs as monthly employees.
- The recruiter moves the candidate with an accepted offer to the hired stage in Workable.
- KoppelHet fetches candidate, offer and legal entity.
- The legal entity determines the Nmbrs company. KoppelHet creates the employee, then employment, contract, schedule and salary.
- The salary becomes an hourly wage or monthly salary, depending on the frequency in the offer.
- The payroll bureau adds BSN, collective agreement, payroll tax credit and pension.
What to watch for with Workable and Nmbrs
- Workable has legal entities, Nmbrs a company per BV. Per entity we record the Nmbrs company, so a new employee does not fall under the BV of another location.
- The salary in a Workable offer has an amount, a frequency and a currency. Per hour becomes an hourly wage in Nmbrs, per month a gross monthly salary; KoppelHet holds an annual amount with a notification.
- In Nmbrs employee, employment, contract, schedule and salary arrive in separate steps. KoppelHet carries them out one after another and reports it if a later step fails, so nobody is in the run without a schedule.
- Workable sends the candidate as they are at the moment of sending. KoppelHet therefore first checks that the offer has the accepted status, so a candidate set to hired by mistake does not enter payroll.
- Whoever grants consent in Nmbrs decides which companies the integration can access. If a new BV is added, it must also be opened up for the integration.
- An integration key in Workable only gets the rights chosen when it is created. For this integration that is only reading candidates, offers and account data.
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 does our payroll bureau notice of the integration?
New employees are in Nmbrs with start date, schedule and the right pay type. The bureau adds the Dutch details.
Does this work with a BV per location?
Yes. Per legal entity in Workable we record which Nmbrs company the new employee belongs to.
What if the offer in Workable has no hours?
We then add an hours-per-week field to the offer or the candidate. Without hours KoppelHet creates no schedule and HR gets a notification.
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.
- Workable is read through a subscription on candidate_moved with stage_slug hired (HMAC-SHA256 in X-Workable-Signature) and the API (/candidates/:id, /candidates/:id/offer with document_variables and salary with amount, frequency and currency_iso, /legal_entities). Token with read scopes r_candidates, r_jobs and r_account.
- Nmbrs is written through the Nmbrs REST API with OAuth; first the employee per company, then address, employment, contract, schedule, salary and department. 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 Workable | Field in Nmbrs | Notes |
|---|---|---|
Kandidaat-ID | Vrij veld bij de medewerker | To recognise a second notification |
firstname en lastname | Voornaam, tussenvoegsel en achternaam | |
address | Adres | |
email en phone | Privé e-mail en telefoon | |
Juridische entiteit | Nmbrs-bedrijf | Through a lookup table |
Startdatum (document variable van het aanbod) | Datum in dienst en begindatum contract | |
Uren per week (document variable of eigen veld) | Rooster | |
Salaris (amount, frequency, currency_iso) | Uurloon of bruto maandsalaris | |
Afdeling van de vacature | Afdeling | Must exist in the Nmbrs company |
Related
Workable → ADP Workforce Now
Workable to ADP Workforce Now integration: from the Hired stage to an in-progress hire per ADP company
Workable → AFAS Profit
Workable to AFAS integration: a candidate in the hired stage starts onboarding in AFAS
Workable → BambooHR
Workable to BambooHR integration: hire with salary interval and later changes
Workable → Dayforce
Workable to Dayforce integration: hire from the Hired stage, validated first