HR to ITSM
Nmbrs EasyVista integration: employees per company and catalog tickets from payroll
With an integration between Nmbrs and EasyVista Service Manager, every employee from Nmbrs is an employee in EasyVista, with BV, department and contract start date, and KoppelHet creates a ticket from your catalog entry for every new employee or departure. The ticket is in the employee's name, so the service desk knows for whom workplace and access must be ready.
What the integration does
Organisations that run payroll in Nmbrs and use EasyVista for IT and facilities often hear about new colleagues through a form from the manager. If the manager forgets that form, laptop and access badge are missing on day one.
- Nmbrs reports a change; KoppelHet fetches the employee with company, department and employment.
- The department is looked up in EasyVista by path, under the BV; if it is missing, KoppelHet creates it.
- The employee is looked up on identification and created or updated.
- Within the agreed lead time before the start date, KoppelHet creates the onboarding ticket.
- An end date is set on the employee and results in an offboarding ticket.
What to watch for with Nmbrs and EasyVista
- In Nmbrs a department belongs to one BV. KoppelHet puts the BV as the top level of the EasyVista department_path, so Sales of one BV and Sales of the other remain two departments.
- EasyVista looks up a ticket's recipient on identification. Because Nmbrs issues numbers per BV, that identification consists of company code and employee number, and the ticket always finds the right employee.
- A department change applies in Nmbrs from a payroll period. KoppelHet changes the employee's department in EasyVista on the first day of that period, so tickets from that employee stay with the old department until then.
- Creating new departments through the EasyVista API is possible from version 2025.2. If the service desk runs an older version, KoppelHet reports a new Nmbrs department to IT and the employee waits until it exists.
- Payroll sometimes only enters a new employee shortly before the first payroll run. If the start date is then already within the lead time, KoppelHet creates the ticket straight after the webhook, with the start date in the description.
- Every API call in EasyVista uses a Service Manager licence. In the daily comparison KoppelHet only requests the fields it compares, with the fields parameter, and not the full employee.
- KoppelHet reads Nmbrs without pay, BSN or bank details. Only name, number, work email, BV, department and dates reach EasyVista.
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?
Yes. The BV is the top level of the departments in EasyVista, and is part of the employee's key.
Can we use a different catalog entry per BV?
Yes. KoppelHet chooses the catalog_guid based on the Nmbrs company.
What if the manager has already filled in the onboarding form?
Then there are two tickets. We agree whether the form stays for extra wishes or is dropped.
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. The SOAP API is retired from 1 March 2027.
- EasyVista through https://{server}/api/v1/{account}/ with an access token. GET /employees with search=identification:... and fields, POST /employees and PUT /employees/{employee_id}; GET and POST /departments (creation from 2025.2, department_path required).
- Tickets through POST /requests with catalog_guid, title, description, recipient_identification and external_reference. KoppelHet stores the ticket number from the HREF per employee per event.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Nmbrs | Field in EasyVista | Notes |
|---|---|---|
Bedrijfscode + personeelsnummer | identification | Unique across all BVs |
Achternaam, voornaam | last_name | |
Zakelijk e-mailadres | e_mail | |
Bedrijf / afdeling | department_path | The BV as top level |
Afdeling | department_id op de employee | |
Datum in dienst | begin_of_contract | |
Datum uit dienst | Vertrekdatum op de employee | Field per configuration |
Nieuwe medewerker of vertrek | catalog_guid | |
Bedrijfscode + personeelsnummer | recipient_identification |
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