Skip to content
Disruptive Lab

Guide European rules

Mandatory e-invoicing and what to prepare

An e-invoice is structured data, not a PDF, and your system must send, receive, check and archive it on the dates your countries set.

Published
Updated
Reading time
8 min read
Editor
David Lahuta

In short

An e-invoice is structured data that software can read without a person retyping it. A PDF sent by e-mail is not one.1 Since 14 April 2025 each EU country may make e-invoices compulsory for invoices between businesses at home.1 From 1 July 2030, invoices between businesses in different EU countries must be e-invoices, and their data goes to the tax authority invoice by invoice.1 Your system must be able to create, send, receive, check and archive them, often through the shared Peppol network.4

What counts as an e-invoice?

In EU law an electronic invoice is an invoice issued, sent and received in a structured electronic format that allows it to be processed automatically.1 The European Commission uses the same definition.3

A PDF does not meet it. A PDF is a picture of an invoice, which a person has to read or a program has to guess at. The structured format has to cover at least the data that is reported to the tax authority.1 A hybrid invoice, a PDF with the structured data embedded in it, therefore counts only if the structured part carries all of that data.1

The structure is set by the European standard on electronic invoicing, EN 16931, which defines the content of an invoice and comes with a list of permitted technical forms (syntaxes).3 The directive requires e-invoices to comply with it, while a country may allow other standards for invoices within its own borders.1

For the people who work with invoices little changes on the screen. They still create and view invoices in their accounting or invoicing program. What changes is what the program sends and receives in the background, and how much of the incoming data it can take over without anyone retyping it.

When does it apply in my country?

The common frame is the EU's VAT reform for the digital age, ViDA, adopted as Council Directive (EU) 2025/516 on 11 March 2025.1 It sets three things that matter for your invoicing.

Each country may make domestic e-invoices compulsory. Since 14 April 2025 a member state may, on conditions it sets, require businesses established there to issue e-invoices for domestic supplies, and it may do so without the recipient's agreement.1 The Commission notes that this option opened when the directive entered into force on that day.2

Cross-border invoices follow from 1 July 2030. From that day an invoice for a supply to a business in another EU country must be an e-invoice to the European standard, issued no later than 10 days after the supply.1 The supplier sends the data of each such transaction to its tax authority when the invoice is issued.1 The Commission calls this the digital reporting requirements for cross-border trade between businesses.2

Countries with their own reporting systems align later. Member states that had real-time reporting of transactions in place on 1 January 2024 have until 1 January 2035 to bring it in line with the EU model.12

The Commission expects the move to e-invoicing to help reduce VAT fraud by up to EUR 11 billion a year.2

So the date that binds you depends on two things. Where you are established decides when your domestic invoices must be e-invoices. Whether you sell to businesses in other EU countries decides whether 1 July 2030 applies to you as well. The section on your country below gives the national dates, the authority and the way invoices travel there.

The countries do not all use the same route, which is why the section on your country names it. Where a country uses Peppol, a network for exchanging business documents built on common international standards, buyers and sellers each need only one service provider to trade with any organisation on the network, at home or abroad.4

What must the system do?

Whatever the country, an invoicing system has the same jobs once e-invoices are compulsory.

  • Create a structured invoice to EN 16931, with every required field filled from the system's own data.1
  • Send and receive through the network or platform the country uses. On Peppol, one accredited provider is enough to reach every organisation on the network.4
  • Check each invoice against the rules before sending and on arrival. Peppol's billing specification is a usage profile of EN 16931, and a document that meets it also meets the European standard.5
  • Read incoming invoices automatically, without anybody retyping them.
  • Match invoices with orders, delivery notes, payments and accounting records.
  • Report the data where the country requires it, on time.
  • Archive the e-invoice itself, in its structured form, for as long as the country's VAT law requires.
  • Give access to an external accountant while the company keeps its own access and its identity on the network.

From 1 July 2030 one more job comes for companies that sell to businesses in other EU countries, the 10-day deadline and the report on every cross-border invoice.1

Should we connect the current system or replace it?

Usually the current system can stay. There are three common routes. The first is the existing accounting or invoicing software, updated by its supplier and connected to an accredited provider. The second is a separate application from a provider, which suits firms with few invoices. The third is a new solution that covers the whole process, when adapting the current software would not work or would cost too much.

Which route fits depends less on the invoice and more on the data behind it. These questions usually decide it.

