Uzbekistan has been one of the conspicuous gaps in Odoo’s localization map for years. Businesses operating in the country had to build their own chart of accounts from scratch, manually configure tax rates, and piece together financial reports that satisfied local requirements. That workaround era is over. Odoo now ships a complete fiscal localization for Uzbekistan, delivered through two modules that auto-install the moment you select the country during company setup.
The localization isn’t a skeleton framework that requires hours of configuration. It arrives ready to use — with a structured chart of accounts, preconfigured VAT categories, and IFRS-aligned financial reports that match what Uzbek businesses actually need to file.
Two Modules, Fully Automatic
The localization is split across two modules that work in tandem. The first, l10n_uz, provides the core accounting infrastructure: a chart of accounts structured according to Uzbek standards, default journal configurations, and the tax setup that businesses need from day one. The second, l10n_uz_reports, layers on localized financial reports — specifically a balance sheet and profit and loss statement built to follow IFRS-style presentation.
Both modules auto-install when a company selects Uzbekistan as its country. There’s no need to hunt through the app store, no dependency chains to manage, and no manual activation steps. Create a company, set the country to Uzbekistan, and the accounting framework populates itself. This is the same installation pattern Odoo uses for its other mature localizations — France, Germany, Mexico, India — which signals that Uzbekistan is now treated as a first-class accounting jurisdiction within the platform.
Tax Configuration That Covers the Real-World Cases
The VAT setup shipped with the localization reflects the actual tax landscape that Uzbek businesses navigate daily. Three categories come preconfigured: the standard 12% VAT rate that applies to most domestic transactions, a 0% rate for export operations, and an exempt category for transactions that fall outside the VAT regime entirely.
The 12% standard rate is straightforward — it’s the default that applies to the majority of sales and purchases within the country. The zero-rated export category is critical for businesses that sell goods or services across borders. Under Uzbek tax law, exports are subject to VAT but at a zero percent rate, which means the transaction must still appear in VAT reporting even though no tax is collected. Getting this distinction wrong — treating an export as exempt rather than zero-rated — creates compliance problems because exempt transactions don’t carry input tax recovery rights while zero-rated ones do.
The exempt category handles the remaining cases: certain financial services, specific healthcare-related transactions, and other activities that Uzbek law explicitly excludes from the VAT system. Each tax category includes practical account mappings so that when an accountant selects a tax rate on an invoice line, the system knows exactly which accounts to debit and credit without manual intervention.
A Chart of Accounts Built for Uzbek Standards
The chart of accounts isn’t a generic template translated into Uzbek. It’s structured according to the account classifications that local regulations require, with account codes, groupings, and categories that align with how Uzbek businesses actually organize their financial data.
For companies migrating from legacy accounting systems or spreadsheet-based bookkeeping, this matters enormously. Instead of starting with Odoo’s generic chart and spending days renaming accounts, adding missing categories, and restructuring the hierarchy to match local conventions, the localized chart provides a ready-made foundation. Businesses can customize it further — adding accounts specific to their industry or operations — but the baseline is already compliant.
The account structure also ties into the tag system that drives financial reporting, which brings us to the most technically interesting piece of the localization.
Account Tags: The Bridge Between Ledger and Reports
Odoo’s localized financial reports don’t pull data from accounts based on account codes or types alone. They use account tags — labels attached to each account that specify exactly which line of which report that account’s balance should appear on. This is the mechanism that makes the balance sheet and profit and loss statement work correctly without manual mapping.
Every account in the Uzbekistan chart of accounts comes pre-tagged to its correct report line. Assets flow to the appropriate balance sheet section. Revenue accounts map to the right income lines on the profit and loss statement. Expense accounts land where they should. The tagging is invisible to most users — it just works in the background when you generate a report.
What makes this system particularly elegant is how it handles accounts that don’t belong on any standard report. If an account has no tags, it functions as an off-balance sheet item — it exists in the general ledger, participates in journal entries, and shows up in the trial balance, but it doesn’t appear on the balance sheet or profit and loss statement. This is exactly how off-balance sheet items should behave, and the tag system achieves it without requiring a separate account type or special configuration.
IFRS-Style Financial Reports
The two reports shipped with l10n_uz_reports— the balance sheet and profit and loss statement — follow an IFRS-style structure. This is a deliberate choice. Uzbekistan has been progressively aligning its national accounting standards with International Financial Reporting Standards, and businesses operating in the country increasingly need reports that satisfy both local requirements and international expectations.
The balance sheet presents assets, liabilities, and equity in the format that IFRS prescribes, with current and non-current classifications. The profit and loss statement follows the function-of-expense method, grouping costs by their purpose rather than their nature. For businesses with foreign investors, international partners, or ambitions to list on exchanges that require IFRS-compliant financials, this alignment removes the need for a separate reporting layer.
What This Means for Businesses in Uzbekistan
The practical impact is simple: an Uzbek business can now install Odoo, select its country, and start issuing invoices with correct tax treatment within minutes rather than days. The chart of accounts is ready. The taxes are configured. The financial reports generate correctly. The system handles the mundane compliance details — which account to debit, which tax line to populate, which report section to update — so that accountants can focus on the decisions that actually require judgment.
For the growing number of Uzbek companies adopting modern ERP systems as the country’s economy liberalizes and digitizes, having a mature localization removes one of the most significant barriers to adoption. No more patching together community modules of uncertain quality. No more maintaining custom tax configurations that break with every upgrade. The localization is part of the core platform now, maintained alongside every other country package and updated with each release cycle.