How to calculate state-to-state miles for IFTA: worked example with odometer checkpoints

Record your odometer reading at every state border crossing, subtract sequential readings to get jurisdictional miles, then build a state allocation table that matches fuel purchases to those exact miles—this method passes every IFTA audit because it removes estimation entirely.

Why GPS alone fails the IFTA audit (and odometer checkpoints don't)

State DOR auditors reject GPS coordinates, route percentages, and fuel-spend estimation as proof of jurisdictional miles. The Iowa Department of Transportation is explicit: distance records must capture beginning and ending odometer readings for every trip. A GPS trace showing you crossed the Arkansas border tells an auditor nothing about how many miles you actually drove in Arkansas. An odometer reading at the state line—142,640 miles when you entered, 143,440 when you left—is a fact they can verify against your ELD or logbook and your fuel receipts.

Manual odometer entry carries a 15–30% error rate. You write down "142,640" at a rest stop and actually jotted "142,460" or "142,680." Electronic odometer capture from your vehicle's ECM (engine control module) reads directly from the dashboard—no transcription, no GPS drift. The ELD is required to obtain and display the ECM odometer value at all times, and safety officials use the odometer value reported on the ELD. If your telematics system (Samsara, Motive, Geotab) pulls odometer data from the ECM, it matches the dashboard exactly. Paper logs with hand-scrawled odometer numbers fail audits. Digital exports from telematics or ELD systems do not.

The three-checkpoint method: entry, border, exit

Checkpoint 1 (departure): Record your full odometer at dispatch or your first fuel stop before the route begins. Date and time must match your logbook entry or fuel receipt timestamp.

Checkpoint 2 (state border): Record odometer when crossing each state line. Every state boundary—TN to AR, AR to OK, OK to TX—gets a reading. If you have an ELD, export the odometer value from the geofence or manual entry at that crossing. If you use telematics, set a geofence at each state border and capture the odometer value at entry and exit. If you're logging manually, photograph the dashboard with a timestamp visible.

Checkpoint 3 (arrival): Record odometer at your final destination or next fuel stop. Use this to validate total trip miles against the sum of state-by-state segments. If your beginning odometer was 142,340 and ending was 145,840, your trip was 3,500 miles. Your TN + AR + OK + TX miles must add to 3,500, not 3,487 or 3,515.

Worked example: Q2 2026 multi-state route with real odometer readings

Driver departs Memphis, Tennessee, on June 2 at 142,340 miles. Crosses into Arkansas at 142,640 miles (300 miles driven in TN). Continues to Oklahoma border at 143,440 miles (800 miles in AR). Enters Texas at 145,240 miles (1,800 miles in OK). Arrives in Houston at 145,840 miles (600 miles in TX). Total trip: 3,500 miles.

Fuel purchased: 430 gallons in Memphis (TN), 220 gallons in Oklahoma City (OK), 310 gallons in Dallas (TX). Total fuel: 960 gallons. Fleet average MPG: 3,500 miles ÷ 960 gallons = 3.65 MPG.

Allocate fuel to states proportionally using this formula: (Miles in State ÷ Total Miles) × Total Gallons.

The auditor verifies: odometer readings match your ELD or logbook, fuel receipts match the purchase dates and locations, and allocated fuel totals equal actual fuel purchased. A 3-gallon rounding tolerance is acceptable (82 + 219 + 492 + 164 = 957 gallons vs. 960 purchased).

Building your state allocation table (the format auditors require)

Create a spreadsheet with these columns: State, Entry Odometer, Exit Odometer, Miles in State, Fuel Purchased (gallons), IFTA Tax Rate, Tax Owed.

For Q2 2026 rates:

This table is what the auditor expects to see. Every number is traceable: odometer readings to ELD or logbook, fuel quantities to receipts, tax rates to IFTA Inc. tax schedules, and tax owed to multiplication of fuel × rate.

How to capture odometer readings in the field (without manual entry errors)

If you have an ELD: Your vehicle's odometer is read directly from the ECM at all times. At each state border, screenshot or export the odometer value from your ELD provider's app or web portal. Timestamp is captured automatically.

If you have telematics (Samsara, Motive, Geotab, etc.): Set up a geofence at each state border. The system will capture the odometer value when the vehicle enters and exits that geofence. Export the data as a CSV. ECM-sourced odometer is always preferred to GPS-based distance calculation.

Manual method (fallback only): Photograph the dashboard odometer at each border crossing. The photo must show the odometer value, a timestamp, and your location (highway, mile marker, town). Timestamp must match your fuel receipt or logbook entry time. This method survives audit if the photos are consistent and the odometer readings reconcile with your fuel allocation.

Do not rely on GPS distance or route percentage tools. Do not estimate or write "approximately 300 miles in Tennessee." The auditor will demand proof via odometer readings.

What happens if your MPG variance exceeds 10%

Auditors calculate Fleet Average MPG = Total Miles ÷ Total Gallons. In the worked example above, fleet average is 3.65 MPG. If a single trip shows 4.2 MPG (15% above average) or 3.1 MPG (15% below average), auditors flag it and request fuel-receipt detail and maintenance records.

High MPG variance can suggest fuel siphoning or logbook falsification. Low MPG variance can suggest fuel waste or unreported driving. Your defense is reconciliation: fuel purchase location must align with trip odometer location.

Example: You fill up 220 gallons in Oklahoma City but drive 1,800 miles in Oklahoma, yielding 8.18 MPG for that leg. If your fleet average is 3.65 MPG, that's a 124% variance. An auditor will ask, "Where did the other 1,100 miles come from?" Your answer: "I filled up in OKC but drove mostly OK miles; I refueled again in Dallas. See the TX fuel receipt dated June 3."

The stronger your separation of fuel-purchase location and mileage-by-state, the less variance you'll encounter.

Records you must retain for four years

For every trip, keep: beginning odometer, ending odometer, date, route (state-by-state miles), driver name. Acceptable formats: ELD export (CSV/XLS), logbook page, or telematics export. As of 2024, PDF and JPG files are no longer acceptable for IFTA audits. Data must be in spreadsheet format.

For every fuel purchase, keep: receipt with date, location (city and state), gallons, price per gallon, tax amount paid, vehicle ID, and driver ID. Receipts must be dated within 24 hours of trip completion. If you filled up on June 2 but the trip didn't end until June 4, an auditor may reject the fuel allocation.

Per quarter, compile: total miles by state, total gallons by state, fleet average MPG, tax liability per state, tax paid per state. If tax owed exceeds tax paid, you owe back tax. Penalty is $50 or 10% of delinquent tax, whichever is greater.

Retain all records for four years following the date the IFTA return was due or filed, whichever is later. Auditors will request records from five years back; failure to provide them results in estimated liability and penalties.