What is an e-invoice? A beginner's guide to Europe's 2026 deadlines

The short answer: an e-invoice is not simply a PDF sent by email. It is an invoice issued, sent and received as structured data so accounting systems can process it automatically. Think of a PDF as a photograph of the information and a structured e-invoice as the information itself, with each value placed in a labelled field.

There is also no single “Europe-wide 2026 deadline” for every business. Several national mandates reached important stages in 2026, but each country sets its own scope, timetable, formats and delivery route. The EU's VAT in the Digital Age package follows a separate, longer timetable for cross-border digital reporting.

What makes an invoice an e-invoice?

The European Commission defines an e-invoice as one issued, transmitted and received in a structured data format that allows automatic electronic processing. In practice, the invoice still contains familiar information such as supplier and customer details, dates, line items, tax rates and totals. The difference is how that information is packaged and exchanged.

• Paper invoice: a person reads and enters the data.
• PDF invoice: it is digital and easy to view, but it usually remains unstructured.
• Structured e-invoice: software can recognise each field without copying it by hand.

A readable view may accompany the structured file, but the visual version is not what makes it compliant. The European standard EN 16931 defines a common semantic model for core invoice data. National systems can still add rules, choose supported technical formats and require particular networks or platforms. The Commission's beginner overview of e-invoicing explains the distinction in more detail.

Why is Europe changing the process?

Structured data removes repeated manual entry. A buyer's system can validate references, route an invoice for approval and post the accepted data into the accounts. Suppliers can receive status information earlier and correct rejected invoices faster.

Tax authorities are also modernising VAT controls. That does not mean every e-invoice is sent through one EU system. Some countries use a central government platform; others rely on certified providers or networks such as Peppol. Some combine e-invoicing with separate transaction or payment reporting.

What actually happened in 2026?

For a beginner, the most important point is that “Europe” is not one deadline. These examples show why the country and transaction type matter:

• Belgium: structured B2B e-invoicing became mandatory for covered domestic transactions on 1 January 2026. The official Belgian guidance says the structured invoice is the legally required invoice; a voluntary PDF copy does not replace it.
• Poland: mandatory use of KSeF began in stages in 2026. Issuing started on 1 February for the largest taxpayers and on 1 April for most others, with a temporary exception for certain low-volume taxpayers. Receiving through KSeF became mandatory from 1 February.
• France: from 1 September 2026, businesses in scope had to be able to receive e-invoices, while large and mid-sized businesses began issuing them. Small and micro-businesses follow for issuing on 1 September 2027.

These dates are examples, not a complete European compliance calendar. A business may also already face e-invoicing when supplying a public authority. Check the official rules for every country where your legal entities operate rather than relying on the customer's location or a general EU headline.

What about the EU's ViDA timetable?

The VAT in the Digital Age package, usually called ViDA, was adopted in March 2025. It allows Member States to introduce mandatory e-invoicing under the package's conditions and creates a longer-term framework for digital reporting.

The major EU-level date for cross-border B2B digital reporting is 1 July 2030, not 2026 or 2028. Existing domestic real-time reporting systems must align with the EU model by 1 January 2035. The European Commission publishes the current ViDA implementation timeline.

So do not treat ViDA and national B2B mandates as the same project. They are connected, but a national obligation can affect you much sooner.

Who needs to act first?

Your priority depends on where you are established, whom you invoice and what type of transaction you make. Start with these groups:

• businesses already covered by a domestic B2B mandate;
• suppliers to public authorities, where B2G rules may already apply;
• larger companies placed in the first phase of a national rollout;
• every business required to receive structured invoices before it must issue them;
• groups with entities in several countries, because each entity may follow a different calendar.

B2B, B2G and B2C are different flows. Being ready for one does not prove that your process covers the others. The same warning applies to domestic and cross-border invoices.

How does an e-invoice move from seller to buyer?

1. The seller creates an invoice in its accounting or billing software.
2. The software converts the invoice data into the required structured format.
3. An approved platform, national system or delivery network validates and routes it.
4. The buyer's system receives the structured data and may return processing statuses.
5. The parties retain the invoice and related evidence under the applicable storage rules.

Email may still be used for a readable copy or notification, but it is not necessarily the legal delivery channel. Likewise, scanning a paper invoice or using OCR does not turn it into a structured e-invoice.

A practical readiness checklist

1. Map your flows. List each legal entity, country, VAT registration and B2B, B2G or B2C invoice flow.
2. Confirm the official scope. Record the dates for receiving, issuing and any separate reporting obligations. Check exemptions instead of assuming them.
3. Question your software provider precisely. Ask which country mandates, formats, networks, status messages, credit notes and archives it supports. “E-invoicing ready” is too vague.
4. Clean your data. Verify customer identifiers, VAT numbers, addresses, tax codes, payment details and purchase-order references.
5. Test the complete journey. Test receiving as well as issuing, including rejection, correction, cancellation and credit-note scenarios.
6. Assign owners. Decide who monitors failures, updates compliance rules and answers customers and suppliers.

Questions to ask before choosing a solution

• Which countries and transaction types are covered today?
• Is support native, or does it depend on another provider?
• Can we export the original structured invoice and its status history?
• How are validation failures explained and corrected?
• What happens if the delivery platform is temporarily unavailable?
• How are access, retention and personal data handled?

The correct solution is not the one with the longest feature list. It is the one that supports your actual legal entities and invoice flows, produces evidence you can retrieve, and gives your team a workable exception process.

The point to remember

An e-invoice is structured business data, not a prettier PDF. Europe is moving in that direction through national mandates and the EU's longer-term ViDA framework, but the rules do not arrive everywhere at once. Identify the country, entity and transaction first; only then choose the format, channel and deadline that apply.

Before changing the delivery method, make sure the invoice content itself is sound with our invoice essentials checklist.

This article provides general information, not personalised legal or tax advice. Timetables and technical requirements can change. Confirm the current position with the relevant national authority and a qualified adviser before making compliance decisions.