ViDA E-Invoice vs E-Reporting: What’s the Difference?

Short answer: one document, two separate destinations

ViDA (VAT in the Digital Age) treats the e-invoice and e-reporting as two different obligations, even though both often start from the same sale. The e-invoice is the structured business document the seller creates and the customer receives; it moves between two companies. E-reporting is something else entirely: it’s the transmission of transaction data to the tax authority, not the sending of the invoice itself. Under Council Directive (EU) 2025/516, this cross-border reporting duty becomes mandatory across the EU from 1 July 2030. Until that date, Estonia, Latvia and Lithuania each regulate their own domestic e-invoicing and reporting under separate national laws, and their deadlines already differ from one another today.

Feature	E-invoice	E-reporting
Who receives it	The buyer, i.e. the customer	The tax authority
What it actually is	A structured business document	An electronic transmission of transaction data
Format	Must allow automatic machine processing	A common electronic message whose format is set by the member state
Who fulfils the obligation	Seller creates and sends it	Seller’s data, and in some cases the buyer’s data too
Applies cross-border from	1 July 2030	1 July 2030

What actually qualifies as a ViDA e-invoice

According to the directive’s definition, an e-invoice is one that contains all the required VAT data and is issued, transmitted and received in a structured electronic format that allows automatic electronic processing. That’s a technical test, not a visual one. The invoice has to be machine-readable, meaning software can read and process the data itself, with nobody retyping numbers by hand.

Is a PDF invoice sent by email an e-invoice?

No. A PDF is built for a human’s eyes, not a machine’s, and under the directive’s treatment, a file like that generally doesn’t support automatic processing. So a PDF invoice emailed to a customer doesn’t meet the ViDA definition of an e-invoice, even if every figure on it is correct. From 1 July 2030, the e-invoice becomes the default format under Article 218 of the directive, but member states can still allow paper invoices or other formats for transactions that fall outside the digital reporting obligation.

What ViDA e-reporting actually requires from 1 July 2030

E-reporting is not an invoice. It’s a separate data flow to the tax authority. Its mandatory scope is narrow: it covers B2B goods supplies from one EU member state to another, intra-Community acquisitions, and specific cross-border reverse-charge supplies and acquisitions, as the directive describes them. A domestic sale, say a Tallinn company invoicing a customer in Tartu, sits outside this EU-level obligation entirely.

The detail that matters most to small businesses: the directive sets no general turnover or amount threshold. Sell goods across the border to a business in another member state, and the obligation applies whether your annual turnover is €5,000 or €5 million.

The timing is exact. For a covered cross-border supply, the seller must issue the invoice within 10 days of the taxable event; an advance payment on a reverse-charge supply triggers that same 10-day clock. The seller’s data goes to the tax authority at the moment the invoice is issued. For self-billing, the deadline stretches to up to five days after issuance. On the buyer’s side, data on an acquisition or a reverse-charge purchase may need to be submitted up to five days after receiving the invoice, though each member state can decide not to impose that buyer-side duty within its own territory. The directive lays out these deadlines precisely this way.

A business can file this data itself or through a third party. Member states are required to offer an electronic filing channel and to accept submissions that follow the European e-invoicing standard, a shared technical format for structured invoices, and its listed syntaxes, the specific data languages that format can be written in.

A worked example: a €1,200 invoice from Estonia to Latvia

Say your Tallinn-based company sells goods to a customer in Riga for €1,200. From 1 July 2030, a goods supply to a business in another member state is exactly the transaction type the cross-border reporting obligation covers.

On the invoice side: you create a structured e-invoice that meets the machine-readability requirement, and you issue it within 10 days of the taxable event, as the directive requires.

On the reporting side: at the same time the invoice goes out, you send the transaction data to the Estonian tax authority. That’s a separate data flow, not a copy of the invoice itself. If the Latvian customer has to report the same transaction on their end as an intra-Community acquisition, they may be required to transmit their data within five days of receiving the invoice, whether that obligation actually applies depends on whether Latvia chooses to implement buyer-side reporting.

This is exactly the two-track structure that causes the confusion: one structured invoice, but two separate obligations, moving in two different directions.

Domestic rules stand apart: Estonia, Latvia and Lithuania

