ELD Data for IFTA: How Automatic Mileage Tracking Works (and What to Verify)

If you're running an ELD, you're already generating most of the mileage data you need for your IFTA quarterly return. The question is whether you're using it — and whether you're checking it before you file.

IFTA requires you to report miles driven in each member jurisdiction every quarter. Historically that meant paper trip sheets, state-line odometer entries, and manual addition. ELDs changed this: most modern devices track GPS position continuously and attribute miles to the correct state automatically.

Here's how that actually works, what the system can and can't do for you, and what you still have to verify before you submit.

What IFTA Requires

The International Fuel Tax Agreement requires qualified motor vehicle operators to report each quarter:

• Total miles driven in each member jurisdiction (the lower 48 states, plus most Canadian provinces)
• Total fuel purchased by jurisdiction
• Tax owed to or credit from each jurisdiction, based on a formula that compares where you drove versus where you bought fuel

The IFTA audit process compares your reported mileage against the trip records and fuel receipts that support it. If those records don't match the return, you may owe back taxes, interest, and penalties. Most IFTA jurisdictions require you to retain records for four years. Check with your base jurisdiction for the specific requirement.

How ELDs Track State Mileage

ELDs use GPS receivers that log vehicle position at regular intervals — often every few seconds to every minute, depending on the device and configuration. When the truck crosses a state line, the system detects the coordinate change based on latitude/longitude and begins attributing subsequent miles to the new jurisdiction.

The specific approach varies by device:

GPS-calculated distance. The ELD tracks position at each interval and calculates distance between consecutive points. Miles are assigned to the jurisdiction where the vehicle was located at each point. This is accurate on open highways with consistent GPS signal.

Engine ECM integration. Many ELDs also pull odometer data directly from the engine's electronic control module. This gives a cross-check between GPS-calculated distance and the actual odometer. When both sources are available, discrepancies between the two can indicate a signal loss or data gap.

State-line interpolation. When a vehicle crosses a state line between GPS data points, the device interpolates the crossing point to split the miles between jurisdictions. The precision of this depends on how frequently the device logs position — at highway speeds, a 60-second logging interval means the device is interpolating the crossing from position data a mile or more apart.

For most trips on major interstates, all of this works well. The gaps to watch for are described below.

What "Qualified Miles" Means

Not every mile on your ELD odometer is an IFTA-reportable mile. IFTA applies to qualified motor vehicles — generally, vehicles with two or more axles and a gross vehicle weight over a specified threshold, or combination vehicles. Most Class 8 trucks in interstate operation are clearly qualified.

Situations that can create non-qualified mileage:

• Operating in a jurisdiction that isn't an IFTA member (rare for over-the-road US operations, but verify)
• Miles driven on private roads or non-public routes that aren't public highways
• Specific exemptions that apply in some jurisdictions for certain vehicle types or operations

For most over-the-road operators in the contiguous US, essentially all driving miles are IFTA-qualified. But if you have any unusual operations, confirm with your base jurisdiction.

Exporting ELD Data for IFTA

Most IFTA-capable ELD platforms give you at least one way to generate a state mileage report:

Built-in IFTA reports. Motive, Samsara, and most major ELD platforms include an IFTA summary report in their web portal or app. You set the date range to match the quarter, and the report shows miles by jurisdiction in a table you can use directly for filing.

Raw data export. Many platforms also let you export GPS or trip logs to CSV. This takes more work to process but is useful if you want to verify individual trip records or reconcile against your own logs.

Integration with fleet or IFTA software. Some ELD platforms integrate directly with trucking management software to pass state mileage data automatically. If your fleet management software supports ELD integration with Motive or Samsara, mileage data can flow into your IFTA reporting without manual entry. This also connects to your fuel tracking so purchases and miles are reconciled in one place.

Check your ELD manufacturer's documentation for the specific steps to pull an IFTA report. If it's not clearly documented, the support line can walk you through it.

What to Verify Before You File

ELD mileage is significantly more accurate than hand-written trip sheets, but it's not infallible. A few checks before you submit:

Compare ELD Total Miles to Odometer

Pull the odometer reading at the start and end of the quarter and compare to the ELD's total mile count. They should be close — within about 1–2% is typical for a well-functioning system. A larger discrepancy points to a GPS signal gap (tunnels, parking structures, remote areas) or a device malfunction that the ELD may have missed logging. Investigate any significant gap before filing.

Look for Data Gaps in the Trip Log

Review the ELD's trip records for any periods where logged time doesn't align with the truck's known activity. A rest break that doesn't match actual location, or a stretch of driving miles that don't appear in the log, may indicate signal loss. Most ELD platforms flag data gaps in their reports — look for those flags and understand what happened.

Spot-Check a Few State Crossings

Pick two or three trips where you know the routes well and can estimate roughly how many miles fell in each state. Compare to the ELD's jurisdiction allocation for those trips. If a Chicago-to-Memphis run shows mostly Illinois miles and almost no Tennessee miles, something is wrong. Spot-checking builds confidence in the data before you sign the return.

Cross-Reference Fuel Purchases Against Mileage

IFTA also requires fuel purchase records by jurisdiction — where you actually bought the fuel, not just how many gallons total. Your fuel receipts should list the state of purchase. Cross-check: does the fuel you show purchased in a given state align with the mileage you're reporting there? A mismatch — large reported mileage in a state where you bought little or no fuel, or vice versa — is worth understanding before an auditor asks about it.

Verify You're Using Current Tax Rates

The ELD handles mileage. It does not calculate IFTA tax. You still need to apply the current quarterly tax rates for each jurisdiction, calculate the net tax owed or credit, and file the return with your base state. IFTA rates change quarterly — don't use last quarter's rates for the current filing.

What the ELD Doesn't Handle

To be direct about the limits:

• ELDs don't file your IFTA return — they provide the mileage input
• They don't track fuel purchases — you have to log those separately or sync from your fuel records
• They don't apply current tax rates or calculate jurisdiction-level tax owed
• They don't catch data gaps automatically — you have to review the records

The ELD is a data source, not a filing system. The better your records around it (fuel receipts, odometer verification, trip logs), the cleaner your return and the easier any audit becomes.

The Audit Angle

IFTA auditors compare your reported miles per jurisdiction to the ELD records. If your return shows 15,000 miles in Ohio for the quarter and your ELD logs show 10,000, that gap needs a documented explanation.

Auditors also look for consistency between fuel purchase locations and mileage by state. Reporting 8,000 miles in Texas while showing only one small fuel purchase there raises a question. With organized records — ELD mileage exports, itemized fuel receipts by state, and a reconciled total — an IFTA audit is a paperwork exercise. Without them, it becomes a reconstruction problem.

Keep your supporting records for the period required by your base jurisdiction. Most require four years, but confirm the specific requirement with your IFTA base state.

Truck Command integrates ELD mileage data from Motive and Samsara directly into IFTA reporting, tracks fuel purchases alongside state mileage, and keeps the quarterly return a verification step rather than a reconstruction project. Plans start at $20/month with a 14-day free trial — no credit card required.