Identity and access management
Nmbrs to Omada integration: payroll as the source for identities in Omada Identity
With an integration between Nmbrs and Omada Identity, Omada reads every employee from Nmbrs as an identity, with company, department, job, manager and a status that follows from the end date. KoppelHet converts the Nmbrs data into one record per employee that Omada's REST collector can read directly, without payroll data.
What the integration does
Organisations that run HR and payroll in Nmbrs and manage access with Omada have no ready-made connection between the two. Employees then reach Omada through an export that is set up for payroll rather than roles, and a departure is only picked up when someone runs the export again.
- Someone with an employer-level Nmbrs login gives the integration one-time consent to read employees and the company structure.
- KoppelHet fetches the employees per Nmbrs company with department, job and manager.
- KoppelHet offers one record per employee on its own secured address, with a key that is unique across all companies.
- Omada's REST collector reads that address as the authoritative source; Omada assigns roles on department and job.
- After the end date the status becomes inactive and Omada revokes access.
What to watch for with Nmbrs and Omada
- Employee numbers in Nmbrs are unique per company, while Omada requires a unique business key for every identity. KoppelHet builds the key from company code and employee number, so employee 1001 of two companies does not end up as one identity in Omada.
- Omada also maintains an identity's status itself and warns that a status from the HR source can overwrite it. We agree with you that a block by security in Omada stays in place, even if Nmbrs still shows the employee as active.
- Department and job in Nmbrs have a start period in payroll rather than a separate effective date. KoppelHet supplies the new value to Omada from the first day of that period, so roles move with the period in which payroll processes the change.
- Nmbrs knows the manager's number, name and email address. Omada needs the key of that manager's identity to route approvals and reviews. KoppelHet converts the manager to that key and reports it if it cannot be found.
- Nmbrs retires its old SOAP integration method on 1 March 2027. An export for Omada that relies on it will then have to change. KoppelHet builds this integration on the REST API straight away, with an employer-level login; an accounting firm's login does not work for it.
- In Nmbrs, BSN, pay and bank account sit close to the employee data. The integration only requests read rights on employees and company structure, and the address Omada reads holds nothing beyond what roles and lifecycle need.
- Omada can set a threshold per import on the number of deleted identities, but that threshold is off by default. A wrongly selected company in Nmbrs could otherwise make all employees disappear at once. We switch that threshold on at go-live.
This integration is also part of joiner, mover, leaver.
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
We use Nmbrs through our accounting firm. Is that possible?
Yes, but the integration needs its own employer-level login. You arrange that together with the firm.
Does payroll data go to Omada?
No. Only name, company, department, job, manager and the start and end dates.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Nmbrs is read through the Nmbrs REST API with OAuth 2.0 and only read scopes for employees and company structure; this needs a login at debtor level. The SOAP API is retired from 1 March 2027.
- Omada reads through the REST collector (Content: Identity data) with OAuth2 Client Credentials; required fields Business key, Unique ID, Name and Status; Filter with #MinRow() or #MaxRow() can enforce one row per key; Thresholds for new, modified and deleted objects as percentages (default 0, off).
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Nmbrs | Field in Omada | Notes |
|---|---|---|
Bedrijfscode + personeelsnummer | Business key en Unique ID | Required in Omada |
Roepnaam en achternaam volgens naamstelling | Name | Required in Omada |
Datum uit dienst | Status | Required in Omada; derived by KoppelHet |
Afdeling (code en omschrijving) | Afdeling | |
Functie (code en omschrijving) | Functie | |
Leidinggevende | Manager | Converted to the manager's key |
Nmbrs-bedrijf | Bedrijf |
Related
ADP Workforce Now → Nmbrs
ADP Workforce Now to Nmbrs integration: the Dutch payroll group from ADP in the right Nmbrs company
AlexisHR → Nmbrs
AlexisHR (Simployer One) to Nmbrs integration: Dutch employees into payroll
BambooHR → Nmbrs
BambooHR to Nmbrs integration: Dutch payroll next to a global HR system
Bullhorn → Nmbrs
Bullhorn to Nmbrs integration: placements with hourly pay and end date in payroll