Invoicea Juros-AI product

What a compliant invoice must show in Lithuania.

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 Lithuania's rules put on the face of the document, beyond the parties, line items and totals every invoice carries.

Document title
PVM sąskaita faktūra VAT 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 Lithuania rules expect on the invoice.

Seller
PVM mokėtojo kodas VAT number · LT + 9 or 12 digits · always
Seller
Įmonės kodas company code · 9 digits · always
Buyer
PVM mokėtojo kodas buyer VAT number · LT + 9 or 12 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.

Atvirkštinis apmokestinimas (PVM įstatymo 95 str.)Reverse charge
Intra-Community supplystatute ↗
PVM 0 proc. — prekių tiekimas į kitą valstybę narę, PVM įstatymo 49 str.0 % — intra-Community supply
PVM 0 proc. — prekių eksportas, PVM įstatymo 41 str.0 % — export
PVM neapmokestinama — PVM įstatymo 20–33 str.VAT exempt
Out of scopestatute ↗
Ne PVM objektas Lietuvoje — paslaugų suteikimo vieta užsienyje (PVM įstatymo 13 str.)Not taxable in Lithuania
Foreign seller (import)statute ↗
Be Lietuvos PVM — prekės iš trečiosios šalies; importo PVM sumoka importuotojas (PVM įstatymo 3 str. 3 d.)VAT not charged — supply outside the scope of Lithuanian VAT; import VAT is accounted for on importation by the importer (Art. 2(1)(d), 30, 70 and 201, Directive 2006/112/EC).

PVM įstatymo 80 str.: išrašymo data, serija ir numeris, PVM mokėtojo kodai, pavadinimai/adresai, prekių pavadinimas/kiekis, tiekimo data, vieneto kaina, nuolaidos, apmokestinamoji vertė, tarifas, PVM suma eurais.

The format, and who sends it

A plain PDF still counts as the invoice in Lithuania; 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 Lithuania 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 Lithuania 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