E-Invoicing - The Mandates, the Dates, and the PDFs That Ignore Them

E-invoicing is the exchange of invoice data in a structured, machine-readable format such as XML or UBL, passed straight from a supplier's system into a buyer's with no manual data entry in between. Governments across Europe, Asia and Latin America are making it compulsory on published timetables, and the first deadline that hits you is almost never the one you were told about. It is the date you have to start receiving, and it usually applies to every business at once, regardless of size.

This guide covers what qualifies as an e-invoice, which mandate applies to you and when, and the part that decides how much work this actually is: the suppliers who will still be emailing you PDFs long after the deadline has passed.

Key takeaways

• An e-invoice is data, not a document. If a person has to read the layout to find the total, it is not an e-invoice, whatever the file extension claims.
• Your real deadline is the receiving date, not the issuing date. In every timetable published so far, the duty to receive lands first and lands on everyone at the same time.
• Obligations follow where a business is established and where it trades, not where the parent is headquartered. A US group with a French subsidiary has a French entity inside the French mandate.
• The staging guarantees a hybrid period measured in years. Structured invoices and emailed PDFs land side by side, and both have to reach your accounting system.

What is e-invoicing?

E-invoicing, or electronic invoicing, is the digital exchange of invoice documents between businesses in a structured format that receiving software can process without human interpretation. Instead of a person reading an invoice and typing its contents into an accounting system, the invoice arrives as fielded data that the system imports directly. (Source: Basware)

The distinction that matters is machine readability, not digitisation. A scanned invoice, an emailed PDF and a photographed receipt are all digital. None of them is an e-invoice, because none of them carries the data in fields that software can read directly. (Source: Thomson Reuters)

The money has noticed. The global e-invoicing market reached $13.5 billion in 2023 and is forecast to grow at a CAGR of 17.7% from 2024 to 2032, reaching $60.9 billion by 2032. (Source: HighRadius, figures as published in 2024.)

Adoption tells a quieter story. In the United States, where nothing is compulsory, take-up among companies was reported at 25%, while automated electronic invoicing is reported to deliver cost reductions of 60 to 80% in most cases. (Source: Pagero) The gap between those two numbers is the whole argument for the mandates. For context on the wider readiness picture, 70% of businesses across the EU had reached a basic level of digital intensity in 2022, and the EU target is for at least 80% of adults to have basic digital skills by 2030. (Source: IMARC Group)

What makes an invoice an e-invoice

Four things have to be true at once.

• Structured, machine-readable data. The invoice arrives as XML, UBL or an equivalent schema, which accounting software and tax authorities read directly. Nobody keys anything.
• A defined transmission route. E-invoices travel through agreed channels: the Peppol network, a direct API, a government clearance platform. An attachment on an ordinary email is not one of them.
• Integration with the receiving system. The data lands inside ERP and accounting systems as data, which is what makes automated approval and real-time reconciliation possible.
• Compliance with a published standard. In Europe that means EN 16931. Structured but non-compliant still fails a mandate.

What does not qualify as an e-invoice

Plenty of things feel like they should count. Under every published mandate, these are all still ordinary invoices:

1. Scanned paper invoices. Turning paper into a PDF or a JPEG produces an image, not data.
2. PDF and Word invoices sent by email. The most common invoice format in business, and the clearest example of a digital document that is not an e-invoice.
3. Invoice details typed into an email body. No structure, no schema, nothing to import.
4. Spreadsheets without a defined schema. Columns a human understands are not machine-readable in the sense a mandate means.
5. Paper invoices carrying a QR code. The code helps a person. The invoice still gets handled by hand unless it is wired into an e-invoicing platform.

One exception is worth knowing, because it confuses people constantly. Hybrid formats such as Factur-X and ZUGFeRD embed structured XML inside a PDF file. The result opens like a normal PDF for a person and reads like structured data for a machine, and it does satisfy the mandates that accept it. The file extension tells you nothing. What is inside it does.

How e-invoicing works

The route varies by country and by network. The sequence rarely does. (Source: HighRadius)

1. Generation. The supplier's billing or ERP system produces the invoice as a structured file rather than something printable. (Source: Pagero)
2. Validation. The file is checked against format rules, and in countries that put the tax authority in the middle of the transaction, against its requirements too, before the invoice goes anywhere.
3. Transmission. The invoice moves through an agreed channel such as Peppol, EDI or a government platform.
4. Processing and approval. The buyer's system imports the data, matches it against purchase orders and routes it for approval.
5. Payment and archiving. Approved invoices trigger payment, then sit in storage until an auditor asks for them.

