Electronic invoicing and system integration

Electronic invoicing has been mandatory in Uzbekistan since 2020. In many companies it works like this: a salesperson opens the state portal, types the data in by hand, searches the classification directory for the right code, and submits the document.

At thirty invoices a day that is two to three hours, every day. And every minute of it is work done twice, because the same data already sits in your own system.

What manual working costs

Calculate it - the figure is usually larger than expected.

Add the errors on top: a wrong classification code, a mismatch against stock, a delay. Every correction costs more time and sometimes a query from the tax authority.

Integration is built once and removes almost all of that work.

How the integration works

The flow runs like this:

1. The sale is recorded in the system. The salesperson enters the order as usual - product, quantity, price, customer.

2. The system builds the document. The classification code, unit of measure and VAT rate come from the product record. Tax number and details come from the customer record.

3. The document is submitted. The system sends it through the operator and waits for a response.

4. The status returns. Accepted, rejected or pending - all visible in the system. Nobody opens the portal.

5. Stock updates. Goods are written off and the balance falls. This happens at the same moment, not later.

The last step matters most. That is exactly where manual working produces discrepancies.

Classification codes: the main source of errors

This is the most delicate part of the integration and it has to be settled up front.

The code must live in the product record rather than being picked when the document is created. If someone searches the directory each time, errors are inevitable - similar codes are numerous.

A practical order:

• The code is attached to the product record once
• The unit of measure is checked against the code requirements
• A product without a code cannot be sold - the system warns
• For new products the code becomes a mandatory field
• When the code directory is updated, the system is updated too

The third point is important. If the system allows a sale without a code, the error surfaces at month end and costs considerably more to fix.

The reverse flow: the purchasing side

Integration is usually considered only from the sales side. Purchasing matters just as much.

A supplier sends you an invoice. Working manually, someone sees it in the portal, approves it, and then enters the data into the system.

With integration the document arrives in the system, the goods appear as a warehouse receipt, and approval is a single click.

It also affects VAT: a buyer can only reclaim VAT shown on an invoice received electronically. With the document in the system, the accounting reconciles automatically.

The link to tax scrutiny

In 2026 the tax system automatically reconciles goods received against goods sold. You booked in goods on an invoice but never sold them - the system sees the mismatch.

Integration closes that question by itself, because inventory and invoicing run on the same data.

Working manually, a gap is unavoidable: the document goes out one day, the goods are booked in another, and sometimes the quantities differ too.

A practical check: compare the quantity booked in through invoices last month against the quantity received into the warehouse. Any gap means you are already exposed.

How the rollout runs

The first step is the longest and the one most often skipped. Fold it into the project and the timeline stretches.

What to measure

The third is the most important, and it is the one nobody usually calculates.

Questions to ask a vendor

• Which operator do you work with and has the integration been proven
• Is the classification code stored in the product record
• How does the system report a rejected document
• Is the purchasing side covered or only sales
• How is the system updated when the code directory changes
• Is catalogue cleaning included in the price

The last question matters - that work usually stays with the client, and it is better to know in advance.

What it costs

The operator's monthly service fee is separate and stays on your side. It is usually a small amount, but it belongs in the budget.

If you already have a system, only the integration is commissioned - one to two weeks of standalone work.

In summary

Electronic invoicing is mandatory, and it has to talk to your system. Otherwise the same data is entered twice and a discrepancy becomes inevitable.

Practical steps:

1. Calculate the time spent on invoices per day - that is your baseline
2. Clean the catalogue; that is work before the system
3. Attach classification codes to product records
4. Ask for the purchasing side to be covered, not only sales
5. Compare stock and invoiced quantities - a gap is a risk