TL;DR
E-invoicing means exchanging invoices as structured, machine-readable data rather than as PDFs or paper. A wave of national mandates is making it compulsory, with major deadlines across Europe, the Middle East, and Asia through 2026 and beyond. Achieving compliance solves transmission and format. It does not resolve matching, coding, or exceptions, and most organizations will handle structured and unstructured invoices side by side for years.
Key Takeaways: An e-invoice is structured data, so a PDF emailed to a supplier does not qualify. Mandates differ by country in format, network, and timeline, which makes multinational compliance a fragmented problem. Peppol and EN 16931 provide common foundations but are not universal. Compliance addresses how invoices arrive, not what happens next. Most AP teams will run hybrid intake indefinitely, since suppliers below thresholds and outside mandated markets keep sending PDFs.
What is e-invoicing?
E-invoicing, or electronic invoicing, is the exchange of invoices between a supplier and a buyer as structured, machine-readable data that can be processed automatically by both parties' systems without manual re-keying.
The important distinction, and the one that trips up most teams first encountering a mandate, is that a digital invoice is not the same as an electronic invoice. A PDF attached to an email is digital, but it is unstructured, a human-readable document that a machine has to interpret. A true e-invoice carries the same information as structured data fields in a defined schema, so the receiving system can read the supplier, line items, tax treatment, and totals directly.
Hybrid formats occupy a middle ground. Factur-X in France and ZUGFeRD in Germany embed structured XML inside a PDF, so the document is readable by both a person and a machine. These are common transitional formats where mandates are phasing in.
Why e-invoicing matters now
E-invoicing has existed for decades in specific supply chains, largely through EDI. What changed is that governments made it compulsory, and for a reason that has little to do with efficiency: VAT collection. Structured invoice data gives tax authorities visibility into transactions, which narrows the VAT gap.
Two broad regulatory models have emerged. Under a clearance model, the tax authority validates or approves the invoice before or as it reaches the buyer, so the government sits in the transaction flow. Poland's KSeF works this way, as do systems in several Latin American countries. Under a post-audit model, invoices are exchanged directly between the parties and reported to the authority afterwards, which has been the traditional European approach.
Mandates also typically arrive in sequence. Business-to-government e-invoicing comes first, since the public sector can mandate its own suppliers, and business-to-business mandates follow. Most EU countries have had B2G requirements in place for some time, which is why the current B2B wave feels sudden but has been building.
The 2026 mandate wave
The current cluster of deadlines reflects a specific regulatory change. The EU's VAT in the Digital Age package, formally adopted in March 2025, removed the requirement for member states to seek permission from Brussels before mandating domestic e-invoicing. Once that constraint lifted, several countries announced firm timelines at once.
Key milestones as of publication:
Belgium went live on 1 January 2026 with a B2B mandate covering all taxable persons simultaneously, exchanged over the Peppol network using Peppol BIS Billing 3.0. A penalty tolerance period ran to 31 March 2026, after which a progressive fine regime took effect. It is the most far-reaching fully active B2B Peppol mandate in the EU.
Poland began phasing in KSeF from 1 February 2026 for taxpayers above PLN 200 million in turnover, with most other VAT-registered businesses following in April 2026 and the smallest taxpayers in January 2027. Invoices must pass through KSeF in the national XML format before they are legally delivered.
France requires every VAT-registered business to be able to receive e-invoices from 1 September 2026, with large and mid-sized enterprises also required to issue from that date and smaller businesses following in September 2027. France routes invoices through certified platforms rather than the public Peppol network directly. The authorities have repeatedly ruled out a delay, though they have signalled that documented good-faith compliance efforts will not be penalised immediately.
Germany has required businesses to be capable of receiving e-invoices since January 2025. Issuing obligations begin in January 2027 for companies above EUR 800,000 in prior-year turnover and January 2028 for all other domestic B2B businesses.
Spain is the cautionary case. Its VeriFactu regime was due to start in 2026 but has been deferred by a year, to January 2027 for corporate income tax payers and July 2027 for everyone else, and the separate Crea y Crece B2B mandate is not expected before 2027 either. Saudi Arabia continued expanding its ZATCA waves through the year, and India operates one of the largest existing systems, requiring businesses above a turnover threshold to register invoices with an authorised portal and obtain an Invoice Registration Number.
Looking further out, ViDA makes structured e-invoicing mandatory for intra-EU B2B transactions from 1 July 2030, with domestic regimes expected to harmonize afterwards and the wider package rolling out to 2035. Because mandate timetables shift, and Spain shows they shift late, verify current requirements for each jurisdiction you trade in rather than relying on any published summary, including this one.
Formats, standards, and networks
Three layers matter, and conflating them causes confusion.
The data standard. EN 16931 is the European core data model defining what an e-invoice must contain. It supports two syntaxes, UBL and UN/CEFACT CII. Most European mandates require one or both, often through a national variant that narrows the standard for local rules.
The network. Peppol is the most widely adopted exchange framework, using a four-corner model in which buyer and supplier each connect through certified Access Points that handle delivery and validation. As of mid-2026 it spans more than four million registered participants across over 100 countries, with dedicated national Peppol authorities in more than twenty. Belgium alone accounts for roughly two million of those participants, which shows how quickly a mandate drives registration.
National platforms. Peppol is not universal. Italy uses SDI, Poland uses KSeF, Romania uses e-Factura, and France uses its own certified platform model. Outside Europe, formats diverge further, with distinct national schemas in Mexico, Malaysia, India, and elsewhere.
The practical consequence for a multinational is that there is no single e-invoicing implementation. There is a portfolio of them, with different formats, channels, validation rules, and go-live dates, and the portfolio changes as new mandates arrive.
What compliance solves, and what it does not
This is the part worth being precise about, because it determines what e-invoicing actually changes in your finance operation.
What mandates solve. Transmission and format. Invoices arrive as structured data in a known schema, validated for completeness, through a defined channel. Re-keying from a PDF disappears for those invoices. Tax reporting becomes more automatic. These are genuine improvements.
What mandates do not solve. Everything that happens after arrival. A structured e-invoice still has to be matched against a purchase order and goods receipt, coded to the correct account and cost centre, routed for approval, and reconciled. If the quantity billed does not match what was received, the invoice being structured does not resolve the discrepancy. It just means the discrepancy arrives in clean XML.
Put plainly, a mandate guarantees the invoice is well-formed. It says nothing about whether the invoice is correct, whether it corresponds to something you ordered, or whether it should be paid.
This distinction matters because compliance programmes are often justified internally on efficiency grounds, and teams are surprised when compliance lands and the AP workload has not fallen proportionally. The exception queue was never made of formatting problems.
The hybrid reality
There is a second reason e-invoicing does not eliminate unstructured intake, and it persists far longer than most compliance roadmaps assume.
Mandates apply by jurisdiction and often by company size. A multinational will therefore receive structured e-invoices from suppliers in mandated markets above the relevant thresholds, and PDFs and emails from everyone else: suppliers in countries with no B2B mandate, suppliers below turnover thresholds, and suppliers in markets like the United States where there is no federal requirement.
So the realistic intake picture for most AP functions is not a migration from unstructured to structured. It is permanent coexistence, with the structured share rising gradually as mandates expand. Any AP process that only handles clean structured input will keep routing the remainder to people.
Where automation fits
Given that split, the useful question is not how to become compliant, which is a project with a defined scope and specialist vendors, but how to handle everything compliance does not cover.
Two capabilities matter. The first is reading the non-compliant tail: invoices arriving as PDFs, scans, and email attachments in inconsistent supplier formats, and extracting them reliably enough to enter the same process as structured invoices. The second is resolving exceptions regardless of how the invoice arrived: mismatches against purchase orders and receipts, missing or incorrect coding, invoices without a PO at all, and discrepancies requiring judgment about what actually happened.
Both are interpretation problems rather than formatting problems, which is why they survived every previous wave of invoice automation and will survive this one.
Because these determinations feed payment decisions and the financial statements, they need to be explainable. An exception cleared through logic nobody can inspect is a control weakness, and in a tax-driven regime where authorities have structured visibility into your transactions, being unable to explain why an invoice was approved is a poor position to be in.
This is the frame Kognitos works on, and the boundary is important. Kognitos is not an e-invoicing network, a Peppol Access Point, or a tax compliance platform. Specialist providers handle format validation, clearance submission, network connectivity, and archiving, and those should remain in place, because compliance is their domain. Kognitos is the reasoning and exception layer that works alongside them and your ERP: reading the unstructured invoices that fall outside mandate scope, and resolving the matching, coding, and exception decisions that structured formatting never addressed, in deterministic, English as code logic so every decision is explainable and produces a complete audit trail. The compliance platform ensures the invoice is valid and delivered; Kognitos determines whether it is correct and what to do about it.
Getting started
If a mandate is approaching, treat compliance and process improvement as two separate workstreams with different owners and different success measures. Compliance has a hard deadline and a specialist answer. Workload reduction does not follow automatically from it.
The useful diagnostic is to look at your current exception rate and ask how many of those exceptions are caused by the invoice format rather than by a genuine discrepancy. In most AP functions the answer is a small minority, which tells you how much of the queue a structured format will remove, and how much will still be waiting for someone the day after go-live.
For related processes, see our guides on accounts payable automation, invoice coding automation and GL assignment, non-PO invoice automation, two-way vs three-way vs four-way matching, and indirect tax automation. To see how deterministic AI handles the invoices and exceptions compliance does not cover, book a demo or try the platform.
