"The Mileage Is Wrong": Finding and Correcting the Causes
The symptom
The vehicle record shows an implausible mileage - or downstream values such as consumption/100 km, cost per km or the leasing projection look impossible. Behind this is almost always one of the automatic write sources, usually a transposed digit in the mileage at the pump.
Step 1: Find out where the value came from
The vehicle mileage ("Kilometerstand" (Mileage) with reading date "Kilometerstand abgelesen am:" (Mileage read on:)) is written by these sources:
| Source | Behaviour |
|---|---|
| Fuel-card import | takes the highest mileage of the released records per vehicle - but only upwards: if the receipt mileage is below the current reading, nothing happens. The import never lowers the reading. |
| Driver reports (mileage, fuel-receipt, damage, tyre-change report) | "Verarbeiten" (Process) sets the reading exactly to the released value - including downwards (article 52) |
| Manual maintenance | vehicle record, "Kilometerstand" (Mileage) field (article 35) |
| YellowFox telematics | takes the device reading unchecked, including downwards (article 117) |
| Odometer history | a mileage correction/odometer replacement sets the reading and date |
Important: every mileage change outside the import additionally creates a 0-euro reading receipt (cost type "Tanken" (Refuelling), 0 litres, with a note of the source such as "Fahrerrückmeldung" (Driver feedback), "Fahrzeugbearbeitung" (Vehicle editing), "YellowFox"). A wrong value therefore sits not only on the vehicle but also as a receipt in the receipt list - and that is where the analyses read it.
What a mileage that is too high does
The KFZ-Info calculation (article 14) calculates from the mileage readings of the receipts: consumption = quantity refuelled/charged divided by the mileage span (smallest to largest receipt mileage) x 100; the mileage/day arises from the monthly mileage spans of the last three full months, and from that the leasing projection.
| Consequence of a single receipt mileage that is too high | Why |
|---|---|
| Vehicle mileage jumps up and does not heal by itself | the import only updates upwards - later correct (lower) receipts change nothing |
| Consumption/100 km too low | the mileage span is artificially inflated |
| A "fuel outlier" is flagged on the following refuelling | the segment consumption to the next refuelling becomes negative or extreme (limit: below 0 or above 50 l/100 km) |
| Mileage/day and leasing projection too high | baseless over-run warning (warning thresholds: 110 % to date / 105 % projection) |
| Cost per km too low | denominator (km since purchase) too large |
Prevention: the "KM-Stand Abweichung" check rule
The import check rule "KM-Stand Abweichung" (Mileage Deviation / MileageDelta) compares consecutive mileage readings of the same vehicle within an import run; default threshold 1,000 km, disabled out of the box. Activate it under Systemadministration → Tankkarten-Regeln (System Administration → Fuel-Card Rules) - conspicuous records then land in the release queue before being booked (article 10).
Correcting in three steps
- Correct the wrong receipt: vehicle record → Belege (Receipts) (or receipt overview), open the receipt and correct the KM-Stand (Mileage) field - if necessary the 0-euro reading receipt as well. Changing only the vehicle mileage is not enough, because the consumption and outlier analyses read the receipt mileage.
- Correct the vehicle: vehicle record, set the "Kilometerstand" (Mileage) and "Kilometerstand abgelesen am:" (Mileage read on:) fields to the true reading (downwards only works manually).
- Have it recalculated: the KFZ-Info calculation runs hourly but only recalculates outdated vehicles. It happens immediately in the Leasing-Rückgabe-Cockpit (Leasing Return Cockpit) (
/applications/vertraege/rueckgabe): the refresh icon of the vehicle row (permissionvertraege.edit), confirmation "Hochrechnung wurde neu berechnet." (Projection has been recalculated.) (article 13).
Afterwards, check the Verbrauch pro KM (Consumption per km) analysis (article 81) - the value should be plausible again.
Related articles
