Odoo for a Lithuanian Company: Full Accounting and Automated Tax Reporting

Challenge

A Lithuanian company was already running its accounting in Odoo. The core bookkeeping worked. The part that mattered most did not. Lithuanian statutory tax reporting kept breaking, and every month it had to be patched by hand. The i.SAF export, currency rates, asset depreciation and bulk data import all needed manual correction before anything could be filed. When the time came to prepare reports for the State Tax Inspectorate, there was always a question mark over whether the numbers were right. The business needed Odoo to simply work under local rules, without a person standing over it every reporting period.

Standard Odoo does not understand the finer points of Lithuanian accounting. The biggest source of trouble was i.SAF. With reverse charge VAT or notional tax codes, the tax has to appear in the books and on the FR0600 VAT return, but the i.SAF file must carry only the taxable amount at a zero rate. Getting both of those right at the same time is where standard behaviour falls apart. On top of that, currency rates were entered manually. Fixed asset depreciation did not calculate on its own. When large batches of invoices were imported from other systems, they were posted under the wrong date instead of the real document date. Every one of these problems was being fixed directly in the live database. So any mistake immediately corrupted the reports the company depended on.

Solution

We set Odoo up so that Lithuanian reporting is accurate from the source data, not repaired afterwards. We configured the i.SAF export to follow the tax authority's own logic. Now, with reverse charge VAT, the tax shows correctly in the accounts and on the FR0600 declaration, while only the required taxable amount is written into the i.SAF file. FR0600 and the other VAT reports are generated automatically from the same underlying records, so the books and the filings always agree. We also brought the GPAIS packaging and waste reporting obligations fully under control.

Currency rates are now pulled automatically from the Bank of Lithuania. Depreciation runs on its own. Debt reconciliation statements work, and the Intrastat export works.

We fixed the bulk invoice import as well. Documents now post with the true invoice date and the full amount, not today's date. So historical data lands where it belongs. To let the client do this without us, we built a separate test database for trial runs and recorded a short video walkthrough. The whole setup runs across several separate databases, which keeps live data cleanly apart from anything being tested. Finally, we moved everything to a new server and checked once more that i.SAF generation and reconciliation statements stayed stable under the move.

Result

Lithuanian tax reporting became a reliable daily routine instead of a monthly risk. i.SAF, FR0600 and the VAT reports come out without errors. Currency rates and asset depreciation are handled automatically. Large batches of invoices can be loaded by the client's own team, with correct dates and amounts. The company has been working in Odoo this way for a long time now. The same proven solutions are now applied for other Lithuanian clients, so new projects no longer start from scratch.