Taxi fleet fuel card management UK — VAT reclaim, fraud controls, and cost-per-mile in 2026

Driver pay is negotiated and contracted; insurance and licensing are annual, predictable, and easy to budget. Fuel is none of those things — it varies with pump price, mileage, driving style, and vehicle condition, and on a cash-and-claim system it is reported by the person with the least incentive to report it accurately. An operator running 30 vehicles without a fuel card programme is typically reconstructing fuel spend from a pile of receipts weeks after the money left the account, by which point there is nothing left to do but note the total.

The commercial cost is not just the fuel itself. Time spent reconciling receipts, chasing missing ones, and processing reimbursement claims is real admin overhead that a fuel card programme removes almost entirely — spend appears on a single consolidated statement, itemised by card and typically by transaction, the moment it happens rather than weeks later.

A dedicated fuel card (Shell, BP, Esso, Allstar, and similar UK/Ireland network cards, plus supermarket-affiliated schemes) restricts spend to fuel and sometimes AdBlue/screenwash at a defined network of stations, with per-card daily or weekly spend limits the operator sets. This is the tightest control structure and the one most fleets should default to — it removes the ambiguity of a general-purpose card being used for anything else.

Mileage reimbursement (paying drivers a rate per mile driven, reconstructed from trip logs) avoids card administration entirely but pushes reconciliation work onto whoever has to verify claimed mileage against actual trips — a dispatch platform's GPS trip log makes this far more auditable than a driver's self-reported figure, but it is still after-the-fact reporting rather than live spend control.

A general company debit or credit card gives drivers the most flexibility and the least control — useful for owner-drivers on some franchise structures where the operator does not want to manage fuel spend at all, but a poor fit for an operator trying to actually control the cost line rather than just pay it.

A VAT-registered operator can reclaim input VAT on fuel used for business mileage, but the mechanics depend on how the vehicle is used and which VAT fuel-scale-charge or mileage-apportionment method the operator applies — this varies enough by fleet structure (operator-owned vehicles used solely for business vs. mixed private/business use on some owner-driver arrangements) that it needs an accountant's sign-off, not a blog post's. What a fuel card programme does reliably provide is the itemised, per-transaction VAT receipt HMRC expects to see behind a reclaim, which a pile of loose paper receipts frequently cannot.

Most UK fuel card providers issue a consolidated monthly VAT invoice covering every transaction on every card, which is materially easier to process through bookkeeping software than reconciling dozens of individual paper receipts of varying quality and legibility. Operators moving from cash-and-claim to a fuel card programme commonly report this alone shortens their VAT-return preparation time noticeably, independent of any spend-control benefit.

Per-card daily or weekly spend caps set at a realistic multiple of the vehicle's typical fuel burn catch the two most common misuse patterns — a card used to fill a second vehicle, or a card used well beyond what that vehicle's mileage could plausibly consume. Caps should be reviewed periodically rather than set once and forgotten, since a driver moved to a longer-mileage route or a higher-consumption vehicle legitimately needs a higher cap.

Network restriction (fuel-only, defined station list) closes the most common general-purpose-card misuse route outright. Real-time transaction alerts — a card used outside its normal geography, at an unusual hour, or twice in quick succession at different stations — catch card-cloning and shared-card misuse faster than a monthly statement review ever will; most mid-tier UK fuel card providers now offer this as standard rather than an enterprise add-on.

The control that closes the loop is tying each transaction back to the vehicle's actual trip log for that period. A card that shows £60 of fuel on a day the vehicle logged no trips, or a transaction at a station nowhere near any of that vehicle's routes, is a five-second flag once fuel data and dispatch trip data sit next to each other — and a near-impossible one to catch from the fuel statement alone.

Fuel spend on its own tells an operator how much left the account; fuel spend divided by that vehicle's logged mileage for the same period tells the operator whether the vehicle is running efficiently, whether a driver's style is burning more than a comparable vehicle on a comparable route, and whether an ageing vehicle has crossed the point where replacement pays for itself in fuel efficiency alone, not just reliability.

This only works if fuel data and mileage data share a common key — the vehicle record — and a common reporting period. Fleets that keep fuel statements in one spreadsheet and trip logs in the dispatch platform end up doing this reconciliation manually, quarterly if at all, which is late enough that a genuinely inefficient vehicle can run for months before anyone notices the pattern in the numbers rather than just a vague sense that 'that car seems to need fuel a lot.'

Per-vehicle cost-per-mile, reviewed monthly against the fleet average, is one of the more useful early-warning signals for a vehicle worth pulling for a mechanical check or retiring — a sudden jump usually shows up in fuel efficiency before it shows up as a breakdown.

Fleets running or transitioning to EVs (see our fleet electrification economics guide) typically need a second card programme alongside the fuel card — a public charging network card (or several, given UK charging-network fragmentation) plus a way to account for home or depot charging, which most fuel-card-style controls were not originally built for. VAT treatment on public EV charging has its own set of rules distinct from petrol/diesel fuel VAT, and depot charging paid through a business electricity account needs its own apportionment approach if any home charging is mixed in.

During a mixed-fleet transition period, cost-per-mile comparison across a petrol/diesel vehicle and an EV on the same route is one of the more concrete ways to build the internal case for further electrification — the same reporting discipline that makes fuel card data useful applies directly to charging data once it exists in a comparable form.

Ask what network restriction options exist, whether spend caps can be set and adjusted per card without a support call, whether real-time transaction alerts are included or a paid add-on, and how quickly a lost or stolen card can be frozen — a card that takes 24 hours to cancel after a driver reports it missing is a 24-hour fraud window. Ask for a sample of the consolidated VAT invoice format before signing, and check your bookkeeping software can ingest it without manual re-keying.

The bigger lever most operators leave on the table is exporting fuel-card transaction data alongside vehicle and trip records from the dispatch platform, rather than treating fuel as a finance-only spreadsheet that never talks to the vehicle records everyone else works from. TaxiCloud's vehicle records already carry MOT, insurance, and PHV plate status as first-class fields (see our licensing renewal automation guide); fuel spend and cost-per-mile reporting sit naturally alongside them once fuel-card data is imported against the same vehicle IDs, giving a controller or owner one place to see whether a vehicle is compliant, available, and running at a sane cost per mile.