The four models e-invoices actually arrive through

Vendor lists are the usual way to explain this, and they answer the wrong question. What a finance team needs to know is what lands in its inbox and how it got there. Sorted by route, there are four models.

1. Network-based exchange, usually Peppol

Peppol, short for Pan-European Public Procurement OnLine, is a network with common rules for addressing, formatting and delivering documents. You do not connect to it directly, you connect through a certified Access Point that handles routing. It is the mandated or default route across much of the EU and in Singapore, Australia and New Zealand. (Source: European Commission)

2. Direct EDI

Electronic Data Interchange predates e-invoicing mandates by decades and still moves enormous volumes in manufacturing, retail and logistics. Formats such as EDIFACT and ANSI X12 are exchanged bilaterally between trading partners who agreed the specification in advance. EDI can satisfy a mandate where it meets the required standard. It does not do so automatically.

3. Government clearance platforms

Some countries put the tax authority in the middle of the transaction, so an invoice is not valid until the government system has cleared it. Italy's Sistema di Interscambio and India's GST e-invoicing portal both work this way. Clearance gives tax authorities real-time visibility, which is exactly why governments like it.

4. ERP and accounting integration

Most major ERP platforms now handle e-invoicing natively or through certified partners. For many businesses this is the least disruptive route, because the invoice never leaves the system of record.

Who must comply, and when

Start with the test, not the table. A mandate applies where a business is established and where it trades, not where its parent is headquartered. A US or UK group with a French subsidiary has a French entity sitting inside the French mandate on the French timetable, and the parent's own domestic rules are irrelevant to that. In France the receiving obligation from 1 September 2026 covers every business established there regardless of size, while the first issuing wave covers large enterprises and mid-caps, the French ETI tier that sits between SMEs and large enterprises.

Dates slip. Treat any timetable here as something to re-check rather than something to file. The figures below were verified in August 2026.

E-invoicing in the European Union

Directive 2014/55/EU established e-invoicing for business-to-government transactions and set EN 16931 as the European standard. The bigger change is ViDA, or VAT in the Digital Age, adopted on 11 March 2025. From 1 July 2030, e-invoicing to EN 16931 becomes mandatory for intra-Community B2B transactions, with transaction data reported to tax authorities within ten days of the chargeable event. Member states operating their own domestic digital reporting systems have until 2035 to align them.

Several member states are running ahead of that timetable. Italy has required B2B e-invoicing for years. Germany's receiving obligation took effect in January 2025. France's first phase begins in September 2026, and it is the one to watch, for two reasons. It drops the receiving obligation on every business at once, and it mandates e-reporting alongside e-invoicing. E-reporting is the separate obligation to send transaction data to the tax authority, so a company can be perfectly able to issue compliant invoices and still be short of what France asks for.

E-invoicing in the United States

The United States has no federal B2B mandate and none scheduled. Federal procurement is the exception: the Bureau of the Fiscal Service directs agencies to manage invoices for federal procurements electronically, so suppliers to federal agencies meet it there. Private-sector adoption is being pushed instead by trading partners and by the Digital Business Networks Alliance, which is building an interoperable exchange framework along the lines of Peppol.

The catch for US finance teams is that having no mandate at home does not keep you out of one abroad. An American group with an EU entity inherits that entity's obligations, and an American supplier billing an EU customer may be asked for a compliant format by the customer rather than by a regulator.

E-invoicing elsewhere

India mandates e-invoicing under GST for businesses above a turnover threshold, routed through the government portal. Singapore runs on the Peppol framework through InvoiceNow, phased across GST-registered businesses. China is rolling out fully digitised e-fapiao nationally through the tax system, and Japan's Qualified Invoice System has applied since 2023. The United Kingdom has no general mandate and drives digital record-keeping and VAT reporting through Making Tax Digital instead. (Source: Qvalia)

As of January 2024, more than 19 countries mandated e-invoicing for all taxable transactions and 49 countries required it for specific transactions. (Source: COST) Both numbers have grown since.

What e-invoicing actually gets you

Governments want e-invoicing because it closes the VAT gap and makes fraud harder to hide. (Source: Tipalti) A finance team wants it for reasons closer to the desk.

