HR to ITSM
Nmbrs BMC Helix ITSM integration: people per company and incidents from payroll
With an integration between Nmbrs and BMC Helix ITSM, every employee from Nmbrs becomes a person in the BMC Helix People form, under the company they belong to in Nmbrs, and KoppelHet creates an incident for the support group for every new employee or end date. Each Nmbrs company becomes a company in Helix, so people with the same employee number at different BVs do not get mixed up.
What the integration does
Organisations that run payroll in Nmbrs and use BMC Helix ITSM as their service desk often have no separate HR system that can feed Helix. The service desk then hears from the manager that someone is starting, often only in the same week.
- Nmbrs reports a change; KoppelHet fetches the employee with company, department, job and employment.
- If the company or department does not yet exist in BMC Helix, it is created first.
- The person is created or updated in CTM:People on the combination of company and employee number.
- Within the agreed lead time before the start date, an onboarding incident follows.
- An end date results in an offboarding incident; after that date the profile becomes non-active.
What to watch for with Nmbrs and BMC Helix ITSM
- Nmbrs numbers employees per company, and BMC Helix finds an incident's customer on a single Corporate ID. KoppelHet builds that ID from company code and employee number, so the onboarding incident always ends up with the right person.
- A Nmbrs company fits the company in BMC Helix, the layer Helix hangs support groups and permissions on. An operating company with its own IT partner thus automatically gets incidents with its own support group.
- Nmbrs only has departments per company, without a higher organisation layer. In BMC Helix KoppelHet puts the department under one fixed organisation per company, because Helix always places a department within an organisation.
- A change of department or job takes effect in Nmbrs per payroll period. The person in Helix moves on the first day of that period, so the incident for new access only reaches the new support group then.
- Nmbrs sends a webhook on a change, but not every change comes in that way. KoppelHet therefore compares the employees per company with CTM:People every night and repairs differences.
- The BMC Helix JWT token is valid for one hour. A daily comparison across several Nmbrs companies can take longer, so KoppelHet signs in again along the way and finishes with a logout.
- Nmbrs also holds pay, BSN and bank details. KoppelHet's OAuth client only gets read scopes on employee, employment and company structure, so that data stays outside the integration.
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
Does this work with several BVs in Nmbrs?
Yes. Every company you designate becomes a company in BMC Helix, with its own departments and support group.
Does the business email come from Nmbrs?
If it is held there, yes. Otherwise IT completes it in Helix or through Active Directory, and the integration does not overwrite it.
What happens when someone moves to another BV within the group?
Then the person's company changes in Helix and an incident for access and equipment is raised, not a departure.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Nmbrs through the Nmbrs REST API with OAuth 2.0 and read-only scopes for employee and employment data and the company structure, per company; webhooks on changes and a daily comparison. The SOAP API is retired from 1 March 2027.
- BMC Helix through the platform REST API with a token from POST /api/jwt/login (valid for one hour, Authorization: AR-JWT header) and POST /api/jwt/logout afterwards. People through POST and PUT on /api/arsys/v1/entry/CTM:People.
- Incidents through POST /api/arsys/v1/entry/HPD:IncidentInterface_Create with Action CREATE, Status, Service_Type, Impact, Urgency, Reported_Source, Description, First_Name, Last_Name, Corporate_ID and Assigned_Group. KoppelHet stores the incident number per employee per event.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Nmbrs | Field in BMC Helix ITSM | Notes |
|---|---|---|
Bedrijfscode + personeelsnummer | Corporate ID | Unique across all BVs |
Voornaam | First Name | |
Tussenvoegsel + achternaam | Last Name | |
Zakelijk e-mailadres | Internet E-mail | |
Bedrijf | Company | |
Afdeling | Department | |
Functie | Job Title | |
Datum uit dienst | Profile Status | Non-active after the date |
Nieuwe medewerker of vertrek | HPD:IncidentInterface_Create met Assigned_Group per bedrijf |
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