Fuel Card Reconciliation Evidence Research 2026

Research question: What evidence lets a small trucking fleet distinguish a legitimate fuel purchase from a transaction that is merely present in a card statement? Fuel data sits at the intersection of trip accounting, driver administration, vehicle controls, and IFTA reporting. Treating the statement as the whole truth can hide unit mismatches, duplicate gallons, or a transaction attached to the wrong trip.

Method and evidence scope

This review compares the Federal Highway Administration's IFTA overview, the International Fuel Tax Association's guidance, IRS transportation recordkeeping material, FMCSA safety and carrier-management resources, and the Department of Energy's Alternative Fuels Data Center information on fuel data. These sources establish regulatory and measurement context; they do not provide a matched sample of small carriers or a national error rate. The practical model below is an evidence design for local records, not tax advice or an assertion about a particular fleet.

A card charge is not a trip record

The card statement proves that an account was charged at a merchant at a time, but it may not prove which power unit moved, whether the odometer reading was captured, or whether the gallons fit the vehicle's tank and route. A useful reconciliation joins the transaction ID to vehicle ID, driver or authorized user, location, date, gallons, product type, odometer or hubometer reading when available, and the trip or dispatch reference. Missing fields should remain visible as missing rather than being filled from memory.

Evidence layers that answer different questions

Use four layers. Merchant evidence answers where and when the purchase occurred. Card-program evidence answers who or what account initiated it. Equipment evidence tests whether the gallons and location are plausible for the vehicle. Trip evidence connects the event to a dispatched movement and the jurisdiction sequence. The IFTA sources provide the tax framework for fuel and miles by jurisdiction, but they do not say that every card record is sufficient on its own. That distinction matters when an administrator prepares a packet for review.

Reconciliation tests worth measuring

Start with completeness: what share of transactions has a vehicle, date, gallons, jurisdiction, and trip reference? Then test duplication by transaction number, amount, timestamp, and merchant. Test plausibility by comparing gallons with tank capacity, the prior and next odometer reading, and the vehicle's route. Test sequence by looking for fuel purchases in a jurisdiction the vehicle could not have reached in the relevant interval. A flagged test is a review queue, not proof of misconduct. Weather, time zones, shared equipment, and delayed uploads can create benign exceptions.

IFTA context without overclaiming

IFTA administration requires carriers to calculate qualified motor-vehicle fuel use and miles across member jurisdictions under the agreement's rules. The agreement and jurisdiction instructions should control the filing interpretation. An internal ledger can support that work by preserving source documents, but it cannot replace the accountable person's review of current rules. Staff may collect receipts, normalize fields, and identify gaps; a responsible operator or tax professional should decide how a disputed record is treated.

What a small-fleet review can reveal

If many records lack vehicle identifiers, the first problem may be card assignment or driver capture rather than fuel usage. If transactions are complete but trip joins fail, dispatch references or integration timing may be weak. If the largest exceptions cluster around one merchant or one unit, review local configuration and access controls before assuming a broad pattern. These are analytical hypotheses. External sources support the need for records and jurisdictional discipline, but only a fleet's own sample can establish its exception pattern.

Designing a review queue

Prioritize exceptions by consequence and evidence quality. A transaction with no vehicle, no trip, and an unusual location needs a different queue position from a duplicate upload where the original receipt and correct vehicle are already clear. Give each item an owner, requested source, due date, and closure reason. This turns reconciliation from an end-of-month hunt into explainable decisions and distinguishes an aging workflow problem from a recurring data-capture problem.

Limitations and role boundaries

The study does not estimate theft, savings, fuel economy, or tax liability. Fuel economy calculated from incomplete miles can be misleading, and merchant geography is not a substitute for a certified mileage record. It also does not recommend disabling cards, disciplining drivers, or changing a filing position from an automated flag. Preserve original records, document the reason for each correction, and route safety, employment, tax, and fraud decisions to the accountable role.

Evidence-led conclusion

The strongest fuel-card control is a traceable join among the transaction, vehicle, and trip, with uncertainty retained instead of hidden. FHWA, IFTA, IRS, FMCSA, and DOE materials support disciplined recordkeeping and careful separation of operational evidence from formal compliance decisions. For a small trucking operation, the most defensible first measure is not a dramatic fuel-economy target; it is the percentage of transactions that can be explained from original evidence and reviewed when they cannot.

Source register

1. IFTA, Inc., International Fuel Tax Association, accessed 2026-08-25.
2. FHWA fuel tax and IFTA resources, Federal Highway Administration, accessed 2026-08-25.
3. IRS Publication 463, Internal Revenue Service, accessed 2026-08-25.
4. FMCSA carrier resources, Federal Motor Carrier Safety Administration, accessed 2026-08-25.
5. Alternative Fuels Data Center, U.S. Department of Energy, accessed 2026-08-25.