Latvia E-Invoicing Requirements: 2026-2028 Guide

Latvia e-invoicing requirements now work on a phased timeline, not a single nationwide switch. Structured e-invoices have already been mandatory for invoices issued to budget institutions since January 1, 2025, with the remaining transition for older contracts ending on January 1, 2026. From January 1, 2026, structured e-invoice data for government-related flows must also be submitted to VID, while the broader domestic business-to-business mandate does not start until January 1, 2028.

That timeline matters because many English-language explainers still reflect the older expectation that Latvia would require general B2B e-invoicing from January 1, 2026. That is no longer the live position. If you are checking whether Latvia e invoice requirements already apply to all business invoices, the short answer is no. The rules already affect suppliers invoicing budget institutions and government-related reporting flows, but ordinary domestic B2B invoicing has a later deadline.

The practical way to read Latvia's regime is by transaction type:

• Now: invoices issued to budget institutions already need to be structured e-invoices.
• From January 1, 2026: government-related flows add structured invoice data submission to the State Revenue Service, or VID.
• From January 1, 2028: the broader structured electronic invoice mandate reaches general domestic B2B transactions.
• Still out of scope for the mandate: B2C is not part of the current rollout.

That phased model is what makes Latvia different from a generic country summary. To stay compliant, you need to separate three questions: which transactions are already in scope, which deadline applies to your workflow, and whether you are dealing with invoice exchange, VID reporting, or both.

---

What changed for invoices to budget institutions

For public-sector invoicing, the first big change arrived on January 1, 2025. From that date, invoices issued by Latvian businesses to budget institutions moved into the structured e-invoice regime. In practical terms, suppliers could no longer treat those invoices as an ordinary PDF-only billing exercise if the public recipient required structured exchange.

There was, however, an important transition layer. Contracts signed by December 31, 2024 could continue under the temporary exception until January 1, 2026. After that date, the carve-out falls away, which is why 2026 still appears in official summaries even though the public-sector obligation began earlier.

The clearest official shorthand comes from Latvia's Ministry of Finance summary of 2026 e-invoice changes, which says that from January 2026 invoices to budget institutions must be issued as e-invoices and that e-invoice data for transactions between companies and state or municipal institutions must be submitted to the State Revenue Service. That statement matters because it confirms both the end of the transition and the added reporting layer.

It also helps to separate invoice format and transmission from ordinary invoice-content compliance. A business can still need the right legal wording, VAT fields, and dating rules even after it moves to structured exchange. If you need that separate compliance layer, see our guide to Latvia VAT invoice fields, deadlines, and wording rules. This Latvia B2G e-invoicing step is about who must issue a structured invoice to a public recipient and when, not about replacing the standard tax-content rules that sit alongside it.

Why Latvia's broader B2B mandate now starts in 2028

The broader all-business mandate now starts on January 1, 2028, not January 1, 2026. That single date change explains most of the confusion in search results. Many advisory alerts and vendor pages were written when 2026 was still the expected deadline, then never fully updated after the postponement. As a result, readers still encounter outdated summaries that make it sound as though every business invoice in Latvia should already be structured.

So when readers search for the Latvia e-invoice mandate 2028, they are usually trying to reconcile those outdated references with the current legal timeline. The practical takeaway is straightforward: ordinary domestic B2B flows are on a preparation path, but they are not yet under the live mandate that already affects public-sector invoicing and government-related reporting.

Latvia Accounting Law Section 11 is still important because it sets the legal direction toward structured electronic invoices between Latvian undertakings. In other words, the idea of B2B structured invoicing did not disappear. What changed was the implementation timing. That distinction matters if you are designing systems or advising clients, because "not yet mandatory" does not mean "ignore it until late 2027."

It is also important to define what remains outside the current rollout. B2C is not part of the mandate, and ordinary domestic B2B does not become mandatory until 2028. So if your business only invoices consumers, or only issues business invoices that do not fall into the government-related scope discussed later in this article, the current legal pressure is lower than for suppliers serving budget institutions.

How invoices circulate in Latvia's decentralized model

Latvia does not operate as though every compliant invoice must pass through one national exchange pipe. The country uses a decentralized e-invoicing model, which is why finance teams need to think about routing as well as mandate dates.

For public-sector flows, the state route matters because eAddress provides a free channel for sending and receiving invoices to public recipients. That is often the simplest way to understand Latvia eAddress e-invoice handling: it is the government-backed delivery route that supports public-sector exchange, rather than a universal rule that every in-scope invoice must follow one identical path.

