Travel and reporting

Work-related mobility reporting: connecting lease and public transport data

For the work-related mobility report, odometer readings of lease cars, public transport trips and expense claims per company registration number must come from one source per part. KoppelHet puts Athlon odometer readings in the AFAS vehicles module and links the employers in AFAS, Nmbrs or Workday to the legal entities in NS Go, so every trip counts once and with the right employer.

What it is

The work-related mobility report asks for data on lease cars, private cars and public transport per company registration number. That data is scattered: odometer readings at the lease company, trips at the mobility provider and expense claims in the payroll system.

Without agreements the same trip counts twice, or a car sits with the wrong employer.

How the integration handles it

  • AFAS regularly asks for odometer readings per car for the lease part, and names supply by the lease company as a reason for an import. The readings Athlon asks drivers for monthly go to AFAS through the integration.
  • AFAS calculates annual kilometres pro rata over the days between two readings. When a car changes driver, KoppelHet takes over the change date from Athlon, so the car is linked to the right employee with the right dates.
  • AFAS links each fuel to a fuel type and leaves out vans with grey plates. KoppelHet maps the fuel of the Athlon car and flags vans.
  • NS Go produces its own CO2 report per company registration number. KoppelHet links the employer in AFAS or Nmbrs, or the company in Workday, to the right legal entity in NS Go.
  • In AFAS the company registration number belongs to the employer, and the report is made per number. A car reaches the right employer through the driver, even if Athlon has one customer for the whole group.

Edge cases we handle

  • AFAS counts an employer-paid NS subscription as a business mobility service, and NS Go also reports public transport. Choose one source for the public transport part, or the same trip counts twice.
  • Since July 2024 Nmbrs records vehicle and fuel only with mileage claims. Someone also claiming public transport in Nmbrs counts twice; the agreement becomes that public transport only runs through NS Go.
  • Kilometres driven in lease cars are not in Nmbrs. For that part the odometer readings in MyAthlon remain the source.
  • If a driver does not submit a reading, no reading reaches AFAS for that month. KoppelHet reports cars without a recent reading.

What KoppelHet does

KoppelHet agrees per part of the report which system is the source, and sets up the integrations accordingly. AFAS and NS Go produce the report itself; the integration makes sure the data in it is complete and sits with the right employer. Tax and reporting rules stay with you and payroll.

Common integrations

Frequently asked questions

Does the integration produce the report?

No. AFAS and NS Go produce the report. The integration fills odometer readings, fuel and employer, so the report is complete.

What if a driver does not submit their odometer reading?

Then no reading reaches AFAS for that month. KoppelHet reports cars without a recent reading, so HR knows where one is missing.

Does a move between companies belong to the new or the old entity?

From the start date at the new company the employee belongs to the new entity. Trips before that stay with the old company in the report.

More on Lease and mobility

Lease and mobility: the overview

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.