E-Invoicing Went Mandatory: Comparing Your Three Automation Routes

What actually changed, in dates

It is worth separating the facts from the noise, because a lot of the commentary published over the summer was wrong about who is obliged to do what and when. Here is the state of play as of today.

• Belgium, 1 January 2026. Domestic B2B e-invoicing between VAT-registered taxpayers became mandatory, exchanged over the Peppol network in Peppol BIS format aligned with the European standard EN 16931. A three-month tolerance period softened the opening weeks.
• Poland, 1 February and 1 April 2026. The national KSeF platform became compulsory for the largest taxpayers — those with 2024 turnover above 200 million złoty — on 1 February, and for essentially all other VAT-registered businesses on 1 April. Micro-entrepreneurs follow on 1 January 2027. From 1 August 2026 the KSeF reference number must be included in bank transfers.
• France, 1 September 2026. Every VAT-registered business must be able to receive structured invoices through an approved platform. Large and intermediate companies must also issue them. Small and micro businesses have until 1 September 2027 to issue — but not to receive.
• Germany, since January 2025. Businesses have had to be able to receive e-invoices for over eighteen months; issuing obligations phase in from 2027.
• The EU, adopted March 2025. The VAT in the Digital Age package, adopted by the Council on 11 March 2025 and published later that month, sets mandatory e-invoicing and near real-time digital reporting for intra-EU B2B transactions from 1 July 2030, with national systems converging on the common model by 2035.

Read together, those dates say something specific: national divergence is the situation for the rest of this decade, and convergence is a 2030s problem. Anything you build now has to tolerate a Belgian invoice arriving over Peppol, a Polish invoice arriving through a state clearance platform, and a French invoice arriving through a private approved platform, all of which mean the same thing commercially and none of which look the same technically.

The preparedness gap is the real story

French readiness surveys taken in the run-up to the deadline make uncomfortable reading. Around 38% of French small and medium businesses had no compliance plan at all. Only about 35% had chosen an approved platform. And roughly 42% of independent firms still believed that emailing a PDF counted as an electronic invoice. The Baromètre France Num data helps explain why: while 69% of small firms have invoicing software and 68% have accounting software, only 23% run a full ERP, so for most of them compliance is not a configuration change inside an existing system. It is a new tool, a new contract and a new integration.

Meanwhile the supply side is crowded. The French tax administration's official register listed roughly 150 approved platforms at the end of August 2026, and it keeps growing as new applicants pass interoperability testing. That is far more suppliers than the market can sustain past the first consolidation wave, which is a risk worth pricing in — as anyone who used Relay.app can attest, having watched its free tier close on 15 August 2026 and paid access end on 14 September. Choosing a compliance provider is a vendor lock-in decision, not just a procurement one.

Why this is an automation story, not a tax story

Compliance teams are treating the mandate as a filing obligation. That framing badly undersells it. For fifteen years, invoice automation projects have spent most of their budget on the least interesting problem in the building: turning a picture of an invoice back into data. Optical character recognition, template training, confidence thresholds, a human reviewing anything under 92% certainty — an entire industry grew up around undoing a lossy conversion that should never have happened.

Mandatory structured invoicing deletes that layer. The invoice arrives as fields, already validated against a European standard, already carrying the supplier's tax identifiers. Whatever you were paying for extraction accuracy becomes free, and the accuracy goes to effectively 100% for the fields the standard covers. That is the upgrade nobody put in the business case.

The size of the prize is well documented. Benchmark data compiled from Ardent Partners and APQC puts best-in-class accounts payable at roughly $2.78 to $2.94 per invoice, against $9.40 to $10.89 for average performers — a differential of around 73%. Touchless processing, the share of invoices that go from receipt to approval with no human intervention, averages 32.6% across the industry and about 49.2% among leaders. Fully manual departments sit somewhere between $12 and $30 per invoice once labour, storage and error correction are loaded in. If you already know where the manual steps in your AP and AR cycle are, the mandate has just removed the hardest technical obstacle to fixing them.

Route 1: the compliance module your existing vendor sells you

Your ERP, accounting package or invoicing tool almost certainly announced an e-invoicing module in the past twelve months. It handles the legal hop: it formats the invoice correctly, hands it to a registered platform or network, receives inbound invoices, and archives everything for the statutory period.

This is genuinely the right answer for a large number of businesses. If you operate in one country, run one system, and your invoice volume is measured in hundreds rather than thousands per month, buying the module and moving on is a rational allocation of attention. The failure mode is subtler than "it doesn't work". It is that the module stops precisely at the edge of the system that sells it. Approval routing that touches Slack or Teams, supplier chasing over email, purchase-order matching against a spreadsheet somebody in operations maintains, pushing payment status back into a CRM — none of that is in scope, and the vendor has no incentive to put it there.

