E-Invoicing in Lithuania: E.sąskaita, PEPPOL & EN 16931
Lithuania requires structured e-invoices for the public sector through the national E.sąskaita platform, built on PEPPOL BIS 3.0 and the EN 16931 European standard. B2B e-invoicing is expanding in line with the EU ViDA reform. aiDoks validates and generates the right format — free.
Suppliers to Lithuanian contracting authorities (state and municipal buyers) must submit structured e-invoices through the national E.sąskaita / SABIS platform, in a format aligned with EN 16931. Paper invoices are not accepted by public-sector buyers.
PEPPOL
Connected to the PEPPOL network
Lithuania participates in the PEPPOL network, so invoices can be exchanged through any certified PEPPOL access point. PEPPOL BIS 3.0 is the practical standard for both public-sector and cross-border invoicing.
B2B
Expanding in line with EU ViDA
A wider B2B e-invoicing mandate is being prepared in step with the EU VAT in the Digital Age (ViDA) reform — transitional B2B measures from 2028 and digital reporting by 2030. Adopting PEPPOL now makes you ready in advance.
Which format do you need?
PEPPOL BIS 3.0 (the standard)
PEPPOL BIS Billing 3.0 (UBL 2.1, conforming to EN 16931) is the format used across Lithuanian public-sector and PEPPOL invoicing. The same file works for cross-border trade with partners elsewhere in the EU.
EN 16931 (baseline norm)
The European e-invoicing standard underlying both E.sąskaita and PEPPOL. A valid PEPPOL BIS 3.0 invoice is always a valid EN 16931 invoice. aiDoks validates against the full EN 16931 rule set, so you catch errors before sending.
E.sąskaita / SABIS channel
Public-sector invoices are submitted through the national E.sąskaita information system, or through a connected PEPPOL access point. The invoice content is the same EN 16931 structure regardless of the channel.
Factur-X / cross-border formats
Trading with German or French partners? They may send Factur-X / ZUGFeRD (hybrid PDF) or XRechnung. aiDoks converts CII and Factur-X to PEPPOL UBL and back, so you can accept and re-issue invoices in whichever format each partner requires.
How e-invoicing works in Lithuania
A structured e-invoice is an XML document (PEPPOL BIS 3.0 / EN 16931), not a PDF. The supplier's software creates the XML and sends it through a PEPPOL access point or the E.sąskaita platform; the buyer receives it directly into their accounting system. Each participant is identified by a PEPPOL participant ID — for Lithuanian companies typically the company or VAT registration number. Because both ends speak the same EN 16931 structure, the invoice is processed automatically, with no manual re-keying.
Who is in scope and when
B2G: any business invoicing a Lithuanian state or municipal buyer must send a structured e-invoice via E.sąskaita.
B2B: not yet a blanket mandate — a wider requirement is being prepared in line with the EU ViDA timeline.
Cross-border: PEPPOL BIS 3.0 is the practical standard for invoicing EU partners — the same file works.
B2C: consumer invoices are outside the structured-invoice scope.
How aiDoks helps Lithuanian businesses
Use aiDoks to validate any PEPPOL BIS 3.0 / EN 16931 invoice against the official schematron before you send it, so a buyer's access point or E.sąskaita never rejects it. Generate a compliant invoice from a simple form, or upload a PDF and let AI OCR extract the data into a structured invoice. And convert between PEPPOL UBL, CII and Factur-X when you trade with partners on other formats. aiDoks prepares and checks the file — your access point handles transmission.
E-invoicing in Lithuania: FAQ
Is e-invoicing mandatory in Lithuania?
For B2G, yes. Suppliers to Lithuanian public-sector buyers (contracting authorities) must submit structured e-invoices through the national E.sąskaita / SABIS platform, in a format aligned with EN 16931. For B2B, structured e-invoicing is not yet universally mandatory, but Lithuania is rolling it out in line with the EU VAT in the Digital Age (ViDA) reform, and PEPPOL BIS 3.0 is the practical standard already in use.
What is E.sąskaita?
E.sąskaita ("e-invoice") is Lithuania's national e-invoicing information system for public procurement. Suppliers invoicing state and municipal buyers prepare and submit structured e-invoices through it (or through a connected PEPPOL access point). It uses the EN 16931 / PEPPOL BIS 3.0 structure, so the same invoice format works for cross-border trade too.
What format does Lithuania use for e-invoices?
PEPPOL BIS 3.0 (UBL 2.1, conforming to EN 16931) is the standard. Lithuania is connected to the PEPPOL network, and the E.sąskaita platform accepts EN 16931-compliant invoices. Because it is the common EU format, an invoice you generate for a Lithuanian buyer also works for partners elsewhere in the EU.
Is B2B e-invoicing mandatory in Lithuania?
Not yet as a blanket mandate. Lithuania's firm requirement today is B2G (public sector). A wider B2B mandate is being prepared in line with the EU ViDA timeline (transitional B2B measures from 2028, digital reporting by 2030). Many Lithuanian businesses already exchange PEPPOL invoices voluntarily because their ERP and accounting software supports it.
How do I send a PEPPOL e-invoice in Lithuania?
Through a PEPPOL access point (a certified service provider) or the national E.sąskaita platform for public-sector invoices. Your software produces the EN 16931 XML and the access point delivers it to the buyer. aiDoks generates and validates the invoice file; the access point or E.sąskaita handles transmission.
How does aiDoks help with Lithuanian e-invoicing?
aiDoks validates PEPPOL BIS 3.0 / EN 16931 invoices against the official schematron so they are accepted on the first try, generates compliant invoices from a guided form or an uploaded PDF (AI OCR), and converts between PEPPOL UBL, CII and Factur-X for cross-border partners. Free to start, no sign-up required to validate.