Visma Raet YouForce logoFrieslandLease logo

Lease and mobility

YouForce to FrieslandLease integration: drivers to FrieslandLease, contract back on the employment

With an integration between Visma Raet YouForce and FrieslandLease, an employee with a lease entitlement goes from YouForce to FrieslandLease as a driver automatically, with the details the leasing company needs. Once the lease contract is active, the contract details are written to the employment in YouForce as custom fields and the signed contract goes into the personnel file.

What the integration does

Employers with staff in YouForce that offer a lease car through FrieslandLease email the details of every new driver to the leasing company and file the signed contract themselves later. Each month payroll searches through emails to find which contract started when.

  1. HR processes an employee in YouForce who is entitled to a lease car.
  2. KoppelHet sends the driver to FrieslandLease, with only the details needed for the contract. If a required detail is missing, HR gets an alert and nothing is passed on halfway.
  3. The driver chooses and signs the contract with FrieslandLease.
  4. Once the contract is active, KoppelHet writes the contract details to the employment in YouForce.
  5. The signed contract goes into the personnel file, once, even if the run happens again later.
Visma Raet YouForce → KoppelHet → FrieslandLeaseSOURCEVisma Raet YouForceTARGETFrieslandLeaseKoppelHetmapping · logging · monitoringVisma Raet YouForce → KoppelHet → FrieslandLeaseSOURCEVisma Raet YouForceTARGETFrieslandLeaseKoppelHetmapping · logging · monitoring
Out: Driver with name, address and contact details · Employer and employment
Back: Details of the active lease contract · Signed contract as a document in the personnel file

What to watch for with Visma Raet YouForce and FrieslandLease

  • YouForce has no standard fields for a lease car. The contract details go into custom fields on the employment, which Visma Raet sets up per integration and per customer. Those fields must exist before the first contract can come back.
  • In YouForce a lease contract belongs to one employment. If a team leader also has a second employment, for example as an on-call worker, the contract details only go to the employment with the lease entitlement.
  • Through the integration YouForce only returns what HR Core has already processed. An appointment still in the self-service workflow therefore does not go to FrieslandLease yet, so no contract starts for someone who does not come after all.
  • Writing to YouForce requires a separate permission for custom fields, next to the read access for persons and employments. The organisation grants exactly those two in the Visma developer portal, and the integration cannot change anything else in YouForce.
  • The signed contract goes into the personnel file once. KoppelHet checks beforehand whether the document is already there, so HR does not find duplicate contracts in the file after a repeated run.
  • FrieslandLease needs the home address, among other things, for a contract. YouForce holds much more about an employee, such as salary and contract hours; KoppelHet only sends the fields in the mapping and leaves the rest in YouForce.
  • When the employment gets an end date, FrieslandLease receives that date, so returning or transferring the car is arranged on time.

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, architecture and compliance

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.

Price indication · Basic

Leave your work email and you see the price indication right away.

We only use your address to follow up on your question about this integration.

Customer case

How it runs at FrieslandLease

How these organisations use the integration. The configuration differs for each customer.

FrieslandLease logo

FrieslandLease

Mobility

Employees of employers working with FrieslandLease flow from YouForce to FrieslandLease. Once the lease contract is active, its details are written to the employment as attributes and the signed documents go into the personnel file.

Frequently asked questions

Do the taxable benefit and employee contribution also go to payroll?

Not in this integration. The contract details are on the employment; monthly amounts to the payroll run can be added later as an extension.

Which employees go to FrieslandLease?

Only employees with a lease entitlement, for example based on job or an attribute in YouForce. We agree that rule with HR.

What if a required field in YouForce is empty?

Then the driver is not passed on to FrieslandLease and HR gets an alert with the missing field. Once completed, they go along in the next run.

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 domain APIs (persons and employments) with OAuth 2.0 client credentials through Visma Connect, filtered on the last sync date. Contract details go back through the Extension API (PATCH on employments/{id}) with the scope Youforce-Extensions:Write_Data; Visma Raet sets up the extension fields during the application onboarding.
  • FrieslandLease does not publish public API documentation. The connection on the FrieslandLease side, for drivers, contracts and contract documents, is agreed with FrieslandLease.

Which fields are transferred

The key fields. The full mapping is agreed per customer.

Field in Visma Raet YouForceField in FrieslandLeaseNotes
PersoonsnummerKenmerk van de berijder bij FrieslandLeaseKey between both systems
Roepnaam, voorletters, voorvoegsel en achternaamNaam van de berijder
Adres en postcodeAdres van de berijderNeeded for the contract
Zakelijk e-mailadres en telefoonContactgegevens
Werkgever van het dienstverbandWerkgever bij FrieslandLease
Begin- en einddatum dienstverbandStartdatum en einddatum dienstverband
Actief leasecontract (terug)Employment extensions in YouForceFields that Visma Raet sets up per integration
Getekend contract (terug)Document in het personeelsdossier

Related

Which systems do you want to connect?

Tell us which systems you use and what should happen automatically. Together we define the smallest working solution, with a clear design and a quote before building.