Intra-EU e-invoicing 2030: what the new obligation changes for your business

Intra-EU e-invoicing 2030: what becomes mandatory

On 1 July 2030, the structured electronic invoice becomes the only valid form for intra-EU B2B transactions, and each transaction must be reported to the authorities the moment it is issued. This is the heart of the first pillar of the ViDA reform ("VAT in the Digital Age"), adopted on 11 March 2025 and in force since 14 April 2025.

In practice, three principles change at the same time. First, the very definition of "electronic invoice" is rewritten: it is no longer a readable document sent in digital form, but a file in a structured format compliant with the European standard EN 16931. Second, the issuer no longer needs the customer's agreement to send an electronic invoice: Article 232 of the VAT Directive is amended to that effect. Third, there is no threshold: all intra-EU B2B transactions are covered, whatever their value or the size of the business.

The scope calls for one precise point, because this is where most content gets it wrong. The 2030 obligation targets intra-EU B2B transactions, meaning cross-border flows between taxable persons in two Member States. It also covers transactions carried out by a non-established supplier falling under the reverse charge under Article 194. By contrast, purely domestic transactions between two operators established in the same country fall under the national mandates, not the 2030 European obligation.

The structured invoice (EN 16931): the PDF is no longer enough

A PDF sent by email is not an electronic invoice within the meaning of the 2030 reform. This is the most common source of confusion, and an expensive one to leave unprepared. The EN 16931 standard requires a structured format, one that a computer system can read and process automatically, not just a human eye.

Three families of formats meet the standard:

• UBL (Universal Business Language) and CII (Cross Industry Invoice): purely XML formats, fully structured.
• Factur-X (identical to the German ZUGFeRD): a hybrid format. It combines a human-readable PDF with a structured XML file embedded inside it.

Transporting these invoices relies on networks and platforms. The Peppol network is one of the most widespread channels in Europe, but it is not the only model, as we will see below with the distinction between centralised and decentralised systems.

The issuing deadline is set at 10 days

The electronic invoice must be issued within 10 days of the VAT chargeable event. Keep that figure in mind, because a stubborn myth, inherited from the original 2022 proposal, still quotes a 2-day deadline. The text finally adopted sets 10 days.

The end of the recapitulative statement: the ESL replaced by e-reporting

The big shift in 2030 is the move from a periodic, aggregated declaration to real-time reporting, transaction by transaction. The mechanism is called the Digital Reporting Requirements (DRR). It replaces and removes the recapitulative statement that businesses file today for their intra-EU transactions.

This point deserves a nuance almost no competitor gets right. The recapitulative statement (in EU terms, the EC Sales List, or ESL) actually splits into two duties today, and they do not share the same fate:

• The VAT recapitulative statement itself (the fiscal reporting of your intra-EU supplies of goods and services) is a pure VAT filing. It disappears entirely and moves into e-reporting on 1 July 2030.
• The Intrastat statistical survey is a different animal. It reports the physical movement of goods for statistical purposes, not for VAT. It belongs to European statistics, not to VAT law, and it is not removed by the reform.

Real-time reporting, transaction by transaction

With the DRR, each transaction is reported the moment the invoice is issued, individually, rather than grouped into a monthly return. The authorities thus receive a near-instant picture of intra-EU flows, which is meant to reduce the VAT gap and carousel-type fraud.

The mechanism has two sides:

• On the supplier side: the report is filed when the invoice is issued, within the 10-day deadline already mentioned.
• On the buyer side: the reporting of intra-EU acquisitions and reverse-charge transactions must be transmitted within 5 days of receipt.

A few fields become mandatory on the invoice to feed this reporting: the IBAN of the account receiving the payment, and the reference of the original invoice for corrective invoices. Note that a field once under discussion, the payment date, was finally dropped.

Before and after: what changes for your reporting

The table below sums up the shift for a business carrying out intra-EU transactions.

2030 European obligation vs national mandates: do not mix them up

The e-invoicing reform plays out on three separate levels, with three different timetables. Confusing them is the most widespread mistake. It is also the main service that clear content can give a finance director.

Here are the three layers to tell apart:

1. National mandates: each State can impose e-invoicing for its domestic transactions. Since 14 April 2025, it can do so without prior EU authorisation (end of the Article 395 derogations), provided it relies on the EN 16931 standard. 2. The intra-EU European obligation: structured e-invoicing and e-reporting for cross-border B2B, on 1 July 2030. This is the subject of this article. 3. Convergence: pre-existing national systems will have to align with the European model by 1 January 2035 at the latest.

National mandates: Belgium, France, Germany, Poland, Spain

Several States have moved ahead on their domestic e-invoicing. These timetables are independent of the 2030 European deadline.

France is a useful reference point here: its own reform, with its own logic and calendar, starts in September 2026. That national timetable is a separate track from the 2030 intra-EU obligation covered in this article.

Clearance or Peppol, and the convergence of national systems in 2035

Two major technical models coexist in Europe, and they will have to converge on the European model by 2035. Understanding this architecture helps you choose your tools without making the wrong bet.

• The centralised clearance model: the invoice passes through a public platform that validates it before transmission to the customer. This is the choice of Italy (SdI) and Poland (KSeF).
• The decentralised Peppol-type model: the invoice moves directly between accredited access points, with no prior central validation. This is the choice of Belgium, Germany and the Nordic countries.

National systems put in place before 1 January 2024, such as Italy's SdI, have an adaptation period: they will have to converge on the European model by 1 January 2035 at the latest. Here too, be wary of older sources that date this convergence to 2028: it is indeed 2035.

Here is the timeline to remember for the invoicing dimension:

• 14 April 2025: ViDA enters into force. End of the derogations: a State can impose domestic e-invoicing freely. End of the customer-agreement requirement.
• 31 December 2027: deadline to transpose the directive across the 27 Member States.
• 1 July 2030: structured intra-EU e-invoicing (EN 16931) and real-time e-reporting become mandatory. Removal of the recapitulative statement.
• 1 January 2035: convergence of pre-existing national systems on the European model.

What the 2030 obligation changes for a non-established business

For a business selling B2B in States where it is not established, the 2030 obligation does not disappear because it does not charge local VAT: it changes shape. This is a poorly understood point, yet a decisive one to anticipate. No competing content covers it clearly.

Let me set the context. On 1 July 2028, another part of ViDA makes the Article 194 reverse charge mandatory across the 27 States: a non-established supplier selling to a VAT-identified customer invoices without VAT, and the customer accounts for the tax. You might think that, no longer collecting VAT, this supplier has nothing left to report. That is wrong.

These reverse-charge transactions fall expressly within the scope of the reporting. Here is who does what from 2030:

• The non-established supplier issues a structured electronic invoice (EN 16931) without VAT, with the reverse-charge mention, within 10 days of the chargeable event, and reports it in real time through e-reporting.
• The customer, liable through the reverse charge, reports the incoming transaction within 5 days and accounts for the tax on its own return.

This new landscape shifts the fiscal representation business. Historically, a non-established business used an agent to register and file its local returns. With generalised reverse charge and the expanded OSS, some of those registrations disappear. But a new need emerges: complying with EN 16931 e-invoicing, producing real-time reporting, and configuring your ERP accordingly.

Misconceptions about intra-EU e-invoicing

Many pages online have not been updated since the original 2022 proposal and keep spreading outdated information. Here are the errors not to repeat.

Need support to prepare for 2030?

Mapping your intra-EU flows, separating what falls under national mandates from the European obligation, choosing your formats and your platform, securing your real-time reporting: that is the work our team carries out for businesses operating across Europe, established and non-established alike.

Book a call with a specialist →