Route 2: a dedicated compliance provider

The second route is contracting directly with a specialist: an approved platform in the French scheme, a Peppol access point in Belgium and much of northern Europe, or an international compliance network that covers both plus Poland, Italy, Spain, Romania and the non-European clearance regimes in Brazil, Mexico, India, Saudi Arabia and Malaysia.

If you invoice across borders, this is close to unavoidable, and the reason is regulatory rather than technical. Each jurisdiction has its own registration regime, its own accepted syntaxes and its own reporting cadence, and keeping up with all of them is a full-time compliance function. Buying that as a service is cheaper than staffing it. The trade-off runs the other way from Route 1: you get excellent coverage of the legal hop and typically a clean API, but the provider knows nothing about your internal process. Their job ends when the invoice is legally transmitted. Yours begins there.

Route 3: an automation layer you own

The third route is not an alternative to the first two so much as the thing that sits above them. A general automation platform — Make, Zapier, Power Automate, Workato, n8n or a self-hosted equivalent — subscribes to the compliance provider's events and orchestrates everything that is specific to your business: routing an invoice to the right approver based on cost centre, chasing a supplier whose invoice failed validation, reconciling a three-way match, updating the CRM when a customer pays, escalating a dispute.

Two things about this layer changed in 2026 and are worth factoring into the decision. First, pricing models moved. Zapier shifted to model-based AI pricing from 15 June 2026, which means the cost of a workflow now depends on what it does rather than only on how often it runs. Second, the agentic layer arrived across the board: Workato shipped Workato ONE with Agent Studio and an enterprise MCP surface, Zapier folded its standalone Agents product into the Zap editor, and Microsoft's Power Automate 2026 release wave 1 ran from April to September 2026 — after which Microsoft stopped publishing release plans for it separately and moved the roadmap under its broader AI at Work programme. Anyone budgeting an invoice automation on last year's pricing sheet should re-run the numbers.

The three routes compared

Five things that break first

The countries already live give a preview of where the failures cluster. In roughly the order they appear:

1. Supplier master data. Structured invoicing requires exact legal identifiers. Directories are matched on registration numbers, not on the trading name somebody typed into your accounting system in 2019. Duplicate, misspelled and merged suppliers surface within the first fortnight.
2. Inbound routing. Invoices stop arriving in the shared mailbox that three people watch. They arrive through an API or a platform inbox nobody has assigned an owner to, and they sit there.
3. Rejections. A structurally invalid invoice is rejected by the platform, not silently accepted. Someone has to notice, interpret the error, and get the supplier to reissue — and that loop is the single highest-value automation in the whole flow.
4. The long tail of suppliers. Your largest vendors will be compliant. The one-person contractor invoicing you €600 a month may not be, and the obligation to receive properly is yours regardless of their readiness.
5. E-reporting, not just e-invoicing. France's regime also requires transaction and payment data reporting for flows outside the domestic B2B scope — B2C sales and cross-border transactions. Teams focused on invoices routinely miss it, and it carries its own penalty line of €250 per missing transmission.

On penalties generally: France set €15 per invoice not issued or received electronically under the original scheme, and the 2026 Finance Bill raised that to €50 per non-compliant document while holding the annual cap at €15,000. Enforcement in the opening phase is intentionally soft — a first breach corrected within 30 days of notice may be waived — and Poland is treating 2026 as a grace year with real fines from 1 January 2027. That leniency is a window, not a reprieve.

A sane sequence for the next 30 days

1. Confirm which obligation actually binds you today. If you are a French small business, receiving is compulsory now; issuing is not until September 2027. Getting this backwards in either direction is expensive.
2. Check the official register directly before signing anything. The tax administration's published list is the only authoritative source for whether a platform is approved, and it changes weekly.
3. Clean your supplier and customer identifiers before you migrate anything. This is unglamorous and it determines whether the first month works.
4. Decide explicitly which route owns the legal hop, and write it down. Ambiguity here is what produces two providers, two invoices and one unresolved audit question.
5. Automate the rejection loop first, not the happy path. The happy path is already handled by the platform. The exceptions are where the labour is.
6. Instrument it. Track touchless rate and cost per invoice from day one, so you can tell whether the mandate improved anything or simply moved the manual work somewhere less visible.

If you are starting from a fully manual process, the guidance in our piece on document and invoice processing still applies to everything downstream of the transmission — with the substantial bonus that the extraction step you were dreading has just been abolished by law.

