SAF-T Lithuaniai.SAF MandatoryLast reviewed October 2026

SAF-T in Lithuania: the i.SAF explained

Lithuania requires VAT-registered businesses to submit invoice data to the State Tax Inspectorate (VMI) every month in the i.SAF file. Accounting data in the SAF-T format must also be available on request. i.VAZ, which is often mentioned in the same breath, is the separate electronic waybill system and not a SAF-T accounting file.

General information only, not tax advice. Rules change, so check the official sources at the bottom of this page before you act.

The mandate

i.SAF - Lithuanian invoice data file (SAF-T)

Who must file

All VAT-registered businesses in Lithuania.

How it works

Accounting system generates the i.SAF invoice file (XML) → submitted every month to the VMI → VMI validates it and cross-checks it against VAT returns.

Key dates for Lithuania

  1. Oct 2016
    i.SAF mandatory for VAT-registered businesses
  2. 2020
    Schema updates and stricter validation rules
  3. On request
    Accounting SAF-T data must be provided when the VMI asks for it

What the file contains

The i.SAF file contains sales and purchase invoice data (invoice header, parties, amounts and VAT) and is submitted every month. It must agree with the VAT return. Separately, accounting data in the SAF-T structure has to be available when the VMI requests it.

What your ERP has to deliver

The accounting or ERP system must export invoice data in the i.SAF schema, with the VAT codes and party data the VMI requires. It must also be able to produce SAF-T accounting data on request.

The data flow, step by step

Accounting system
i.SAF invoice file (XML)
Monthly submission to the VMI
VMI validation and cross-checks.

Practical insights

  • i.SAF covers invoices only. Teams sometimes assume it is a full ledger file, but the general ledger is requested separately, when the VMI asks for it.
  • The VMI compares i.SAF data with VAT returns and with the data of trading partners, so mismatches are visible quickly.
  • Many companies submit i.SAF through their ERP. Missing or wrongly mapped VAT codes are the most common cause of rejected files.

Common pitfalls

  • Confusing i.SAF (invoices) with i.VAZ (waybills) and treating them as one project.
  • Invoice totals in i.SAF that do not match the VAT return for the same month.
  • Incorrect or missing VAT classification codes on invoice lines.

Linked obligations in Lithuania

E-Invoicing: Lithuania is moving toward structured e-invoicing, which will need to line up with i.SAF data.
i.VAZ: the electronic waybill system is separate from i.SAF but the data should be consistent.

SAF-T Lithuania: questions, answered

Official sources

More SAF-T guides

Cookie Preferences

We use cookies to enhance your experience. You can manage your preferences below. Privacy Policy.