home

Indirect Tax

Sovos Docs

Lithuania

Lithuania's SAF-T system, i.MAS, modernizes tax administration with comprehensive reporting requirements for VAT transactions, transport documents, and accounting data.

Modules

Lithuania's SAF-T implementation, known locally as i.MAS (Intelligent Tax Administration System), consists of three distinct modules:

ModuleDescriptionFiling requirementDeadline
i.SAFVAT invoice register with sales and purchase informationMandatory monthly20th day of the following month
i.VAZTransport/consignment documents for domestic goods movementMandatory before goods movementPrior to transport
i.SAF-TComprehensive accounting data including general ledger, customer/supplier information, assets, and inventoryOn-request onlyWithin 30 days of request
Note:

While i.SAF requires regular monthly submissions from all VAT-registered entities, the full i.SAF-T module is only submitted when specifically requested by tax authorities during audits or investigations.

Possible penalties

Non-compliance with Lithuania's i.MAS requirements can result in significant penalties:
  • Failure to submit i.SAF: Penalties ranging from €200 to €6,000 depending on severity and frequency

  • Late submission: Administrative penalties based on the delay period

  • Inaccurate data: Penalties proportional to the tax impact of errors

  • Repeated violations: Increased penalties for systematic non-compliance

Special considerations

Non-residents
Foreign entities with Lithuanian VAT registration must comply with i.SAF monthly reporting requirements. However, only resident businesses are required to maintain i.SAF-T readiness for on-demand submission.
Small businesses
The implementation of i.SAF-T was phased based on business size:
  • From January 1, 2019: Companies with revenue exceeding €45 million in 2018

  • From January 1, 2020: Companies with revenue between €3 million and €45 million in 2019

  • From January 1, 2021: Companies with revenue less than €3 million in 2020

Currently, all businesses must comply regardless of size.

Industry specific requirements
All industries must comply with the same technical requirements. There are no industry-specific variations in the i.MAS system.

File structure

Lithuania's i.MAS files must be generated in XML format with specific structures:
  1. i.SAF structure
    • Header: contains metadata about the reporting entity and period

    • Master file: Contains data from registers of issued and received VAT invoices

    • Source documents: Details of each invoice with optional payment information

    • Format: XML following Lithuania's specific schema

  2. i.SAF-T structure
    • Header: Metadata about the file, company, and reporting period

    • Master files:
      • Chart of accounts

      • Customer and supplier information

      • Product and service classifications

      • Tax tables

      • Unit of measure tables

      • Analysis codes

    • General ledger entries: All accounting transactions during the period

    • Source documents: Detailed information about invoices, payments, and other transactions

    • Assets: Fixed asset register and movement information

    • Inventory: Stock item details and movements

  3. VAT classification codes
    • Lithuania requires specific coding of transactions based on VAT treatment

    • Proper classification is essential for correct reporting

    • Both domestic and cross-border transactions require appropriate coding

Lithuania's i.SAF-T implementation follows the OECD standard but includes country-specific adaptations to align with local tax requirements.

Submission requirements

Deadlines
The i.MAS system has different deadlines for each module:
  • i.SAF (VAT invoice register): Must be submitted by the 20th day of the month following the reporting period. This is a strict monthly requirement for all VAT-registered entities.

  • i.VAZ (Transport documents): Must be submitted before the domestic movement of goods begins. This is an immediate requirement tied to each transport operation.

  • i.SAF-T (Full accounting data): Must be submitted within 30 days of receiving a request from tax authorities. There is no regular filing schedule; submissions are only required during audits or investigations.

Unlike some other countries, Lithuania does not currently require periodic submission of the full i.SAF-T file, but businesses must maintain their systems in a state of readiness to generate compliant files when requested.

Filing formats & methods

  • File format: XML only, following specific Lithuanian schemas
  • Character encoding: UTF-8
  • File size limits: 4 MB for manual upload; 5 MB for automated submission
  • Submission methods:
    1. Electronic Declaration System (EDS): Primary submission portal

    2. API Integration: For automated submissions from ERP systems

    3. Manual upload: Through the VMI portal for smaller businesses

Note:

Lithuania requires strict adherence to its XML schemas. Files that do not conform to the specifications will be rejected.

Authentication

Files must be authenticated using one of these methods when accessing the Electronic Declaration System (EDS):
Electronic Banking Authentication
Using credentials from Lithuanian banks
Smart-ID
Digital identity solution
Mobile signature
Mobile-based digital signature
Qualified electronic signature
EU-compliant digital signature

Each submission receives a digital stamp from the tax authority as confirmation of receipt.

How to file

  1. Prepare your i.SAF/i.SAF-T file:
    • Extract required data from your accounting system

    • Ensure proper VAT classification of all transactions

    • Format according to the required XML schema

    • Validate file structure before submission

  2. Validate the file:
    • Use the VMI's validation tools available on their website

    • Check for format errors and data consistency

    • Address any validation issues before proceeding

    • Generate a validation report for your records

  3. Access the Electronic Declaration System (EDS) portal:
    • Go to https://deklaravimas.vmi.lt

    • Log in using your authentication method

    • Go to the appropriate i.MAS section

  4. Upload and submit:
    • Select the correct reporting period

    • Upload your XML file

    • Review submission details

    • Complete the submission process

  5. Alternative: API submission:
    • For businesses with high transaction volumes

    • Implement direct system-to-system communication

    • Ensure proper error handling and confirmation processing

    • Maintain logs of all submissions and responses

Confirmation and follow-up

The Electronic Declaration System (EDS) provides a two-stage confirmation process for i.MAS submissions. First, you receive an immediate technical receipt confirmation. Later, usually within 24 hours, you receive a content validation confirmation. Each confirmation includes a unique document number, submission timestamp, and digital stamp from the tax authority.

You can check the status of your submission through the "Document Status" section of the EDS portal. If validation fails, you will receive notification of errors with the option to submit corrections.

If errors are detected in your submission, you must correct and resubmit within the timeframe specified by the tax authority. For i.SAF, corrections should be submitted as soon as possible, as this data affects your VAT compliance status.

Archive expectations

All supporting documents and underlying data must be retained for tenyears from the end of the financial year. This includes all transaction data that forms the basis of i.SAF and i.SAF-T submissions.

Electronic records must remain accessible throughout the retention period, with clear audit trails maintained between documents, entries, and reports. System changes or upgrades must not compromise access to historical data.

Lithuanian tax authorities may conduct detailed cross-checks between i.SAF monthly submissions and the i.SAF-T data provided during audits. Any inconsistencies can trigger additional scrutiny. Your systems must maintain the ability to regenerate historical reports and demonstrate data consistency across time periods.

Archived data must be secured against unauthorized changes while remaining accessible for audit purposes. Companies must document their accounting systems and processes to explain how data is generated and maintained.