Transportation ERP Consultant, Canada

One load, two countries, two currencies

Consider a Canadian truckload carrier hauling from southern Ontario to a customer in Ohio, with a return load from Michigan. The outbound rate is in US dollars to a Canadian shipper, the return is billed in US dollars to a US broker, fuel is bought at a Canadian cardlock and a US truck stop, tolls and border costs are paid along the way, and the driver is paid in Canadian dollars. That is one round trip with entries in two currencies and several tax jurisdictions.

Some carriers handle this by converting everything at an average rate in a spreadsheet. The results are hard to defend: a lane looks better or worse depending on the month's rate, and fuel surcharge revenue cannot be compared with fuel cost. I design the load record so every revenue and cost line keeps its original currency and amount, with a documented policy for the rate used in management reporting and a separate treatment for realized exchange gains and losses.

This is different from ERP for Canadian forwarders and customs brokers, who arrange cross-border moves rather than drive them. For the general fleet model, see my ERP for transportation overview.

Owner-operators, company drivers and pay by the kilometer

Canadian fleets often mix company drivers paid by the kilometer, hour or load with owner-operators who supply their own tractor and are paid a rate per kilometer or a share of revenue. Some drivers are incorporated, and how each driver is engaged has tax and employment consequences that your accountant and legal advisors should confirm. The ERP has to follow whichever arrangement the contract sets, cleanly and consistently.

For company drivers, the design sends approved kilometers, hours, border crossings, layovers and other premiums to payroll as inputs. For owner-operators, it produces a settlement statement: gross pay from loads, then fuel bought on the carrier's card, advances, insurance, plate costs, holdbacks and other agreed deductions. Each deduction has a running balance the contractor can see.

Cross-border pay adds detail. Premiums for US runs, per diem treatment and meal costs need rules, and those rules are better encoded in the system than remembered by the payroll clerk. I document them with your payroll provider and test them in UAT with a real pay period that includes US loads, a breakdown and a layover.

Fuel tax, logging devices and provincial permits

Carriers running across provinces and into the United States report fuel and distance by jurisdiction, and registration for vehicles that travel between jurisdictions is typically apportioned by distance as well. The data comes from electronic logging devices or telematics, which record distance and duty status, and from fuel card transactions. Those systems are the record for hours of service and distance; the ERP should consume their summaries, not recreate them.

What the ERP holds is cost and control: fuel invoices reconciled to card statements, fuel cost per unit and per load, the cost of plates, permits and insurance for each tractor and trailer, and a renewal calendar covering safety inspections and driver qualifications. I design the flow from logging data and fuel cards to whichever tool prepares fuel tax reports, with reconciliation points so differences show up early.

Provincial rules add variety. Seasonal weight restrictions in some provinces affect what loads can move, oversize and overweight permits are issued province by province, and inspection regimes differ. The ERP does not need to know the rules themselves, but it should hold each permit as a record with cost, dates and the unit it belongs to. Check current requirements with your safety and compliance provider.

GST/HST, Quebec and invoicing across provinces

How sales tax applies to Canadian freight turns on the place of supply, and continuous freight movements that cross the border can be treated differently from domestic moves. Provinces with HST, those with GST plus a provincial tax, and Quebec with its own sales tax administration each need correct codes on customer invoices and on purchases such as fuel and repairs. I list each charge type and route pattern and ask your accountant to confirm treatment, then configure the ERP so tax codes are applied by rule rather than by memory.

Quebec operations raise another requirement: documents, customer communications and some system screens in French. When I script vendor demonstrations, French invoices and statements are part of the test, not an afterthought.

Fuel bought in the United States, US repair invoices and US tolls also need clean handling for tax recovery purposes, which is another reason to keep original currency and jurisdiction on every line. For wider Canadian ERP topics, my Canada ERP consulting page goes into more depth.

Winter, equipment cost and choosing a platform

Canadian equipment costs have a seasonal shape. Winter brings tire changes, block heaters, fuel additives, more breakdowns and slower trips; spring brings road restrictions in some regions and catch-up maintenance. If maintenance is posted only to a general account, cost per kilometer looks erratic and nobody can tell which units are wearing out. I design unit-level capture for repairs, tires, parts and road service, so seasonality and unit age can be separated.

On systems, a familiar pattern is an accounting package beside a trucking TMS, with spreadsheets for settlements and fuel. The choices are to keep the TMS and strengthen accounting, to build trucking functions into an ERP, or to adopt a trucking suite with its own accounting. I run vendor selection with scripted Canadian scenarios: a cross-border round trip in two currencies, an owner-operator settlement, a Quebec invoice in French and one unit's annual cost.

Delivery is remote, by video workshops and shared documents, scheduled to suit teams spread across Canadian time zones. The Canada hub covers my other work in the country.