Managing fleet fuel expenses week to week, not just on setup day.

Managing fleet fuel expenses with virtual cards means running a short, repeatable routine after the cards are already issued: check declines and pending transactions weekly, review spend by vehicle monthly, and adjust caps or the merchant restriction whenever a route, a fuel price swing, or a new driver changes what a card actually needs to cover.

Setup gets you the cards. Management keeps them working.

Issuing a capped card for every vehicle or driver solves the first problem: a shared card or a cash float that nobody can trace back to a specific vehicle. But a card that was sized correctly in January does not stay sized correctly forever. Fuel prices move, a driver gets reassigned to a longer route, a vehicle needs an unplanned repair, and the cap that made sense at setup starts producing declines or, worse, sits so loose that nobody notices a problem for a month.

That is the gap this guide covers: not how to create a card, but how to run the fleet once the cards already exist. For the setup steps themselves, card type, funding source, and how to size a cap the first time, see how to set up a virtual card for fleet and fuel spend. This guide picks up from there.

The weekly check: declines and pending transactions

A weekly check does not need to take long. Open the dashboard and look at two numbers: Declined Transactions and Pending Transactions. A decline on a card that has never declined before is worth a look, since it usually means one of three things: the cap is too tight for what the vehicle is actually spending, the merchant restriction blocked a charge it should have allowed, or something about the card itself needs attention.

Pending transactions matter too, especially at fuel pumps. Pump terminals often authorize for more than the actual fill-up before settling the real charge later, so a card sitting close to its cap can decline a second stop the same day even though the vehicle's fuel spend for the week is still reasonable. Reading the pending list before assuming a cap is wrong saves a round of unnecessary adjustments.

The monthly review: spend by vehicle, not just spend in total

Once a month, look past the fleet-wide total and read spend card by card. A fleet-wide total can look perfectly normal while hiding real trouble: one vehicle running way over its usual pattern, another running way under, the two cancelling each other out on the summary screen. That's exactly why you read spend card by card, not just the bottom line. Because each card is already labeled by vehicle or driver, this review is mostly reading what the dashboard already grouped, not rebuilding the grouping from receipts.

• The Transaction Categories view breaks fuel and maintenance out from other spend, so a vehicle whose maintenance line jumped stands out from one whose fuel line jumped.
• The Recent Transactions table filters by card, so pulling one vehicle's full month of activity for a closer look takes a filter, not a spreadsheet rebuild.
• Export the period you need from the Recent Transactions table when a cost report by vehicle has to leave the dashboard, for example into a monthly ownership-cost review.

Adjusting caps as routes and fuel prices move

A cap is a field on the card, not a permanent setting. On plans that support it, raise or lower the spending limit on the same card when a route gets longer, a vehicle gets reassigned, or fuel prices shift enough to matter, rather than closing the card and issuing a new one. If your card's limit interval is set to monthly, a cap that was right for a shorter route last month can quietly start producing declines this month if the vehicle's driving pattern changed and the cap did not.

Treat a cluster of declines on one card as a signal to check the route before assuming the driver did something wrong. A cap that was sized to a normal week and is now seeing every fill-up decline near the end of the month usually means the vehicle is driving more than it was when the cap was set, not that spending needs tighter control.

Confirming the merchant restriction is still doing its job

A merchant restriction narrows a card to specific merchants based on the controls your account supports, and it is worth confirming periodically rather than trusting it silently once it is turned on. For the mechanics of how that restriction gets applied at setup, see the fleet card setup guide. What matters for the ongoing routine is simpler: check it, don't assume it.

Pull a sample of cleared transactions from a fuel-restricted card every so often and check the merchant names against the stations your drivers actually use. If charges are clearing at merchants that do not look like fuel stops, the spending cap becomes the control doing the real work until you can confirm what's happening at that terminal.

Handling the two exceptions that come up most

Two situations account for most of the mid-month adjustments a fleet manager makes. The first is a driver who needs more than the cap allows for a legitimate reason, a longer route, a detour, an unplanned repair. Check the dashboard to confirm the decline was really a cap issue and not a restriction issue, then raise the limit on that card rather than issuing a new one.

The second is a vehicle that gets sold or reassigned, or a driver who leaves. Cancel that card from your dashboard once you know the change is happening; a pump hold authorized right before cancellation can still settle afterward even though the card stops working for new charges. Because each card was scoped to one vehicle or driver from the start, cancelling it does not touch anyone else's fuel access. For a card issued as a virtual card with no physical plastic, there's nothing to track down first. Issue a fresh, similarly capped card for whoever or whatever takes that vehicle's place.

Keeping the routine simple as the fleet grows

The routine above does not change shape as a fleet adds vehicles; it just covers more cards. A category rule set up once, watching for a specific merchant name and auto-tagging future charges from it, keeps a repeat fuel stop from needing manual relabeling every week no matter how many vehicles use that station. The same weekly-decline and monthly-review structure that works for five vehicles works for fifty, because the work scales with how many cards need a five-minute scan, not with how complicated the process is.

Keep records that support your vehicle-related expense claims as part of this routine, not as a separate task at tax time. See IRS Publication 463, Travel, Gift, and Car Expenses for guidance on what documentation to retain. If your fleet runs commercial motor vehicles, the FMCSA's vehicle inspection and maintenance rules cover separate federal recordkeeping duties worth reviewing alongside your spend records.

Related reading: One Job, Two Kinds of Workers.

Frequently asked questions