Import odometer readings
Readings from the portal are recorded on the vehicle with their source — the same plausibility check as manual entry, the same basis for mileage-based maintenance intervals.
Core platform
Telematics integration
Where telematics is already in the vehicle, the odometer does not need capturing twice. The integration fetches readings and electronic licence checks and writes them where they are needed anyway.
ProvidersYellowFox · CSV file import
Data kindsOdometer · licence checks
SyncAutomatic and manual
LicenceIncluded in every edition
Odometer readings nobody retypes
The integration is deliberately narrow: it takes exactly two kinds of data — odometer readings and licence checks — and leaves everything else alone. Each is switched on separately. Without a supported portal you use the CSV file import; the data then travels the same path and lands in the same fields.
What it does
What the module actually does
Electronic licence checks
If your telematics provider performs the visual check via RFID seal, those checks are imported and appear as evidence in driving licence control.
Provider-neutral file import
Without a supported portal you drop odometer*.csv and fuehrerschein*.csv into an import directory. Processed files are renamed so no run reads the same reading twice.
Each data kind switched separately
Odometer readings and licence checks are two switches. If you only need readings, only readings are transferred.
Connection test before going live
Portal address and credentials can be verified before the first automatic run. Stored secrets survive a save when the field is left empty.
Sync automatically or on demand
A background service syncs regularly; in addition a run can be triggered by hand at any time.
Last run with its result
Per integration you see when the last run happened and what it produced, in numbers — how many readings and how many checks were taken over.
Several integrations side by side
A mixed fleet may run several integrations at once; each is enabled, tested and reported on individually.
Frequently asked questions
Yes, through the provider-neutral CSV file import. Your portal exports odometer readings as a file, a directory picks them up, and from there they travel the same path as a direct integration. A real integration with further portals is available on request — that is project work, not a switch.
No. Only odometer readings and, if enabled, licence checks. Movement data, positions and driving behaviour are deliberately not fetched — that would amount to monitoring conduct and performance, with consequences of its own under works-council law.
No. What is imported are checks your telematics portal produced itself — via an NFC reader in the vehicle, for instance. A direct integration with a pure seal-check provider is not included. Drivers checked externally can be flagged in the driver file with their provider and fleet ID, so it stays clear who is controlled in-house and who is not.
In your installation, like all other data. The integration is configured inside the application; the credentials live in your database and never leave your infrastructure.
Works together with
Vehicle file
Every vehicle with technical data, registration, plate history, tyres, due dates and costs in one file.
Driving licence control
Licence data, recurring visual checks, UVV driver safety instructions and a booking block when the required class is missing.
Driver submissions
Drivers report odometer, tyre change, damage and fuel receipts themselves — administration just reviews.
Fuel card import
Read statement files, validate them by rules, release the flagged rows and only then post.
See this module with your own data
30 minutes, no sales pressure: we show the module in the context of your fleet — self-hosted in your data centre, GDPR-compliant, made in Germany.