HaHR to ITSM
Nmbrs to HaloITSM integration: employees per company in Halo and tickets on joining and leaving
With an integration between Nmbrs and HaloITSM, every company from Nmbrs becomes a customer in Halo and every employee a user at the right company, and a new employee or an end date in Nmbrs automatically creates a ticket for IT. A leaver becomes inactive after the last working day, and someone who returns later gets their old Halo user back.
What the integration does
Organisations with several companies in Nmbrs, paid through a payroll bureau, and one IT department serving everything with HaloITSM often hear about new colleagues through a planner or manager. Equipment of a departed employee is only missed when the replacement asks for it.
- Payroll enters a new employee in Nmbrs, at the company where they join.
- KoppelHet creates the user in Halo, under the customer that belongs to that company, with job and department.
- An onboarding ticket is created in the new user's name, with start date and company.
- As soon as the end date is in Nmbrs, an offboarding ticket for tablet, phone and access is created.
- After the last working day the user becomes inactive.
What to watch for with Nmbrs and HaloITSM
- Halo has the customer level above the site. Each company from the Nmbrs environment becomes its own customer in Halo, so IT can report and recharge tickets and issued equipment per operating company.
- Employee number 17 can exist at two companies in Nmbrs. KoppelHet stores company code and number together in a custom field in Halo and searches on that, because Halo always creates a new user for an unknown one.
- An employee who moves from one company to another gets a new employment at the other company in Nmbrs. KoppelHet moves the existing Halo user to the new customer, so their tickets and equipment move with them and no offboarding follows.
- The end date in Nmbrs is often only fixed when the final pay run is prepared. If that date is then within a week, the offboarding ticket is created straight away, with the date in the title.
- Job and department apply per pay period in Nmbrs. A move as of next month only changes the Halo user when that period starts.
- If payroll runs through a payroll bureau, the bureau gives the integration access to only the organisation's own companies. Halo therefore never receives employees of the bureau's other clients.
- If a former employee returns under the same number at the same company, KoppelHet reactivates their inactive Halo user. Their old tickets and equipment are still there.
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
Would we not rather use sites than customers in Halo for our companies?
That works too. If you already use the customer level for something else, each company becomes a site under one customer. We record that in the design.
Is the work email address in Nmbrs?
Not always. If it is not there, KoppelHet creates the user without an email address and IT fills it in, or it comes from Entra ID later.
Can the payroll bureau manage the integration?
The bureau only grants access to the companies. Management, logging and error alerts sit with KoppelHet and your IT department.
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 only read scopes for employee and employment data and the company structure, per company; webhooks on changes and a daily comparison. The SOAP API stops in 2027.
- Halo is written through the Halo REST API with an API application (client credentials). POST /Client per company, POST /Users with client_id, site_id, department, title, customfields and inactive. GET /Users with client_id and includeinactive to find a user again. POST /Tickets with tickettype_id, user_id, client_id and summary. Rate limit 700 calls per 300 seconds per tenant.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Nmbrs | Field in HaloITSM | Notes |
|---|---|---|
Bedrijfscode + personeelsnummer | Eigen veld personeelsnummer (customfields) | Key; the number alone is unique per company |
Bedrijf | client_id | Each Nmbrs company a customer in Halo |
Voornaam, tussenvoegsel en achternaam | firstname en surname | |
Zakelijk e-mailadres | emailaddress | |
Functie | title | |
Afdeling | department | |
Datum in dienst | Onboardingticket: tickettype_id, user_id, client_id, summary | |
Datum uit dienst | Offboardingticket, daarna inactive = true |
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