Latvia VAT Invoice Requirements: 2026 Checklist

Latvia VAT invoice requirements are stricter than a generic field checklist. A compliant Latvian VAT invoice should show the supplier and customer details required by law, a unique sequential invoice number, the invoice date, the supply date if it differs, a description of the goods or services, the taxable amount, the VAT rate, the VAT amount, and the total payable. It also needs the wording "self-billing" when the customer issues the invoice, "reverse charge" when the customer is liable for VAT, a check on whether the invoice had to be issued by the fifteenth day after the supply or advance payment, and, where another currency is used, a VAT amount expressed in euro.

For most readers, the practical question is not whether Latvia has VAT invoice rules. It is what must be on an invoice in Latvia so the document can be issued, reviewed, and booked without a later compliance problem. The useful starting point is Latvia's Value Added Tax Law invoice rules, especially Section 125, which sets out the core content requirements and also ties in the wording and timing rules that make Latvian invoices different from a generic EU checklist.

In operational terms, start with these checkpoints:

• Supplier identification, including VAT registration details where the law requires them
• Customer identification, including VAT details where applicable
• A unique sequential invoice number
• The invoice date
• The supply date or period, if it is different from the invoice date
• A clear description of the goods or services
• The taxable amount
• The applicable VAT rate
• The VAT amount
• The total amount payable
• The correct wording where the invoice is self-billed or subject to reverse charge

That base checklist matters because Latvia's law does more than require standard document fields. The same legal framework also recognizes simplified invoices for certain inland transactions under EUR 150 excluding VAT, generally requires invoices no later than the fifteenth day after the transaction or advance payment, and expects VAT amounts to be shown in euro if the invoice is issued in another currency. Those details are where many broad country-guide templates stop being useful.

If you are reviewing a Latvian invoice, treat the checklist as a sequence rather than a loose group of fields. First confirm that the document identifies the parties and the transaction clearly enough for VAT purposes. Then check whether the invoice type changes the rule set: simplified invoice, self-billing, reverse charge, foreign-currency invoice, or a transaction that falls under the timing rules discussed below. That Latvia-specific sequence is what keeps this from being just another high-level VAT explainer.

When a Latvian VAT Invoice Must Be Issued

The timing rule is straightforward once you separate the common cases. In general, when a Latvian VAT invoice is required, the outside deadline is no later than the fifteenth day after the taxable supply or after receipt of an advance payment. Section 131 is the provision finance teams should have in mind here. The legal question is not only whether the invoice exists, but whether it was issued within the period the law allows.

This matters most in two situations. The first is the ordinary domestic workflow where goods or services are supplied and the supplier still has a short period to issue the invoice. The second is the cross-border workflow, especially certain intra-EU supplies and services, where the relevant date can shift into the following month and the fifteenth day becomes the deadline marker for the invoice. If you are validating files for VAT support rather than drafting them yourself, this is the point where you should stop relying on a supplier's internal practice and check the legal timing rule instead.

In practice, the safest way to review timing is to compare three dates:

1. The date of supply or the period the invoice covers
2. The date any advance payment was received
3. The invoice date shown on the document

If the invoice date falls outside the permitted window, the document may still contain the right content, but the issuance requirement has not been met properly. That distinction matters because content errors and timing errors are different compliance problems.

The European Commission's VAT reference materials help frame the cross-border context, but Latvia's own law is the operative rule set for invoice issuance timing. For teams comparing neighboring jurisdictions, the main lesson is that "fifteenth day" is not just a drafting convention. It is a working compliance deadline that should be reflected in your review process, especially for advance payments and intra-EU transactions.

If you are building a review checklist, make the timing test explicit:

• Was there an advance payment that started the invoicing clock earlier?
• Is this an intra-EU transaction with a next-month fifteenth-day deadline?
• Does the invoice date shown on the document actually fall within that window?

That kind of date-based check is often the difference between a document that looks fine at a glance and one that is legally late.

When Latvia Allows a Simplified Invoice

Latvia does not require a full-form VAT invoice for every low-value domestic transaction. The main rule to know is that a simplified invoice can be used for inland transactions under EUR 150 excluding VAT. Section 126 is the part of the Latvian VAT law that matters here. That is the threshold most readers mean when they search for the Latvia simplified invoice threshold.

The important compliance point is that "simplified" does not mean informal. A lower-value document still has to fall within the legal conditions for simplified invoicing. If the transaction is above the threshold, cross-border, or otherwise outside the simplified route, you should expect the fuller invoice detail required under the ordinary VAT invoice rules.

This is where review teams often get caught out. A short invoice, receipt-style document, or compact point-of-sale output may look acceptable on first pass, but the real question is whether the transaction was one that Latvia allows to be documented in simplified form. The law also contains narrower low-value document rules for certain cash-register or equivalent records, so small-amount documents are not all treated the same way.

Operationally, a simplified invoice is best seen as an exception with conditions, not a lighter version you can choose for convenience. If the supplier or your AP team cannot explain why the document qualifies for simplified treatment, pause there and verify whether the transaction should instead carry the fuller detail associated with a standard VAT invoice. That check becomes even more important when the invoice later feeds into VAT reporting or audit support.

