Fuel management software connects diesel purchased to distance run: every fill recorded with quantity, location and odometer, mileage computed per vehicle and per driver, credit accounts and fuel cards reconciled against fills actually recorded, and variance surfaced where a vehicle's consumption departs from its own established pattern. With Pentoggle, an operator can describe how fuel is actually bought and consumed and generate the starting application around it.
Diesel is typically among the largest single costs in a road transport operation and a substantial share of total running cost. It is also frequently the cost tracked least precisely, because it is bought in many small transactions across many locations by people who are not in the office.
Many operators already run Tally for accounting and a GPS or telematics provider for vehicle data, and some have fuel sensors. Those stay where they are. What is often still managed outside them is the connection between litres purchased and kilometres run, per vehicle, over time.
Key takeaways
- Mileage only means something against a vehicle's own baseline. A fleet standard compares vehicles that differ in age, load, terrain and route, and it produces conclusions that are unfair and usually wrong.
- The reconciliation problem is separate from the mileage problem. Pump credit accounts, fuel cards and cash advances each create their own gap between what was billed and what was recorded.
- A single trip's mileage is noise. Variance is only interpretable over a run of trips, which is why event-by-event investigation wastes effort.
- Consumption differences have many legitimate causes before theft, and assuming theft first produces both wrong answers and damaged relationships with drivers.
- A useful number is mileage variance against each vehicle's own rolling baseline.
The spreadsheet is often not the problem
A diesel register with date, vehicle, litres and amount works, and many operators run one accurately.
The trouble starts at identifiable points.
When the odometer is not recorded
Litres are captured because they are on the bill. Distance is not, because nobody wrote down the reading. Without both, mileage cannot be computed at all, and this is a common gap.
When fuel is bought in several ways
Some fills on a pump credit account, some on a fuel card, some in cash from a driver advance. Three payment routes, three sets of records, and no combined view of what a vehicle actually consumed.
When statements arrive monthly
The pump's monthly statement lists sixty transactions. Matching them to trips and vehicles a month later is a job nobody has time for, so the total is accepted and posted.
When mileage is a fleet figure
An average across the fleet hides the vehicle that has drifted from 4.1 to 3.6 over four months, which is exactly the case worth catching.
What fuel management software holds
Fill record
Date, time, vehicle, driver, pump or source, quantity, rate, amount and odometer reading.
Payment route
Credit account, fuel card, cash advance or company payment, so each can be reconciled to its own source.
Distance and mileage
Distance between fills from odometer readings, producing mileage per fill and a rolling figure per vehicle.
Vehicle baseline
Each vehicle's own established mileage range, by load condition where relevant.
Variance
Departure from the vehicle's baseline, over a window rather than per event.
Reconciliation
Pump statements and card statements matched against fills recorded, with unmatched items listed.
Trip context
Load carried, route and terrain, held with the fill so that variance can be read fairly.
Cost per kilometre
Fuel cost divided by distance, per vehicle and per lane.
Every vehicle has its own baseline
The instinct is to set a fleet mileage standard and measure everyone against it. It tends to mislead, and it does so in a specific way.
Vehicles differ genuinely. A newer truck and a nine-year-old one are unlikely to return the same mileage. Nor are a vehicle on hill routes and one on plains, a vehicle running fully loaded in both directions and one running loaded one way, two different makes, two different body types, or the same truck before and after an engine overhaul.
Measured against a single fleet standard, the older truck on the hill route is permanently in deficit and the newer one on the plains is permanently fine, regardless of how either is actually being driven. The report is stable, it is wrong, and everyone learns to ignore it.
The alternative is straightforward. Each vehicle establishes its own baseline from its own history, with a normal range rather than a single figure. Variance is measured against that. A truck running 3.4 when its own baseline is 3.4 is fine even if another truck does 4.2. A truck running 3.9 when its own baseline is 4.3 is the one worth looking at even though it is above the fleet average.
Two refinements make it sharper. Hold separate baselines for loaded and empty running where the fleet does significant empty running, since load affects consumption. And re-establish the baseline after a major repair or an engine overhaul, because the old one no longer applies.
Reconciliation is a different problem from mileage
These get conflated and they are distinct questions.
Mileage asks whether the fuel that went into the vehicle produced the distance it should have.
Reconciliation asks whether the fuel that was billed to you actually went into your vehicles at all. It is a control question, and it has its own failure modes depending on how fuel is bought.
Pump credit accounts. A monthly statement lists transactions. Each should match a fill recorded against a vehicle at approximately that time. Unmatched entries on either side are the finding: a billed transaction with no corresponding fill, or a recorded fill absent from the statement.
Fuel cards. Transaction data is usually better and the card is typically tied to a vehicle. The gap is between the card transaction and the odometer reading, which the card cannot supply.
Cash advances. The weakest link, because the record depends entirely on the driver producing a bill, and highway fills do not always produce one that ties cleanly to a vehicle.
The practical approach is a periodic reconciliation with a short list of unmatched items rather than an attempt to verify everything. Most items match. The ones that do not are few, and they are the only ones worth anybody's time.
Variance has many causes and theft is not the first
When a vehicle's consumption worsens, the assumption in many operations is pilferage. Sometimes it is. Frequently it is not, and starting there produces both wrong conclusions and a damaged relationship with a driver who did nothing.
The legitimate causes are numerous. Load, since a heavier vehicle uses more. Terrain and route, since gradient matters considerably. Traffic and idling, particularly on city work. Tyre pressure and condition, which affects consumption measurably. Engine condition, filters and injectors, which degrade gradually. Vehicle age. Driving style, which is real and improvable. Air conditioning use. And fuel quality, which varies.
There is also a measurement cause behind a good deal of apparent variance: tank fill level. Mileage computed between two fills assumes both filled to the same point. If one was a partial fill, the calculation is wrong for that interval and self-corrects at the next full fill. This is why single-fill variance is noise and only a run of readings is informative.
The sequence that works is to look at variance over a window rather than an event, to check the mechanical and route explanations first because they are the most common and the easiest to verify, to compare the same vehicle over time rather than against other vehicles, and to look at whether variance follows the vehicle or the driver when it persists.
That last test is the useful one. A vehicle that returns poor mileage with every driver has a vehicle problem. A driver whose mileage is poor across every vehicle he takes has something worth a conversation, which may be driving style and may be training rather than anything worse.
Where fuel management looks different by business type
- Truck Fleet Management Software, where fuel is the dominant cost per kilometre on long lanes.
- City Distribution Software, where idling and stop-start running make mileage look poor for legitimate reasons.
- Bulk and Tanker Transport Software, where loaded and empty consumption differ enough that separate baselines matter.
- Transport Contractor and Fleet Owner Software, where diesel is advanced to drivers and reconciliation is part of settlement.
- Container Transporter and CFS Software, where long gate waits mean idling is a real component of consumption.
- Tempo and Small Commercial Vehicle Software, where the owner usually knows the diesel figure precisely and little else.
Why operators choose Pentoggle for fuel management
Baselines per vehicle
Variance measured against each vehicle's own history rather than a fleet standard that fits none of them.
Odometer captured with the fill
The one field that makes mileage computable, entered on a phone at the pump.
Every payment route reconciled
Credit accounts, cards and cash advances each matched to their own source, with a short unmatched list.
Variance read over a window
A run of fills rather than a single event, so effort goes to real drift rather than to noise.
Sits around your accounting
Tally and comparable systems continue handling accounting and supplier payments. Pentoggle adds the operational layer connecting litres to kilometres.
A useful number for fuel management
Mileage variance against each vehicle's own rolling baseline.
Not fleet average mileage, which compares vehicles that are not comparable. Not mileage against a target, which is arbitrary. The vehicle's departure from its own established pattern, which is what isolates change from difference.
Report it as a list of vehicles outside their normal range over the last several fills, not as a table of every vehicle's mileage. The short list is actionable and the full table is not.
Watch direction more than magnitude. A vehicle that has moved slightly below baseline and stayed there for several weeks is a more useful signal than one that dropped sharply for a single interval and recovered, because the first suggests a change in the vehicle and the second may simply be a partial fill.
Ready to build fuel management software?
You know exactly what you spent on diesel last month.
You cannot say which vehicle stopped returning the mileage it used to.
Describe how you buy diesel and what you record to Pentoggle in plain English and generate a working first version in hours, then refine it around your process.