Country deep dive
Canada's federal government moved decisively on its own procurement; everything beyond that has stayed at the study-and-signal stage for several years running.
The Canada Revenue Agency begins early-stage research initiatives into e-invoicing — years before any concrete proposal would follow.
The Canada Revenue Agency conducted stakeholder research into a possible domestic B2B e-invoicing mandate. No legislation or firm timeline has followed — GST/HST rules remain format-neutral, and paper, PDF, and EDI invoices are all currently acceptable provided they carry the required tax information.
Since April 2022, Public Services and Procurement Canada (PSPC) has required suppliers to submit invoices electronically through its SAP Ariba-based electronic procurement solution. There is no federal B2B e-invoicing mandate.
CRA's forward regulatory plan includes various digital reporting rules for this period, but none explicitly names an e-invoicing mandate — a signal that the topic remains on the agenda without a committed timeline.
Outside federal procurement, Canada doesn't prescribe a format at all — the requirement is about invoice content, not structure.
CRA doesn't care whether your invoice is structured XML or a scanned PDF — what matters is that it carries the required tax information and can be traced back to your books during an audit.
These fields exist for two reasons: CRA compliance, and enabling your customer's Input Tax Credit claim. Missing the GST/HST number specifically can block your client's ITC entirely.
This is the one place in Canada where structured-format preferences actually exist in writing — everywhere else, content is what matters, not structure.
Because Canada has no national Peppol Authority or identifier scheme, Canadian businesses wanting Peppol connectivity use an international identifier agreed bilaterally with trading partners — there's no local accreditation step to complete.
A static invoice footer that assumes a single tax rate is a real risk for any business selling across provincial lines — the correct tax treatment depends on the customer's province of supply, not your own.
Two entirely separate worlds exist side by side: a mandated federal channel, and an unregulated everything-else.
This is a genuine, existing, unambiguous requirement — if you sell to the Government of Canada, there's no ambiguity about what's expected of you.
There's no unified national network for domestic B2B — businesses use whatever their trading partner accepts, from paper through to enterprise EDI.
Be clear-eyed about this: Peppol adoption in Canada today is driven by multinational groups extending infrastructure they already run elsewhere, not by any domestic push.
A handful of isolated provincial or municipal digital-invoicing pilots exist, but there's no coordinated cross-provincial framework comparable to what's happening federally.
What "getting ready" means here depends entirely on which side of the federal/everything-else line your business sits on.
This is the one genuinely mandatory step in the entire Canadian landscape — confirm your registration and integration are current.
Business name, GST/HST/Business Number, date, invoice number, description, amount, correct provincial tax breakdown, total, and payment terms.
Confirm your invoicing system applies the correct tax treatment based on the customer's province of supply — Ontario HST, Quebec's separate GST/QST lines, or Alberta's GST-only rule all require different logic.
If a European or Australian counterparty requests Peppol connectivity, register under a GLN or DUNS identifier through any standard Access Point — there's no domestic requirement driving this decision.
Keep invoices and supporting documents for at least six years from the end of the relevant tax year — CRA can request them well after the fact during an audit or review.
There's no countdown to plan around — instead, periodically check CRA's published regulatory plans for any future signal that a domestic e-invoicing mandate is moving from study to proposal.
No penalty framework exists for B2B non-adoption — because there's nothing mandatory to fail to adopt.