Fleet Fuel Monitoring That Accounts for Every Litre
Fuel is the largest controllable cost in most fleets and the one recorded with the least precision. KO Fleetz keeps a running ledger for every vehicle: what went in, what came out, and what the trip should have burned. The reconciliation happens daily instead of at month end.
Nobody can say what yesterday actually cost
Ask a depot supervisor which vehicle burned the most fuel yesterday and you will get an opinion, not a number. The card statement has not arrived. The driver's fuel slips are in the cab, or in a jacket, or gone. Distance comes off an odometer photograph taken at whatever moment the driver remembered to take it.
By the time the invoice lands three weeks later, the reconciliation is archaeology. Somebody sits with a spreadsheet, matches transactions to registration numbers, divides litres by kilometres, and produces a figure that is roughly right for the fleet and useless for any individual vehicle. The trips that produced it ended a month ago.
So fuel gets managed as a budget line rather than an operation. The lever everyone reaches for is the fuel card policy, because it is the only thing visible. The actual variance — a bowser that dispenses more than it records, a vehicle running two litres per hundred kilometres over its siblings, a shift that idles half its day — stays hidden inside a fleet average that nobody can decompose.
A running fuel ledger per vehicle
KO Fleetz puts tank level, ignition state, distance and trip boundaries on the same timeline. That is enough to open and close a fuel account for every vehicle: opening level, litres added, litres burned, closing level. Each refill is an entry with a volume, a place and a time, and each trip carries the consumption it was responsible for.
Purchased litres and delivered litres are then two separate columns rather than one assumption. Card transactions, depot bowser issues and manual slips all post against the same ledger, and the difference between what was bought and what the tank received is a number on screen instead of a hunch in a meeting.
What this module deliberately does not do is accuse anyone. It reports variance; it does not decide that variance is theft. A vehicle running heavy on a hill route is a legitimate explanation, and the module will show you that route. When a drop genuinely has no explanation, that is a different job, handled by fuel theft detection, and the ledger is what feeds it.
Capabilities
What KO Fleetz fuel monitoring gives your team
Live tank level per vehicle
Current litres in the tank for every vehicle on one screen, with the last reading timestamp so you know whether the number is fresh or stale.
Refill and drain ledger
Every level rise and fall is posted as a dated entry with volume and place, so a vehicle's fuel history reads like a bank statement.
Card and receipt reconciliation
KO Fleetz matches fuel card transactions to the tank rise they should have produced, leaving unmatched purchases visible rather than absorbed.
Consumption per trip
Litres are attributed to the trip that burned them, so a delivery run carries its own fuel cost instead of a fleet-wide average.
Idle burn accounting
Fuel consumed with the engine running and the vehicle stationary is counted separately from fuel that moved a load.
Depot bowser records
Internal pump issues post to the same ledger as retail purchases, closing the gap where own-site fuelling normally goes unrecorded.
Variance reporting
Purchased litres against delivered litres against burned litres, per vehicle and per period, with the residual shown rather than rounded away.
Low-fuel and dry-tank alerts
Warns before a vehicle strands itself mid-route, and flags tanks that reach reserve well ahead of the planned refuelling stop.
How it works
How KO Fleetz does it
Step 1: Connect the fuel signal
Tank data arrives from a calibrated sensor, a CAN feed or the vehicle's own telematics. Whatever the source, it lands on one timeline with ignition and distance.
Step 2: Open the ledger
Each vehicle gets an account. Fills post as credits, consumption posts as debits, and closing level is checked against the arithmetic at the end of every shift.
Step 3: Post the purchases
Fuel card feeds, bowser issues and manual slips are matched to the tank rise they claim to have caused. Anything that fails to match stays on screen as an open item.
Step 4: Review the variance
Supervisors work a short exception list rather than a full report — the vehicles where bought, delivered and burned do not agree within tolerance.
Outcomes
What changes
- Reconciliation instead of month-end archaeology
- Daily
- Fuel accounted to an asset, not to the fleet
- Per vehicle
- Consumption attached to the work that caused it
- Per trip
- Unmatched purchases stay visible until closed
- Open items
Frequently asked questions
Monitoring is the accounting layer. It tells you what each vehicle received and burned, whether or not anything is wrong. Theft detection is an exception layer that sits on top and asks whether a specific drop can be explained. Every fleet needs the first one; the second only earns its keep once the ledger exists, because you cannot call a loss suspicious until you know what normal looks like for that vehicle.
Partly. Odometer readings and fuel card transactions alone give you consumption per vehicle over a period, which is enough to rank vehicles and spot a bad outlier. What you lose is timing and delivery confirmation: you will know a vehicle used more than it should have, but not which day, which trip, or whether the litres you paid for ever entered the tank. Sensors turn a monthly figure into an operational one.
Yes, and this is usually where the biggest blind spot sits. Own-site fuelling tends to be recorded in a logbook by whoever was holding the nozzle. KO Fleetz posts bowser issues to the same vehicle ledger as card transactions, so a dispensed volume that never appears as a tank rise shows up as an unmatched item. Pumps drift too, and a bowser that consistently over-reports becomes visible across many vehicles rather than one.
The gap is shown as a gap. KO Fleetz does not interpolate a plausible line across missing data, because a smooth curve invented by software is indistinguishable from a real one and destroys the value of the whole record. The trip is marked as having incomplete fuel data, the device health alert fires separately, and the ledger entry stays open rather than being closed with a guess.
Accurate enough to manage by, not accurate enough to bill by. Tank sensors read a level and infer volume from a calibration table, and tanks are irregular shapes that read best in their middle range. Over a shift the numbers are close. Over a single ten-minute segment, expect noise. Where you need precision, compare a full-to-full cycle rather than two arbitrary points on the curve.
That is the normal case. Trucks with aftermarket probes, vans reporting tank percentage over CAN, and older vehicles with nothing but a fuel card can all sit in the same ledger — they simply carry different levels of detail. The reports state which vehicles have sensor-grade data and which are card-only, so nobody compares a measured figure against an inferred one without knowing.
Put your fuel spend on a ledger
Send us a month of fuel card data and one depot's vehicle list; KO Fleetz will tell you what reconciles and what does not.