Fuel Cards for Passenger Fleets: Controls, Reporting, and Catching Fuel Fraud

Fuel is one of the largest variable costs in a passenger transportation fleet, and it is also the least supervised line item in most operations. Drivers fuel up alone, at all hours, in neighborhoods where no manager is watching, with a company card and a receipt that may or may not match what went into the tank. A fuel card program turns that blind spot into a controlled, monitored, reportable system — and for shuttle, NEMT, limo, and charter operators, it is one of the few expense controls that pays for itself within the first months through a combination of pump discounts, eliminated leakage, and data that makes every other fuel decision smarter.

This guide covers how fuel card programs work, which controls actually stop the money leaks, how to read the reports for both fraud and maintenance problems, and how to choose and enforce a program that drivers accept instead of work around.

What a Fuel Card Program Actually Is

A fuel card is a payment card restricted to fuel — and sometimes maintenance — purchases, paired with a reporting platform that records every transaction in detail: date, time, location, gallons, price per gallon, product type, and often the odometer reading the driver enters. The card itself is the least important part. The program is the assignment, the limits, and the review loop built around the card.

Two card families dominate the market, and they suit different fleets:

• Universal cards. Accepted at nearly any station nationwide, these suit passenger fleets that cover wide territories — airport transfer work, intercity runs, charter trips that cross state lines. The trade-off is weaker pump discounts and less control over where a driver fuels, since any station will do.
• Network cards. Tied to a specific branded network or truck-stop chain, these deliver deeper per-gallon discounts and tighter reporting, but they require drivers to plan fuel stops around the network. A fixed-route shuttle operation with a known service area can concentrate fueling at two or three network stations and capture the discount on every gallon; a charter operator cannot.

Passenger fleets have a hybrid option many overlook: issue universal cards for road-trip vehicles and network cards for local, home-based vehicles, so the discount applies where the fleet actually lives and flexibility applies where it must.

Assignment: Cards to Vehicles, Not Just Drivers

The single most consequential setup decision is what each card is bound to.

• Card-per-vehicle ties every purchase to a specific unit. The report answers "what did this van consume this week," which is the question maintenance and budgeting need. The weakness is that a driver borrowing another unit can fuel it with his own card, muddying the record.
• Card-per-driver ties purchases to a person, which is the assignment that fraud controls need. The weakness is that consumption data scatters across whoever drove the unit that week.
• The working compromise most passenger fleets land on is card-per-driver with the vehicle number captured at every transaction — via the odometer prompt, a vehicle-number prompt on the keypad, or telematics auto-matching. You get person accountability and vehicle consumption in the same report.

Cards also need a lifecycle policy from day one: issued with signed acknowledgment, retrieved the day a driver leaves, and deactivated in the platform the same afternoon. A card that stays active in a former driver's wallet is an open expense account, and unused-but-active cards are the most common finding in any fuel-card audit.

The Controls That Actually Stop the Leaks

Fuel cards come with a control panel, and most fleets switch on only the PIN. The controls that matter:

• PINs, enforced. A card without a PIN is findable cash. Require a PIN on every card and never post it on the visor or the key fob — the classic violation that turns a control into a courtesy pass for anyone in the vehicle.
• Odometer prompts, mandatory. Require an odometer entry at each fueling and set the platform to reject or flag implausible entries — an odometer that moves backward, or does not move between purchases. Odometer data is what converts fuel transactions into miles-per-gallon figures per vehicle, which is where the maintenance value of the program lives.
• Volume limits per transaction. A passenger van holds a known tank size. Set the maximum gallons per transaction slightly above that tank and the platform will flag a fifty-gallon fill on a vehicle that holds twenty-five — which is almost always fuel going into a second vehicle, usually a personal one.
• Transactions per day and per cycle. Limit each card to one or two fueling events per day. Multiple fills in a day is the signature of a driver topping off a personal vehicle alongside the company unit.
• Product-type restrictions. Restrict cards to the correct fuel grade — diesel cards should decline gasoline and vice versa — and decline non-fuel categories unless you deliberately enable maintenance purchases. A card open to the full merchant category list becomes a snack-and-lottery budget within a month.
• Time-of-day and day-of-week windows. If your operation fuels overnight or on assigned days, set the windows. Fueling at 2 a.m. in a vehicle that runs a 7 a.m. shift deserves a question, and a window setting turns that question into an automatic flag.
• Geographic fencing where feasible. Some platforms let you restrict fueling to a radius around the depot or flag transactions outside the service area. For fixed-route and home-garaged fleets, this is a strong control; for charter and airport work, use it as a flag rather than a hard block so legitimate road trips do not turn into support calls.

None of these settings is exotic. What separates a controlled program from a loose one is that the settings exist on every card and someone actually reviews the exceptions.

