Nmbrs to One Identity integration: employees from payroll in One Identity Manager

What the integration does

Organisations with Nmbrs for payroll and One Identity Manager for identities often import employees through an export from Nmbrs. That export is made for payroll, counts employee numbers per company and sometimes still runs on the old SOAP integration Nmbrs switches off in 2027.

1. Someone with an employer-level Nmbrs login gives the integration consent to read employees and company structure.
2. KoppelHet fetches employees, departments and jobs per company.
3. KoppelHet places an employee file and a department file where the synchronisation server can read them.
4. One Identity Manager imports both files with the CSV connector and applies its rules for accounts and permissions.
5. After the end date One Identity Manager sees the departure in the file and follows its own leaver process.

What to watch for with Nmbrs and One Identity

• An employee number in Nmbrs is only unique within one company. One Identity Manager's CSV connector can have more than one key column. KoppelHet therefore supplies company code and employee number as two columns that together form the key, so nobody is matched to a colleague from another company.
• Nmbrs records whether someone uses their own name, their partner's name or a combination. KoppelHet puts the surname in the file as the employee uses it, so One Identity Manager does not base display names and email addresses on the birth name if someone does not want that.
• Department and job in Nmbrs have a start period instead of an exact date. KoppelHet puts the new value in the file from the first day of that period, so One Identity Manager switches permissions at the same moment as payroll.
• One Identity Manager does not treat an imported file as a source that can mark missing persons as outstanding. KoppelHet therefore keeps someone who leaves in the file with the end date, instead of dropping the row.
• Departments in Nmbrs are lists per company, and two companies can both have a "Sales" department. KoppelHet gives every department a path with the company in front, so One Identity Manager sees them as separate departments in one tree.
• Nmbrs retires the SOAP API on 1 March 2027. An export for One Identity Manager that relies on it then stops. KoppelHet reads through the REST API with an employer-level login, so the files keep coming after that date.
• If the synchronisation server cannot reach the folder with files itself, One Identity Manager works with a remote connection server. KoppelHet places the files on that server through an outbound connection, so no share needs to be opened to the outside.

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.

Frequently asked questions

Related

• Identity and access management
• Nmbrs integrations
• One Identity integrations

→

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