Litres to Ledger: An Audit-Ready Carbon Record for a Thirty-Van UK Fleet

Carbon reporting has a habit of becoming a separate paper exercise: a sustainability lead asks for litres, a fleet manager sends a fuel-card export, and the numbers are never reconciled to the miles actually driven. For a thirty-van UK fleet, that approach is both fragile and wasteful. The same transaction-level data that supports an audit-ready carbon ledger can also expose cost anomalies, provided it is built once and used properly.

Begin with the transaction, not the annual total

A fuel-card export is not a carbon report. It is a set of purchase events. Each line should carry the date, time, site, product, litres, odometer reading where captured, vehicle registration and VAT treatment. Before any emissions factor is applied, confirm that the export is complete: card transactions, bunkered fuel drawn on site, and any ad hoc purchases outside the card scheme. A ledger that omits a depot tank or a driver reimbursement is not conservative. It is simply wrong.

For a thirty-van fleet, the practical starting point is a single month of data. Pull the fuel-card file, the telematics distance report and the depot fuel-management system into one working sheet. Keep the original exports unchanged. Any adjustment should be made in a separate reconciliation tab, with a note explaining what changed and why.

Reconcile litres to telematics before applying factors

The most common audit weakness is a carbon ledger that cannot connect litres bought to miles driven. Fuel cards record purchases; telematics records movement. The two will never match perfectly, because tanks are filled at different levels and some fuel may be drawn for non-road equipment. But the variance should be explainable.

A workable method is to calculate litres per 100km for each vehicle, compare it with the telematics distance for the same period, and flag any vehicle that sits outside a reasonable band for its type and duty cycle. A short-hop van may legitimately return poorer consumption than a long-distance van. What matters is that the variance is investigated, not averaged away. Odometer gaps, missing telematics days, and transactions recorded against the wrong registration should be corrected at source where possible and documented where not.

This same reconciliation catches cost problems early. A vehicle that appears to use more fuel than its mileage suggests may have a leaking tank, a faulty fuel-level sensor, or a driver buying fuel for another vehicle. The carbon ledger and the cost review are looking at the same signal.

Put each source into the correct scope

The Scope 1 stack for a UK van fleet is mostly diesel combustion, but not exclusively. Diesel purchased on a fuel card and burned on the road is Scope 1. HVO blends need separate treatment because the renewable fraction carries a different emissions profile from the fossil fraction. Depot charging electricity is normally Scope 2 for the operator, unless the electricity is generated on site from owned or controlled equipment, in which case the fuel input may sit in Scope 1. Do not merge these categories into a single litres figure and apply one factor.

Use the current UK Government conversion factors for company reporting, and record the version used. For diesel, the factor is applied to litres. For HVO blends, the supplier should provide documentation on the renewable content and the applicable emissions factor. If that evidence is not available, the blend should not be presented as a low-carbon solution in the ledger. For electricity, use metered kWh for depot charging, not an estimated mileage multiplier, and state whether the figure is location-based or market-based.

Treat HVO as a contract, not a pump label

HVO is increasingly offered to UK fleets as a drop-in alternative, but a carbon ledger cannot rely on the nozzle label alone. The audit trail should include the supplier's sustainability declaration, the blend ratio, the delivery date and the tank or vehicle to which it was assigned. If the fuel is stored in a shared tank, allocate it by draw records or by a documented methodology. A blanket claim that all diesel was HVO will not survive scrutiny.

The cost side matters too. HVO is usually more expensive per litre than diesel, and the carbon benefit depends on the feedstock and the supply chain. A fleet should compare the cost per kilometre, not the cost per litre, and keep the carbon evidence alongside the invoice. That way the premium can be justified or challenged on the same sheet.

Use one dataset for carbon and cost

Once the data is reconciled, the same workbook can support both reporting and control. Carbon reporting needs total litres by fuel type, distance by vehicle, and the correct factor. Cost control needs price per litre by site, out-of-hours transactions, odometer gaps and consumption outliers. Both need a clear owner and a monthly close.

A simple exception report is enough for most thirty-van fleets. Flag transactions where the litres exceed the tank capacity, where the odometer is lower than the previous reading, where the site price is materially above the fleet's benchmark, or where a vehicle has refuelled outside its normal operating area. Each flag should have a resolution note. Over time, the pattern of flags becomes more useful than any single month's total.

Build the audit file as you go

An audit-ready ledger is not a last-minute compilation. It is a folder with the original fuel-card export, the telematics export, the depot fuel records, the electricity meter readings, the factor version, the calculation workbook and a short assumptions log. Name the files with the reporting period and keep them read-only. If an auditor asks why a vehicle's litres do not match its mileage, the answer should be in the reconciliation tab, not in an email.

The discipline is not glamorous, but it is cost-effective. A fleet that reconciles fuel-card litres to telematics once a month will know its carbon position and its fuel spend with the same level of confidence. The ledger stops being a paper exercise and becomes a management tool.