Question Points to connecting Points to replacing or rebuilding
Does the system hold clean customer data, such as VAT numbers and addresses? Yes, kept in one place Spread across spreadsheets and e-mails
Can it produce every field of the standard from its own records? Yes, or with small changes Key data lives outside it
Does its supplier commit to a date for e-invoices and the network? A date before your country's deadline No date, or after the deadline
Are incoming invoices processed or retyped today? Processed, with matching to orders Retyped by hand

Connecting is the cheaper path when the answers are on the left. When most are on the right, the deadline is a good moment to fix the data flow behind invoicing rather than to add a converter on top of it.

What should we prepare this quarter?

The work is mostly checking and deciding, not building. A sensible order for the weeks before the end of the year looks like this.

  1. List your countries. Where are you established, and where do you invoice businesses? Look up each country's date in the section on your country or on its tax authority's pages.
  2. Ask your system's supplier for dates. When will it create invoices to EN 16931, connect to the network and read incoming e-invoices automatically?
  3. Clean the customer data. VAT numbers, addresses and the details the network needs to find each recipient.
  4. Agree who does what. Who receives, checks and posts invoices, and how the accountant gets access.
  5. Try it early where the law allows. Some countries let businesses send e-invoices before their own date, which is the cheapest way to find gaps in the data.
  6. Note 1 July 2030 if you sell across borders. Plan for the 10-day deadline and the report on every cross-border invoice.1

Country by country

At EU level the frame is the same everywhere. Since 14 April 2025 every member state may require e-invoices for domestic supplies, EN 16931 is the shared standard, and from 1 July 2030 e-invoices and digital reporting apply to supplies between businesses in different member states.1 These are the countries whose official sources we have read so far.

Country What applies From when
Austria No duty. An electronic invoice needs the recipient's consent, and invoices to the federal government are electronic.1718 Federal government since 2014
Belgium Compulsory between Belgian enterprises liable to VAT, through Peppol6 1 January 2026
Croatia Compulsory, with each e-invoice reported. VAT-registered businesses issue and receive, the others receive.28 1 January 2026, the others issue from 1 January 2027
Czech Republic No duty. An electronic invoice needs the customer's consent,15 and public bodies accept the European standard.14 No date set16
Denmark No duty. Registered bookkeeping systems enrol their users unless they opt out.2223 2027
Estonia No duty. A registered buyer may demand an e-invoice.27 1 July 2025
Finland No duty. A buyer may demand an e-invoice from a seller with turnover above EUR 10,000.24 1 April 2020
France Compulsory through approved platforms. Every company receives, large and intermediate companies issue.8 1 September 2026, smaller companies issue from 1 September 2027
Germany The e-invoice is the rule between German businesses.9 Other formats with the recipient's consent during a transition.10 1 January 2025, transition until 31 December 2026, or 2027 for turnover up to EUR 800,000
Italy Compulsory for every Italian VAT holder, consumers included, through the national exchange system SdI20 1 January 2019
Latvia Compulsory, with the data sent to the State Revenue Service within five working days2526 1 January 2028
Netherlands Planned by a cabinet decision, not yet law19 1 July 2030, planned
Poland Compulsory through the national system KSeF7 1 February 2026 for the largest firms, 1 April 2026 for the rest
Slovakia Compulsory through Peppol. VAT payers issue, every business receives,12 and the provider reports the data.13 1 January 202711
Slovenia Compulsory for every business, through Peppol or a registered provider, not by e-mail29 1 January 2028
Spain Compulsory between businesses established in Spain21 6 October 2027 for turnover above EUR 8 million, 6 October 2028 for the rest

For any other country, its tax authority is the place to check the date, and the Commission publishes country factsheets on e-invoicing.3

Next step

If it would help, we can meet and go through your current invoicing system together, what it already handles, what e-invoices and the network would add, and whether connecting it or replacing it makes more sense. We helped Serensia deliver its e-invoicing platform on time for the French e-invoicing mandate. What you do with the result is entirely your decision.

Custom business systems and applications

