Skip to content
DT Nova

E-invoicing in the EU: ViDA, national mandates and what to prepare

E-invoicing in the EU is moving from optional to mandatory. A growing number of Member States already require structured electronic invoices between businesses, and the EU's VAT in the Digital Age package, ViDA, makes e-invoicing and digital reporting the rule for cross-border business supplies from 1 July 2030. This guide explains the EU rules, the national mandates that apply already, and what to prepare in your invoicing and accounting systems. Sources are listed at the end, each read on 12 November 2026.

What counts as an e-invoice

The key word is structured. Under Council Directive (EU) 2025/516, an electronic invoice is one issued, transmitted and received in a structured electronic format allowing its automated and electronic processing (recital 9). A PDF attached to an email is an invoice in electronic form, but a machine cannot read it reliably, so it is not an e-invoice in the new sense. Hybrid invoices, which combine a human-readable part with embedded structured data, are covered if the structured part includes all the data to be reported.

The common language is the European standard on electronic invoicing, EN 16931, and its list of syntaxes, set up under Directive 2014/55/EU. Article 7 of that Directive requires public contracting authorities to receive and process e-invoices that comply with the standard. ViDA builds on the same standard for business invoices.

ViDA: the EU timeline

DateWhat changesSource
14 April 2025Directive 2025/516 in force (published 25 March 2025). Member States may require domestic e-invoicing without an EU derogation, and may remove the recipient's right to refuse an EN 16931 e-invoiceDirective 2025/516, Articles 1, 6(1) and 7
1 July 2030E-invoicing and digital reporting for intra-EU B2B supplies; e-invoices comply with EN 16931 by default; cross-border invoices issued within 10 days of the chargeable eventDirective 2025/516, Articles 5 and 6(5)
By 1 January 2035Member States with a domestic real-time reporting system in place before 2024 align it with the EU modelDirective 2025/516, Article 6(5)

From 2030, the invoice and the VAT report merge: the data on the e-invoice is what the tax authority receives, close to real time, instead of a recapitulative statement filed later. That is why the structured data has to be right the first time.

National mandates that apply now

Domestic e-invoicing is decided country by country, and several countries started before ViDA. Two examples with official sources:

  • Germany. The Federal Ministry of Finance states that since 1 January 2025, a structured e-invoice is regularly required for supplies between domestic businesses, and that a plain PDF no longer counts as one. Businesses must be able to receive e-invoices; for issuing, paper and other formats remain possible until 31 December 2026, and until the end of 2027 for issuers whose prior-year turnover is up to 800,000 euro (BMF FAQ on the e-invoice, page dated 29 October 2026).
  • France. The French public service portal states that e-invoicing is introduced progressively from 1 September 2026, first for large companies and mid-sized companies, then extended to SMEs and micro-enterprises from 1 September 2027, with new mandatory invoice mentions (Entreprendre Service Public, Mentions obligatoires sur une facture, checked 11 August 2026).

Other Member States have their own models, such as central government platforms or national networks. Because the rules and dates change, we check the official source for each country where you invoice before any build work begins, and set the system up per country.

Formats and networks

EN 16931 defines the content of an invoice, and the syntaxes define how it is written as a file. In practice you meet a handful of names:

  • UBL and UN/CEFACT CII: the two XML syntaxes on the EN 16931 list.
  • National profiles built on them, such as XRechnung in Germany, and hybrid PDF formats such as ZUGFeRD and Factur-X, which carry the structured data inside a PDF.
  • Peppol: an exchange network with its own billing specification, used by many public bodies and some national systems.
  • Government platforms and certified platforms, through which invoices pass in countries that use a clearance or reporting model.

The format is the easy part. The work is in the data behind it: correct VAT IDs, VAT categories and exemption reasons, unit codes, purchase order references, and bank details on every invoice.

What to prepare in your systems

  1. Map where invoices come from. ERP, billing system, web shop, project tool, spreadsheets. Each source has to produce structured data, not a PDF.
  2. Clean the master data. Customer VAT IDs validated, addresses complete, products with VAT categories and unit codes, customer order references stored where the customer requires them.
  3. Receive first. Mandates usually start with receiving. Incoming e-invoices should be validated, shown in a readable form, matched to purchase orders and posted, instead of printed and retyped.
  4. Choose the channels per country. Peppol access point, government platform or certified platform, depending on where your customers are.
  5. Archive the structured file. The XML is the original invoice. Keep it, together with the readable view, for the retention period that applies in each country.
  6. Test with real counterparties before the date that applies to you, including credit notes, partial deliveries and foreign customers.

