Training and certificates
Nmbrs to Docebo integration: employees per company and department as branch, with manager
With an integration between Nmbrs and Docebo, every employee from Nmbrs automatically becomes a Docebo user, in the branch of their company and department, with their manager as manager and job and cost centre as additional fields. After the termination date the integration deactivates the user, so no licence keeps running for someone who has left.
What the integration does
Organisations that run payroll in Nmbrs, often for several companies in one environment, and use Docebo for mandatory courses often create users by hand per company. Leavers then stay active and keep a licence occupied, and a new department in Nmbrs does not exist as a branch.
- Payroll enters the employee or change in the right company in Nmbrs.
- Nmbrs reports the change and KoppelHet retrieves the employee.
- If their department does not exist as a branch yet, KoppelHet first creates it under the company branch.
- The employee becomes a user in that branch, with manager and additional fields; Docebo assigns the courses.
- After the termination date KoppelHet deactivates the user.
What to watch for with Nmbrs and Docebo
- Employee numbers in Nmbrs are only unique within a company, and so are department codes. KoppelHet puts the company number in front of both the Docebo username and the branch code, so two employees with number 7 in different companies remain two users.
- Every Nmbrs company becomes a top branch in Docebo with the departments below it. A course that applies to one company only is thus assigned by the administrator on the company branch, and reports in Docebo follow the same structure as payroll.
- Nmbrs sends a webhook per change, and Docebo allows no concurrent batches and no concurrent branch calls. KoppelHet queues the notifications and processes them one after another, so a monthly run with many changes does not produce unpredictable branches.
- Docebo requires an email address and a password when creating a user. For frontline employees Nmbrs often lacks a business address. KoppelHet does not create a user with a private address for them, but puts them on a list; with single sign-on a new user gets a random password that nobody uses.
- Department, job and cost centre have an effective period in Nmbrs. KoppelHet only moves an employee to another branch on the day the new department takes effect, so Docebo does not take them out of their current courses too early.
- Docebo expects the manager to be a user that already exists. If a team in Nmbrs gets a new manager who has just joined themselves, KoppelHet first creates the manager and only then sets them as manager on their employees.
- Nmbrs only grants REST access at debtor level with scopes the owner approves. The integration only requests employee and company data; pay, bank account and payslips stay out of reach.
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
Do completed courses go back to Nmbrs?
Not in the first version. Nmbrs is the payroll system; the learning history stays in Docebo. A write-back can be added later as an extension.
What if our payroll bureau manages Nmbrs?
Then the owner of the environment approves the access. The integration works at debtor level; an accountant login does not work for this.
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 (authorization code, at debtor level) and only the scopes for employee and company data, with webhooks as the trigger and a daily check. The SOAP API stops on 1 March 2027 and is not used.
- Docebo is written through the REST API - /manage/v1/orgchart for branches (always sequential), /manage/v1/user and /manage/v1/user/batch (advice at most 100, never concurrent) with branch, manager, active and additional fields. On a 429 KoppelHet waits and retries.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Nmbrs | Field in Docebo | Notes |
|---|---|---|
Bedrijfsnummer + Personeelsnummer | username | Employee numbers are only unique per company |
Roepnaam / Naamstelling | firstname, lastname | |
Zakelijk e-mailadres | email | Empty? Then no user but an alert |
Bedrijf | Branch (bovenste niveau) | |
Afdeling | Branch onder het bedrijf (code) | |
Leidinggevende | manager | |
Functie, Kostenplaats | Additional fields | |
Datum uit dienst | Gebruiker inactief |
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