What the mandate wave actually requires
Since 2019, a growing list of governments has required businesses to issue invoices in a structured electronic format rather than PDF or paper, and to route them through or report them to a government system in something close to real time. Italy was first, mandating that all invoices between businesses pass through its centralized Sistema di Interscambio (SdI) platform starting January 1, 2019, with exemptions for small taxpayers phased out by January 2024 (European Commission, 2024).
The list has since grown well past Italy. Germany now requires every business to be able to receive structured e-invoices, a rule in force since January 1, 2025 under the Wachstumschancengesetz (Growth Opportunities Act). Issuance becomes mandatory for businesses with prior-year turnover above 800,000 euros starting January 1, 2027, and for all remaining businesses from January 1, 2028 (EY, 2024).
Poland's national system, KSeF, became mandatory for large taxpayers, those with 2024 turnover above 200 million zloty, on February 1, 2026. The rest of Poland's VAT-registered businesses must comply by April 1, 2026, with a final group of smaller, digitally excluded taxpayers following January 1, 2027 (EY, 2025).
France's mandate lands next. Every company established in France must be able to receive electronic invoices starting September 1, 2026, and large and mid-sized companies must also issue them from that date. Small and micro-enterprises get a longer runway to issue, until September 1, 2027 (EY, 2026).
Behind all of it sits the EU's VAT in the Digital Age package, adopted by the Council on March 11, 2025. It sets a 2030 horizon: from July 1, 2030, e-invoicing in the EN 16931 format becomes mandatory for cross-border transactions between businesses in different EU member states, with near-real-time digital reporting attached to each invoice (Council of the European Union, 2025).
Why now
Two forces are driving this at once. Governments lose a meaningful share of VAT revenue to fraud and reporting gaps every year, and a structured invoice validated by tax authorities before or immediately after issuance closes much of that gap. The second force is technical: structured formats and real-time transmission are now cheap enough to mandate at national scale, which was not true a decade ago.
For procurement and finance teams, the practical effect is the same regardless of motive: invoice formats and workflows that were internal choices become legal requirements with fixed dates and real penalties for missing them.
Two compliance models, and the difference matters
Governments have settled on two broad approaches, and a system built for one will not automatically satisfy the other.
Clearance model. The tax authority (or its platform) validates the invoice before it is legally valid and before, in some cases, it even reaches the buyer. Italy's SdI works this way, as does Poland's KSeF: the invoice does not exist as a valid tax document until the government system has accepted it (European Commission, 2024; EY, 2025).
Decentralized network model. The invoice is valid the moment the supplier issues and delivers it to the buyer, typically through certified access points such as the PEPPOL four-corner network. The tax authority audits later rather than clearing up front. Germany's mandate is built this way, with no central clearance platform for domestic B2B invoices (EY, 2024).
A procure-to-pay or accounts payable system configured for one model will fail silently in a jurisdiction that runs the other. A supplier onboarding flow that assumes post-audit reporting will not produce a legally valid invoice in a clearance jurisdiction, and the failure often surfaces as a blocked payment rather than a clear error message.
What to check before the next system decision
For any organization operating across more than one of these jurisdictions, four questions matter more than vendor feature lists: which compliance model does the vendor support natively in each country you operate in, clearance or network, and is that support certified rather than in development; does the platform already handle the country-specific structured formats in use, such as FatturaPA in Italy, XRechnung or ZUGFeRD in Germany, and the formats France's DGFiP has approved for its own rollout; what happens to a rejected or unvalidated invoice in the workflow, since a clearance rejection has to route back to correction before payment, not sit unresolved in an exception queue; and who owns the compliance mapping as mandates phase in on different dates across different countries, since this is a moving target through at least 2030, not a one-time setup task.
Where procurement teams get caught out
The most common mistake is treating e-invoicing as an accounts payable problem alone. The obligations fall on both the issuer and the receiver, which means supplier-facing procurement processes, catalog and purchase order systems, and supplier onboarding all need to reflect the same format and routing rules as the invoice itself.
The second mistake is timeline assumption. Poland's, Germany's and France's mandates all treat large and mid-sized companies as first movers, with smaller suppliers given later deadlines. A buyer that is ready early can still get blocked by suppliers who are not, so supplier readiness belongs on the same tracking sheet as the buyer's own compliance date.