Canadian Trucking — Canadian Hours of Service Compliance and Reporting in Canadian Units (Odoo 19 Community)

Why one more module, and not one more flag

The US foundation's compliance engine holds five rules for both countries, because no duration is written into it: daily driving, daily on-duty time, consecutive rest, driving break, cycle total. Run against a Canadian regime, it reaches the correct findings — and this is proven by a test that feeds it a complete Canadian regime and checks that it errs in neither direction.

Six Canadian rules do not fit this mold, not for lack of parameters but because they cannot be reduced to “a measurement against a ceiling”:

Elapsed time. The Canadian regime does not count a window from the start of duty: it counts the time elapsed between two periods of eight consecutive hours of rest. The starting point is not the same as for the US window.

Total daily rest. Ten hours of rest in the day, of which the consecutive block is only a part. Nothing of the kind exists in the United States.

The two hours outside the block. A rule on how rest is distributed, not on its length: part of the daily rest may not be counted within the eight-hour block.

Daily rest deferral. Four quantified conditions covering two days at once — total rest over the two days, total driving over the two days — and a fifth that is not a duration: a written declaration in the daily log. To our knowledge, this is the only rule in this field where the text requires a written statement. It is checked separately, because a deferral that is fully compliant in its durations but undeclared cannot be relied on in an inspection.

Twenty-four consecutive hours within fourteen days. A rolling window that looks for a block, not a total: two days with twelve hours of rest each do not add up to a twenty-four-hour rest.

Reset and cycle switching. Thirty-six hours for cycle 1, seventy-two for cycle 2, in both directions.

No duration is hard-coded here

As with the base's five rules, each limit is read from the regime record. A field left at zero disables its rule — and that is exactly what happens for the north of the 60th parallel regime, which has no equivalent of the ten-hour daily off-duty, the two hours outside the block, or the deferral. The module then records no finding on these three rules, rather than a wrong one.

The finding, and the line the module does not cross

A finding names a rule, a section, a measurement and a limit. It never names a consequence. What to do next belongs to the carrier; it may depend on split sleeper-berth rest, a ferry crossing, a special permit, an emergency or adverse driving conditions — all situations this module does not know about and does not claim to know about.

The declaration, and the units trap

The quarterly return is the one from the US module, and this is not a shortcut: it is the same agreement. An Ontario carrier files the same return as a Texas carrier.

The change comes down to one sentence: an Ontario-based fleet records kilometers and liters, and the US jurisdictions it travels through publish their rates per gallon. Applying a per-gallon rate to a volume in liters gives a wrong number that looks like a right one — the kind of error an audit catches three years later, with interest. The module therefore shows, line by line, the unit of the published rate and that of the return, and flags the mismatch instead of silently converting. Silent conversion would produce an unverifiable result.

The taxable volume converted using the procedures manual factor is displayed alongside, for reconciliation — never substituted for the consolidated volume.

What this module does not do

It files no return. It is not an electronic logging device. It does not cover the Canadian trip inspection — National Safety Code Standard 13, adopted province by province, could not be obtained as of 09/14/2026 and nothing about it is guessed: see VERIFICATION.md.