ViDA: What the EU's VAT in the Digital Age Directive Means for Your Invoicing

VAT in the Digital Age (ViDA) is a comprehensive EU directive that modernizes the European VAT system for the digital economy. It was proposed by the European Commission in December 2022, survived two missed target dates and political deadlock, then moved rapidly: the ECOFIN Finance Ministers agreed unanimously in November 2024, the European Parliament approved it in February 2025 by a large majority, and the Council formally adopted it on 11 March 2025.

ViDA was published in the Official Journal on 25 March 2025 (OJ L, 2025/516) and entered into force on 14 April 2025. It consists of three legal instruments: Council Directive (EU) 2025/516, Council Regulation (EU) 2025/517, and Council Implementing Regulation (EU) 2025/518. The directive is being rolled out progressively until January 2035.

ViDA covers three pillars:

When ViDA entered into force on 14 April 2025, three things changed right away:

Starting 1 July 2030, all intra-EU B2B transactions will require structured electronic invoices. This is the core mandate. Here are the specifics.

ViDA also introduces Digital Reporting Requirements (DRR): invoices for intra-EU B2B supplies must be issued within 10 days of the chargeable event, and the supplier's digital report is submitted at the time of invoice issuance. In self-billing and intra-Community acquisition scenarios, the recipient must also report within 5 days. The report is derived from the structured e-invoice — you don't create it separately. This replaces EC Sales Lists, which are abolished. The purpose is to close the EU's VAT gap by giving tax authorities visibility into transactions as they happen.

The EU-wide mandate covers intra-EU B2B from July 2030. But many member states are not waiting — they are implementing domestic B2B e-invoicing requirements on their own timelines. Every country is doing it differently: different formats, different models (Peppol vs clearance vs platform), different timelines. National mandate dates below are based on published government announcements and may be subject to change — verify with the relevant national authority.

This fragmentation is exactly why having invoicing software that generates to the EN 16931 standard matters — it's the common denominator.

EN 16931 is the European standard for electronic invoicing. It defines the semantic data model — what information a structured invoice must contain and how it relates. It was created under EU Directive 2014/55/EU for public procurement (effective April 2019 for central government authorities, with sub-central contracting authorities following by April 2020) and is now the mandated standard for ViDA's e-invoicing requirements.

The standard is implemented in two approved syntaxes: UBL 2.1 (used by Peppol and most cross-border implementations) and CII (used in French Factur-X and German ZUGFeRD hybrid formats). Both are equally compliant.

An updated version, EN 16931-1:2025, received CEN formal approval on 13 February 2026 and is expected to be published by 31 May 2026. It supersedes EN 16931-1:2017 and adds key B2B capabilities: IBAN mandatory for payment, multiple orders per invoice, early payment discounts, late payment charges, new VAT codes and exemption reasons, margin scheme support, and goods/services indicators. No formal transition period between the 2017 and 2025 versions has been defined — this is a known gap that businesses and software providers need to watch.

Most ViDA coverage is written for tax directors at large corporations. But the directive affects every EU business that issues invoices — including freelancers, consultants, and small SaaS companies. Let's make it concrete with an example.

You do not need to panic. The EU-wide mandate is 2030, and most domestic mandates have transition periods. But starting to prepare now means you avoid a rushed migration later.

Invoxo already generates EN 16931 compliant structured invoices in UBL 2.1 format, conforming to the PEPPOL BIS Billing 3.0 profile. This is available today on the Business plan. You can download compliant XML for every issued invoice (type code 380) and credit note (381).

Every structured invoice is generated from immutable snapshot data — the seller details, buyer details, payment information, and tax payload recorded at the time of issuance. Tax payload integrity is verified by hash before export. Totals are reconciled against canonical columns. These are not optional safeguards — they run on every export.

Invoxo's EU VAT handling ensures that the underlying tax logic is correct before it is expressed in a structured format. Automatic VAT treatment determination, VIES validation, reverse charge detection, and OSS for digital services are all handled by the tax engine.

Peppol network delivery — sending structured invoices directly to buyers via the Peppol network — is on the roadmap. Generation is the standards-compliant part. Delivery is the transport layer.