Where AI belongs in this, and where it does not

There is an obvious temptation to point an AI agent at the whole flow. Resist it on the regulated segment. Transmission, format validation and tax reporting must be deterministic, reproducible and auditable — three properties a probabilistic model does not offer. When a tax authority asks why a specific invoice was reported the way it was, "the model decided" is not an answer.

The edges are a different matter, and they are where the remaining human effort actually sits. Reading an unstructured supplier email that explains why an invoice is late. Drafting a dispute response for a human to approve. Classifying a spend category that the standard does not capture. Summarising a month of rejections into the three supplier onboarding problems causing most of them. Those are judgment tasks with a human checkpoint behind them, which is exactly the shape of work where agents earn their cost. It also keeps you clear of the statistic that should give every buyer pause: industry surveys put the share of agent pilots that never graduate to production at around 88%, with evaluation gaps and governance friction the most cited blockers. A pilot that fails on dispute drafting costs you a quarter. A pilot that fails on tax reporting costs you an audit.

FAQ

What exactly changed on 1 September 2026 in France?

From that date every VAT-registered business in France must be able to receive structured electronic invoices through an approved platform, regardless of its size. Large and intermediate companies must also issue them from the same date. Small and micro businesses get until 1 September 2027 to issue, but the obligation to receive applies to them now. This is the point most commentary got wrong: the 2027 date is only about sending.

Is a PDF invoice sent by email still an electronic invoice?

No, and this is the single most common misunderstanding. A compliant electronic invoice is structured machine-readable data in a format aligned with the European standard EN 16931 — Factur-X, UBL or CII in the French scheme, Peppol BIS in Belgium, the KSeF XML schema in Poland. A flat PDF carries no structured data and does not satisfy any of these mandates. Surveys run before the French deadline found that roughly 42% of independent firms still confused the two.

Which countries are already live and which are next?

Belgium made domestic B2B e-invoicing over the Peppol network mandatory on 1 January 2026. Poland's KSeF system began with the largest taxpayers on 1 February 2026 and extended to most other VAT-registered businesses on 1 April 2026, with micro-entrepreneurs following in January 2027. France went live on 1 September 2026. Germany has required businesses to receive e-invoices since January 2025, with issuing obligations phasing in from 2027. At EU level, the ViDA package adopted in March 2025 sets cross-border digital reporting for July 2030 and full convergence of national systems by 2035.

Should I just use the compliance module my ERP vendor sells?

It is the right answer for a lot of businesses, particularly single-country operations that already run everything inside one system. The trade-off is that the module usually covers only the legal hop — issuing, receiving, archiving — and stops at the boundary of your ERP. Everything around it, such as approval routing, supplier chasing, exception handling and reconciliation with tools outside the ERP, remains yours to build or to do by hand.

What is an approved platform and do I have to pick one?

In the French scheme it is a plateforme agréée, formerly called a plateforme de dématérialisation partenaire, registered by the tax administration to transmit invoices and report data on your behalf. Around 150 of them were on the official register at the end of August 2026. You must route your invoices through one — the state portal was scaled back and no longer plays that role for everyone. In Belgium and most of the rest of Europe the equivalent is a Peppol access point.

Does mandatory e-invoicing actually make automation easier?

Yes, and this is the underrated part. Most invoice automation projects spent their budget on optical character recognition and on guessing which number on a PDF was the total. Structured invoices remove that step entirely, which is why the mandate is better read as a free data-quality upgrade. Benchmark data compiled from Ardent Partners and APQC puts best-in-class accounts payable at roughly $2.78 to $2.94 per invoice against $9.40 to $10.89 for average performers, with touchless processing rates of about 49% for leaders versus a 32.6% industry average.

Where does an AI agent fit into an e-invoicing flow?

Narrowly, and never on the legal hop. Transmission, format validation and tax reporting must be deterministic and auditable. An agent is useful on the messy edges — reading an unstructured supplier email, drafting a dispute reply, explaining a mismatch to a human — where a wrong answer is caught before it becomes a filing. Given that industry surveys put the share of agent pilots failing to reach production at around 88%, putting one on the compliance path is an avoidable risk.

What are the penalties for getting this wrong?

In France the original scheme set a fine of €15 per invoice not issued or received electronically, and the 2026 Finance Bill raised the figure to €50 per non-compliant document, with the annual cap held at €15,000. E-reporting failures carry €250 per missing transmission under the same cap. Enforcement in the opening phase is deliberately lenient: a first breach corrected within 30 days of notice can be waived. Poland is running 2026 as a grace period with strict enforcement starting 1 January 2027.