🌐ENESDEFR
← Back to global tracker
🇨🇦

Country deep dive

Canada

Americas · CA
Last updated: 2026-07-21
Compliance model: No mandate — federal B2G runs on SAP Ariba by choice
🍁There is no e-invoicing mandate in Canada — not for B2B, and not for B2G — and none is currently proposed on a fixed timeline. Federal suppliers invoice through CanadaBuys, the procurement portal built on SAP Ariba, and many do so electronically; nothing obliges them to. The CRA accepts any readable format, including paper, and no penalty attaches. This page covers that honest state of affairs.
E-invoicing mandate
B2G VOLUNTARY Suppliers invoice via CanadaBuys (SAP Ariba), most electronically, but none must: CRA accepts paper, no penalty.
B2B NO MANDATE No B2B mandate; CRA accepts invoices in any form, paper or electronic
B2C NO MANDATE No B2C e-invoicing duty; cash register slips or invoices suffice for GST/HST
NO MANDATE
E-reporting
No federal duty. Quebec's WEB-SRM covers restaurants, bars, catering, accommodation and taxis only
6 yrs
Archiving
Keep records and invoices 6 years from end of last tax year they relate to
NOT REQUIRED
Digital signature
No signature required on invoices; CRA cites digital signatures only as optional
SAP Ariba
B2G channel via CanadaBuys
9 fields
CRA-required invoice content
2021
CRA's B2B feasibility study
01

Compliance timeline

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.

2021
2021-06-01In effect
CRA studies a potential B2B e-invoicing mandate (no mandate enacted)

The Canada Revenue Agency began preliminary feasibility research in January 2021, followed by broader 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.

2022
2022-04-01In effect
CanadaBuys (SAP Ariba) becomes the federal procurement channel — electronic invoicing available, not required

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.

2025
2025-01-01In effect
CRA's regulatory plans list digital reporting initiatives — but not e-invoicing by name

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.

02

File format & data specification

Outside federal procurement, Canada doesn't prescribe a format at all — the requirement is about invoice content, not structure.

What CRA actually requires

FormatAny readable format — paper, PDF, or EDI
NumberingNo prescribed format, but must be unique and traceable to your records

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.

The 9 required fields

IdentityBusiness name, GST/HST/Business Number, invoice number, date
TransactionDescription, amount
TaxTax breakdown, total
CommercialPayment terms

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.

For federal government suppliers

Preferred standardsPeppol BIS format or UBL-XML
DeliveryVia SAP Ariba, or any certified Peppol network provider

This is the one place in Canada where structured-format preferences actually exist in writing — everywhere else, content is what matters, not structure.

No Canadian Peppol identifier

CRA Business NumberCannot be used as a Peppol ID
WorkaroundRegister under GLN (scheme 0088) or DUNS (scheme 0060)

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.

Provincial tax variation

Ontario13% HST (combined federal + provincial)
Atlantic provinces (NS, NB, PE, NL)15% HST
Quebec5% GST + 9.975% QST, shown as separate lines (QST calculated on subtotal only)
Alberta, NWT, Nunavut, Yukon5% GST only — no provincial sales tax
Other provinces5% GST plus separately administered PST, per province

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.

03

Scope & transmission

Two entirely separate worlds exist side by side: a federal channel most suppliers now use, and an unregulated everything-else. Neither is a mandate.

Federal B2G (voluntary)

DoD — ~59% of contract dollarsDFARS 252.232-7003: WAWF, mandatory since 2003
Treasury, VA, EPAOwn clauses mandating IPP or an equivalent
GSAElectronic submission incentivised, not required
ScopeFederal agency procurement only — not the DBNAlliance network

Which agency you sell to decides whether you have a duty at all — there is no government-wide rule, and GSA rewards electronic submission rather than requiring it.

Domestic B2B (voluntary)

Common practicePDF email, EDI in established trade sectors
Real-time reportingNone — GST/HST runs entirely on periodic returns

There's no unified national network for domestic B2B — businesses use whatever their trading partner accepts, from paper through to enterprise EDI.

Peppol's actual use case in Canada

Realistic scenarioCross-border — EU/Australian operations invoicing Canadian subsidiaries
Local accreditation neededNone

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.

Provincial & municipal fragmentation

Coordinated frameworkNone
Example pilotVancouver School Board's digital invoicing portal

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.

04

Getting compliant

What "getting ready" means here depends entirely on which side of the federal/everything-else line your business sits on.

If you supply the federal government, register in SAP Ariba via CanadaBuys

This is the one genuinely mandatory step in the entire Canadian landscape — confirm your registration and integration are current.

For everyone else, confirm your invoices carry all 9 CRA-required fields

Business name, GST/HST/Business Number, date, invoice number, description, amount, correct provincial tax breakdown, total, and payment terms.

Get your provincial tax logic right

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.

Choose a Peppol identifier only if you actually need cross-border connectivity

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.

Set up 6-year record retention

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.

Watch CRA's regulatory plan cycle, not a fixed deadline

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.

05

Penalties & enforcement

No penalty framework exists for B2B non-adoption — because there's nothing mandatory to fail to adopt.

06

Related jurisdictions — Americas

Other countries in the same region, ordered by their next dated milestone. Each links to a full briefing.