Excess and shortfall mileage is the most expensive surprise in a fleet — and the most avoidable one. The return cockpit values it in euros long before the contract ends, and states how much the projection can be relied on.
A vehicle rarely carries just one contract: finance lease, maintenance agreement, telematics and mobile data run side by side with their own terms and their own deadlines. So contracts are maintained on the vehicle, and the four overview screens read across the fleet — without a second place where the same figure could be maintained.
Finance, technical and mileage lease, rental, ownership with credit, service, telematics, mobile and other. What a contract type does not know is cleared on save rather than merely hidden — otherwise an invisible figure reappears the moment you switch the type back.
Contracted kilometres in total and per year, a tolerance in both directions, excess and shortfall rates and a capped refund. If a rate is missing, the return screen reports 'contract incomplete' instead of a wrong zero.
List price, base price, down payment, optional equipment, delivery, registration, leasing factor and the employee's own contribution. Plus the notice deadline, the notice period in months and the actual termination date.
Seven, 14, 30, 60 or 90 days, in two tabs for leases and insurance. Two automation date sources — notice deadline and tax due date — send the reminder to whoever owns it.
Mileage projected to contract end and valued against the terms: expected additional payment or refund, the two-sided tolerance respected, the refund cap applied, open damage cases flagged alongside.
Every projection states what it rests on: the number and age of reported odometer readings determine low, medium or high confidence. A vehicle with a single reading from last year is not handed a projection that pretends to be solid.
Due date, annual amount, tax number, exemption with an end date, direct debit and the tax office as a partner. The forecast shows over any period what falls due when — and the vehicle cost report charges the pro-rated annual amount.
A daily service sends one mail covering every vehicle running over or under threshold — thresholds, a grace period for young contracts and recipients are configurable per tenant. One mail about N vehicles, not N mails.
On the vehicle. The four overview screens read across the fleet what is stored there and link back. A second write path onto the same table is exactly how rows without a contract type and without mileage terms come into existence — rows the return cockpit cannot value.
From the vehicle's reported odometer readings, computed as a daily average of the lifetime and the three-month rate and projected to contract end. Without a contract end date or contracted kilometres there is deliberately no projection rather than a guessed one.
Because purchase leasing, depreciation and tax agreements describe data that is kept here as master data in its own right — acquisition data and vehicle tax respectively. Separate contract types for them would be a second, competing home for the same information.
Not yet. Purchase price, book value and monthly depreciation are kept on the vehicle, but the Fleet Cost Cockpit does not currently feed them in as a cost category of their own — a new category there would change the totals of every existing report. Lease instalments and contract costs are included.
Every vehicle with technical data, registration, plate history, tyres, due dates and costs in one file.
Total cost of ownership across fuel, maintenance, leasing, fines, insurance, damages, receipts and devices.
A report hub with 34 reports, one shared export layer and per-vehicle KPIs.
Workshops, suppliers, insurers and authorities with contacts and a communication trail.
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.