ViDA only harmonizes cross-border B2B reporting. Domestic e-invoicing and domestic transaction-based reporting, meaning invoices where both seller and buyer sit in the same country, are left to each member state to decide, and a country can set its own rules and even limit them to particular categories of taxpayer. Member states that already had a domestic real-time, transaction-based reporting system running, or legally mandated, before 1 January 2024 get until 1 January 2035 to bring that system into line with the ViDA framework. That deadline applies specifically to countries whose system fits that description, not automatically to every member state.

The three Baltic states are currently on three different domestic paths.

Estonia runs a buyer-chooses model as of 1 July 2025: a company that has publicly registered itself as an e-invoice recipient in the e-business register can demand an e-invoice from a seller, but otherwise trading partners simply agree on format and submission terms between themselves. For public-sector bodies, the existing e-invoice submission rules stay essentially unchanged.

Latvia’s timeline is staged and more granular than Estonia’s. A structured e-invoice has been mandatory since 1 January 2025 for transactions with state and municipal authorities (G2G, B2G, G2B); transmitting the data from those e-invoices to Latvia’s tax authority, VID, becomes mandatory from 1 January 2026. For transactions between businesses (B2B), a structured e-invoice and its simultaneous submission to VID become mandatory from 1 January 2028. That B2B deadline was originally set for early 2026 but was pushed back two years by a legislative amendment.

Lithuania has been running a different system for some time: the i.SAF register, where VAT-registered businesses must submit data on both issued and received VAT invoices. Legal entities file this for each calendar month by the 20th of the following month, while the deadline for sole proprietors depends on their own VAT declaration period. This is periodic, monthly reporting, not real-time transaction-based transmission, and it runs on its own pre-ViDA logic, not the 1 July 2030 cross-border model.

What to prepare now, and what not to assume

There’s time before 1 July 2030, but it’s worth adjusting software and processes now rather than scrambling as the deadline closes in.

• Structured-format support: your invoicing software needs to produce invoices that meet the European e-invoicing standard and the syntaxes listed in the directive. Looking “tidy” as a PDF isn’t enough.
• VAT-number verification: check that your system validates the customer’s VAT number before the invoice goes out, since how a cross-border transaction gets treated depends on it.
• Complete invoice fields: every required VAT data point has to sit on the invoice in machine-readable form, not just described in free text.
• A correction workflow: think through how you’d fix an invoice or report that’s already been transmitted if an error turns up later. Manually correcting two separate systems by hand takes far longer than getting it right the first time.
• Customer format checks: especially for Estonian B2B sales, where a registered buyer can require an e-invoice, your system needs to correctly identify that customer and pick the right format for them.
• A separate channel to the tax authority: the e-reporting data feed is not the same channel as the invoice itself. These are two separate integrations, even when the data comes from the same invoice.

The most common misunderstanding is assuming the 2030 deadline automatically brings domestic real-time reporting to Estonia, Latvia or Lithuania. It doesn’t. The directive directly regulates only cross-border B2B activity; each country still decides its own domestic setup. The second common mistake is assuming a small turnover exempts a business from cross-border reporting; there’s no general threshold in the directive. And the third: Latvia’s 2028 B2B deadline and the EU’s 2030 deadline are two separate obligations from two different legal sources. One doesn’t replace the other.

FAQ

Mis vahe on e-arvel ja e-aruandlusel?

E-arve on struktureeritud äridokument, mis saadetakse kliendile. E-aruandlus on eraldiseisev tehinguandmete edastamine maksuametile. Mõlemad sünnivad samast tehingust, kuid liiguvad eri sihtkohtadesse.

Kas PDF-arve loetakse e-arveks?

Ei. PDF on mõeldud inimese silmale, mitte masinale, ega võimalda automaatset töötlust. ViDA nõuab struktureeritud, masinloetavat vormingut.

Millal hakkab ViDA e-aruandluse kohustus kehtima?

Piiriülene e-aruandluskohustus hakkab kehtima 1. juulil 2030. Kodumaised reeglid jäävad liikmesriikide otsustada ja kehtivad juba erinevatel aegadel.

Kas kodumaised tehingud kuuluvad ViDA alla?

Ei. ViDA ühtlustab ainult piiriülest B2B-aruandlust. Kodumaised tehingud jäävad liikmesriigi enda reguleerida, nt Eesti, Läti ja Leedu reeglid on erinevad.