Lease and mobility
YouForce to Shuttel integration: employees from Visma Raet YouForce into and out of Shuttel on time
With an integration between Visma Raet YouForce and Shuttel, every new employee from YouForce appears in Shuttel automatically, with one account per person, even if someone has several employments. Only when the last employment in YouForce ends is the employee deregistered in Shuttel, so the card stops neither too early nor too late.
What the integration does
Employers that use YouForce for HR and payroll and give staff a Shuttel card for commuting and business travel register everyone in Shuttel by hand. Employees with several employments make that harder, and leavers who do not go through their own department are missed.
- Payroll processes the new employment in YouForce.
- KoppelHet fetches the persons and employments changed since the previous run.
- Using a lookup on org unit or job profile, KoppelHet decides the Shuttel group, based on the main employment.
- The employee is in Shuttel with employee number, name, work email, employer and group.
- When the last employment ends, KoppelHet deregisters the employee in Shuttel on the end date.
What to watch for with Visma Raet YouForce and Shuttel
- Visma itself names linking to an application for business mobility and travel expenses as a use of the YouForce API with basic data. KoppelHet only uses that API and has no access to payroll data.
- In YouForce one person can have several employments at the same time. Shuttel gets one account per person. The group follows the main employment, and deregistration only happens when the last employment ends.
- The work email, which Shuttel needs for the invitation, is only released by YouForce together with citizen service number, addresses and private details. KoppelHet discards the rest immediately. If you do not want to grant those rights, we take the work address from the account system.
- A leaver only stays visible in the YouForce API for a configured period, and a deleted record for just a few days. KoppelHet deregisters within that period and keeps its own record of who is in Shuttel, so nobody drops out of sight without being deregistered.
- YouForce shows what payroll has already processed, even if the effective date is still in the future. KoppelHet only applies a transfer or departure on the date itself, so the employee stays in their old group until that day.
- Shuttel names Visma | Raet among the payroll systems it connects with to process allowances. That flow stays as it is. This integration only decides who is in Shuttel, with the YouForce employee number as the shared key.
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 KoppelHet see payroll data in YouForce?
No. The integration only uses the API with basic data on persons, employments, jobs and organisation. Pay is not in it.
What if someone gets a second employment with another employer within YouForce?
Then it stays one Shuttel account. Which employment decides the group and employer is agreed up front, for example the employment with the most hours.
Does Visma need to set anything up?
You authorise KoppelHet as an application for your YouForce environment in the Visma developer portal, with only the scopes this integration needs.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- YouForce is read through the Basic API (persons, employments, jobProfiles, organizationUnits) with OAuth 2.0 client credentials through Visma Connect and the Youforce-Basic:Get_Basic scope, on latestSync with from and to. The work email requires the Youforce-Basic:GetPrivateContactDetails scope. Leavers stay visible within the subscription's historicaldays; deleted records for seven days.
- Shuttel publishes no public API documentation; the connection on the Shuttel side is agreed per customer.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Visma Raet YouForce | Field in Shuttel | Notes |
|---|---|---|
personCode | Personeelsnummer | One Shuttel account per person, not per employment |
Roepnaam en voornaam | Voornaam | |
Voorvoegsel en achternaam | Achternaam | |
Zakelijk e-mailadres | E-mailadres | Only with the contact details scope, or from the account system |
company (dienstverband) | Werkgever | |
organizationUnit en jobProfile | Gebruikersgroep | Through a lookup HR maintains |
Begindatum dienstverband | Startdatum | |
dischargeDate (laatste dienstverband) | Afmelden |
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