Printing, postage, storage and manual keying all disappear on the invoices that arrive structured. Speed follows: some companies report cutting invoice processing from several weeks to under 48 hours. (Source: Basware) Because the data is validated at source, the transcription errors that come with manual data entry go with it, and so do the duplicate payments that follow them.

Two more benefits get less attention and matter most on the day someone asks awkward questions. Tax validation happens inside the exchange instead of being reconstructed at quarter end, and every invoice carries a verifiable trail, which is the difference between an audit and an archaeology project.

Note what none of that applies to. Every one of these gains lands only on the invoices that actually arrive structured. On the rest, nothing changes.

The supplier who has not switched

This is the part that decides your actual workload, and it is usually a footnote.

Every mandate published so far separates the duty to receive from the duty to issue, then phases the second one by company size. France requires every business to be able to receive structured invoices from September 2026 but does not require smaller companies to issue them until September 2027. Germany has required receiving since January 2025 and does not require issuing from everyone until January 2028.

Read that from the buyer's side and the consequence is unavoidable. For a period measured in years, a mid-sized company will receive structured e-invoices from its largest suppliers and emailed PDFs from everyone else, and both have to end up in the same accounting system. Add the suppliers in countries with no mandate at all, and the PDF pile never reaches zero. It only stops growing.

There are two honest ways to handle the remainder.

One is an AP automation platform that runs its own Peppol Access Point and bolts OCR onto the side. For a large AP function that also needs approval routing, purchase order matching and supplier onboarding in one place, that is the right answer. It is also a substantial piece of software, with a price and an implementation timeline to match.

The other is to keep the two flows separate and give each one a tool built for it. Your Access Point provider handles the structured invoices. An AI document parser reads the PDFs and delivers the same fields to the same destination.

That second flow is where Parseur fits, and the boundary is worth stating plainly. Parseur is not an e-invoicing platform. It is not a Peppol Access Point, it does not transmit invoices, and it will not make you compliant with any mandate. What it does is take the invoices that were never going to be compliant in the first place and stop anyone retyping them.

The mechanism is deliberately unglamorous. Suppliers email PDF invoices to a dedicated Parseur mailbox, or you forward them there. The Vision AI engine reads each one and pulls out the fields you need, invoice number, supplier name, dates, line items, tax and totals, with no template built per supplier layout. The extracted data goes to your accounting system, ERP, spreadsheet or API, through a direct integration or a platform like Zapier or Make. A layout the engine has never seen is handled like one it has, which matters, because the long tail of non-compliant suppliers is exactly the part of your supplier base that keeps changing.

If you want the detail on that path rather than the summary, the invoice processing guide covers the workflow end to end, and the invoice data extraction page lists the fields captured by default.

How to prepare

The order matters more than the list, because receiving obligations arrive first and there is no partial credit for being ready to issue.

1. Work out what applies to you, country by country. Obligations follow where you are established and where you trade, not where your head office sits. A US or UK company with a French subsidiary is inside the French mandate.
2. Sort out receiving before issuing. Being unable to accept a compliant invoice from a large customer is the failure that hurts soonest.
3. Choose an Access Point provider if you trade in Peppol territory. This is a procurement decision with lead time, not a switch you flip.
4. Count the suppliers who will not be in scope. Run your supplier list against the thresholds in every country you buy from. The number comes back higher than people expect, and it is what decides how much intake capacity you still need for unstructured invoices.
5. Check that both flows land in one queue. Structured invoices and PDFs arriving into different systems is how a team ends up with two reconciliation processes and no single view of what it owes.
6. Confirm your archiving meets local rules. Retention periods and formats vary by country and stay invisible right up until an audit.
7. Tell your suppliers early. Software is not what slows these projects down. Supplier readiness is.

Where this ends up

E-invoicing stopped being a question of whether some years ago. The published timetables run from France in September 2026 through ViDA in 2030 and domestic alignment by 2035, and the list of countries only grows.

What no timetable changes is the arithmetic on your desk. Thresholds leave most small suppliers outside for years, plenty of trading partners sit in countries with no mandate at all, and every one of those invoices still arrives as a PDF attached to an email that has to reach your accounting system without anyone typing it.

Plan for both and the mandate is a project. Plan for one and it is a surprise.

Last updated on August 6th, 2026