Deep Vision

Digital Tax Experience: E-Invoicing, ERP and Government Systems — Uzbekistan's Lessons for Business in Tajikistan

E-invoicing has been mandatory in Uzbekistan since 2020. How the lessons learned connecting ERP to government systems over those years can help companies in Tajikistan.

Published: 4 min read
Digital Tax Experience: E-Invoicing, ERP and Government Systems — Uzbekistan's Lessons for Business in Tajikistan

Tax reports, invoices and data sent to government systems are still separate, manual work in many companies. The accountant sees sales in one program, issues invoices in another and prepares reports in a third. This takes time, and mistakes can lead to fines and audits.

Tajikistan is moving fast along the path of the digital economy. On the President's initiative 2025–2030 were declared the Years of Digital Economy and Innovation Development, and according to the World Bank the economy grew 8.2% in the first half of 2026. Digitising tax and public services is part of that path, and electronic invoicing and online tax services are developing in Tajikistan too. This article looks at the practical experience built up over several years in neighbouring Uzbekistan and how companies in Tajikistan can use it.

Why digital tax matters for business

E-invoicing is not just replacing paper with a PDF. It affects the company's whole accounting process:

  • Data must match. The amount on the invoice, the customer's tax ID and the product name must match the accounting entry.
  • Speed goes up. Sending and receiving an invoice takes minutes, not hours.
  • Oversight gets stronger. The tax authority sees data faster, so mistakes become visible faster too.
  • Manual entry becomes risky. Re-entering the same data into two or three systems multiplies errors.

So the key question in moving to digital tax is not "which portal do we log into" but "where is the invoice data born, and how does it get there without errors".

Uzbekistan's experience: e-invoicing since 2020

In Uzbekistan electronic invoicing became mandatory on 1 January 2020 (Kun.uz, 27 June 2019). A digital product-marking system (Asl Belgisi) was launched later. For several years companies have been solving one problem: how data should flow automatically and correctly between the ERP, accounting and government systems.

Over those years Deep Vision built ready-made Odoo modules for the Uzbek market:

  • Didox integration — sending and receiving electronic invoices (ESF) and documents directly from Odoo;
  • Asl Belgisi integration — linking digital marking codes to warehouse and sales operations in Odoo.

An important clarification: these modules were built for Uzbekistan's systems. Tajikistan has its own government systems and requirements. But the approach and experience gained in Uzbekistan — preparing data, integration architecture, error control — are useful in any country.

Which lessons carry over to Tajikistan

1. Clean data first

Most problems come not from the integration but from messy data: the customer record has no tax ID, product names are written differently, units of measure are mixed. Before moving to e-invoicing, clean up the customer, supplier and product master data.

2. The invoice should be born in one place

The right flow: sales order → delivery → invoice → accounting entry, all inside the ERP. The invoice is not retyped by hand in another portal; it comes out of the ERP. That way amounts and details stay identical.

3. Status tracking

Sent, accepted, rejected — these statuses should be visible in the ERP. Otherwise the accountant checks the portal by hand every day.

4. Reconciliation

At month end, sales in the ERP are reconciled with invoices in the tax system. An automatic report shows differences immediately.

5. API-based integration architecture

Government systems change: new fields, new formats. If the integration is built as a separate module, changes can be made without breaking the whole system.

6. People and process

Accounting, sales and warehouse staff need to understand the new routine: who creates the invoice, who approves it, what to do if it is rejected.

How Odoo helps

  • One database: sales, inventory, purchasing and accounting live in one system, so invoice data is entered once.
  • API and modules: Odoo has an open API for connecting to external systems, and the integration is built as a separate module.
  • Reporting: for Deep Vision clients reporting is kept on an IFRS basis and also adapted to national reporting requirements.
  • Odoo AI: connected for almost all our clients; helps with financial analysis and spotting unusual amounts.

Example: a wholesale distributor

The scenario below is illustrative, not real client figures. A wholesale distributor in Tajikistan issues about 1,500 invoices a month. Today sales are in Excel, accounting is in a separate program and invoices are prepared by hand.

  • Problem: the same data is entered three times, and month-end reconciliation takes several days.
  • Solution: sales, inventory and accounting are combined in Odoo; customer and product master data are cleaned; invoices come out of the ERP; an integration that fits local requirements is planned as a separate module.
  • Expected result: less manual entry, reconciliation becomes an automatic report, and the manager sees sales and tax figures on one dashboard.

Readiness checklist

  1. Check the tax IDs of customers and suppliers.
  2. Standardise product names, codes and units of measure.
  3. Decide who creates the invoice and at which stage.
  4. Confirm current requirements with your tax adviser or accountant.
  5. Put the integration into the project as a separate phase.

Deep Vision in brief

  • per odoo.com/partners (November 2026), the only Gold-tier Odoo partner in Central Asia;
  • ready-made Odoo modules for Didox and Asl Belgisi in Uzbekistan, and practice connecting ERP to government systems;
  • 7 certified experts, 89% client retention;
  • projects in Central Asia are run in Russian.

More: 15 reasons for Tajik business, What happens after go-live. To discuss your project, leave a request.

Frequently asked questions

Do the Didox and Asl Belgisi modules work in Tajikistan?

No, they were built for Uzbekistan's systems. In Tajikistan an integration that fits local requirements is planned separately, but the experience from Uzbekistan speeds up that work.

Is there e-invoicing in Tajikistan?

Yes, electronic invoicing and online tax services are developing in Tajikistan too. Exact requirements should be checked with the tax authority and your accountant.

Can Odoo connect to government systems?

Yes, Odoo has an open API. The integration is built as a separate module depending on what the government system offers.

Where should we start with e-invoicing?

With cleaning data: customer tax IDs, product names and codes, units of measure.

Which standard is reporting in?

For Deep Vision clients reporting is kept on an IFRS basis and adapted to national reporting requirements.

Sources

  • Kun.uz: e-invoicing mandatory from 1 January 2020, 2019-06-27
  • Deep Vision: Odoo modules for Didox and Asl Belgisi
  • World Bank, Tajikistan Economic Update, 2026
  • Khovar: 2025–2030 Years of Digital Economy and Innovation Development
  • Odoo: External API documentation (odoo.com/documentation)