
Stichting Firmitas
To be defined
Data from Nmbrs enriches existing Entra ID accounts with job title, department, employee type, mobile number, manager, contract and hire and leave dates.

Identity and access management
With an integration between Nmbrs and Microsoft Entra ID, a new employee in Nmbrs automatically has a Microsoft account before the first working day, with manager, groups and licence. After the end date sign-in is blocked, without IT having to wait for a request from the manager.
Anyone running HR and payroll in Nmbrs has a new colleague there well before the start date, because payroll processes the contract. IT only hears about it when the manager submits a request, and a leaver stays in Entra ID until someone notices.
This integration is also part of joiner, mover, leaver.
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.
Customer case
How these organisations use the integration. The configuration differs for each customer.

To be defined
Data from Nmbrs enriches existing Entra ID accounts with job title, department, employee type, mobile number, manager, contract and hire and leave dates.
Yes, but the integration needs its own login at employer level. The firm's own login does not work for this integration.
As soon as the employee is in Nmbrs with a start date, the integration can prepare the account. It is only enabled in the days before the start.
KoppelHet then cannot set the manager automatically. The platform reports it, so IT handles it by hand or HR changes the manager.
No, only blocked at first. Deletion follows after the period you choose, so mail and files can be handed over first.
For those who want to know how it works under the hood: APIs, fields and sources used.
The key fields. The full mapping is agreed per customer.
| Field in Nmbrs | Field in Microsoft Entra ID | Notes |
|---|---|---|
Personeelsnummer | employeeId | Unique per Nmbrs company; with a prefix when there are several companies |
Roepnaam | givenName | |
Achternaam volgens naamstelling | surname en displayName | Own name, partner's name or a combination |
Naamgevingsregel | userPrincipalName en mailNickname | |
Functie (omschrijving) | jobTitle | |
Afdeling (omschrijving) | department | |
Leidinggevende | manager | Matched through the manager's employee number or work email |
Nmbrs-bedrijf | companyName en e-maildomein | |
Datum in dienst | employeeHireDate | |
Datum uit dienst | accountEnabled = false |
ADP Workforce Now to Nmbrs integration: the Dutch payroll group from ADP in the right Nmbrs company
AlexisHR (Simployer One) to Nmbrs integration: Dutch employees into payroll
BambooHR to Nmbrs integration: Dutch payroll next to a global HR system
Bullhorn to Nmbrs integration: placements with hourly pay and end date in payroll
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.