Fleet Fuel Card Transaction Exception Rate

A fuel card used at a station far from the assigned vehicle is the classic trigger for a review. Fleet fuel card transaction exception rate measures the share of fuel transactions that trigger defined verification rules, such as vehicle-card mismatch, volume anomaly or missing odometer.

It is a screening measure, not a fraud verdict, and Geotab's documentation of fuel transaction records and exception reconciliation, including matching transactions with telematics information, does not establish that an exception proves misconduct. Start by defining the rules: location mismatch, fuel type, quantity, time and repeated purchases may each warrant review, and the links between card, driver, vehicle and allowed purchases must be kept current.

Context often explains a flag, such as a vehicle in service or on a different route, a volume above tank capacity that reflects separate containers or a data error, or a diesel swipe on a petrol-only vehicle that actually fills an assigned generator. Documented emergency fuel under company policy and shared vehicles whose driver mapping changes during shifts are also legitimate causes.

Data quality creates many false positives. Local time zones, delayed card posting and delayed telematics feeds can create false mismatches, so set a reasonable matching window, and remember that missing GPS points make a location match inconclusive.

A missing or implausible odometer reading can reflect a keypad error rather than an unauthorised purchase, a minor amount difference can come from tax, exchange rate or settlement adjustments, and a miscoded station category should be investigated before assuming a restricted purchase. Count transactions, not alerts.

One purchase that triggers several rules is one flagged transaction in the overall rate, and the denominator should be eligible posted transactions in the audit period, including those after settlement, with the point-in-time rate preserved. Check reversals against the card statement before treating a voided purchase as a net cost, reconcile the card provider's bill to accounting postings before assigning responsibility, and link itemised receipts so fuel can be told apart from snacks or vehicle-care products.

Separate open exceptions from confirmed loss, because the rate counts flags while investigation results need their own categories such as valid, error, policy exception and unresolved. Track severity and age, since a large-volume outlier and a missing odometer should not be treated identically, and a high closure rate can still conceal one costly case open for months.

Report the amount ultimately established as an unauthorised or erroneous charge only after investigation, separately from the gross value of transactions initially flagged, which avoids describing unresolved exposure as a realised loss. Protect due process and keep the rules useful.

Do not accuse a driver from an automated rule alone, use a second reviewer for sensitive findings when employment consequences could follow, and link any supervisor approval or maintenance note to the original transaction instead of substituting for it. Do not reward fewer flags by turning off useful rules; test false positives, update thresholds as new vehicle types and fuel suppliers appear, compare fleets carefully because capacity, geography and fuelling arrangements differ, and restrict location and driver details to authorised reviewers.