ViDA (VAT in the Digital Age, the EU’s reform of VAT reporting and e-invoicing rules) rolls out in four steps: 1 January 2027, 1 July 2028, 1 July 2030 and 1 January 2035. Directive (EU) 2025/516 was adopted on 11 March 2025 and entered into force on 14 April 2025; the European Commission’s ViDA overview confirms the package unfolds gradually through January 2035. Estonia, Latvia and Lithuania had to transpose and publish the first set of national rules by 31 December 2026, taking effect from 1 January 2027. The deadline that actually matters for a small business, though, is 1 July 2030, when digital reporting becomes mandatory for cross-border intra-EU B2B sales of goods and services.

What does the ViDA timeline look like in brief: 2027, 2028, 2030 and 2035?

The easiest way to remember it: 2027 brings small technical corrections for businesses using the OSS scheme, 2028 widens single VAT registration and puts new liability on platforms, 2030 is the actual e-invoicing and data-reporting mandate for cross-border B2B trade, and 2035 only applies to countries that already run their own domestic real-time reporting system. The first three dates matter directly to you as a business owner. The last one is mostly a compatibility problem between tax authorities, not something you’ll feel day to day.

What changes on 1 January 2027: the first adjustments to OSS and platform sales?

From this date, the corrections in Directive 2025/516 apply, and they mostly touch businesses using the One Stop Shop (OSS) and Import One Stop Shop (IOSS), simplified schemes that let a company report VAT on cross-border EU sales through a single return instead of registering in every country it sells to. These are technical fixes, not a general e-invoicing requirement. If your company doesn’t use OSS or IOSS, this step will pass you by without you noticing.

What changes on 1 July 2028: single VAT registration and platform liability?

This is where things get real. OSS expands, a new special scheme covers moving your own goods to another member state, and mandatory reverse charge kicks in whenever the seller isn’t VAT-registered in the destination country, meaning the buyer, not the seller, accounts for the VAT. Platforms offering short-term accommodation or ride-hailing face a deemed-supplier rule: stays of up to 30 consecutive nights count as short-term, and in those cases the platform itself can become liable for the VAT, as if it had made the sale. Member states can postpone applying this specific platform rule until 1 January 2030. The technical detail on registration data sits in Implementing Regulation 2026/1869, adopted on 27 July 2026.

What happens on 1 July 2030: the real break point for intra-EU B2B e-invoicing and digital reporting?

From this date, VAT-exempt intra-Community supplies of goods and certain reverse-charge sales of goods or services fall under mandatory digital reporting. The invoice has to be issued no later than 10 days after the taxable event happens (or 10 days after receiving an advance payment); the seller sends the transaction data to the tax authority no later than the invoice deadline itself; and where self-billing applies (the buyer issuing the invoice on the seller’s behalf), the deadline tightens to five days. All of this comes straight from Directive 2025/516. It’s worth being precise about scope here: this obligation does not automatically extend to a domestic sale, for example an Estonian company invoicing an Estonian client. It’s aimed squarely at cross-border B2B trade with a business in another EU member state.

What does ViDA actually require for EN 16931, UBL and Peppol?

The law requires your invoice to match the European e-invoice standard set out in Commission Implementing Decision 2017/1870: EN 16931, the standard that defines exactly which data fields a machine-readable invoice must contain, from VAT amounts to buyer and seller identifiers. The accepted formats are UN/CEFACT CII XML and UBL 2.1 (Universal Business Language, an XML-based format for structuring business documents). Peppol (the Pan-European Public Procurement Online network used to exchange e-invoices between businesses and their software) is one way to transmit these invoices, but the directive doesn’t require it specifically. What actually matters is whether your software can generate and read an EN 16931-compliant machine-readable invoice, not which network carries it.

What happens between 2032 and 2035: evaluation, transition and the limit on domestic systems?

The next milestone under Regulation 2025/517, on 1 July 2032, deals with administrative cooperation between member states and data exchange through VIES, the VAT Information Exchange System tax authorities use to verify VAT numbers across borders. It’s not a new invoicing deadline for businesses. And 1 January 2035 only requires harmonisation in member states that already run their own domestic real-time transaction reporting system, so this date doesn’t hand every member state a fresh automatic obligation.

What’s the checklist for a Baltic SME between now and 2030?

  • Map how much of your revenue goes to a business in another EU member state. That’s the group the 2030 obligation targets.
  • Check with your accounting or ERP software provider whether it can already generate an EN 16931-compliant e-invoice.
  • Start collecting your customers’ VAT numbers now, since the 2028 reverse-charge rule depends on having them exactly right.
  • Watch your own country’s tax authority for implementing acts between 2026 and 2027. The domestic detail gets finalised before 1 January 2027.

FAQ

Millised on ViDA pöördepunktid aastatel 2027–2035?

ViDA ajakava põhipäevad on 1. jaanuar 2027, 1. juuli 2028, 1. juuli 2030 ja 1. jaanuar 2035. Need kuupäevad määravad, millal hakkavad kehtima eri e-arvete ja digiaruandluse sammud.

Mida tähendab 1. juuli 2030 e-arveldamise jaoks?

Alates 1. juulist 2030 muutub ELi-sisene B2B kauba- ja teenusemüük teatavatel juhtudel digitaalse aruandluse kohustuslikuks. Arve tuleb väljastada hiljemalt 10 päeva jooksul pärast maksustatava teokoosseisu tekkimist.

Kas EN 16931 ja Peppol on üks ja sama nõue?

Ei. ViDA nõuab, et arve vastaks Euroopa e-arve standardile EN 16931. Peppol on üks võimalik edastuskanal, kuid direktiiv ei tee seda eraldi kohustuslikuks.

Kas 1. jaanuar 2035 toob automaatselt uue kohustuse kõigile riikidele?

Ei. 1. jaanuar 2035 ühtlustab eelkõige nende liikmesriikide reegleid, kellel on juba riigisisene reaalajas tehingupõhine aruandlussüsteem. Seetõttu ei tähenda see automaatset uut koormust kõigile.