Sources

  1. 1. Council Directive (EU) 2025/516 of 11 March 2025 amending Directive 2006/112/EC as regards VAT rules for the digital age, Official Journal of the European Union. Read on 17 November 2026
  2. 2. European Commission, Taxation and Customs Union, VAT in the Digital Age (ViDA). Read on 17 November 2026
  3. 3. European Commission, Digital Building Blocks, eInvoicing. Read on 17 November 2026
  4. 4. OpenPeppol, Peppol for end users. Read on 17 November 2026
  5. 5. OpenPeppol, Peppol BIS Billing 3.0. Read on 17 November 2026
  6. 6. FPS Finance Belgium, Structured electronic invoices between companies are compulsory since 2026. Read on 17 November 2026
  7. 7. Ministerstwo Finansów, Krajowy System e-Faktur, Od kiedy trzeba wystawiać faktury w KSeF. Read on 17 November 2026
  8. 8. Direction générale des Finances publiques, impots.gouv.fr, Foire aux questions, Je découvre la facturation électronique (version of 1 September 2026). Read on 17 November 2026
  9. 9. Umsatzsteuergesetz, § 14 Ausstellung von Rechnungen, gesetze-im-internet.de. Read on 17 November 2026
  10. 10. Umsatzsteuergesetz, § 27 Allgemeine Übergangsvorschriften, paragraph 38, gesetze-im-internet.de. Read on 17 November 2026
  11. 11. Finančná správa Slovenskej republiky, eFaktúra. Read on 17 November 2026
  12. 12. Finančná správa Slovenskej republiky, Povinná elektronická fakturácia pre firmy, živnostníkov a ďalšie podnikateľské subjekty od 1. 1. 2027 (manual, 26 August 2026). Read on 17 November 2026
  13. 13. Finančné riaditeľstvo Slovenskej republiky, Najčastejšie otázky a odpovede k eFaktúre, 9/DPH/2025/IM (16 November 2026). Read on 17 November 2026
  14. 14. Ministerstvo financí ČR, Elektronická fakturace, Základní informace. Read on 17 November 2026
  15. 15. Zákon č. 235/2004 Sb., o dani z přidané hodnoty, § 26, e-Sbírka (znění k 17. 11. 2026). Read on 17 November 2026
  16. 16. Ministerstvo financí ČR, Jiří Žežulka, ředitel sekce kontroly GFŘ, v rozhovoru pro Ekonomický deník (27. 5. 2026). Read on 17 November 2026
  17. 17. Rechtsinformationssystem des Bundes, Umsatzsteuergesetz 1994, § 11. Read on 17 November 2026
  18. 18. Bundesministerium für Finanzen, e-Rechnung.gv.at, Rechtliche Information. Read on 17 November 2026
  19. 19. Rijksoverheid, Kabinet kiest voor invoering e-facturatie en rapportage voor bedrijven (11 September 2026). Read on 17 November 2026
  20. 20. Agenzia delle Entrate, Guida, La fattura elettronica e i servizi gratuiti dell'Agenzia delle Entrate (December 2025). Read on 17 November 2026
  21. 21. Agencia Estatal de Administración Tributaria, Factura electrónica, Calendario de implantación. Read on 17 November 2026
  22. 22. Erhvervsstyrelsen, E-fakturering. Read on 17 November 2026
  23. 23. Retsinformation, BEK nr 811 af 22/09/2026 om ændring af bekendtgørelse om krav til digitale standard bogføringssystemer. Read on 17 November 2026
  24. 24. Finlex, Laki hankintayksiköiden ja elinkeinonharjoittajien sähköisestä laskutuksesta 241/2019. Read on 17 November 2026
  25. 25. Latvijas Vēstnesis, Grozījumi Grāmatvedības likumā, 2025/111.1. Read on 17 November 2026
  26. 26. Latvijas Vēstnesis, Ministru kabineta noteikumi Nr. 749 (9 December 2025), 2025/240.17. Read on 17 November 2026
  27. 27. Riigi Teataja, Raamatupidamise seadus. Read on 17 November 2026
  28. 28. Narodne novine 89/2025, Zakon o fiskalizaciji. Read on 17 November 2026
  29. 29. Uradni list RS 85/2025, Zakon o izmenjavi elektronskih računov in drugih elektronskih dokumentov (ZIERDED). Read on 17 November 2026

Change log

  1. Published.

Let's talk about your project

Leave us your contact details and we will get back to you with a date. Free and without obligation.

With the country code, for example +44.

We use your details only to answer you. Privacy notice

This form is protected from automated submissions by Google reCAPTCHA. Google Privacy Policy (opens in a new window) Google Terms of Service (opens in a new window)

Or contact us directly

Write to us office@disruptivelab.dev
Call us +420 777 702 032

Our preferred language of communication is English.

All contact details and addresses