ViDA 2026: What Baltic SMEs Actually Need to Prepare

No — the European Commission’s 2026 work programme for ViDA (short for „VAT in the Digital Age“) does not impose a single new e-invoicing or reporting obligation on any small business in Estonia, Latvia or Lithuania. It’s the Commission’s own to-do list, not a law that changes what you owe. The binding deadlines come from a directive already adopted in 2025, and they arrive in stages: OSS/IOSS clarifications on 1 January 2027, platform and stock-movement rules on 1 July 2028, and cross-border B2B reporting on 1 July 2030.

A work programme is not a deadline

The implementation plan carries the date 13 May 2026, and the Commission describes it on its ViDA page as an overview of activities provisionally scheduled for 2026 and early 2027. It lists what the Commission itself is building — technical specifications, guidance, IT solutions. None of it is a deadline your bookkeeping has to run toward.

The binding dates come from elsewhere. The ViDA package was adopted on 11 March 2025 and entered into force on 14 April 2025 — that’s how the Commission’s overview puts it. The substance of the obligations sits in Council Directive 2025/516, which Member States transpose into their own law in stages.

That’s where three things are worth keeping apart. First, there’s EU law already adopted, with fixed dates. Second, there are technical rules still being written — the exact data set for reporting, for example. Third, there are domestic obligations that each country sets for itself and that do not follow from ViDA automatically. Since 14 April 2025, Member States may impose mandatory domestic e-invoicing under the conditions in the directive, but that’s a national choice, not an EU-wide duty.

Find your business’s ViDA track

Before the dates, check which of them touches you at all. Most of the rules hit only specific transaction types.

Your profile	What ViDA changes for you	First date
Domestic sales only, in one country	Cross-border ViDA reporting doesn’t apply; domestic depends on national law	watch national legislation
Cross-border B2B seller or buyer in the EU	Structured e-invoice and transaction-level reporting	1 July 2030
OSS/IOSS user (distance sales to consumers)	Clarified registration and correction rules	1 January 2027
You move your own goods between Member States	Own-goods transfer scheme under a single registration	1 July 2028
Supplier B2B in a country where you’re not established	Mandatory reverse charge	1 July 2028
Short-term accommodation, road passenger transport, and the platforms that facilitate them	Platform „deemed supplier“ rule	1 July 2028 (a country may defer to 1 January 2030)

If your business fits the first row, ViDA is almost entirely a monitoring matter for now. If you’re in one of the last rows, it’s worth getting the calendar out already.

The first real changes land on 1 January 2027

The first binding milestone concerns OSS and IOSS users — those who sell goods or services to consumers in other Member States and declare the VAT through a single portal. Member States must adopt the domestic rules needed for these measures by 31 December 2026 and apply them from 1 January 2027.

These are clarifications, not a reversal of who owes what. The Commission calls them minor legislative clarifications for OSS and IOSS users, including a new correction mechanism. The detail sits in Commission Implementing Regulation 2026/1869, adopted on 27 July 2026 and in force from 17 August 2026; its registration-data changes apply from 1 January 2027, while the larger OSS/IOSS and stock-movement changes only take effect on 1 July 2028.

The practical read: if you use OSS or IOSS, spend some of 2026 reviewing your registrations and your cross-border consumer sales. Nothing more is needed for that date.

2028 rewires the VAT logic for platforms and stock

On 1 July 2028 the more substantive reforms of the Single VAT Registration begin. They include the own-goods transfer scheme and a mandatory reverse charge where a supplier not established in a country makes a B2B supply to a VAT-registered customer.

Reverse charge means the recipient of the supply accounts for and declares the VAT, not the seller. When you move your own goods from one Member State to another — say, from a warehouse in Estonia to one in Germany — the directive creates a new scheme within the OSS framework, meant to reduce the cases where you’d otherwise need several VAT registrations and to simplify the VAT obligations tied to certain own-goods transfers.

Accommodation and transport platforms: who answers for the VAT

For the platform sector, 1 July 2028 brings the so-called deemed supplier rule. Under the directive, a platform facilitating short-term accommodation in the EU — up to 30 nights — or road passenger transport is generally treated as responsible for the supply, unless the actual service provider gives the platform its VAT number and confirms it will account for the VAT itself. Member States may exclude supplies made under their small-business scheme (the SME scheme).

