Lease and mobility
YouForce to Athlon integration: lease drivers and their end date from YouForce at Athlon automatically
With an integration between Visma Raet YouForce and Athlon, Athlon receives every employee with a lease entitlement from YouForce, with the name they use, home address and cost centre. As soon as HR records the end of the last employment in YouForce, Athlon receives that date, so returning or taking over the car is arranged in time.
What the integration does
Employers with staff in YouForce and a group of lease drivers at Athlon often keep track of who has a lease entitlement in an Excel list. The fleet manager only hears about a departure or a move when HR remembers to pass it on.
- HR records in YouForce that the employee has a lease entitlement.
- KoppelHet picks up the change and sends the lease driver with name, address, email and cost centre to Athlon.
- A move or a new cost centre in YouForce then also goes to Athlon.
- When HR records the end of the last employment, Athlon and the fleet manager receive the end date.
What to watch for with Visma Raet YouForce and Athlon
- YouForce has no standard field for a lease entitlement. It becomes a custom field on person or employment, which Visma Raet adds to the API for this integration and this customer. Without that field the integration does not know who should go to Athlon.
- In YouForce the home address only comes with a separate permission for private data, which also releases the citizen service number and private phone. KoppelHet requests that permission only for the address and sends Athlon nothing beyond name, address, email and cost centre.
- A person can have several employments at the same time in YouForce, but a lease car belongs to the person. KoppelHet only reports a departure to Athlon when the last employment ends, not when a second appointment stops.
- A leaver drops out of the YouForce API after a set period. Anyone who only watches who disappears sees a departure too late. KoppelHet records the end date the moment YouForce shows it and sends it to Athlon straight away.
- In YouForce an employee can be split over several cost centres. Athlon needs one cost centre per driver. KoppelHet picks the cost centre with the largest share and alerts HR on an equal split.
- YouForce records how someone uses their surname, for example with their partner's name. KoppelHet sends the name in that order to Athlon, so the contract and MyAthlon account carry the name the employee recognises.
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 Athlon's taxable benefit also come back into YouForce?
Not in this integration. Taxable benefit and contribution stay in payroll. A return flow can be added later, once delivery into YouForce is agreed per customer.
What if someone changes job internally and loses their lease entitlement?
Then HR switches off the lease entitlement field. The integration reports that to Athlon and the fleet manager as the end of the driver role, separate from the employment.
Does Athlon get the citizen service number?
No. The YouForce permission does release the number to the integration, but KoppelHet does not pass it on and does not store it.
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 Youforce IAM API (api.youforce.com/IAM, OAuth 2.0) with the scope Youforce-IAM:Get_Basic for persons, employments and cost allocations, and Youforce-IAM:GetPrivateContactDetails for the home address. Persons outside the historicaldays are not returned; the API only shows what HR Core has already processed.
- The lease entitlement comes through the Youforce Extension API as an extension field on person or employment; Visma Raet configures it per application and customer.
- Athlon publishes no API documentation for employer integrations; the connection on the Athlon side is agreed per customer with Athlon.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Visma Raet YouForce | Field in Athlon | Notes |
|---|---|---|
Persoonsnummer | Personeelsnummer berijder | Per person, not per employment |
Roepnaam en achternaam volgens gebruik achternaam | Naam berijder | |
Woonadres | Adres berijder | |
Zakelijk e-mailadres | E-mailadres berijder | |
Kostenplaats uit de loonverdeling | Kostenplaats berijder | With several lines the cost centre with the largest share |
Vrij veld leaseregeling | Wel of geen berijder | |
Einddatum laatste dienstverband | Einddatum berijder |
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