Fleet-card spend controls: managing dozens of driver cards without losing the plot

One driver with one card is easy to keep an eye on. Fifty drivers across multiple depots, each spending on fuel, tolls, maintenance, parking and incidentals, is a different problem entirely. At that scale the question is no longer whether you trust your drivers, it is whether your spend is attributable, capped and visible before money leaves the account, rather than reconciled weeks later from a thick statement.

This is the operational counterpart to fuel-card fraud. If skimming and misuse explain why loose cards leak cash, spend controls are the how of stopping it across a real fleet. This guide walks through the controls that matter and how they hold up as you grow. It is general information for transport operators, not financial advice.

Why controls matter once you scale

A small operator can manage card spend by memory and a glance at the bank feed. That stops working fast. As you add drivers, vehicles and depots, the number of transactions multiplies, the spend categories diversify, and the gap between a purchase happening and you seeing it widens. By the time a month-end statement lands, any problem is already paid for and weeks old.

The shift you need is from after-the-fact reconciliation to before-the-fact control. Rather than checking what was spent, you decide in advance what each card can spend, where, and how much, and let the card enforce it automatically. That turns a sprawling, trust-based process into a set of rules that scale with the fleet rather than against it. It also makes fraud, covered in our guide on fuel-card fraud and skimming, far less damaging when it does occur.

Per-card limits and merchant locks

Two controls do most of the heavy lifting. The first is a per-card daily or weekly limit sized to the route. A regional day-cab on short runs does not need the same ceiling as a long-haul tractor crossing several countries, and matching the limit to the work means a misused card cannot drain far beyond a single legitimate need. The second is merchant-category restriction, where you lock a card to the categories it is meant for, for example fuel and tolls only, so spend outside those categories is declined at the point of sale.

Used together, these mean a card is useful for exactly the job it exists to do and close to useless for anything else. A driver card locked to fuel and tolls with a sensible daily limit cannot be quietly used to buy goods, fuel a personal vehicle, or run up a surprise balance, whether the cause is fraud or simple drift in what people think the card is for.

Attribution and the joiner-leaver problem

Control is only half the picture; you also need to know who spent what. The cleanest way is one card per driver or per vehicle, so every transaction is attributable without guesswork. Shared cards destroy this: when a card floats between people, a disputed or fraudulent transaction has no clear owner and reconciliation becomes detective work.

Then there is the lifecycle. Drivers join, leave and move between vehicles constantly, and each change is a control risk. You want to issue a card instantly when someone starts and freeze it instantly when they leave or a card goes missing, without waiting days for a replacement to arrive or a cancellation to process. A card that stays live after a driver has gone is a standing liability, and at fleet scale there is always someone leaving.

Real-time visibility across depots and entities

The last piece is seeing the whole picture as it happens. Real-time visibility means you watch spend as it occurs rather than waiting for a month-end statement, so an anomaly, an overspend or a control that needs tightening surfaces while it still matters. For a single depot this is convenient; for a multi-depot operation it is essential.

Multi-depot and multi-entity fleets have a further need: the ability to group cards and read spend by team, vehicle or entity. If you run separate operating companies, or simply want each depot's fuel and toll spend reported cleanly on its own, lumping everything into one undifferentiated feed hides exactly the patterns you need to manage. Where those tolls and fuel buys cross borders and currencies, our guide on cross-border tolls versus fuel costs covers paying in the right currency.

How Altery fits

This is a direct fit for what Altery does. Altery issues virtual and physical business cards with per-card spend limits and merchant and category controls, which is precisely the combination this guide is built around. You can size each card's limit to the route it serves and lock it to fuel, tolls or whatever categories that card should cover, with off-category spend declined automatically.

Because cards can be issued and frozen on demand, the joiner-leaver problem becomes a click rather than a process: a new driver gets a controlled card immediately, and a departing driver's card is dead the moment they go. Real-time balances and alerts give you spend as it happens instead of a month-end surprise, and multi-entity management lets multi-depot fleets keep separate operating companies and their spend cleanly apart while still seeing the whole. For cross-border lanes, the underlying multi-currency accounts let you hold and spend in USD, EUR and GBP.

Altery is not a bank and does not lend. It is the place your fleet's cards live and are controlled. This is general information, not financial advice.

Frequently asked questions