That doesn’t mean every host, driver or platform carries exactly the same duty from 1 July 2028. A Member State may defer the rule until 1 January 2030. If you rent out accommodation or arrange rides in Estonia, Latvia or Lithuania, your precise obligation depends on which date and which exemptions your country picks. Until then, it’s worth knowing who your VAT number has been passed to on the platform and who declares the tax today.

1 July 2030 — the cross-border B2B e-invoice date

For a business that sells to or buys from VAT-registered parties in other Member States, the date that matters most is 1 July 2030. From that day the Digital Reporting Requirements apply to defined intra-Community B2B supplies and acquisitions.

In effect, the current recapitulative statement (the EC Sales List for intra-Community turnover) is replaced by transaction-level electronic data transmission: each covered transaction sends its own data record to the tax authority, not a period summary. The basis for it is a structured e-invoice.

The timing shifts too. Under the directive, the supplier transmits the required data when the invoice is issued or should have been issued; for self-billing and buyer-side reporting the deadline is five days. The deadline for issuing the cross-border invoice itself is 10 days after the chargeable event. In practice, waiting weeks to issue an invoice stops being an option.

Does ViDA require Peppol?

No. The directive requires Member States to allow reporting from e-invoices that comply with the European e-invoicing standard and its listed syntaxes, but it names no mandatory transmission network — Peppol included. The technical rule for who delivers the data, and how, is part of what’s still being built. That’s one reason not to nail your business to any particular network or interface in 2026.

Domestic invoices are a separate story

This is where two things often get confused. ViDA’s cross-border reporting and your own country’s e-invoicing rules are not the same thing. In Estonia, ViDA imposes no new domestic e-invoicing obligation. Per the Ministry of Finance, an e-invoice may be required by a buyer that has publicly registered itself as an e-invoice recipient in the business register; the ministry recommends the European standard, but both the Estonian and the European e-invoice standards remain permitted. There are roughly 18,000 companies in Estonia registered as such recipients.

Estonia also has a separate data-based declaration reform moving on its own track: on 19 June 2026 the Ministry of Finance sent a draft bill for consultation that would replace income-tax and social-tax declaration forms with data sets pulled straight from accounting software. As of that date, it was a proposal in the consultation round — not an enacted ViDA transposition, and not an immediate invoice-based reporting duty. In Latvia and Lithuania, domestic obligations mean watching each country’s own legislation; ViDA doesn’t enact them for you.

The same logic applies to 2035. The 1 January 2035 harmonisation deadline concerns Member States that already have a domestic real-time, transaction-level reporting obligation, or a corresponding legal authorisation predating 1 January 2024 — it is not a general 2035 domestic e-invoicing deadline for every country.

What to do now, and what to leave alone

The dates are far off, but the preparation that pays off by 2030 is mostly hygiene that serves you anyway. A short list you can work through over 2026–2027:

• Map your transactions and VAT numbers. Sort out which of your transactions are cross-border B2B, which run under OSS/IOSS, and which are movements of your own goods. Check that your partners’ VAT numbers are correct and current — transaction-level reporting surfaces errors immediately.
• Improve structured e-invoicing and source-data quality. If you send and receive machine-readable e-invoices that match the European standard, you’re already closer to the 2030 requirement. Clean underlying data matters more here than any particular software.
• Keep an invoice correction trail. The new correction mechanisms and transaction-level reporting assume that invoice changes stay traceable. A proper history pays off in front of both auditors and the tax authority.
• Watch your own country’s legislation. Estonia, Latvia and Lithuania each have their own transposition and domestic timetable — three separate stories. If you sell in all three, follow all three.

And what not to rush: don’t buy against specifications the EU hasn’t finished. No mandatory transmission network has been named, the technical data sets are part of the Commission’s ongoing work, and the exact start date for the platform rules depends on your country’s choice. Locking yourself to a specific network or interface before those rules are done would mean paying now for something whose shape isn’t settled. Tidying up your data pays off regardless — the rest can wait until the rules actually exist.