ViDA e-invoice vs e-reporting: what is the difference?

Short answer: one document, two different destinations

ViDA (VAT in the Digital Age) e-invoice and e-reporting are not the same thing, although both often arise from the same transaction. An e-invoice is a structured business document that is prepared by the seller and received by the customer. It moves between two companies. E-reporting is instead the transmission of transaction data to the tax authorities, not the sending of the invoice itself to the customer. According to Council Directive (EU) 2025/516 This cross-border reporting obligation at the EU level will come into effect from 1 July 2030. Until that date, Estonia, Latvia and Lithuania will regulate their domestic e-invoicing and reporting with completely separate laws, and these deadlines are already different in the three countries today.

Feature	E-invoice	E-reporting
Who does this go to?	To the buyer or customer	To the Tax Board
What is it essentially?	Structured business document	Electronic transmission of transaction data
Format	Must allow automatic machining	A common electronic message, the format of which is determined by the Member State
Who fulfills the obligation?	The seller prepares and sends	Seller details, in some cases also buyer details
Valid cross-border from	From July 1, 2030	From July 1, 2030

What qualifies as a ViDA e-invoice?

According to the definition of the directive An e-invoice is an invoice that contains all the required VAT information and is prepared, sent and received in a structured electronic format that allows for automatic electronic processing. This is a technical test, not a visual one. The invoice must be machine-readable, meaning that the software can read and process the invoice data itself without anyone having to manually retype the numbers.

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

No. PDF is made for the human eye, not a machine, and according to the directive's approach such a file generally does not support automatic processing. This means that a PDF invoice sent to a customer by email does not meet the ViDA definition of an e-invoice, even if the content of the invoice is exactly correct. From 1 July 2030, e-invoice will become the default format under Article 218 of the Directive, but Member States may allow the use of a paper invoice or another format for transactions that are not subject to the digital reporting obligation.

What ViDA e-reporting actually requires from July 1, 2030

E-reporting is not an invoice. It is a separate data flow to the tax authorities. The mandatory scope is narrowly defined: it applies to supplies of goods from one EU Member State to another between businesses (B2B), intra-Community acquisitions and specific cross-border reverse charge supplies and acquisitions, such as: the directive describes them. Domestic transactions, such as an invoice from a Tallinn business to a Tartu customer, are not covered by this EU obligation.

The most important detail for small businesses: The directive does not provide for a general turnover- or amount-based threshold. If you sell goods cross-border to a business in another Member State, the obligation applies regardless of whether the turnover is 5,000 or 5 million euros.

The timing is precise. In the case of a covered cross-border supply, the seller must issue the invoice no later than 10 days after the chargeable event occurs; the advance payment for a reverse charge supply also triggers the same 10-day deadline. The seller's details are transmitted to the tax authorities at the time of issuing the invoice, in the case of self-invoicing, the deadline is up to five days after issuance. On the buyer's side, the details of the acquisition or reverse charge purchase may be transmitted up to five days after receipt of the invoice, but a Member State may decide that such an obligation on the part of the buyer shall not apply in its territory. The directive sets these deadlines exactly like that.

The data can be submitted by the company itself or through a third party; Member States are obliged to offer the option of electronic submission and accept submissions that comply with the European e-invoice standard and its listed syntaxes.

Example: 1200 euro invoice from Estonia to Latvia: invoice and reporting journey

Let's say your Tallinn company sells goods to a customer in Riga for 1,200 euros. From 1 July 2030, the supply of goods to a business in another Member State is exactly the type of transaction that cross-border reporting obligation covers.

Invoice side: you prepare a structured e-invoice for the customer that meets the machine-readable requirement and issue it no later than 10 days after the taxable event occurs, as follows: the directive requires.

Reporting side: At the same time as the invoice is issued, you send the transaction data to the Estonian Tax Authority. This is a separate data flow, not a copy of the invoice itself. If the Latvian customer needs to report the same transaction as an intra-Community acquisition on their side, they may be required to submit the data within five days of receiving the invoice. The exact obligation depends on whether Latvia decides to implement buyer-side reporting.

It is precisely this two-pronged model that causes confusion: one structured bill, but two separate obligations moving in two different directions.

