Accounts in applications
Nmbrs to Magister integration: staff accounts in Magister from payroll in Nmbrs
With an integration between Nmbrs and Magister, every new employee payroll enters in Nmbrs automatically gets a staff account in Magister, with employee number, work email and unit. The end date of the employment in Nmbrs becomes the expiry date in Magister, after which KoppelHet blocks the account.
What the integration does
Schools that process payroll in Nmbrs and use Magister as student administration have no separate HR system driving accounts. Payroll is first to know who starts and leaves, but the Magister account is created and blocked by hand, separately.
- KoppelHet requests a partner client from Magister with only the scopes for staff accounts, and the school creates a Nmbrs token for KoppelHet.
- Payroll enters the new employee in Nmbrs, with department and work email.
- KoppelHet compares the employees per Nmbrs company daily with the previous state and creates an account in Magister for new employees.
- An end date in Nmbrs becomes the account's expiry date.
- After the end date KoppelHet blocks the account.
What to watch for with Nmbrs and Magister
- Nmbrs returns employees per company and has no list of only the changes. KoppelHet therefore fetches all employments and personal details per company, compares them with the previous round and only sends new employees and new end dates to Magister.
- An employee number in Nmbrs is unique within a company, not across companies. If a foundation has several Nmbrs companies under one Magister environment, KoppelHet agrees a prefix per company, so two employees with the same number are not linked to the same staff record in Magister.
- Nmbrs has a request for personal details without BSN. KoppelHet uses it, so the citizen service number never leaves payroll; Magister does not need it for an account either.
- Nmbrs has a work and a private email address, and Magister accepts only one, at creation only. KoppelHet only uses the work address and waits with creation until it is filled in Nmbrs.
- An end date sits on the employment in Nmbrs and is often known before the last payroll run. KoppelHet sets that date as expiry date in Magister straight away, so access stops even if nobody remembers.
- Departments have a history per period in Nmbrs, and Magister only accepts the unit at creation. When an employee's department changes in Nmbrs, KoppelHet reports it to the Magister administrator instead of changing the account.
- Nmbrs switches off the SOAP API, which this data currently comes from, on 1 March 2027. KoppelHet moves to the Nmbrs REST API; nothing changes for Magister or the school as a result.
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 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
Is Nmbrs the right source for Magister accounts?
If Nmbrs is your only personnel administration, yes. Payroll has the start and end date first; without a work email the integration waits.
Why daily and not immediately?
Nmbrs does not announce changes. One comparison per day is enough, because the start date is usually known well in advance.
Are pupils linked as well?
No. Only staff accounts can be created through the SCIM API.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Nmbrs through the SOAP EmployeeService - PersonalInfoWithoutBSN_Get_GetAllEmployeesByCompany (EmployeeNumber, FirstName, Nickname, Prefix, LastName, EmailWork), Employment_GetAll_AllEmployeesByCompany (StartDate, EndDate) and Department_GetAll_AllEmployeesByCompany. The SOAP API stops on 1 March 2027; after that through the REST API with OAuth 2.0.
- Magister through the SCIM API (SCIM v2.0) - POST User (staff only) with name, emails, employeeCode and organizationalUnits; PATCH User for blocked and expiresOn; SEARCH on employeeCode to prevent duplicate accounts. Scopes iam.scim.user.read, iam.scim.user.create, iam.scim.user.manage and iam.scim.user.attributes.manage. Client through magister.nl/partners.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Nmbrs | Field in Magister | Notes |
|---|---|---|
EmployeeNumber | employeeCode | Make unique if there are several Nmbrs companies; at creation only |
Nickname of FirstName, Prefix en LastName | name | At creation only |
EmailWork | emails | One address, at creation only |
Afdeling | organizationalUnits | Lookup table; at creation only |
EndDate van het dienstverband | expiresOn | |
Einddatum verstreken | MagisterIamUser.blocked |
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