Accounts in applications
Nmbrs to Zenya integration: Zenya users with function, department and manager from payroll
With an integration between Nmbrs and Zenya, every new employee from Nmbrs automatically becomes a Zenya user with position, organisation unit and manager, so the protocols and reading tasks of their department are there straight away. After the end date in Nmbrs the integration sets the user to inactive in Zenya, and approved leave shows up as out of office.
What the integration does
Organisations that keep payroll and personnel data in Nmbrs and use Zenya for their quality manual, incident reports or risks often have no identity provider that fills Zenya. Application management then creates new colleagues by hand, puts them in a department and forgets leavers. Read confirmations of protocols therefore do not match who actually works there.
- Application management records which Nmbrs departments belong to which organisation units in Zenya, per company.
- KoppelHet reads the employees of the designated companies in Nmbrs every day, without BSN and without wage data.
- A new employee becomes a Zenya user with their function as position, the organisation unit of their department and their manager.
- Approved leave from Nmbrs goes into Zenya as an out-of-office period.
- After the end date KoppelHet sets the user to inactive; their documents, reports and read confirmations remain.
What to watch for with Nmbrs and Zenya
- A position in Zenya consists of a name only and can be created through the API. When payroll enters a new function in Nmbrs, KoppelHet creates that function name as a position in Zenya, so nobody has to update a list of functions in Zenya first.
- Organisation units in Zenya form a tree with a parent unit and their own managers. Nmbrs has a flat list of departments per company. KoppelHet therefore does not create units, but links each department per company to an existing unit through a lookup table; a department without a rule goes to application management.
- In Nmbrs the manager is a separate manager record with name and email address, not a reference to another employee. Zenya needs an existing Zenya user for manager_id. KoppelHet looks it up by the manager's email address and leaves the field empty if they have no Zenya account, instead of guessing.
- Zenya has an out-of-office period per user with a start and end date. KoppelHet fills it with approved leave from Nmbrs, so tasks and reports do not wait for someone who is on holiday. Sickness absence is kept separately in Nmbrs and is not passed on.
- Function and department change in Nmbrs per payroll period, not on a given day. KoppelHet updates position and organisation unit in Zenya on the first day of that period, so someone does not get the protocols of their new department mid-month, or still miss them a month later.
- Zenya distinguishes personal accounts and group accounts, such as an account for a ward tablet. KoppelHet only manages personal accounts with an Nmbrs ID as external ID and leaves group accounts and manually created users, such as external auditors, alone.
- When a former colleague returns, they get a new employment for the same employee in Nmbrs. KoppelHet finds the inactive Zenya user through the external ID and reactivates it, so their earlier read confirmations stay with the same person.
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
Why not through Entra ID and Zenya's SCIM connector?
If Entra ID is already filled from Nmbrs, that works. SCIM only sets users and groups; positions, organisation units, manager and out of office then still come directly from Nmbrs.
Does Zenya see salary or BSN?
No. Only name, work email, phone, function, department, manager, leave periods and the end date leave Nmbrs.
What happens to a leaver's documents?
They stay in Zenya. The user becomes inactive and application management transfers documents and open reports.
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 and read access only to personal and employment data. In the SOAP EmployeeService the sources are called PersonalInfoWithoutBSN, Function_GetCurrent, Department_GetCurrent, Manager_GetCurrent and Leave_GetList; the SOAP API ends on 1 March 2027, so new integrations use REST.
- Zenya through the Zenya REST API v5 with a bearer token from POST /tokens. POST /users with login_code and name required, plus email_address, phone_number, external_id, position_id, manager_id and organization_unit_ids; PATCH /users/{user_id} for changes, out_of_office (from and to as yyyyMMdd) and active = false. Positions through GET and POST /positions, units through GET /organization_units.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Nmbrs | Field in Zenya | Notes |
|---|---|---|
EmployeeId | external_id | Fixed key, also on return |
EmailWork | login_code en email_address | Or the login name you use for Zenya |
Nickname, Prefix en LastName | name | |
TelephoneWork of TelephoneMobileWork | phone_number | |
Function (huidige periode) | position_id | Position by name; if missing, KoppelHet creates it |
Department per bedrijf | organization_unit_ids | Through the lookup table |
Manager (e-mail) | manager_id | Looked up as an existing Zenya user |
Leave (goedgekeurd) | out_of_office.from en out_of_office.to | |
Datum uit dienst | active = false |
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