Reading the Reports: Fraud Patterns and What They Look Like

Fuel fraud in passenger fleets is rarely dramatic. It is small, repeated, and almost always visible in the data if someone reads it. The recurring patterns:

• The personal fill-up. The company card purchases fuel for a personal vehicle — either a second transaction on the same stop or a separate visit. The tells: volume above tank capacity, two transactions within minutes, odometer jumps that do not match trip logs, or fueling on days the assigned vehicle was idle.
• Card sharing and lending. A driver without his card borrows a coworker's. The tell: one PIN used across drivers, transactions logged under a driver who was off shift, or fueling locations nowhere near that driver's routes.
• Odometer games. Inflated or falsified odometer entries distort miles-per-gallon reporting and, in fleets that reconcile fuel against mileage for reimbursement, quietly inflate claims. Cross-check entered odometers against GPS-derived trip miles from your telematics and driver scorecard data — the two sources should agree within a small band, and divergence is a flag in either direction.
• Small-purchase leakage. Non-fuel items slipped onto enabled cards — car washes, drinks, cigarettes. The tell is merchant-category detail in the transaction export, which is why the monthly review should look at product-level data, not just the fuel summary.
• Station-side and third-party skimming. Rarer but real: cloned cards used at compromised pumps. The tell is transactions at stations your vehicles never visit, or simultaneous transactions in distant locations. Modern card platforms with chip security and real-time alerts cut this exposure sharply.

Run a monthly exception review — a fixed thirty-minute routine, same day every month: pull flagged transactions, volume-versus-tank exceptions, odometer discrepancies, after-hours fills, and declined-attempt reports. Declined attempts matter because a card with working limits generates visible failed fraud attempts, and their pattern tells you who to watch. Document every review. When you do confront a violation, the record — not the accusation — is what makes the conversation clean, and the same evidence discipline that governs chargebacks and disputed fares applies to internal disputes too.

What the Data Buys You Beyond Fraud Control

The transaction file is a fleet-management dataset that most operators never fully use:

• Miles per gallon by vehicle. Odometer-plus-gallons yields real fuel economy per unit. A vehicle whose economy drops over weeks has a problem — a dragging brake, an underinflated tire load, an engine issue — and the fuel card often flags it before the driver or the check-engine light does.
• A defensible fuel budget. Consumption history by vehicle and by month turns fuel from a surprise into a forecast, and gives you the baseline you need when weighing whether operational fuel-cost levers are actually working.
• Clean fuel-tax records. Jurisdiction-by-jurisdiction purchase data feeds the mileage and fuel accounting that commercial carriers file, and it pairs directly with the recordkeeping behind IFTA fuel-tax basics. Reconstructing quarterly fuel tax from shoeboxed receipts is hours of pain; exporting the card file is minutes.
• Surcharge and customer billing support. When contracts allow fuel-adjustment pricing, the card data is the purchase evidence that supports the surcharge calculation and the conversation with the client who questions it — the commercial logic covered in fuel surcharge programs.
• A cheaper negotiation position. Gallon volumes across the fleet, concentrated on one network, are the leverage for pump discounts. Fleets that centralize their fueling at two or three stations consistently negotiate better cents-off rates than fleets whose purchases scatter.

Choosing a Program and Making It Stick

Evaluate programs on the terms that actually drive cost and friction:

• Fees versus discount. Card platforms charge per-card monthly fees, transaction fees, or both. A deep advertised discount means little if per-card fees on a forty-card fleet eat it; run the math on your real monthly gallon volume before signing.
• Acceptance where your routes run. Map your actual fueling geography against the accepted network before choosing, especially for airport corridors where diesel can be thin.
• Real-time data and alerts. Choose a platform that pushes exception alerts the day they happen rather than a monthly statement you read three weeks late. Real-time text alerts on limit breaches change driver behavior faster than any retrospective report.
• Integration. If you run telematics, prefer a platform that can auto-populate odometer readings and reconcile against GPS miles — it removes the weakest link in the data, which is the driver's own keypad entry.
• The policy, in writing, taught once. The program fails when rules live in the manager's head. Write a one-page fuel policy — assigned card, PIN confidentiality, odometer entry, where to fuel, what to do when the network station is closed, and what happens on violation — hand every driver a copy at onboarding, and collect a signature. Drivers respect a program that is explained once and enforced evenly; they work around one that appears arbitrary, and every workaround shows up later as an exception you have to investigate.

Handled this way, the fuel card program becomes what it should have been all along: not a payment convenience, but the fleet's fuel ledger, its early-warning system for both theft and maintenance, and one of the quietest margins in the operation — earned a gallon at a time, protected by controls that run whether or not anyone is watching the pump.