Nmbrs logoMicrosoft Entra ID logo

Identity and access management

Nmbrs to Entra ID integration: Microsoft accounts from the payroll records

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.

What the integration does

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.

  1. Someone with the right Nmbrs login gives the integration one-time consent to read employees.
  2. Payroll processes a new contract in Nmbrs, as always.
  3. Before the first working day the Microsoft account is ready, with an email domain based on the Nmbrs company.
  4. The employee has a manager, is in the groups for company, department and job, and has a licence.
  5. After the end date sign-in is blocked and the licence is removed after the agreed period.
Nmbrs → KoppelHet → Microsoft Entra IDSOURCENmbrsTARGETMicrosoft Entra IDKoppelHetmapping · logging · monitoringNmbrs → KoppelHet → Microsoft Entra IDSOURCENmbrsTARGETMicrosoft Entra IDKoppelHetmapping · logging · monitoring
Out: Employee with employee number and name format · Job and department · Manager · Nmbrs company as the basis for domain and groups · Microsoft 365 licence

What to watch for with Nmbrs and Microsoft Entra ID

  • A Nmbrs environment can contain several companies, and employee numbers are unique per company. With more than one company the number in Entra ID gets a prefix per company, so two employees with number 1001 do not end up on the same account.
  • Nmbrs records whether someone uses their own name, their partner's name or a combination. KoppelHet shows the name in Teams and Outlook as the employee uses it, and keeps the sign-in name the same if that changes later.
  • Nmbrs knows a manager's number, name and email address, but not their Microsoft account. KoppelHet looks up that account first and only then sets the manager.
  • Job and department names in Nmbrs are often set up for the payslip and collective agreement grading, for example with a code in front. A lookup table converts them to the name that should show in Teams and Outlook.
  • Nmbrs retires its old integration method on 1 March 2027. This integration uses the new one, which needs its own login at employer level; an accounting firm's login does not work for it.
  • Nmbrs holds BSN, salary and bank details. The integration may only read employee data and passes on nothing but what Entra ID needs.
  • The work email address only exists once the Microsoft account is there. KoppelHet can write it back to Nmbrs, so payslips and notifications from Nmbrs go to the right address.

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, 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.

Customer case

How it runs at Stichting Firmitas

How these organisations use the integration. The configuration differs for each customer.

Stichting Firmitas logo

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.

Frequently asked questions

We use Nmbrs through our accounting firm. Is that possible?

Yes, but the integration needs its own login at employer level. The firm's own login does not work for this integration.

Is an employee in Entra ID before payroll has finished?

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.

What if the manager is not in Nmbrs?

KoppelHet then cannot set the manager automatically. The platform reports it, so IT handles it by hand or HR changes the manager.

Is the account deleted when someone leaves?

No, only blocked at first. Deletion follows after the period you choose, so mail and files can be handed over first.

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 the scopes for employee data; this needs a login at debtor level, an accountant login does not work. The SOAP API is retired from 1 March 2027.
  • Entra ID is written through Microsoft Graph. employeeId (with a prefix per company), givenName, surname and displayName from the name format, userPrincipalName and mailNickname, jobTitle, department, manager (looked up through employeeId or email), companyName, employeeHireDate and accountEnabled.
  • The work address can go back to the business email field in Nmbrs.

Which fields are transferred

The key fields. The full mapping is agreed per customer.

Field in NmbrsField in Microsoft Entra IDNotes
PersoneelsnummeremployeeIdUnique per Nmbrs company; with a prefix when there are several companies
RoepnaamgivenName
Achternaam volgens naamstellingsurname en displayNameOwn name, partner's name or a combination
NaamgevingsregeluserPrincipalName en mailNickname
Functie (omschrijving)jobTitle
Afdeling (omschrijving)department
LeidinggevendemanagerMatched through the manager's employee number or work email
Nmbrs-bedrijfcompanyName en e-maildomein
Datum in dienstemployeeHireDate
Datum uit dienstaccountEnabled = false

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.