Does Latvia’s E-Invoice Mandate Apply to Estonian Firms?

The short answer: no. The obligation doesn’t arise simply because your customer sits in Latvia. VID, the State Revenue Service (Latvia’s tax and customs authority), describes structured e-invoice circulation as a duty of public administration and of companies registered in Latvia, not as a duty falling on a seller established in another member state. The B2B provision of the Accounting Law likewise talks about an invoice issued by a Latvia-registered company to another Latvia-registered company. So three things decide your case: whether you have a branch or permanent establishment in Latvia, whether your customer is a Latvian state authority, and how the invoice technically travels. The private-sector B2B obligation starts in Latvia on January 1, 2028 — not in 2026. That date has been circulating wrongly in public debate. Cross-border Estonia–Latvia invoicing gets its own rules separately, from July 1, 2030.

Why “Registered in Latvia” Is the Deciding Phrase

A structured e-invoice is not a PDF attached to an email. It’s a machine-readable XML file, and under government Regulation No 749 its structure has to follow the UBL 2.1 and Peppol BIS Billing 3.0 specifications. UBL is the standard XML invoice format, and Peppol BIS Billing is the European profile of it used across the Peppol network. The regulation was adopted on December 9, 2025 and entered into force on December 13, 2025.

Latvia is switching over in stages. According to VID’s timeline, e-invoices are mandatory from January 1, 2025 between public administration and companies registered in Latvia (G2G, B2G and G2B), from January 1, 2026 invoice data in those same segments must also be reported to VID, and from January 1, 2028 the obligation extends to B2B invoices between companies registered in Latvia. During 2026 and 2027, reporting is voluntary for the private sector.

One practical nuance worth keeping in mind: VID states outright that these requirements don’t stop a Latvian company from issuing a structured e-invoice to a partner that isn’t registered in Latvia, if both sides agree to it. Your Latvian customer may well ask for one long before 2028, but the argument will be commercial, not legal.

How a Branch or Permanent Establishment Changes the Answer

This is where the comfortable answer disappears. The Accounting Law lists among its subjects the branch of a foreign merchant and the permanent representation of a non-resident in Latvia. If your Estonian company has a registered branch or a permanent establishment in Latvia, you are no longer just a foreign seller — you are a subject of the law, which means the public-sector requirements apply to you, and so does the 2028 B2B obligation.

Check this first, and check it on documents rather than on gut feel: is there an entry in the Latvian commercial register, and does your activity on the ground amount to a permanent establishment?

Does a Latvian VAT Number Alone Create the Obligation?

If you have no branch and no permanent establishment in Latvia but do hold a Latvian VAT registration number, the official materials reviewed don’t resolve that situation clearly. VID describes the circle of obliged persons more broadly than just companies. The list also includes “other subjects of the Accounting Law and the VAT Law”, and VID publishes a separate list of the law’s subjects. On the registration alone you can’t say the obligation arises, nor that it definitely doesn’t. The sensible step is to ask VID for a written position on your specific facts, and to keep the answer on file.

What Changes When Your Customer Is a Latvian State Authority

Here the answer is considerably clearer. In settlements with Latvian state authorities the e-invoice is mandatory according to VDAA, Latvia’s state digital development agency, and those authorities have to accept e-invoices. The supplier may deliver the invoice via the e-address, by email, or in another way agreed in the contract. For an Estonian seller, one detail matters: the e-address, Latvia’s official state electronic communication channel, can’t be used between legal persons that aren’t state authorities. For a non-resident, the invoice travels through a Peppol Access Point — in practice, through a certified operator.

Before the first send, sort out three things: the authority’s correct recipient identifier, the agreed channel, and XML validation. VDAA lists the most frequent errors as exactly these: the wrong message type, validation failures in hand-built XML, and an attachment containing only a PDF with no XML file.

How Fast Must the Invoice Reach VID, and What If the System Fails?

If the reporting obligation does apply to you, Regulation No 749 sets out that the e-invoice is submitted to VID once, no later than five working days after the day it was sent. In case of a system failure, you must notify it no later than the next working day after the deadline passed, and submit the invoice within three working days after the fault is fixed. For breaching the rules on issuing and registering source documents, the Accounting Law provides for a warning or a fine of up to 86 fine units, which at the current value of the unit means a maximum of €430.

Why July 1, 2030 Is a Separate Layer

Cross-border Estonian–Latvian sales won’t stay behind Latvia’s domestic logic forever. Council Directive (EU) 2025/516 brings an e-invoice-based digital reporting obligation for cross-border B2B transactions across the EU from July 1, 2030. That comes from EU law, not Latvian law, and it reaches Estonian companies with no presence in Latvia at all. If you fall outside Latvia’s requirements today, that’s a good reason to build Peppol capability calmly rather than in a hurry. There’s time — but the date is fixed.

Also available in: eesti keeles · latviski

Last reviewed: 14 September 2026