Invoicea Juros-AI product

What a compliant invoice must show in Latvia.

The fields, the party identifiers, the exact statutory wording for each tax treatment and the EUR rule — each cited to the statute or the tax authority, not a summary of one.

Tax figure in EUR Legal format EN 16931 UBL (Peppol BIS 3.0) PDF counts as the invoice

What the invoice must show

The content Latvia's rules put on the face of the document, beyond the parties, line items and totals every invoice carries.

Document title
Rēķins Invoice
Tax shown in
EUR
Payment terms
Due date or payment terms required

How each party is identified

The registration numbers and their formats the Latvia rules expect on the invoice.

Seller
PVN maksātāja numurs VAT number · LV + 11 digits · always
Buyer
PVN maksātāja numurs buyer VAT number · LV + 11 digits · when registered for the tax

The exact wording, by tax treatment

When no tax is charged, the invoice has to say why — in the words the law names. Each is linked to the statute or tax authority it was read from.

nodokļa apgrieztā maksāšana (PVN likuma 142. pants)Reverse charge
Intra-Community supplystatute ↗
PVN 0 % — preču piegāde Eiropas Savienības teritorijā, PVN likuma 43. panta 4. daļa0 % — intra-Community supply
PVN 0 % — preču eksports, PVN likuma 43. panta 1. daļa0 % — export
Atbrīvots no PVN — PVN likuma 52. pantsVAT exempt
Out of scopestatute ↗
Nav apliekams Latvijā — pakalpojuma sniegšanas vieta ārvalstīs (PVN likuma 19. pants)Not taxable in Latvia
Foreign seller (import)statute ↗
Bez Latvijas PVN — piegāde no trešās valsts; importa PVN maksā importētājs (PVN likuma 5. panta 1. daļas 2. punkts)VAT not charged — supply outside the scope of Latvian VAT; import VAT is accounted for on importation by the importer (Art. 2(1)(d), 30, 70 and 201, Directive 2006/112/EC).

PVN likuma 125. pants: datums, numurs, PVN numuri, nosaukums/adrese, preču daudzums un veids, piegādes datums, vienības cena, atlaides, ar nodokli apliekamā vērtība pa likmēm, likme, nodokļa summa; atsauce uz atbrīvojumu.

The format, and who sends it

A plain PDF still counts as the invoice in Latvia; a structured e-invoice is accepted where the buyer asks for it.

Legal format(s)
EN 16931 UBL (Peppol BIS 3.0) · PDF invoice
Transmission
Sent supplier→buyer; no government clearance in the path

Don't just look these rules up. Generate them.

Invoice by Juros-AI builds the Latvia e-invoice — EN 16931 UBL (Peppol BIS 3.0) — and checks it against the official schema on your own machine before anything is sent. Invoice by Juros-AI reads any invoice into clean data and is adding compliant invoice creation — the same rules on this page, built into the engine, run entirely on your own hardware. No cloud, nothing uploaded, no figure invented.

Talk to us about Latvia invoicing → or see the product — free to evaluate, no account

Every generated invoice is validated on your machine against the official artefacts — the OASIS UBL/CII schemas, the CEN EN 16931 schematron, Peppol BIS 3.0, KoSIT XRechnung, FatturaPA, KSeF FA(3) and the Peppol PINT packages. This page is a reference for build scoping; it is not legal or tax advice.

Invoice rules for other markets