How to split a single trip's mileage across multiple states for IFTA reporting

Record your odometer reading every time you cross a state line, then subtract the previous reading to calculate miles driven in each jurisdiction—this is the only method state auditors will accept as proof of where you actually drove.

Odometer readings at state borders are your audit defense, not GPS percentages

State DOR auditors reject GPS-only allocations and fuel-spend guesses. The IFTA individual trip report form from Ohio DOR explicitly requires jurisdictional line odometer readings to calculate miles in each state. Odometer math is defensible: exit reading minus entry reading equals jurisdictional miles.

Real example: a driver crosses the Texas/Oklahoma border at odometer 45,230, then leaves Oklahoma at 46,847. That's 1,617 miles in Oklahoma. No guessing. No GPS algorithm. No fuel-receipt back-calculation.

GPS data and tracking apps support the narrative but do not replace the odometer record. If your ELD reports 1,800 miles in Texas and your odometer shows 1,787, auditors ask which one is correct—and the odometer wins because it's a mechanical instrument, not a software interpretation of satellite position.

The three-step field process: start, cross, refuel

Step 1: Log odometer at trip start and note the state. Write it down (or photograph it) before you pull out of the yard. Include the date and state abbreviation.

Step 2: Log odometer at every state line crossing, including the new state name. The moment you see the "Welcome to [State]" sign, check your odometer and record the number. Do this at every border, not just the ones where you plan to refuel. This takes 20 seconds per crossing.

Step 3: Log odometer again if you refuel, along with the fuel receipt. Fuel receipts pair with odometer readings, not GPS coordinates. The receipt shows the gallons, price, and (usually) the location; the odometer reading on that same day proves you were in that state and adds to your mileage record there.

This method saves 40+ hours in audit response time. When a state DOR auditor requests records four years back, you hand over a spreadsheet with dates, odometer readings, state names, and receipts.

Why fuel purchases alone do not split mileage across states

A driver may buy 200 gallons in Texas but drive 1,800 miles there and 800 in Oklahoma. IFTA requires you to report miles driven per state, not gallons purchased per state. The tax is owed on the fuel consumed based on mileage, not on where you bought the fuel.

State DOR reconciles reported miles against fuel purchases. If you report 2,600 miles but only bought fuel in one state, auditors flag it as suspicious and request proof of where the miles were actually logged. Odometer readings prove you were physically in each state; receipts prove you paid tax on fuel there. But they are two separate facts.

One owner-operator in Q3 2024 lost an IFTA dispute because Samsara GPS showed 1,200 miles in Arkansas but his fuel receipt showed fuel purchased in only one county. Without an odometer checkpoint to connect the miles to the purchase, the auditor asked: "If you drove 1,200 miles in Arkansas, where did you buy fuel for the other 900 miles?" He had no answer and owed a surcharge.

Worked example: three-state run with odometer checkpoints and fuel records

A driver departs Dallas, Texas on Monday, June 5, 2026 at odometer 52,100. At Love's Travel Stop (Exit 201, TX), the driver buys 280 gallons of diesel at $2.89/gallon (receipt logged).

The driver crosses into Oklahoma at odometer 53,950. Mileage in Texas: 53,950 − 52,100 = 1,850 miles.

In Tulsa, the driver refuels at Pilot Flying J with 150 gallons at $2.71/gallon (receipt logged).

The driver crosses into Missouri at odometer 55,480. Mileage in Oklahoma: 55,480 − 53,950 = 1,530 miles.

The driver arrives in Kansas City and refuels one final time with 120 gallons in Missouri at $2.68/gallon (receipt logged at TA/Petro on I-70).

Trip ends at odometer 56,200. Mileage in Missouri: 56,200 − 55,480 = 720 miles.

Total trip: 4,100 miles, 550 gallons purchased, 7.45 MPG fleet average (4,100 ÷ 550).

Now calculate fuel consumed per state using the overall MPG:

*Rounding: 249 + 206 + 97 = 552 (fuel consumed slightly exceeds purchased due to rounding; this is normal and acceptable).

This driver bought 280 gallons in Texas but consumed only 249 gallons there (the rest went to miles driven in OK and MO). The Texas DOR gets paid tax on 249 gallons; Oklahoma gets paid on 206; Missouri on 97. Odometer readings proved where the miles went. Receipts proved where fuel was purchased. The spreadsheet reconciles both.

Four-year audit retention: why legible odometer logs matter more than GPS clouds

IFTA auditors can request records going back four years. Paper trip logs with odometer readings are admissible; GPS traces disappear or get overwritten when devices are reset or replaced.

Dispatchers who store odometer data in a spreadsheet or ELD system have survived audits. Those relying on app screenshots have not, because app data is proprietary, version-dependent, and often deleted after 90 days.

Keep the receipts. Keep the odometer log. Pair them together by date. A four-year archive takes up less than 2 MB in a cloud folder; losing it costs thousands in audit penalties and interest.

ELDs and GPS tracking tools: what they do and don't prove

FMCSA ELD rules mandate latitude/longitude capture at each change of duty status, but do not mandate state-line odometer logging. That's an IFTA requirement, not a safety requirement.

Geotab, Verizon Connect, and Motive all report "miles by state" using geo-fence algorithms. These estimates are not legally binding for IFTA purposes. If your ELD shows 1,800 miles in Texas and your odometer shows 1,787, the auditor asks which one is correct.

The hybrid method works: use GPS to spot-check and verify the odometer miles; do not use GPS as your primary record. ELD data is a cross-reference, not a replacement.

Non-IFTA jurisdictions (Alaska, Hawaii, DC, Mexico) do not appear in your quarterly filing

Miles driven in Alaska, Hawaii, District of Columbia, Yukon, Northwest Territories, Nunavut, or Mexico are excluded from IFTA calculations. If a driver hauls to Anchorage, record the odometer but do not include those miles in your Q2 filing.

Many owner-operators miscount because they forget to exclude Alaska runs. Verify your route map against the IFTA Inc. jurisdiction list before filing. A single misfiled 1,200-mile Alaska run can trigger an audit if your fuel-to-mile ratio looks impossible for the lower 48 states.

Surcharge states (Kentucky, Virginia, New York, New Mexico) require surcharge-based odometer tracking

Kentucky adds 2.0¢ surcharge per gallon consumed (not purchased); Virginia adds 6.5¢; New York adds 0.95¢; New Mexico adds 1.0¢. You must allocate miles to these states even if you bought zero fuel there, because the surcharge is always owed.

Odometer reading at Kentucky border entry and exit is mandatory. Without it, auditors cannot validate your surcharge liability. Example: a driver enters Kentucky at odometer 78,400 and exits at 79,680 (1,280 miles in KY). That's 1,280 miles ÷ 7.45 MPG = 172 gallons × 2.0¢ surcharge = $3.44 owed to Kentucky, regardless of where fuel was purchased. The surcharge never generates a credit, even if you bought excess fuel in another state.