A practical review shortcut is to ask three questions before accepting simplified treatment:

• Is the transaction domestic rather than cross-border?
• Is the value within the legal threshold?
• Does the document type match a route the law actually recognizes for simplified invoicing?

If any answer is unclear, default to checking whether a full VAT invoice should have been issued instead.

Required Wording for Self-Billing and Reverse Charge

Two short phrases carry a lot of compliance weight on Latvian invoices: "self-billing" and "reverse charge." They are not optional labels added for convenience. They signal that the invoice is being issued under a different VAT treatment, and finance teams should review them accordingly.

If you are checking Latvia self-billing invoice wording or Latvia reverse charge invoice wording, focus first on the legal trigger behind each phrase and only then on the label itself.

"Self-billing" is used when the customer, rather than the supplier, issues the invoice. Section 130 is the key reference point here. Under Latvia's VAT framework, that arrangement is not just an administrative shortcut. It should rest on prior agreement between the parties and an acceptance procedure so the supplier accepts the invoices created on its behalf. If you see self-billing wording on a document, the review question is whether the commercial arrangement genuinely supports customer-issued invoicing, not merely whether the phrase appears on the page.

"Reverse charge" serves a different purpose. It tells the reader that the customer is liable for the VAT instead of the supplier. That has direct consequences for how the invoice is reviewed, posted, and supported. A reverse-charge invoice should therefore be checked against the underlying transaction logic, not only against the wording itself. If the liability position is wrong, the label does not fix the document.

For AP and bookkeeping teams, the practical discipline is to separate the two labels:

• Self-billing changes who issues the invoice and requires an agreed process.
• Reverse charge changes who accounts for the VAT.

They can overlap in some workflows, but they are not interchangeable. If you work across multiple EU jurisdictions, Luxembourg's VAT invoice rules on simplified invoices and mandatory wording offer a useful comparison point because they show how another country also treats mandatory invoice wording as a substantive compliance signal rather than a formatting detail.

In day-to-day review work, that usually means asking for more than the invoice itself. For a self-billed document, you may need evidence of the underlying agreement and the supplier's acceptance process. For a reverse-charge document, you may need enough transaction context to confirm that the VAT liability really sits with the customer.

Foreign-Currency Invoices Still Need VAT Amounts in Euro

Latvia allows invoices to be issued in another currency, but that does not remove the need to show VAT in euro. For cross-border finance teams, this is one of the most practical Latvia-specific rules to build into invoice review and system validation.

For any Latvia foreign currency VAT invoice, that means your review cannot stop at the commercial totals and exchange-rate presentation.

The reason is simple: VAT accounting still needs a euro expression of the VAT amount payable or adjusted, even when the commercial invoice itself is denominated in another currency. If that euro expression is missing, the document may be harder to support in downstream VAT records, and the issue is easy to miss if your review process focuses only on the invoice total.

From a controls perspective, this rule deserves its own check. Teams often confirm the invoice currency, exchange rate logic, and total amount, then move on. Latvia's rule adds another question: is the VAT amount itself expressed in euro where required? That is especially relevant when invoices move through shared-service AP processes or cross-border bookkeeping workflows where reviewers are not Latvian tax specialists.

This is also a good example of why generic country pages can be misleading. They often explain foreign-currency invoicing in broad EU terms without highlighting the local expression rule that actually changes how a document should be validated. If you are comparing similar treatment elsewhere, Ireland's VAT invoice checklist for simplified invoices and euro conversion is a useful internal reference because it also deals with the practical crossover between local invoicing rules and currency handling.

What Latvia's E-Invoicing Rollout Changes, and What It Does Not

One reason this query is harder than it looks is that the live SERP mixes ordinary VAT invoice requirements with Latvia's structured e-invoicing rollout. Those are related topics, but they are not the same rule set.

The key distinction is this: structured e-invoicing changes how certain invoices are transmitted and handled in the workflow, but it does not replace the baseline VAT invoice content rules described above. Teams still need to check the invoice fields, the issue deadline, the simplified-invoice threshold, the self-billing and reverse-charge wording, and the euro expression of VAT amounts where another currency is used.

The current official timeline matters because searchers are seeing fresh update coverage. Based on the latest European Commission Digital Building Blocks guidance, mandatory B2G e-invoicing in Latvia has applied since January 1, 2025. The planned B2B mandate was then postponed on June 5, 2025 and is now due from January 1, 2028. That postponement is important because older summaries may still describe a nearer deadline.

For readers tracking Baltic developments, Estonia's e-invoicing requirements if you also need Baltic e-invoice context help illustrate the difference between transmission mandates and the underlying content checks finance teams still have to perform. In Latvia, the State Revenue Service of Latvia is also part of the practical monitoring picture because finance teams need to watch official implementation updates as the structured e-invoice regime expands.

The practical takeaway is that structured e-invoicing is an additional workflow layer. It does not make the ordinary VAT invoice checklist irrelevant.