What changes in accounts payable

Receiving e-invoices changes more inside a company than sending them. Today many invoices arrive as PDFs and are read by a person or by text recognition, with errors to correct. Structured e-invoices arrive as data: supplier, VAT ID, amounts, VAT rates, order reference and bank account are already in fields. That makes automatic matching against purchase orders and goods receipts realistic, so only invoices that do not match go to a person. It also means checks can run on arrival, such as whether the bank account is the one on file for that supplier, a common point of invoice fraud. The approval rules, cost centres and posting logic stay yours; the input simply becomes reliable.

Two practical points are often missed. First, the structured file is the legal invoice, so the readable view your staff look at must be generated from it, not stored instead of it. Second, suppliers will send in different formats and through different channels for some years, so the receiving side has to accept structured e-invoices, hybrid formats and, where still allowed, PDFs, and route them into one process. That process, from capture to approval and payment, is what we build as accounts payable automation.

Common mistakes

  • Treating e-invoicing as a file format project, when the real work is master data and processes.
  • Switching on sending but leaving receiving manual, so staff retype structured data.
  • Archiving only the PDF view and discarding the structured file.
  • Planning for one country when customers or subsidiaries are in several.
  • Waiting for the last date, when testing with customers and suppliers takes months.

Ready-made invoicing software or custom integration?

Most accounting and ERP products now offer e-invoicing, and for a company with one invoicing system and customers in one country, switching it on is often enough. Custom work makes sense when invoices start in several systems, when a sector-specific system has no e-invoicing module, when incoming invoices should be matched automatically against orders and deliveries, or when you invoice into several countries with different channels. Then a small integration layer that turns your data into valid e-invoices and routes them per country is usually the cleanest answer.

How we help

We build that layer: export of structured invoices from your systems, validation against EN 16931 and the national profiles before sending, connections to Peppol access points or national platforms, and automatic capture of incoming e-invoices into your accounting. Our document workflow automation page covers invoice approval and matching, API integration covers the connections, and ERP systems and financial software development cover the systems that produce the invoices. As with all our work, the code is yours and the data stays in your accounts, hosted in the EU.

Questions people ask

Is a PDF invoice an e-invoice?

Not under the new rules. ViDA defines an electronic invoice as one issued, transmitted and received in a structured electronic format that allows automated and electronic processing. A PDF sent by email is an invoice in electronic form, but it is not a structured e-invoice. Germany applies the same distinction since 1 January 2025. Hybrid formats that embed the full structured data, such as ZUGFeRD or Factur-X, can qualify when the structured part contains all the data required.

When does e-invoicing become mandatory across the EU?

For intra-EU business-to-business supplies, the digital reporting requirements and mandatory e-invoicing under Directive (EU) 2025/516 apply from 1 July 2030. For domestic transactions, each Member State decides: since 14 April 2025 they may require domestic e-invoicing without asking the EU for permission, and several already do.

What is EN 16931?

The European standard on electronic invoicing, with its list of syntaxes, set up under Directive 2014/55/EU. Public bodies in the EU must accept e-invoices that comply with it, and under ViDA it becomes the default standard for e-invoices. In practice the main syntaxes are UBL and UN/CEFACT CII, with national profiles such as XRechnung, Peppol BIS Billing and Factur-X built on top.

Do we need Peppol?

It depends on the country and the customer. Peppol is a network for exchanging e-invoices that many public bodies and some national mandates use. Other countries route invoices through a central government platform or through platforms certified by the tax administration. Your invoicing system should be able to send through whichever channel each of your customers' countries requires.

Does e-invoicing affect small companies?

Yes, because mandates usually start with receiving. In Germany, all domestic businesses must be able to receive e-invoices for B2B supplies from 1 January 2025, with transition periods only for issuing. In France, the phased start from 1 September 2026 concerns large and mid-sized companies first and SMEs and micro-enterprises from 1 September 2027.

Sources