Domestic rules are separate: Estonia, Latvia and Lithuania

ViDA only harmonises cross-border B2B reporting. Domestic e-invoicing and domestic transaction-based reporting, i.e. invoices where the seller and buyer are both in the same country, remain at the discretion of the Member State according to the directive; a country may establish its own rules and limit them to certain categories of taxpayers. For Member States that had a domestic real-time transaction-based reporting system in place or required by law before 1 January 2024, the Directive gives them until 1 January 2035 to align their system with the ViDA framework. This deadline specifically concerns those countries whose system meets this description, and not all Member States automatically.

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

Valid in Estonia from From July 1, 2025 Buyer-chooses model: a company that has publicly registered itself as an e-invoice recipient in the e-business register can request an e-invoice from the seller, but otherwise the transaction partners agree on the format and submission conditions themselves. For public sector institutions, the current e-invoice submission procedure will essentially remain in effect.

In Latvia, the schedule is more gradual and precise than in Estonia. Structured e-invoice is mandatory from 1 January 2025 in transactions with state and local government authorities (G2G, B2G, G2B); the transmission of data from these e-invoices to the Latvian State Tax Board (VID) will become mandatory from 1 January 2026. For business-to-business (B2B) transactions, a structured e-invoice and its simultaneous submission to VID will be mandatory from 1 January 2028. This B2B deadline was originally planned for the beginning of 2026, but was postponed by two years by an amendment to the law.

A different system has been in place in Lithuania for some time now, i.SAF register, where VAT payers must submit data on VAT invoices issued and received. Legal entities submit them by the 20th of the following month for the calendar month, but the deadline for natural persons depends on their VAT declaration period. This is a periodic, monthly reporting, not a transaction-based real-time transmission, and it operates according to its own logic, originating from the pre-ViDA era, and not according to the 1 July 2030 cross-border model.

What to prepare now and what not to expect

There is time until July 1, 2030, but it is worth adapting software and processes now, not at the last minute as the deadline approaches.

• Structured format support: Your invoicing software must be able to generate invoices that comply with the European e-invoice standard and the syntaxes listed in the directive. It is not enough for an invoice to „look good“ in PDF.
• VAT number check: Check that the system validates the customer's VAT number before issuing the invoice, as the correct handling of the cross-border transaction depends on it.
• Completeness of invoice details: All required VAT information must be in machine-readable format on the invoice, not just described as text.
• Correction flow: Think about how you will correct an invoice or report data that has already been submitted if an error is discovered later. Making manual corrections in two separate systems is many times more time-consuming.
• Customer format choice: Especially in Estonian B2B sales, where a registered buyer may request an e-invoice, your system must be able to correctly identify the customer and select the format accordingly.
• Separate interface for the tax authorities: The e-reporting data channel is not the same as the invoicing channel. They are two separate integrations, even if the data comes from the same invoice.

The most common misconception is that the 2030 deadline automatically means domestic real-time reporting obligations in Estonia, Latvia or Lithuania. This is not the case. The Directive directly regulates only cross-border B2B activities, the domestic arrangements are left to each country to decide. Another common mistake is to think that a small turnover exempts from cross-border reporting. There is no general minimum threshold in the Directive. And third: the Latvian 2028 B2B deadline and the EU 2030 deadline are two different obligations from different legal sources. One does not replace the other.

FAQ

What is the difference between e-invoicing and e-reporting?

An e-invoice is a structured business document that is sent to a customer. E-reporting is a separate transmission of transaction data to the tax authorities. Both arise from the same transaction, but go to different destinations.

Is a PDF invoice considered an e-invoice?

No. PDF is designed for the human eye, not a machine, and does not allow for automatic processing. ViDA requires a structured, machine-readable format.

When will the ViDA e-reporting obligation come into effect?

The cross-border e-reporting obligation will enter into force on 1 July 2030. Domestic rules remain at the discretion of the member states and are already in force at different times.

Are domestic transactions covered by ViDA?

No. ViDA only harmonises cross-border B2B reporting. Domestic transactions remain regulated by the Member State, e.g. Estonia, Latvia and Lithuania have different rules.