A Canadian manufacturer selling into Europe has spent years treating invoicing as a solved problem: generate a PDF, email it, wait for payment. Across 2026 and 2027 that stops working in several of Canada's larger European markets, and the way it stops working is unusually unforgiving, because the consequence does not arrive as a compliance notice. It arrives as an unpaid receivable.
Key Takeaway
The EU formally adopted the VAT in the Digital Age package on 11 March 2025, removing the requirement that member states obtain a derogation before mandating domestic e-invoicing. National mandates followed immediately: Belgium went live 1 January 2026 for all businesses simultaneously via Peppol; Poland's KSeF clearance system began 1 February 2026 for large taxpayers and 1 April 2026 for most other VAT-registered firms; France begins 1 September 2026, when every VAT-registered business in France must be able to receive e-invoices. Germany has required the ability to receive since January 2025, with issuing obligations phasing in from January 2027. Intra-EU B2B e-invoicing becomes mandatory 1 July 2030 under ViDA. Canada has no equivalent domestic mandate, so Canadian exporters have no home-market process forcing readiness. The practical exposure for most is not a direct legal obligation but a commercial one: non-compliant invoices may be rejected for VAT deduction purposes, which means customers stop accepting them.
The Asymmetry Canadian Exporters Are In
Businesses in Belgium, Poland, France and Germany are being carried into structured e-invoicing by their own domestic mandates. Their accounting software vendors have been building toward it, their advisors have been briefing them, and their peers are doing the same thing on the same timetable. Compliance is a shared local project.
A Canadian exporter has none of that. There is no Canadian mandate creating deadline pressure, no domestic vendor roadmap forcing the upgrade, and no peer group navigating it in parallel. The requirement arrives as an unfamiliar demand from a single foreign customer, often routed to whoever handles that account rather than to anyone thinking about invoicing architecture, and frequently after the deadline rather than before.
That asymmetry, rather than the technical difficulty of e-invoicing itself, is the reason this deserves attention from Canadian finance teams now. The rules are not especially hard. Encountering them for the first time when a large customer's accounts payable system rejects your invoice is what makes them expensive.
Why All At Once: The ViDA Trigger
The clustering of mandates around 2026 and 2027 is not coincidence, and understanding the cause tells you the direction of travel.
In 2024 and 2025 the European Council finalized the VAT in the Digital Age directive, which removed the longstanding requirement that EU member states obtain a derogation from Brussels before mandating domestic e-invoicing; once that door opened, France, Belgium, Poland, Spain and Germany all announced firm rollout schedules clustered around 2026 and 2027[1]. The EU formally adopted the ViDA package on 11 March 2025[1].
ViDA is described as the European Union's comprehensive plan to modernize VAT through digitalization, aiming to simplify cross-border trade, reduce fraud and harmonize e-invoicing and digital reporting across member states, introducing a standardized framework for real-time transaction reporting and making e-invoicing the default invoicing system, while allowing countries to align national models with the new rules[2]. Over the coming years it aims to gradually replace fragmented national systems[2].
The end-state dates matter for planning: intra-EU B2B e-invoicing becomes mandatory 1 July 2030, with domestic e-invoice regimes required to harmonize by 1 January 2035[1]. The interim period, roughly now through 2030, is the fragmented phase in which each country runs its own model, which is precisely the phase that is hardest for a foreign supplier.
The 2026 And 2027 Calendar
The specific dates, because vagueness here is useless.
Belgium. Mandatory B2B e-invoicing went live 1 January 2026 on the Peppol network using BIS 3.0, with a three-month tolerance period for companies that can prove they began compliance work in time[1]. All VAT-registered businesses in Belgium must exchange structured e-invoices via Peppol, in Peppol-BIS format aligned with the European standard EN 16931, and Belgium applied its mandate to all businesses at the same time regardless of company size[3], an approach described elsewhere as a "big bang"[4].
Poland. The KSeF mandate begins 1 February 2026 for businesses above PLN 200 million turnover, 1 April 2026 for most other VAT-registered firms, and 1 January 2027 for micro-entrepreneurs[1]. All invoices must be submitted through KSeF in FA(3) XML format before they are legally considered delivered[3].
France. The mandate begins 1 September 2026 for large and mid-sized companies; from that date every VAT-registered business in France must be able to receive e-invoices[1]. Issuing obligations apply from the same date to large enterprises above €1.5 billion turnover and mid-sized businesses between €250 million and €1.5 billion, with SMEs and micro-businesses required to issue from 1 September 2027[5]. France designated its tax authority, the DGFiP, as the national Peppol Authority in July 2025[6].
Germany. Businesses have been required to receive e-invoices since January 2025, with issuing obligations phasing in from January 2027 for companies with turnover above €800,000 and all companies from 1 January 2028[5][3].
Netherlands. No active domestic B2B mandate currently, but in March 2026 the Dutch Ministry of Finance presented a design framework to Parliament proposing a domestic B2B regime launching January 2030, timed to coincide with ViDA's intra-community requirements[7].
The France Provision That Names Non-Residents
One provision speaks directly to businesses in Canada's position, and it is the single most important sentence in this article for an exporter.
Non-resident companies without a fixed establishment in France must comply with e-reporting rules in 2026 but will not have to issue e-invoices until 2027[4].
Two things follow. First, France has explicitly contemplated foreign suppliers, which means a Canadian business selling into France cannot assume it falls outside the regime simply by being foreign; the distinction drawn is between e-reporting and e-invoicing obligations and between 2026 and 2027, not between resident and exempt. Second, the obligations are staged differently for non-residents than for domestic businesses, which means a Canadian exporter's timeline is genuinely different from its French customer's and should be established specifically rather than inferred from general coverage.
Whether a particular Canadian business has a French VAT registration, a fixed establishment, or neither is determinative here and is a question for tax counsel rather than a general article. What this article can say is that "we are Canadian, so it does not apply to us" is not a safe conclusion, and that the applicable date for a non-resident may be 2027 rather than 2026 for issuing while e-reporting bites earlier.
Three Different Models, Not One Standard
The most operationally significant fact about the current phase is that these are not the same rule implemented on different dates. Forbes summarizes the divergence: Poland ties e-invoicing directly to real-time tax reporting; Belgium focuses first on how invoices are sent, keeping reporting separate; France uses approved private platforms to handle invoice exchange and introduces a new layer of digital reporting[4].
Formats differ accordingly: Peppol-BIS 3.0 and UBL 2.1 in Belgium, FA(3) XML in Poland, with the European standard EN 16931 as the common reference point. Analysis aimed at multi-country operations notes that such businesses need solutions handling varying requirements without separate integrations per country[5].
For a Canadian exporter with customers in two or three European countries, this is the practical problem. There is no single "European e-invoice" to build once. Until ViDA's harmonization dates arrive at the end of this decade, the requirement is country-by-country, which argues strongly for a service provider handling the format and routing differences rather than building anything in-house.
Clearance: When An Invoice Is Not Legally Delivered
Poland's model deserves separate treatment because it changes something more fundamental than format.
Poland uses a clearance model in which the tax authority approves each invoice before it reaches the buyer[3], and all invoices must be submitted through KSeF in FA(3) XML format before they are legally considered delivered[3].
Read that last clause carefully. Under a clearance regime the invoice does not exist as a legal document until the tax authority has processed it. A Canadian supplier emailing a PDF to a Polish customer has not delivered an invoice late or in the wrong format; in the relevant legal sense it has not delivered an invoice at all. Payment terms that run from invoice date do not begin. Aged receivables reports showing the amount as outstanding for thirty days are describing something that has not started.
This is why the framing matters. A format problem gets fixed in a software configuration. A document that does not legally exist is a working capital problem that compounds silently until someone asks why a specific customer's payments have stopped.
The Real Enforcement Mechanism
Most compliance writing frames penalties as the risk. Here the commercial mechanism is sharper and arrives sooner.
Non-compliant invoices may be rejected for VAT deduction purposes[8].
Follow the incentive. A European customer that cannot deduct input VAT on your invoice faces a real cost equal to the VAT rate, which across these markets is a substantial share of the invoice value. That customer will not absorb it. It will require a compliant invoice before paying, and if you cannot produce one it will find a supplier who can.
This inverts the usual compliance calculus in a way Canadian finance teams should register. The party with the strongest incentive to enforce these mandates against a Canadian supplier is not a European tax authority with limited practical reach over a foreign business. It is the customer, who has both immediate financial motivation and complete leverage, because they hold the payment.
It also means the timeline that matters is not the legal deadline but the date your customer's accounts payable system starts rejecting non-conforming documents, which will generally be on or shortly before the deadline and will not be negotiated with you.
Direct Obligation Versus Derived Pressure
Precision matters here, and much coverage is imprecise in a way that could mislead in either direction.
The direct legal obligations described in these mandates generally attach to businesses established or VAT-registered in the country concerned. Belgium's requirement is framed as applying to all VAT-registered businesses in Belgium[3]; France's receiving requirement to every VAT-registered business in France[1]. A Canadian company with no establishment and no local VAT registration may well fall outside the direct obligation in a given country, with France's explicit non-resident provision[4] showing that the position is jurisdiction-specific rather than uniform.
But the derived pressure operates regardless of whether the direct obligation does. If your customer is legally required to receive structured e-invoices and to hold compliant documentation to support its VAT deduction, then its ability to accept a PDF from you is constrained by its own obligations, not by yours. A Canadian supplier can be entirely outside the scope of a foreign mandate and still find its invoices unusable to the customers that mandate covers.
The practical instruction is to stop asking whether the mandate applies to you and start asking whether it applies to your customers. The second question determines whether you get paid; the first determines only whether a foreign authority has jurisdiction to penalize you, which for most Canadian SMEs is the less pressing concern.
What A Structured Invoice Actually Is
A definitional point, because many businesses believe they already comply and do not.
E-invoicing refers to the exchange of invoice data in a structured digital format that allows automatic processing between systems; unlike traditional PDFs or paper invoices, true electronic invoicing involves machine-readable formats such as XML, with the European Union standardizing the approach through frameworks like EN 16931[9].
A PDF is not an electronic invoice for these purposes, and neither is a PDF attached to an email, a scanned document, or an invoice generated electronically and printed. The distinction is machine-readability: the receiving system must be able to parse the fields without a human reading them. Many Canadian businesses that describe themselves as having gone paperless are producing PDFs, which satisfies none of these mandates.
This matters because it determines the size of the project. A business that already produces structured output has a routing and format-mapping problem. A business producing PDFs from a system that cannot emit structured data has a systems problem, and should establish which of those it is before assuming a deadline is achievable.
Peppol, And Why It Matters To You
One piece of infrastructure recurs across mandates and is worth understanding as a strategic choice rather than a technical detail.
Belgium's model relies on the four-corner Peppol framework, where buyers and suppliers exchange invoices via certified Access Points, service providers that ensure every transaction meets security and compliance requirements[6]. France designated the DGFiP as its national Peppol Authority in July 2025, and while Peppol is not explicitly mandated by French law it is the standard interoperability framework envisaged by the reform[6]. Belgium is set to deepen integration further, with continuous transaction reporting from 1 January 2028 possibly using the Peppol five-corner model, mirroring approaches taken in Singapore, the UAE and Oman[6].
For a Canadian exporter the implication is that connecting to Peppol through a certified Access Point provider addresses a meaningful share of European requirements through a single connection, rather than integrating separately with each national system. It does not address everything, Poland's KSeF is a distinct national platform, but it is the closest thing to a common on-ramp available during the fragmented phase.
The Canadian Gap
Canada has no domestic B2B e-invoicing mandate comparable to those described here, which is the source of the asymmetry this article opened with and has a second implication worth naming.
Because no Canadian requirement is driving adoption, Canadian accounting software configurations, ERP implementations and finance processes have had no reason to build structured invoicing capability. A European supplier facing the same mandates typically discovers its existing systems already support the required formats because its vendors built toward the local deadline. A Canadian business frequently discovers the opposite.
There is also a forward-looking consideration. Given ViDA's 2030 and 2035 harmonization dates and the pattern of adoption across Europe, Asia and the Gulf noted below, the probability that structured e-invoicing becomes a general expectation in international trade over the coming decade is high. A Canadian business building this capability for a French customer in 2026 is unlikely to find the investment stranded, which improves the case for doing it properly rather than improvising a workaround for one account.
A Worked Case: The Ninety-Day Surprise
A Canadian industrial components manufacturer with roughly a fifth of revenue in Europe, split between customers in France, Belgium and Germany. The reconstruction below illustrates a recognizable pattern rather than a specific engagement.
The company had heard nothing about e-invoicing until its Belgian customer's accounts payable department began returning invoices in early 2026 with a reference to Peppol. The account manager, treating it as a customer-service issue, resent the PDFs. Payment stopped. By the time the query reached the controller, roughly ninety days of invoices to that customer were outstanding and the customer's position, entirely reasonable, was that it had received no compliant invoice.
Two aggravating factors emerged during remediation. The company's accounting system could not emit structured output without a module it had never licensed, making the fix a systems project rather than a settings change. And the same issue was six months from arriving with its French customers under the 1 September 2026 date, which nobody had connected to the Belgian problem because the two had been treated as separate customer complaints rather than as one regulatory pattern.
The cost was not a penalty. It was a quarter of European receivables aged well beyond terms, a customer relationship strained at exactly the moment a competitor could have solved the problem, and an unplanned systems expenditure executed under deadline pressure at a worse price than it would have commanded with lead time.
What To Do, In Order
Map customers to jurisdictions and dates. Which customers are in Belgium, Poland, France, Germany or Italy, and what proportion of revenue do they represent. This is a half-day exercise and it determines everything else.
Establish whether you can emit structured output at all. Ask your accounting or ERP vendor directly whether the system produces EN 16931-compliant structured invoices, and if so whether it is licensed and configured. Producing PDFs is not compliance.
Determine your own jurisdictional position. Whether you hold local VAT registration or a fixed establishment materially affects your direct obligations, and France's explicit non-resident provision shows this is jurisdiction-specific. This is a question for tax counsel, not for guesswork.
Ask your affected customers what they require. They know, because they are subject to the mandate and have already implemented for it. This is faster and more accurate than researching the requirement independently, and it converts a coming conflict into a cooperative conversation.
Consider a Peppol Access Point provider. A single certified connection addresses a meaningful share of European requirements, and is generally more sensible than country-by-country integration for a business with a handful of European customers.
Reforecast your receivables for affected accounts. If any customer sits in a clearance jurisdiction, model the cash impact of invoices that are not legally delivered, because that risk is a working capital exposure rather than a compliance line item.
Beyond Europe
Europe is the immediate pressure but not the whole picture. Saudi Arabia has continued expanding Phase 2 of its ZATCA Fatoora programme, pulling smaller taxpayers into the mandate[1], and the continuous transaction control approaches Belgium is contemplating for 2028 mirror frameworks already adopted in Singapore, the UAE and Oman[6]. Italy has operated a mandate since 2019[5].
On trajectory, the Billentis global e-invoicing report projects the market will grow at roughly 28% per year between 2024 and 2028, reaching about EUR 22 to 24 billion by 2028[1]. That figure describes vendor revenue rather than adoption directly, and comes from a report commissioned within the industry, so it should be read as directional, but the direction is corroborated by the mandate schedules themselves.
A Canadian exporter with customers in the Gulf or Southeast Asia should treat the European analysis in this article as a template rather than an exhaustive list, and should run the same customer-to-jurisdiction mapping for those markets.
The Limits Of This Analysis
Several caveats matter. Mandate schedules have been revised repeatedly across these jurisdictions, and several sources cited here carry different dates for the same mandate; where sources conflicted we have reported the most consistently corroborated dates, and readers should verify current schedules before relying on any date. Every source cited is industry, vendor or press commentary rather than primary legislation or tax authority guidance, and several are published by e-invoicing solution providers with a commercial interest in urgency. This article deliberately distinguishes direct legal obligation from derived commercial pressure, but whether a specific Canadian business falls within a given mandate depends on its VAT registration and establishment position in each jurisdiction, which is a technical question for qualified tax counsel and is not addressed here. Nothing in this article is tax, legal or VAT advice.
Frequently Asked Questions
Does this apply to me if I am a Canadian company?
Is a PDF invoice acceptable?
What actually happens if I send a non-compliant invoice?
What are the key dates?
Can I build one solution for all of Europe?
Does Canada have a mandate coming?
References
- Billed. (2026, May 20). E-Invoicing Mandates 2026: Country Deadlines And Formats, including ViDA adoption on 11 March 2025, the derogation change, Belgium, Poland and France dates, ZATCA expansion and the Billentis market projection. billed.app/hub/invoicing/e-invoicing-mandates-2026
- Fiskaly. (2025, October 8). E-Invoicing In Europe 2026: Complete Roadmap Of Mandates And Deadlines, on ViDA's objectives and design. fiskaly.com/blog/e-invoicing-mandates-in-europe-2026
- SPS Commerce. E-Invoicing Mandates In Europe: The 2026 Business Guide, on Belgium's Peppol-BIS requirement and EN 16931 alignment, and Poland's KSeF clearance model and FA(3) XML format. spscommerce.com/community/articles/e-invoicing-mandates-in-europe-the-2026-business-guide
- Bal, A. (2025, November 2). 2026: The Year Mandatory E-Invoicing Sweeps Across Europe. Forbes, including the non-resident provision for France and the divergence of national models. forbes.com/sites/aleksandrabal/2025/11/02/2026-the-year-mandatory-e-invoicing-sweeps-across-europe
- Novutech. (2026, May 18). E-Invoicing In Europe: Overview Of Mandates 2025-2027, on France's turnover thresholds and phasing, Germany's schedule and Italy's existing mandate. novutech.com/news/e-invoicing-in-europe-overview-of-mandates-2025-2027
- Fonoa. (2026, April 27). Peppol Adoption In Europe 2026: Key Mandates, ViDA & What's Next, on the four-corner model, Access Points, the DGFiP Peppol Authority designation and Belgium's 2028 plans. fonoa.com/resources/blog/peppol-adoption-europe-2026-mandates-vida
- Lasernet Group. (2026). The Complete Guide To 2026 And 2027 E-Invoicing Mandates, on the Netherlands proposal framework. lasernetgroup.com/news-blogs/complete-guide-to-2026-and-2027-einvoicing-mandates
- Invoice Navigator. (2026, July 12). EU E-Invoicing Deadlines 2026–2030: When Each Country Goes Live, on VAT deduction rejection for non-compliant invoices. Note: published by an e-invoicing validation vendor. invoicenavigator.eu/deadlines
- RTC Suite. (2026, March 30). E-Invoicing In Europe: 2026 Mandates & EU Timeline, on the definition of structured e-invoicing and EN 16931. Note: published by a compliance software vendor. rtcsuite.com/e-invoicing-in-europe
This article discusses foreign e-invoicing mandates and is provided for general informational purposes. It is not tax, VAT or legal advice. Mandate schedules have been revised repeatedly and sources report differing dates; verify current requirements with qualified tax counsel in each jurisdiction before relying on anything stated here.