Short answer: Odoo localization means fitting the system to Uzbekistan's chart of accounts, 12% VAT, work in UZS and USD, e-invoices via Didox, Asl Belgisi digital marking and local document forms. An Odoo set up from a template for Dubai, Europe or any other country does not know these rules and needs rework later. Deep Vision, an Odoo Gold Partner in Tashkent, builds on the official Uzbekistan localization in Odoo 19, ready-made Didox and Asl Belgisi modules and local templates.
Odoo is a global system with localization packages for many countries. The problem is not the software but which package and which template are chosen. A team working in another country usually starts from the settings it is used to: its own chart of accounts, its own tax rate, its own currency and document forms. That is where Odoo localization becomes an issue: the system works, just not for the Uzbek market. This article explains what may not fit, how to check it and what a correct setup looks like when you choose an Odoo implementation partner.
What is Odoo localization and why does it matter?
Odoo localization is the adaptation of the chart of accounts, taxes, currency, document forms and integrations with government systems to the rules of a specific country.
A localization mistake is invisible on day one. It shows up at month-end: reports do not match what the accountant needs, VAT is calculated wrongly, e-invoices are not sent, and nobody knows where exchange differences were posted. Changing the chart of accounts later is expensive because entries are already in the books.
According to Gartner, by 2027 more than 70% of recently implemented ERP initiatives will fail to fully meet their original business goals (Gartner). A system built on the wrong foundation is one of the routes there.
What does not fit in an Odoo configured abroad?
An Odoo specialist or partner from Dubai, Europe, Turkey, India, Russia or Kazakhstan may be strong in their own market. But a team from a different business environment has to learn Uzbekistan's requirements first, and it faces built-in disadvantages in delivering the project properly. Mismatches usually appear here:
- Chart of accounts: another country's template or a generic one is used, and the chart and report structure used in Uzbekistan is patched by hand later.
- Taxes: a different VAT rate and different rules; in Uzbekistan VAT is 12% (PwC).
- Currency: AED, EUR or USD is chosen as the company currency, although books must be kept in sum.
- Document forms: instead of an English invoice, the business needs a nakladnoy (delivery note), schyot-faktura (invoice), doverennost (power of attorney) and akt sverki (reconciliation statement).
- Government systems: e-invoicing, digital marking and local banks are left out of the plan entirely.
A simple example: a wholesaler's system is configured with the dollar as company currency and a generic chart of accounts. Three months later the accountant cannot produce tax reports from Odoo because reports follow a different structure and VAT uses a different rate. E-invoices are still typed by hand in a separate program, and the storekeeper prints delivery notes from Excel. The company runs two systems and trust in Odoo drops. Fixing this often costs more than setting it up correctly at the start, because the data already entered has to be moved as well.
How do you set up sum, dollars and exchange differences?
Many companies in Uzbekistan agree prices with suppliers in dollars and sell to local customers in sum. In a correctly configured Odoo:
- The company currency is the sum; dollars and other currencies are kept as secondary currencies.
- Exchange rates are updated regularly, and each document uses the rate of its own date.
- When a payment arrives, the exchange difference is posted automatically to a separate account.
- Foreign-currency balances are revalued at period end and the result appears in reports.
- Even when the pricelist is in dollars, the invoice is issued in sum.
If the company currency is chosen wrongly, changing it later is almost like starting a new database. That is why this decision is made in the first week.
Which local integrations will you need?
A local integration connects Odoo to the government and service systems used in Uzbekistan: the e-invoice operator, digital marking, banks, SMS and telephony.
- E-invoices: mandatory in Uzbekistan since 1 January 2020 for obligated taxpayers (EDICOM); they are sent through an operator such as Didox.
- Digital marking (Asl Belgisi): introduced product group by product group, for example household appliances from 1 December 2021 and water and soft drinks from 1 March 2022 (Gratanet).
- Bank statements: check that your local bank's statement format can be imported into Odoo and reconciled automatically.
- SMS and telephony: customer messages and linking calls to the CRM; for example, Deep Vision's dooCall product tracks calls on an ordinary phone.
These integrations rarely come up abroad, so a team from another country often pushes them to "the next phase". The business, however, needs them from day one. More: Didox and e-invoice integration, Asl Belgisi guide.
How can you check that Odoo localization was done right?
Ask your implementation team these questions, or check a system that is already running:
- Is the company currency the sum, and are dollar balances revalued?
- Which chart of accounts is used, and was it agreed with your accountant?
- Is 12% VAT calculated correctly and does it flow into tax reports?
- Are e-invoices sent directly from Odoo through an operator?
- Are marking codes recorded at receipt and sale?
- Do delivery notes, invoices and powers of attorney print in the local format?
- Can your staff use the interface in Uzbek or Russian?
- Can your local bank's statement be imported?
If several answers are "no", the system will need reconfiguring. Confirm specific tax requirements with your accountant. On tax settings: taxes and VAT in Odoo.
How does Deep Vision fit Odoo to the Uzbek market?
Deep Vision is an official Odoo Gold Partner in Tashkent. Our Odoo partner page lists 7 certified experts and 20+ client references.
- We start from the official Uzbekistan localization in Odoo 19 and complete it together with your accounting team.
- We have ready-made modules for Didox (e-invoices) and Asl Belgisi (digital marking).
- We prepare local forms, such as delivery notes, invoices and reconciliation statements, in Uzbek and Russian.
- Our team did Odoo's Uzbek translation: in the Odoo 19 source, Deepvision is credited in 360 of 376 Uzbek translation files. More: Odoo in Uzbek.
- The team includes experienced finance and industry specialists, not only programmers.
- We have moved companies to Odoo from 1C, SAP and scattered tools.
Overview: Odoo in Uzbekistan. Service details: Odoo implementation. Want your current setup checked? Send a brief.
Frequently asked questions
Does Odoo have a localization for Uzbekistan?
Yes, Odoo 19 includes an official Uzbekistan localization. It is a starting point: document forms, integrations and company processes are configured on top.
Can an Odoo configured abroad be fixed?
Often yes, but if the company currency or chart of accounts is wrong, the work is substantial. Start with diagnostics.
What if the company currency is the dollar?
Local reporting and taxes are required in sum, so the company currency should normally be the sum; confirm your case with your accountant.
How is Didox integrated?
Deep Vision has a ready-made module: the e-invoice is sent from the Odoo document through the operator, and the module is connected around your company's process.
How long does localization take?
It depends on project scope. Standard Sales and Inventory often go live in 6–8 weeks, and localization is part of that plan.
Sources
- PwC — Uzbekistan: other taxes (VAT)
- EDICOM — e-invoicing in Uzbekistan
- Gratanet — mandatory digital labelling
- Gartner — on ERP initiatives
- Odoo — Deep Vision partner page
Want Odoo fitted properly to the Uzbek market? Send a brief or call +998 77 093 00 07.