Training and certificates
Nmbrs to Cornerstone integration: employees per company as users, department and cost centre as organisational units
With an integration between Nmbrs and Cornerstone OnDemand, every employee from Nmbrs automatically appears in Cornerstone, with their company as legal entity and with department, job and cost centre as organisational units. After the termination date the user becomes inactive, so Cornerstone only assigns training to people who still work there.
What the integration does
Organisations that run payroll in Nmbrs, often across several companies, and offer mandatory training in Cornerstone keep the users in Cornerstone up to date with a periodic file. Employees with the same employee number in two companies then clash, and a new cost centre in Nmbrs does not yet exist in Cornerstone.
- Payroll enters the employee or change in the right company in Nmbrs.
- Nmbrs reports the change; KoppelHet collects the notifications and retrieves the employees.
- New departments, jobs, cost centres and the employees go to Cornerstone together in one job.
- Cornerstone assigns the mandatory training based on that structure; KoppelHet reports rejected records to payroll.
- After the termination date the user becomes inactive.
What to watch for with Nmbrs and Cornerstone OnDemand
- An Nmbrs environment often contains several companies, with their own employee numbers and department codes. Cornerstone requires a unique ID for every user and every organisational unit. KoppelHet therefore puts the company number in front of the employee number and the department code, so department 10 of one company does not merge with department 10 of the other.
- Nmbrs sends a webhook on every change, while Cornerstone limits creating jobs to five per minute. KoppelHet collects the notifications per quarter of an hour into one job, so a monthly run with many changes does not hit that limit.
- Department, job and cost centre have an effective period in Nmbrs. KoppelHet sends the value that applies today and only passes on a change with a later effective date on that date, so Cornerstone does not assign the new job's training too early.
- Cornerstone places an employee without a valid manager under the integration's user. Nmbrs does not have a manager for everyone. KoppelHet then uses a fixed contact per company that you provide, so requests from those employees reach a real person.
- Nmbrs only allows REST access at debtor level, with scopes the owner of the environment approves. KoppelHet only requests the scopes for employee and company data; payslips, salary and bank details stay outside the integration, even when a payroll bureau uses the same environment.
- Every Nmbrs company becomes a Legal Entity unit in Cornerstone. A training that is mandatory for one company only, for example because of its own collective agreement, can thus be assigned by the training coordinator to exactly those employees.
- Nmbrs stops the SOAP API on 1 March 2027. This integration only uses the REST API, so it does not have to be rebuilt after that date.
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
Does completed training go back to Nmbrs?
Not in the first version. Nmbrs is the payroll system; the transcript stays in Cornerstone. 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, not with an accountant login.
Are there costs on the Cornerstone side?
Yes. The Bulk API is free in pilot and stage environments; for production Cornerstone charges an annual fee based on the number of licensed users.
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.
- Cornerstone is written through the Bulk API (OAuth 2.0, asynchronous) - one job with imports for Legal Entity, Division, Position, Cost Center and Employee; references to managers and units must exist or be in the same job. Throttling five calls per minute on /jobs; capacity 50 jobs and 5 imports per type, shared with Edge Import.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Nmbrs | Field in Cornerstone OnDemand | Notes |
|---|---|---|
Bedrijfsnummer + Personeelsnummer | User ID | Employee numbers are only unique per company |
Roepnaam, Naamstelling | Voornaam en achternaam | |
Zakelijk e-mailadres | E-mail | |
Leidinggevende | Manager (User ID) | |
Bedrijf | Legal Entity-OU | |
Afdeling | Division-OU | Code prefixed with the company |
Functie | Position-OU | |
Kostenplaats | Cost Center-OU | |
Datum uit dienst | Status 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