Four structural requirements decide whether a TMS saves a small carrier time or adds a system to maintain. The rest is preference.
Key takeaways
A 5 to 50 truck carrier should require four things from a transportation management system, in this order: that it holds the records the law already obliges you to keep, in the fields the regulator asks for; that it integrates with a certified electronic logging device rather than a generic GPS feed; that it produces your fuel tax and registration data without re-keying; and that it will give the data back in a readable format when you leave.
Everything else — dashboards, load boards, driver apps, customer portals — is a preference. The four above are structural, and a system that fails any of them will cost more in clerical work than its licence fee.
A TMS is, functionally, a records system that happens to dispatch. Start by listing what you are obliged to hold, because those obligations set the minimum schema.
Read that list against a demo. If the system cannot show you a driver’s six-month chronological duty-status file in one click, it is not a compliance system; it is a dispatch board with storage attached.
The hours-of-service regulations define an electronic logging device as one that automatically records driving time and facilitates the record of duty status, and that is certified by an accredited certification body under section 79.1. Certification is not marketing language; Transport Canada publishes the list of certified devices and a registry of accredited certification bodies.
The standard is also moving. Transport Canada records that the CCMTA Technical Standard for ELDs version 1.3 was made public on 29 September 2025, replacing version 1.2 posted on 27 October 2020, and that it will lead the implementation and coming-into-force process, recognising that providers and certification bodies need a transition period. So a fair question to any TMS vendor is: which certified devices do you integrate with today, and what is your plan for the new standard?
Note also the anti-tampering provision, which is a governance constraint on how you configure the system: nobody may disable, deactivate, disengage, jam, block or degrade a signal, or re-engineer, reprogram or otherwise tamper with an ELD so that it does not accurately record and retain required data, and nobody may enter inaccurate information into a record of duty status or falsify, alter or destroy the records or supporting documents. An edit workflow that quietly overwrites driver logs is a compliance problem regardless of intent.
IFTA reporting is where small carriers lose the most administrative time, and it is entirely mechanical. Ontario’s Interjurisdictional Carrier’s Manual specifies exactly what a distance record must contain, and it maps directly onto TMS fields: trip start and end dates, point of origin and destination, list of highways used, odometer or hubodometer readings at trip start and end and at each jurisdiction’s borders, total trip distance, distance by jurisdiction, power unit or VIN, fleet or unit number, and the registrant’s name.
Fuel records have their own required contents: date of purchase, seller’s name and address, litres purchased, tax paid, fuel type, price per litre or total, the unit number of the vehicle fuelled, and the purchaser’s name. Supplier’s statements are not acceptable fuel receipts, and altered receipts are rejected. If a TMS cannot capture those fields, your quarterly filing stays a spreadsheet exercise.
The cost of getting it wrong is defined. Ontario imposes a penalty of 5 per cent of the net tax due where a return is filed late, payment is short, the return is incomplete, or an amended return produces a substantial increase — with interest based on the Canadian federal Treasury Bill rate plus 2 per cent, adjusted quarterly, accruing a full month for any part of a month unpaid. Returns are due April 30, July 31, October 31 and January 31.
A threshold worth checking before you buy modules
Ontario’s IFTA page defines a qualified motor vehicle as one with two axles and a gross or registered gross vehicle weight over 11,797 kg, three or more axles regardless of weight, or a combination over 11,797 kg with a trailer. On the same page, the International Registration Plan paragraph states that all interjurisdictional carrier vehicles weighing more than 11,793 kg should also register under the International Registration Plan. The two figures are both published by Ontario, on the same page, for the two different programmes. Where an official source gives you two numbers, quote each against its own programme rather than picking one.
This is the requirement carriers skip and regret. Your tax records must be retained in an electronically readable format for six years, and they must be kept at a place of business or residence in Canada, or another place designated by the Minister. If your TMS holds the only copy of your trip, fuel and settlement history and you leave the vendor, you have a records problem, not a procurement one.
Ask three concrete questions before signing: what is the export format and does it include every table or only reports; what happens to your data on termination and after what period; and can you take a full export today, in the trial, without asking support. A vendor that cannot answer the third has answered the first two.
Eighteen power units, Ontario-plated, running into Michigan and Ohio. Current stack: a spreadsheet dispatch board, a standalone ELD portal, and a bookkeeper who rebuilds IFTA from fuel receipts each quarter.
The requirements that follow from the facts: CVOR obligations because the trucks are over 4,500 kg registered gross weight; hours-of-service record retention with the 20-day forwarding and 30-day deposit rule and 6-month chronological file; IFTA distance and fuel records to the field list above, kept four years; and advance commercial data to the CBSA, which requires highway carriers to transmit cargo and conveyance data so that it is received and validated at least one hour before the shipment arrives at the border. The CBSA notes that its eManifest Portal was developed primarily for small and medium-sized businesses, which is the right default for a fleet this size unless the TMS transmits by EDI.
Ranked by hours recovered, the wins are: IFTA automation from trip data the ELD already produces; eManifest transmission from the load record rather than re-keyed into a portal; and a duty-status file that can be produced on request without a scramble. Load boards and analytics come later.
The reliable jobs are document-shaped: reading rate confirmations and bills of lading into structured load records, matching invoices to settlements, and drafting the exception correspondence a dispatcher writes twenty times a day. Those are high-volume, low-judgment tasks with a human check at the end.
What it does not do is decide whether a driver has hours available, whether a load may lawfully be dispatched, or whether a safety event warrants action. Those are determinations with regulatory consequences, and the carrier’s duty to monitor compliance and take remedial action sits with a person.
You need the records. At five trucks a disciplined set of spreadsheets plus a certified ELD can meet the obligations. What breaks first is usually IFTA reconstruction and duty-status retrieval — when those consume more than a day a month, the TMS pays for itself.
Often, for compliance. It is usually weaker on customer-facing work — quoting, documents, invoicing. Buy on where your clerical hours actually go.
Ontario applies a penalty of 5 per cent of the net tax due plus interest, and notes that failure to file may result in your licence being revoked.
No. It holds records and surfaces exceptions. The regulations place the monitoring duty on the carrier, and the anti-tampering and accuracy provisions in section 86 apply to whoever operates the system.
A 30-minute call is enough to tell you whether AI pays for itself in your back office.
