Flotauto 2025 Innovation Award
Fleet mileage tracking: trips and odometer readings
The mileage of every vehicle, compared with the mileage set in the contract, so an overrun is seen coming before the return invoice.
Renault Trafic
Lyon branch · long-term lease
Contract km
120,000 km
Current km
98,400 km
Remaining km
21,600 km
Months left
14
Odometer readingsMileage run rate: 2,500 km/month
82% of the mileage for 71% of the term- Hosted in France, by OVHcloud
- GDPR
- €6 excl. VAT per vehicle per month, free up to 50 vehicles
Three facts about mileage tracking
7,980 odometer readings
Two sources of readings
Telematics
Automatic
Manual
Non-connected vehicles
The contract sits on the vehicle record
Contract km
120,000 km
Remaining km
21,600 km
Mileage run rate
2,500 km/month
Months left
14
Why an overrun is discovered too late
Contract mileage150,000 km
Recorded mileage193,000 km
Excess kilometers43,000 km
Rate€0.09 / km
Amount due€3,870.00
Logbook, page 14
Sep 2: 13,980?
Aug 4: 14,050
Re: end-of-month mileage reading
I'll send it Monday, I don't have the vehicle.
Real mileage is only read at the return
The overrun invoice is charged by the kilometer
Manual readings are scattered
What you get with Dadycar
Trips and odometer history feed the vehicle record. The contract is the reference, the gap becomes continuously visible, vehicle by vehicle and site by site.
Trip history
Odometer history
Odometer history
Automatic readings with no entry
Odometer · Renault Trafic
98,400 km
Source: telematics · today, 8:14 am
Manual readings for the rest of the fleet
Import data
Type
Odometer entry
odometer_readings.xlsx42 rows
Contract mileage and overrun
Renault Trafic
Contract km120,000 km
82% of the mileage for 71% of the term
Remaining km: 21,600 · 14 months left
Run rate and end of contract
How it works
Contract mileage, monthly payment and end date join the vehicle record.
A GPS-OBD device or a connected OEM vehicle: trips and odometer report themselves.
The overrun is read per vehicle and exported in the reports by site and by period.
Import data
Vehicles, contracts and sites
- Download the data
- 2Connect the data
- 3Review and import
Match the columns
Who it is for
Fleet managers
Remaining km per vehicle
Citroën Jumper−3,400 km
Peugeot 308 SW43,800 km
Assign a vehicle
SME leaders
Anomaly detected
To handleContract mileage overrun
Citroën Jumper · odometer 3,400 km beyond the contract.
Transport and logistics
Mileage run rate · Citroën Jumper
2,500km/month
Your fleet, compared with your contracts
Bring an extract of your lease contracts: we show where every vehicle stands against its planned mileage.
Your questions before getting started
“Do I need a device?”
Not for mileage tracking: manual readings are enough. A device or a manufacturer connection removes the data entry and adds the trip history.
“What about driver privacy?”
Trips fall under location tracking: time slots and zones frame how they are used, as the regulations require.
“How long does it take to start?”
As soon as the fleet is imported with one odometer reading per vehicle, the gap against the contract is calculated.
Frequently asked questions
What is contract mileage on a long-term lease?
How do you know whether a vehicle will exceed its contract mileage?
What is a vehicle's mileage run rate?
Can mileage be recorded without a telematics device?
What is the difference between a trip and an odometer reading?
Is mileage tracking used for mileage allowances?
See Dadycar on your own fleet
- Hosted in France, by OVHcloud
- GDPR
- Flotauto 2025 Innovation Award
- €6 excl. VAT per vehicle per month, free up to 50 vehicles