Odoo e-invoicing in Canada
The Canada e-invoicing picture in full: the scheme, the authority behind it, who it binds, and every requirement we map before a build is quoted.
No national e-invoicing scheme. Federal B2G e-invoicing over Peppol using UBL, plus a Quebec sector fiscalisation regime (WEB-SRM)
Authority: No Peppol Authority exists for Canada. The Canada Revenue Agency sets invoice and record-keeping rules; Revenu Quebec runs the Quebec sales recording regime
Canada has no B2B or B2C e-invoicing mandate as of 2026-08-22, and a PDF invoice is still legally fine. E-invoicing only bites in federal procurement and in two Quebec sectors.
Suppliers to the federal government, where the buying department requires electronic invoices. Separately, Quebec restaurants, bars, caterers and food trucks must run a certified sales recording system that reports to Revenu Quebec.
Every requirement, in full
5 requirements. Each one has to end up as a field, a document layout, a stored response, or an API call in your Odoo build. This is the list an e-invoicing project in Canada gets costed against.
- 1 Nothing structured for ordinary domestic B2B trade: no XML, no clearance, no real-time reporting, no QR code, no accredited intermediary.
- 2 Federal government e-invoices are exchanged in UBL format, over the Peppol network, which was introduced in Canada in 2018.
- 3 Records supporting a GST/HST position must be archived for 6 years from the end of the fiscal year, and the system must preserve confidentiality, integrity and availability. Archiving abroad is allowed with conditions.
- 4 Quebec restaurants: a certified sales recording system feeding the WEB-SRM cloud. New businesses registered after 1 November 2023 had to use WEB-SRM immediately; established businesses had until 31 May 2025 to move off a physical SRM.
- 5 Canada is not on the Peppol Authority list, so there is no domestic Peppol governance body or Canadian identifier scheme to register with.
Checked Localization notes on this page checked on 22 August 2026.
Rates, formats, thresholds and submission windows change. We configure against the rules in force at build time and confirm every figure with your accountant or tax advisor before sign-off. If a rule moves after go-live, it is a support ticket, not a rebuild. Read more on our Odoo localization service.
How we build e-invoicing for Canada
The delivery method behind the list above. The same four steps on a 10-user rollout and on a multi-company programme, with the depth scaled to the scope.
- 1 Requirements first, code second. Each line above becomes a field, a report, or an API call on a written mapping sheet. Anything with no home in Odoo is quoted as a build before the project starts.
- 2 Numbering is settled on day one. Invoice sequences are the part that breaks quietly and costs the most to unwind after go-live, so they are signed off before the first test document.
- 3 Submission runs from a queue. Retries, idempotency keys, stored responses and an audit trail. A failed send becomes a ticket with evidence, not a missing invoice you find at month end.
- 4 Your finance team signs it off. Real documents, in a test database, checked with your accountant or tax advisor before cutover, with a rollback plan in writing.
What we need from you to quote it
Bring these to the first call and you get a scoped, priced e-invoicing plan for Canada instead of a range.
- โ Your tax registration details and the entity each one belongs to.
- โ A sample of every document type you issue: invoice, credit note, debit note, self-billing if you use it.
- โ Any registration, certificate or portal credential the authority has already issued you.
Services behind this work
The rest of the Canada localization detail
Each topic has its own page with the full item list, the same way this one does.
E-invoicing in other markets we cover
Running the same rollout across borders? These pages carry the same depth for each market, so you can compare before scoping a multi-country phase.
Scope e-invoicing for your Canada rollout.
Send us the list above with your answers against it. We come back with what is configuration, what is a connector, and what is a build, priced before the project starts.