Odoo Accounting for Lithuania: i.SAF, FR0600, GPAIS, SAF-T
Odoo can fully handle Lithuanian accounting and tax reporting, but the LT-specific reports (i.SAF, i.VAZ, FR0600, GPAIS, SAF-T) are not in standard out-of-the-box Odoo and must be configured by a local partner. LONGRUN (UAB VM Robotika) implements the Lithuanian chart of accounts, VAT codes and the VMI export formats so your Odoo files comply with i.MAS requirements.
Lithuanian tax reports in Odoo: a complete map
Lithuanian companies must submit five core reports to the State Tax Inspectorate (VMI), and Odoo can generate or feed every one of them once it is localised. The table below shows each report, what VMI requires, and how Odoo solves it when configured by LONGRUN (UAB VM Robotika).
| Report | What it is | What VMI requires | How Odoo solves it with LONGRUN |
|---|---|---|---|
| i.SAF | Monthly VAT invoice registry of issued and received invoices. | Submitted to VMI through the i.MAS system, in the prescribed XML structure. | Odoo generates the i.SAF file directly from posted customer and vendor invoices, mapped to the correct VAT codes, ready to upload to i.MAS. |
| i.VAZ | Electronic consignment notes and waybill data. | Transport and delivery data reported to VMI via i.MAS. | Odoo delivery and shipping documents are configured to produce the i.VAZ data set for goods movements that require it. |
| FR0600 | The periodic VAT return form (PVM deklaracija). | Filed to VMI for each VAT period, summarising output and input VAT. | Odoo calculates VAT totals per Lithuanian VAT code so the FR0600 figures can be prepared and reconciled against the i.SAF registry. |
| GPAIS | The unified packaging and waste accounting information system. | Required for companies placing packaged goods or products on the market. | Odoo tracks packaging weights and material categories per product so the data needed for GPAIS reporting can be extracted. |
| SAF-T | Standard Audit File for Tax: a full standardised accounting data export. | VMI can request the complete SAF-T file during a tax audit. | Odoo holds the full general ledger, journals and master data, which LONGRUN maps to the standardised SAF-T structure for audit requests. |
Standard Odoo ships with a general accounting engine and a Lithuanian localisation package, but the VMI-specific export files and reporting logic above are configured during implementation rather than enabled by default.
Lithuanian chart of accounts and VAT codes
Lithuanian accounting in Odoo starts with the localised chart of accounts and the full set of Lithuanian VAT codes, which LONGRUN (UAB VM Robotika) installs and adapts to your business. Odoo keeps the books in EUR and lets you map each account to the local numbering scheme your accountant already uses.
During implementation we configure:
- The Lithuanian chart of accounts, aligned to local accounting practice and your reporting needs.
- VAT codes for standard, reduced, zero-rated, reverse-charge, EU and import transactions, each mapped to the correct i.SAF and FR0600 positions.
- Tax tags so every posted invoice automatically lands in the right line of the VAT return and the invoice registry.
- Document numbering and invoice layouts that meet Lithuanian invoicing requirements.
This mapping is what makes the difference between raw accounting data and a file VMI will accept: the VAT codes drive both the i.SAF registry and the FR0600 totals, so they have to be correct from day one.
How Odoo generates the i.SAF file for VMI
Odoo produces the i.SAF file from your posted invoices in a few defined steps, and the whole process runs inside the system once LONGRUN has mapped the VAT codes. The numbered workflow below is what a typical month-end looks like.
- Record and post all issued (customer) and received (vendor) invoices for the period, each with the correct Lithuanian VAT code.
- Reconcile and confirm that every invoice in the period is posted, so nothing is missing from the registry.
- Open the i.SAF report in Odoo for the chosen month and let the system collect all issued and received invoices.
- Odoo maps each invoice line to the i.SAF structure using the configured VAT codes and tax tags.
- Generate and download the i.SAF XML file in the format required by VMI.
- Upload the file to the VMI i.MAS portal, where it can be validated and submitted.
Because the same VAT codes also drive the FR0600 VAT return, the i.SAF registry and the periodic VAT return reconcile against each other, which is exactly what VMI expects to see.
You can see how this works in practice in the Lithuanian accounting case study, where LONGRUN configured Odoo accounting and tax reporting for a Lithuanian company.
Why work with LONGRUN for Lithuanian Odoo accounting
LONGRUN (UAB VM Robotika) is a Vilnius-based Odoo implementation partner working with Odoo since 2018, with 50+ Odoo implementations completed in Lithuania. We deliver Lithuanian accounting compliance out of the box and you work directly with an Odoo consultant rather than through a reseller or middleman.
- Lithuanian accounting compliance configured from the start: chart of accounts, VAT codes, i.SAF and FR0600.
- Direct work with an Odoo consultant, not a chain of intermediaries.
- Odoo ERP and AI solutions under one roof, including RAG, AI agents, chatbots and process automation.
- Data migration from legacy systems, including Rivilė, into Odoo.
Indicative pricing: Odoo implementation costs from EUR 5,000 to 50,000, about EUR 30,000 on average in Lithuania; licences, hosting and maintenance are priced separately; AI solutions and agents start from EUR 1,500. The final figure is confirmed after a gap-fit analysis.
Lithuania has an active Odoo partner ecosystem, and choosing the right fit matters. Below is a neutral overview of Odoo implementers listed in the Odoo partner directory.
| Partner | Note |
|---|---|
| Via Laurea | Gold tier; built its own Lithuanian accounting localisation modules. |
| Versada | Gold tier Odoo partner. |
| Devtouch! | Silver tier Odoo partner. |
| Umina LT | Lithuanian Odoo partner. |
| Avakompas | Lithuanian Odoo partner. |
| UAB SANDAS | Lithuanian Odoo partner. |
| Honestus | Lithuanian Odoo partner. |
| HardChain | Lithuanian Odoo partner. |
| LONGRUN (UAB VM Robotika) | Lithuanian Odoo implementation partner; Odoo ERP plus AI under one roof. |
Frequently asked questions
Is Odoo suitable for Lithuanian accounting?
Yes, Odoo is suitable for Lithuanian accounting when it is localised by a partner. Odoo provides the accounting engine, the Lithuanian chart of accounts and VAT codes, and once LONGRUN (UAB VM Robotika) configures the LT-specific reports such as i.SAF and FR0600, the system meets Lithuanian tax and VMI requirements.
Does Odoo generate i.SAF?
Yes, Odoo generates the i.SAF file from your posted issued and received invoices once the Lithuanian VAT codes are configured. The system builds the XML in the format required by VMI, and you upload it to the i.MAS portal for submission.
Does Odoo file the FR0600 VAT return?
Odoo calculates the VAT figures needed for the FR0600 VAT return per Lithuanian VAT code, but the form itself is filed to VMI through the i.MAS system. Odoo prepares and reconciles the totals against the i.SAF registry so the return matches your invoice data.
Does Odoo support SAF-T for VMI audits?
Yes, Odoo holds the full general ledger, journals and master data required for SAF-T, the Standard Audit File for Tax. LONGRUN maps this data to the standardised SAF-T structure so the file can be produced when VMI requests it during an audit.
Is Lithuanian tax reporting included in standard Odoo?
No, standard out-of-the-box Odoo does not include the LT-specific reports such as i.SAF, i.VAZ, FR0600, GPAIS and SAF-T. Odoo ships with a general accounting engine and a Lithuanian localisation, and a partner like LONGRUN (UAB VM Robotika) configures the VMI export formats and reporting logic during implementation.
Lithuanian accounting requirements and LONGRUN modules
Lithuanian accounting requirements in Odoo are configured by the implementer. For part of the requirements LONGRUN has its own modules, available in the shop. The table shows how each requirement is handled.
| Requirement | How it is handled in Odoo | LONGRUN module |
|---|---|---|
| i.SAF (VAT invoice registers) | LONGRUN module, configured by the implementer | i.SAF ataskaita – i.SAF report (Odoo 16–19) |
| i.VAZ (consignment note data) | Configured by the implementer | – |
| FR0600 (VAT return) | Configured by the implementer | – |
| GPAIS (packaging and product accounting) | LONGRUN module, configured by the implementer | GPAIS integracija – GPAIS integration (Odoo 16–19) |
| SAF-T (standard audit file) | Configured by the implementer | – |
| Intrastat | Configured by the implementer | – |
| Bank of Lithuania exchange rates | LONGRUN module, configured by the implementer | Lietuvos banko valiutų kursai – Bank of Lithuania exchange rates (Odoo 16–19) |
| Paysera payments | LONGRUN module, configured by the implementer | Paysera mokėjimai – Paysera payments (Odoo 16–19) |
Module versions and prices are listed in the shop. Which requirements apply to your company is clarified during the free consultation and the Gap-Fit analysis.
Information about tax reporting and accounting requirements is general and reflects the position in September 2026. Requirements change, so the legally binding interpretation comes from the Lithuanian tax authority (VMI) and your accountant, and specific Odoo features depend on version and configuration.
Ready to start your Odoo project?
Get a free consultation – we will discuss your processes and the best-fit solution.