Fleet Fuel Management Software That Closes the Loop From Pump to Burn
Fuel is bought by one team, dispensed by another, burned by a third and reconciled by a fourth several weeks later. KO Fleetz puts all four on one record per vehicle: what was paid for, what reached the tank, what the work required, and what is missing.
Four teams own fuel. None of them own the number.
Procurement negotiates the card rate and is measured on it. The depot dispenses from its own bowser into a logbook. Drivers fill up wherever the route allows and hand in slips, mostly. Finance receives a statement weeks later and posts it against a cost centre. Every one of them is doing the job they were given, and between them the fleet still cannot say what a specific vehicle burned on a specific Tuesday.
The losses live in the joins. A card transaction proves money moved; nothing downstream proves the litres reached the tank on the receipt, or that tank at all. A depot pump that has been over-dispensing since last year makes every vehicle it serves read slightly wrong, consistently, in a way no single reading reveals. AdBlue bought on the same card lands inside the diesel figure and quietly corrupts consumption for the whole site.
So fuel ends up managed with the only lever anyone can reach, which is policy. Tighter card rules, a memo about idling, a firmer line on receipts. That has some effect, and it never touches the expensive parts, because the expensive parts stay invisible until something measures the tank. A programme built on purchase data alone is a purchasing report wearing a fleet badge.
Four numbers, and make them reconcile
Purchased, delivered, burned, unexplained. KO Fleetz captures card transactions, depot dispensing and manual slips as purchase. Tank telemetry supplies delivery and burn. The residual that none of them account for is carried as a line of its own rather than smoothed into a rounding difference at the foot of a report nobody reads to the end.
KO Fleetz sits all four against a vehicle and a period, which is the only arrangement that lets them be set against each other. A purchase with no matching tank rise stays open until somebody closes it. A burn rate drifting against that vehicle's own history is raised before it becomes a quarterly surprise. A drop with no consumption behind it escalates while there is still something at the scene worth looking at.
KO Fleetz is direct about what it cannot separate alone. A vehicle running heavy might be leaking, idling, driven hard, badly maintained or being drained, and the fuel signal by itself will never say which. What it does is narrow the field, by putting idle hours, driving events, workshop history and location alongside the litres, so the question that reaches the depot manager is specific enough to be answerable.
Capabilities
What KO Fleetz Fleet Fuel Management Software does
Purchase capture across every source
Card issuer feeds, depot dispensing records and hand-written slips post to one place, including the own-site fuelling most fleets never fully account for.
Tank telemetry as the reference
A measured level is what turns a purchase into a verified delivery. Without one, a fuel programme can report what was bought and never what arrived.
Purchase-to-tank matching
KO Fleetz matches each transaction to the level rise it should have caused, leaving short-fills and phantom purchases as open items rather than absorbed costs.
Loss escalation with evidence
Unexplained volume becomes an event with a time, a place and a sensor trace, routed to a supervisor while the vehicle is probably still where it happened.
Consumption normalised to the work
Load, lane, terrain and vehicle class travel with the litres, so a hill route at full weight is never ranked against a motorway run carrying half a load.
Standing burn on its own clock
Fuel consumed while stationary with the engine running is counted in hours and litres, because a distance-based rate structurally cannot see it at all.
AdBlue and non-fuel separation
KO Fleetz splits out DEF, lubricants, screenwash and the coffee bought on the same card, so they stop silently distorting the consumption figure for a whole depot.
Policy exceptions, not policy theatre
Out-of-hours fills, wrong fuel grade, volumes exceeding tank capacity and stations far off the route surface as named exceptions with the trip attached.
How it works
How KO Fleetz does it
Step 1: Bring the purchases in
Card feeds, bowser issues and slips land on one ledger per vehicle. This alone exposes the own-site fuelling gap, and it needs no hardware to begin.
Step 2: Put a measurable signal on the tank
A calibrated sensor, a CAN channel or an OEM feed makes delivery and burn observable. Coverage can be staged, starting with the vehicles you already suspect.
Step 3: Reconcile at operational speed
Bought, delivered and burned are compared per vehicle per day. Supervisors work a short exception list instead of reading a report that agrees with itself.
Step 4: Escalate what is left over
The unexplained residual routes to loss investigation, mechanical drift or behaviour, depending on what the surrounding evidence says it most resembles.
Outcomes
What changes
- Purchased, delivered, burned, unexplained
- Four numbers
- Retail and own-site fuel on one ledger
- Card and pump
- The gap is a line item, not a rounding
- Residual named
- A specific question, not a general suspicion
- Narrowed
Explore in detail
Every fleet fuel management software capability
Each of these is a capability page in its own right, with the workflow, the limits and the awkward questions answered.
The systems a fuel programme has to reach
On the purchase side, fuel card issuers supply transaction feeds, and depot dispensing equipment — automated fuel management systems, pump controllers, bulk tank gauges — supplies own-site issues and stock on hand. On the vehicle side, tank level probes, CAN fuel channels and OEM connected-vehicle feeds supply level, distance and engine hours. Finance and ERP systems receive the reconciled cost for posting, and fuel duty or tax reclaim processes take the same detail wherever a jurisdiction allows recovery. Fleets that have started electrifying can bring charge point management and network billing data onto the same energy ledger. How far any of this goes depends on one unglamorous fact that varies enormously by market: whether your particular card issuer and pump controller publish a usable feed at all.
Explore integrationsFrequently asked questions
Start with purchase capture, which needs no hardware and usually finds something on its own — unmatched transactions, own-site issues nobody had reconciled, non-fuel items sitting inside the diesel figure. Then fit sensors in stages, taking the vehicles with the worst apparent consumption and the routes with the worst reputation first. Staging works because the ledger is the same either way; sensor-grade vehicles simply carry more detail. KO Fleetz states which vehicles are measured and which are inferred, so nobody compares the two without knowing it.
It will not stop it, and a vendor claiming otherwise should end an evaluation. Software has no physical authority over a tank cap. What KO Fleetz removes are the two things theft depends on: time and ambiguity. A loss is detected within the shift rather than in a quarterly variance, and it arrives carrying a location, a volume and a sensor trace instead of a suspicion. The deterrent effect of an operation where losses are visibly caught and attributable is real, and it is a different claim from prevention.
Yes, and this matters more than it sounds. DEF is consumed at a small fraction of diesel and bought on the same card at the same stop, so leaving it inside the fuel total inflates apparent consumption in a way that looks like a driver problem and is not one. Line items classify by product code where the issuer provides one, and by rule where it does not. Anything unclassifiable is held out and listed rather than dropped into the fuel figure to keep a total looking tidy.
Energy becomes the honest unit once a fleet is mixed, and cost per kilometre is the only comparison that survives the transition intact. Charge sessions from charge point management systems and network billing post to the same vehicle ledger diesel posts to, so a depot running both can compare the same route on both. The awkward part is not technical. Home charging reimbursement, tariff timing and depot load management are commercial questions that vary by country, and a fuel module does not resolve them.
It weakens it rather than breaking it, and it is worth knowing before you buy. A driver-held card resolves a transaction to a person, so when that driver moves between vehicles the litres have no certain asset behind them. Matching transaction time and place against tracking data infers the vehicle in most cases and says so plainly where it could not. The durable fix is a policy change to vehicle-bound cards. Either way, unresolved transactions are reported as unresolved rather than spread across the fleet to make a total balance.
Fuel management owns the ledger and the exceptions: what was bought, what arrived, what burned, what is unexplained, and who needs to look at each. It answers questions about fuel. Analytics sits above every module and answers questions that cross them — whether the depot with the fuel variance is also the one with the ageing vehicles and the overdue services, which is a pattern no single module can see from where it stands. If you cannot currently account for your litres, start here rather than there.
Find the litres nobody can account for
Send a month of fuel card data and one depot's bowser log. KO Fleetz will tell you what matches, what does not, and what the gap is worth looking at.