Training and certificates
Nmbrs to aNewSpring integration: participants with company and job, and skill profiles per job
With an integration between Nmbrs and aNewSpring, every employee from Nmbrs automatically becomes a participant in aNewSpring, with their company, job and department, in their department's group and linked to the skill profile of their job. After the last working day the integration archives the participant, so they no longer use a licence and their results are kept.
What the integration does
Organisations that offer their own learning programmes per job in aNewSpring and run payroll in Nmbrs put new employees into aNewSpring by hand or with a CSV file. A job change in Nmbrs does not reach the skill profile, and former employees remain active participants.
- Payroll enters the new employee in Nmbrs, with company, department and job.
- KoppelHet creates the participant in aNewSpring, with company and employee number as external ID.
- The participant joins their department's group and is linked to the skill profile of their job.
- On a new job or department KoppelHet moves the participant to the new group and the new profile.
- After the end date KoppelHet archives the participant.
What to watch for with Nmbrs and aNewSpring
- Nmbrs gives each company in an environment its own number range for employees. aNewSpring looks up a participant by their external ID, and that ID must be unique. KoppelHet therefore builds the external ID from company and employee number, so two employees with number 7 remain two participants.
- aNewSpring has a separate company field on a participant. KoppelHet fills in the name of the Nmbrs company there, so an administrator or supervisor in aNewSpring sees which company in the group someone works for.
- A participant in aNewSpring can be linked to a skill profile and removed from it again. KoppelHet links a profile per Nmbrs job, so an employee who changes job sees the skills of their new job.
- In aNewSpring the login is an email address by default, unless support switches the environment to another login form. In Nmbrs frontline employees often lack a business address. At the start we agree whether those employees use a private address or the environment moves to usernames.
- Job and department changes in Nmbrs take effect per payroll period. KoppelHet only moves the participant in aNewSpring when the new period starts, so nobody sits in the group and profile of their next job a month early.
- aNewSpring can archive or delete a participant. KoppelHet archives after the end date, so results stay and a rehire in Nmbrs with the same details gets their old account back.
- Employees already in aNewSpring through a CSV have no external ID yet. aNewSpring can give an existing account an external ID by login. KoppelHet does that once, so no duplicate participants appear on the first run.
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 results go back to Nmbrs?
Not in the first version. Nmbrs is the payroll system and results stay in aNewSpring. Reporting back can come later as an extension.
Are employees enrolled in courses automatically?
Yes, through the group. If the administrator links a course run to a department's group, every new employee of that department is enrolled.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Nmbrs through the REST API with OAuth 2.0 (authorization code flow) at debtor level and only read scopes for employee data, with webhooks as the trigger and a daily check. No SOAP; it stops on 1 March 2027.
- aNewSpring through the API (5.4.4) with an API key in the X-API-Key header. Users with POST /addOrUpdateUser/{userID} (login, firstName, middleName, lastName, function, company, archived), POST /initializeId/{login}/{userID} for existing accounts; groups with addGroup, addGroupUsers and deleteGroupUsers; profiles with addSkillProfileUsers and deleteSkillProfileUsers.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Nmbrs | Field in aNewSpring | Notes |
|---|---|---|
Bedrijfsnummer + personeelsnummer | userID (extern ID) | Employee numbers are unique per company |
Zakelijk e-mailadres | login | Without a business address: another login form, see below |
Roepnaam | firstName | |
Tussenvoegsel | middleName (Prefix) | |
Achternaam | lastName | |
Bedrijfsnaam | company | |
Functie | function en vaardigheidsprofiel | |
Afdeling | Deelnemersgroep | |
Datum uit dienst | archived |
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