At the same time, Latvia also allows room for commercial service operators and interoperable networks. In practice, that means some parties may exchange invoices through operator-led connections or Peppol-compatible routes, depending on the recipient setup and the services being used. When people ask about Latvia Peppol e-invoicing, the key point is that Peppol can be relevant as a transport or interoperability option, but it is not the same thing as saying Latvia has one mandatory Peppol-only architecture for every invoice.

The European Commission's country guidance also adds an important technical point: public authorities use EN 16931, and Latvia does not apply a national CIUS or local extension on top of it. That keeps the Latvian model more flexible than some country implementations that impose a tighter domestic specification.

If you want a wider public-sector comparison, our article on public-sector e-invoicing through Peppol or state portals shows how another EU setup handles government routing. For a different interoperability example, our guide to Finvoice, TEAPPSXML, and Peppol routing models helps illustrate how routing logic can differ even when the compliance question looks similar on the surface.

---

Invoice exchange and VID reporting are not the same task

One of the most useful distinctions in Latvia's phased model is this: sending a structured invoice to the recipient is not automatically the same thing as submitting invoice data to VID. Those are related compliance tasks, but they are not identical.

From January 1, 2026, Latvia adds a reporting step for government-related flows. The briefest way to frame it is:

• G2G: government-to-government transactions
• B2G: business-to-government transactions
• G2B: government-to-business transactions

For those flows, you need to think about two layers at once. First, how is the structured invoice exchanged with the counterparty? Second, what structured invoice data must be submitted to the State Revenue Service, and who in the process is responsible for doing it? A workflow can satisfy the delivery side and still fail on the reporting side if that second question is left vague.

That reporting step should be understood as a structured data obligation, not just proof that an invoice was sent somewhere. In other words, teams should not assume that emailing a visual invoice copy, or even routing a structured invoice to the recipient, automatically completes the VID side. The requirement concerns the invoice data itself, so businesses need to confirm which structured fields, identifiers, totals, and counterparty details are passed forward in the reporting flow and whether that handoff happens automatically or through a separate control.

That is why Latvia VID e-invoice reporting should be treated as a control problem, not just a file-format problem. Teams need to know which transactions are covered, where the structured data originates, whether the submission step is built into their operator setup, and who checks that the data sent to VID matches what was actually exchanged with the public-sector counterparty.

Before you change systems or supplier instructions, confirm four points internally:

1. Which of your transactions fall into G2G, B2G, or G2B scope.
2. Which route you are using for invoice exchange, such as eAddress or an operator connection.
3. Which team or service is responsible for VID submission.
4. How you will handle exceptions, corrected invoices, and mismatches between exchanged and reported data.

What finance teams should do before the next phase

The most practical response to Latvia's timeline is to treat 2026 and 2028 as separate implementation projects that share some groundwork. You do not need to rebuild every invoice workflow immediately, but you do need a clearer map of your in-scope transactions and data responsibilities.

Start with the basics:

1. Map transaction scope. Separate invoices to budget institutions, other government-related flows, ordinary domestic B2B, and B2C.
2. Confirm exchange channels. Document when eAddress is required, when a commercial operator is used, and when Peppol-compatible routing is relevant.
3. Validate structured fields early. Make sure the data you generate or capture can support compliant structured exchange and later reporting.
4. Assign VID ownership. Decide whether finance, tax, IT, or an external provider is responsible for data submission and exception handling.
5. Test edge cases. Check credit notes, contract transitions, cross-team handoffs, and invoices that enter the process in mixed formats before they are converted or standardized.

This is also the point where many organizations realize that ordinary invoice compliance and structured workflow design are separate workstreams. You may already know your legal invoice fields, yet still need better controls for collecting, normalizing, and validating invoice data across suppliers and channels. If your team is tightening invoice data extraction workflows, the objective is to prepare reliable structured data before exchange or VID submission, not to replace the legal routing rules that Latvia imposes.

Suppliers working with public bodies should also review contract dates, recipient onboarding requirements, and any operator dependencies well before a deadline. Advisors and shared-service teams should update their client or entity playbooks now, because the hardest part of Latvia's model is usually not understanding one rule in isolation. It is keeping timing, routing, and reporting responsibilities aligned across multiple parties.

The phased model gives finance teams time, but not much value in waiting. 2026 is about operational readiness for government-related flows. 2028 is about broader B2B readiness. The teams that start mapping scope, channels, and data quality now will have a much cleaner path through both stages.