Electronic Logging Device Mileage by Jurisdiction, Fuel Card Purchase Imports, Quarterly Return Generation and Driver Qualification File Vaults for a Custom US Carrier Compliance Platform

This article is part of our series on Custom IFTA Fuel Tax And DOT Compliance Platform Development for US Motor Carriers: Building a Jurisdictional Mileage, Fuel Import And Driver File System

Introduction: The Same Mile Arrives From Several Directions

A single trip reaches a compliance platform from several directions at once. The ELD reports it as hours of service. The telematics unit reports it as a trail of location readings. The fuel card reports the purchases made along the way. Dispatch reports it as a load. Payroll reports it as pay.

None of those systems was built for fuel tax or driver qualification, and each tells a slightly different story. The work of carrier compliance platform integrations is reconciling them into records that hold up, while keeping each source’s original data intact.

This article covers the four carrier compliance platform integrations that define a custom build, the supporting connections around them, and the reconciliation discipline that ties them together.

They are the data layer of the full custom software development guide to IFTA and DOT compliance software development, surfaced through compliance dashboard development for the people who work the exceptions.

Electronic Logging Device Mileage by Jurisdiction

What the ELD Can and Cannot Tell You

An ELD records location for hours-of-service purposes, at intervals and at reduced precision, and hours-of-service data only has to be kept for six months.

Many ELD vendors also expose higher-frequency GPS from the same hardware, but that data, its retention and its export format vary by vendor. Confirm what each provider actually delivers before designing around it.

Computing Jurisdiction Distance

The platform takes each vehicle’s sequence of location readings, calculates the distance between them, determines where boundaries were crossed, and totals distance by jurisdiction. Odometer readings at trip start and end provide a cross-check on the GPS total.

Keeping What the Auditor Will Ask For

The IFTA Procedures Manual lists what vehicle-tracking records must contain, beginning with the original location data and including the calculated distance between readings, the route, totals and distance by jurisdiction.

The platform stores the raw readings, not just the results, for the longest applicable retention period. Fleets with several telematics vendors, often after acquisitions, need a normalization layer that preserves each source’s original format. Where the fleet runs in-cab tablets alongside those units, Android app development is usually the device question that follows.

Fuel Card Purchase Imports

Fuel card programs deliver transactions through files or APIs, each with its own layout, product codes and timing. The platform imports from every program the fleet uses and normalizes them into one fuel ledger.

Each purchase is matched to a vehicle and a location. Card transactions usually carry a unit number entered at the pump, and that entry is wrong often enough that the platform should verify it against where the vehicle actually was at that time.

Purchases outside the card program arrive as receipts. Custom mobile app development for capture at the pump, with the receipt attached to the unit, closes most of the gap.

Text extraction from the image can speed entry, provided a person verifies it, which makes it reasonable AI product and agent development work with the boundary in the same sentence: it never fills gaps in records, generates receipts, edits hours-of-service records, makes qualification decisions or infers proficiency, origin or immigration status.

Bulk fuel from the carrier’s own tanks needs dispensing records tied to units, plus tax-paid status for the bulk purchases themselves.

And the import must never create what was not there. A missing receipt is a gap to investigate, not a transaction to infer from mileage.

Quarterly Return Generation

Return generation is the step where integration quality becomes visible, because every unresolved gap shows up as a number someone has to defend.

The platform totals taxable distance and fuel by jurisdiction and fuel type, applies that quarter’s rates from tables maintained as data, and computes tax due or credit by jurisdiction and the net amount for the base jurisdiction.

Before anything is filed, a person reviews the worksheet: open gaps, fuel economy outliers, jurisdictions with unusual changes from the prior quarter.

Filing itself usually happens through the base jurisdiction’s online portal, many of which accept an upload file but offer no API. Design for preparing a clean file and recording what was filed and when, rather than assuming direct transmission.

Amended returns need the same treatment, with the original preserved beside the amendment.

And the same reconciled distance feeds IRP renewal mileage and any weight-distance tax reports, which is the strongest argument for doing the reconciliation once, properly. The full return, registration and audit features are covered in Carrier Compliance Software Features: What a US Motor Carrier Compliance Department Actually Needs in the First Release.

Driver Qualification File Vaults

A driver file vault is a document store with a requirement model on top, and most of its integrations bring in records the carrier must not alter.

Motor vehicle records arrive through state systems or consumer reporting agencies, which brings Fair Credit Reporting Act disclosure, authorization and adverse action duties along with them. Since June 2025, the record for a CDL driver also carries the medical certification status the carrier must check.

Clearinghouse queries are run in FMCSA’s system with the driver’s consent, and the vault records the query, the consent and the result.

Pre-employment screening reports, previous employer responses and road test records come in as documents with dates and sources. Electronic signature captures applications, consents and acknowledgments.

Drug and alcohol program records from service agents go into a confidential partition with restricted, logged access.

What the vault never does is make the decision. It shows what is complete, what is missing and what is expiring, and it never screens drivers on inferred proficiency, origin or immigration status.

Supporting Connections

Dispatch or the transportation management system, to block assignment of drivers with lapsed qualifications and to supply trip and load documents.

Payroll and expense systems, a source of hours-of-service supporting documents.

Maintenance systems for odometer readings and unit changes.

State fuel tax and IRP portals, usually through prepared upload files rather than APIs.

FMCSA’s Motus system for registration updates, which replaced the legacy portal in 2026. Verify what can be automated before scoping it.

Insurers and safety consultants who request driver and fleet records.

Each connection carries its own onboarding and terms. Confirm them before designing around them.

Reconciliation and Failure Handling

The failure that matters most is silent: a telematics unit that stopped reporting in March, discovered when the return is being prepared in late April.

The others are familiar: fuel attributed to the wrong unit, a card program’s file that failed to arrive, a driver document uploaded to the wrong file, a motor vehicle record that came back unreadable.

Three reconciliations earn their place: GPS distance against odometer readings for each unit every month, fuel purchases against vehicle location at the time of purchase, and every active driver against the requirement model every day. Each exception gets an owner and a resolution record, which is what keeps carrier compliance platform integrations auditable rather than merely connected.

Telematics source count and raw-data retention drive the budget, covered in From MVP to Full Platform: What US Motor Carriers Pay at Each Stage.

Conclusion

Carriers that integrate for evidence rather than convenience, keeping each source’s original data, reconciling distance and fuel once for every report that needs them, treating gaps as investigations, and letting the driver vault inform people rather than decide for them, end up with a platform whose numbers can be defended years later.

In fuel tax and driver compliance, that defensibility is the whole return, and it is what to ask of the software companies in the United States quoting you.

If mixed telematics sources and quarter-end reconciliation are why you are considering a custom platform, designing the raw-data layer and reconciliation first is where most of the value sits.

FAQ