HR to ITSM
YouForce EasyVista integration: employees, departments and tickets from the Youforce IAM API
With an integration between Visma Raet YouForce and EasyVista Service Manager, every employee from YouForce is an employee in EasyVista, with department, location, job title and contract dates, and KoppelHet creates a ticket from your onboarding or offboarding catalog entry for every new or ended employment. The department tree in EasyVista follows the organisational units from YouForce.
What the integration does
Organisations that use YouForce and run EasyVista for IT and facilities only see a reorganisation in YouForce reflected in the EasyVista departments weeks later. Until then tickets land with the wrong department and reports per department are wrong.
- KoppelHet fetches the changes since the previous latestSync from the Youforce IAM API.
- New or renamed units become departments in EasyVista, with their path.
- The employee is looked up on identification and created or updated.
- Within the agreed lead time before the start date, KoppelHet creates an onboarding ticket.
- An end date is set on the employee and results in an offboarding ticket.
What to watch for with Visma Raet YouForce and EasyVista
- The organisational units from YouForce form a tree. KoppelHet converts it to the department_path that EasyVista requires for a new department, with the parent units in front.
- Creating departments through the API is only possible from EasyVista 2025.2. On an older version IT gets a notification for a new unit in YouForce, and the employee in that unit waits until the department exists.
- An employee can be split across several cost centres in YouForce. EasyVista has no standard field for that; KoppelHet can put the main cost centre in a custom e_ field if the service desk charges on it.
- YouForce supplies planned changes ahead of time. KoppelHet only changes the employee's department in EasyVista on the effective date, so tickets stay with the current department until that day.
- EasyVista rejects a ticket with a 406 if the recipient falls outside the API user's domains. With several domains we agree in which domain the integration creates employees, so the onboarding ticket then succeeds too.
- Changing the email address of an existing employee through the API is only allowed with a master profile. When the business address changes in YouForce, the API profile grants that right, or KoppelHet reports it to IT.
- The IAM API only returns deleted employments for a short time. KoppelHet processes them in the next run, so a withdrawn hire also updates the open onboarding ticket in 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 the department tree in EasyVista fully follow YouForce?
Yes, from version 2025.2 KoppelHet creates new departments itself with their path. On older versions IT gets a notification.
Is the cost centre included?
If you want, in a custom field. With a split across several cost centres we take the main one.
Which rights does the API user need in EasyVista?
An access token with rights on employees, departments, locations and requests, within the domain the employees belong to.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- YouForce through the Youforce IAM API with the scope Youforce-IAM:Get_Basic (Persons, Employments, Employment Planned Changes, Organization Units, Locations, Cost Allocations), incrementally with from on latestSync, paging with take and nextLink.
- EasyVista through https://{server}/api/v1/{account}/ with an access token as bearer token. GET /employees?search=identification:..., POST /employees and PUT /employees/{employee_id} with AM_EMPLOYEE fields; POST /departments with department_path (from 2025.2); GET /locations. Paginated with @next since 2024.3.
- Tickets through POST /requests with catalog_guid, title, description, recipient_identification and external_reference; a task on an existing ticket through POST /requests/{rfc_number}/tasks.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Visma Raet YouForce | Field in EasyVista | Notes |
|---|---|---|
personCode | identification | Key |
Achternaam en roepnaam | last_name | |
Zakelijk e-mailadres | e_mail | |
Organisatorische eenheid met bovenliggende eenheden | department_path | When creating the department |
Organisatorische eenheid | department_id op de employee | |
Locatie | location_id | |
Begindatum dienstverband | begin_of_contract | |
Einddatum dienstverband | Vertrekdatum op de employee | Field per configuration |
Nieuw of beëindigd dienstverband | catalog_guid | |
personCode | recipient_identification | |
Kostenplaats (costAllocation) | Eigen veld e_ op de employee | Optional |
Related
ADP Workforce Now → Visma Raet YouForce
ADP Workforce Now to YouForce integration: requests for new Dutch hires and contract changes
Bullhorn → Visma Raet YouForce
Bullhorn to YouForce integration: a placement becomes a hire request
Carerix → Visma Raet YouForce
Carerix to YouForce integration: a placed candidate starts the hire workflow in YouForce
Darwinbox → Visma Raet YouForce
Darwinbox to YouForce integration: hires and pay changes from Darwinbox as a request in YouForce