Quick answer: A TMS (transportation management system) is the software that runs dispatch, invoicing, and driver settlements. An ELD (electronic logging device) tracks hours of service. IFTA is the quarterly fuel-tax report every interstate carrier files. A DVIR is the pre- and post-trip inspection report drivers submit, and IRP is the plate registration system that splits your fees across the states you drive in. Fleet owners run into all five terms within the first month of operating, and mixing them up is the fastest way to misconfigure your software or miss a filing.
Key takeaways
- A TMS and an ELD are not the same category — a TMS manages the business (loads, pay, invoicing), while an ELD is a federally mandated device that records driving hours, per the Federal Motor Carrier Safety Administration (FMCSA).
- IFTA returns are due quarterly, with the FMCSA's own partner agency structure requiring one return per carrier even if you drove in a dozen member jurisdictions.
- A DVIR isn't optional paperwork — FMCSA regulations under 49 CFR 396.11 require a written or electronic inspection report any time a driver finds a defect that could affect safety.
- IRP (International Registration Plan) and IFTA (International Fuel Tax Agreement) are often confused because both involve multi-state fees, but one covers registration and the other covers fuel tax.
What does TMS actually mean in trucking?
TMS stands for transportation management system — the core software a carrier uses to manage loads, dispatch, invoicing, and driver pay in one place. Before TMS software became common, fleets ran this on spreadsheets, paper rate confirmations, and phone calls between dispatch and drivers.
A modern TMS typically touches:
- Dispatch — creating loads, assigning drivers, tracking status from pickup to delivery.
- Invoicing — turning a completed load into a bill for the customer.
- Settlements — calculating what each driver is owed based on pay terms.
- Compliance tracking — flagging expired documents or missing inspections.
- Reporting — weekly statements, fuel tax summaries, and driver pay history.
The confusion usually starts because some tools call themselves "dispatch software" when they only handle load assignment, not the accounting side. We broke down that distinction in detail in TMS Software vs Dispatch Software: Differences — the short version is that dispatch is one function inside a TMS, not a replacement for it.
What's the difference between an ELD and a TMS?
An ELD records hours of service; a TMS runs the rest of the business. They solve different problems and most fleets need both, even though drivers and owners sometimes use the terms interchangeably.
An ELD (electronic logging device) connects to a truck's engine and automatically records driving time, according to FMCSA rules under 49 CFR Part 395. Its job is narrow and federally defined: prove how long a driver has been behind the wheel, so carriers stay within hours-of-service limits.
A TMS has no such narrow mandate — it's built by the software vendor, not required by regulation, and it can include dispatch, invoicing, settlements, and compliance tracking. Some TMS platforms pull ELD data in through an integration so hours-of-service status shows up alongside load and driver information in one place, rather than requiring dispatchers to check a separate ELD portal.
Don't skip this: An ELD keeps you compliant with hours-of-service law. A TMS keeps your business organized. Neither one substitutes for the other — a fleet with a great TMS but no ELD is still out of compliance with FMCSA regulations.
What is IFTA and who has to file it?
IFTA (International Fuel Tax Agreement) is a cooperative arrangement among U.S. states and Canadian provinces that lets a carrier file one fuel tax return covering all member jurisdictions, instead of filing separately in each state it drove through. It applies to qualified motor vehicles — generally trucks with a gross vehicle weight over 26,000 pounds or with three or more axles — operating in more than one member jurisdiction.
Carriers file quarterly, reporting total miles driven and fuel purchased in each jurisdiction, then pay or receive a refund based on where the tax was actually owed versus where fuel was actually bought. Filing deadlines and precise thresholds are set by IFTA, Inc. and administered through each carrier's base jurisdiction, so confirm your state's exact due dates with your base jurisdiction's IFTA office before each filing period.
Manual IFTA calculation means manually pulling fuel receipts and mileage logs by state — a process that eats hours every quarter and is easy to get wrong. We cover the full filing process, common errors, and what records to keep in IFTA Reporting Explained: What Every Fleet Owner Needs to Know.
What is a DVIR and when is one required?
DVIR stands for Driver Vehicle Inspection Report — a written or electronic record of a pre-trip or post-trip inspection that documents the condition of a truck and trailer. Under FMCSA regulation 49 CFR 396.11, a driver must prepare a report at the end of each day of work on every vehicle operated, and the report must note any defect that would affect safety or cause a mechanical breakdown.
Key rules that trip up new fleet owners:
- A DVIR is required even when no defects are found — the report itself, not just the defect, is the compliance requirement.
- If a defect is noted, the carrier must certify the repair was made (or that repair wasn't necessary) before the vehicle is dispatched again.
- Records generally must be kept for a defined retention period — confirm the current requirement with FMCSA, since retention rules can change.
- Electronic DVIRs are permitted and increasingly standard, replacing the old triplicate paper form drivers used to leave in the cab.
The move from paper to app-based DVIR submission is less about convenience and more about the fact that a paper form sitting in a truck cab doesn't stop a dispatcher from assigning a load to a vehicle with an open defect. That gap — and what closes it — is the subject of Paper DVIR Logs vs Mobile DVIR App: Fleet Changes.
IRP vs IFTA: what's actually different?
IRP handles vehicle registration across states; IFTA handles fuel tax across states. Both split a fee proportionally based on where a truck operates, which is exactly why fleet owners mix them up — but they are administered separately and serve different purposes.
| Term | Full name | Covers | Filed | Administered by |
|---|---|---|---|---|
| IRP | International Registration Plan | Vehicle registration fees split across states of operation | Annually, at registration renewal | Base state's IRP office |
| IFTA | International Fuel Tax Agreement | Fuel tax split across states/provinces of operation | Quarterly | Base jurisdiction's IFTA office |
| ELD | Electronic Logging Device (mandate) | Hours-of-service recording | Continuous, not a filing | FMCSA (Part 395) |
| DVIR | Driver Vehicle Inspection Report | Daily vehicle condition and defects | Daily, per vehicle used | FMCSA (Part 396) |
| TMS | Transportation Management System | Dispatch, invoicing, settlements, compliance | Continuous, not a filing | Vendor-defined, not regulatory |
A carrier operating in multiple states pays into IRP once a year based on the proportion of miles driven in each state, and separately files IFTA every quarter based on fuel purchased and consumed in each state. Getting these confused can mean a fleet under-registers a truck for the states it actually runs, or misreports fuel tax because it assumed IRP mileage records automatically satisfy IFTA reporting. They're related data — mileage by state — but two separate filings with two separate agencies.
What other software terms should a fleet owner know?
Beyond the five core terms above, a few more show up constantly in vendor conversations and compliance discussions:
- DOT compliance software — tools that track driver qualification files, inspection history, drug and alcohol testing records, and other items the FMCSA's Compliance, Safety, Accountability (CSA) program monitors.
- Driver settlement software — calculates what a driver earns based on pay terms (per mile, percentage of load, or hourly), factoring in deductions, bonuses, and reimbursements before a statement is generated. This calculates and reports the numbers; the carrier still pays the driver through its own bank or payroll system.
- Cost-per-mile calculator — a tool or spreadsheet method for dividing total operating costs (fuel, maintenance, insurance, driver pay) by miles driven, used to set rates and evaluate load profitability.
- Trucking invoice software — generates and sends bills to customers once a load is delivered, often pulling load details automatically instead of requiring manual re-entry. The gap between manual invoicing and automated invoicing is bigger than it looks on paper — we walk through it in Manual vs Automated Trucking Invoice Software: The Real Gap.
- Driver mobile app — the driver-facing counterpart to a TMS, used for viewing loads, submitting DVIRs and photos of bills of lading, and checking pay statements from a phone.
Here's a quick checklist for a fleet owner evaluating whether their current software actually covers these bases:
- Confirm your ELD is FMCSA-registered and reporting hours-of-service data correctly.
- Check that your DVIR process is either fully electronic or has a clear paper trail with signed defect certifications.
- Verify your IFTA filings are submitted every quarter, not just when someone remembers.
- Review whether your IRP registration reflects your actual current operating states.
- Ask whether your settlement process routes every payable item through a human approval step before it's finalized — not auto-calculated and auto-paid.
- Test whether your dispatch, invoicing, and compliance tools share data, or whether someone is re-typing the same load information three times.
If you're weighing whether to consolidate several of these tools into one system, the questions worth asking a vendor before switching are laid out in 8 Questions Before Switching Trucking Software, and a fuller evaluation framework is in The Best TMS for Trucking Companies: A Buyer's Checklist.
Where a unified system fits into all this
None of these terms live in isolation — a load moves from dispatch, through a DVIR check, into fuel purchases that feed an IFTA report, and ends in a driver settlement and a customer invoice. Yolda is built around that full sequence for U.S. trucking companies: dispatch and a driver mobile app on one side, and DOT compliance tracking, quarterly IFTA calculation, driver settlement reporting, and invoicing on the other. Every payable item — load pay, bonuses, reimbursements — passes through a human review queue before it ever reaches a settlement, and Yolda calculates and reports those numbers while the carrier pays drivers through its own bank.
If your fleet is still juggling separate tools for dispatch, compliance, and fuel tax reporting, or you're just trying to make sense of which term applies to which part of your operation, reach out to Yolda to see how the pieces fit together for a business your size.
