Electronic Document Flow, ESF and Soliq: How to Automate and Avoid Penalties

Why the ESF in Uzbekistan is an obligation, not a formality

The electronic invoice (ESF) in Uzbekistan stopped being a formality long ago. Since the full transition to electronic document flow, the ESF has become a legally binding document, without which a transaction between legal entities is effectively "invisible" to the tax authority. If you provided a service or delivered goods to another legal entity, the ESF is mandatory and cannot be replaced by a work-completion act. The act is issued on top, as a supplementary document, but the basis for VAT accounting and proof of turnover is the ESF itself.

In practice, businesses find that the volume of documents grows faster than the accounting team. Every invoice has to be entered manually in the Didox cabinet or directly in Soliq, the counterparty's TIN must be checked, along with IKPU codes (the goods and services classifier), the VAT rate or the "VAT-exempt" mark, dates and amounts. One manager handling 30-50 deals a day becomes a bottleneck, and errors start piling up.

Where companies lose money on manual entry

Manual document flow is not just spent hours. It carries direct financial risks that often surface only during reconciliation or an audit.

• Late ESF issuance. An ESF must be issued within the set deadline after shipment or service delivery. In manual mode invoices get stuck, and the counterparty cannot credit the VAT.
• IKPU code mismatches. A wrong code for a good or service leads to incorrect accounting and questions from the tax authority.
• Duplicates and omissions. Under heavy volume, some documents get issued twice while others are lost, and this is only discovered in the reconciliation act at the end of the period.
• Human typos in amounts and TINs. The counterparty rejects the ESF, the cycle restarts, and payment is delayed.

What "automating" document flow actually means

Automation is not buying yet another program into which an accountant types the same data by hand. It is integrating your accounting system (CRM, ERP, warehouse, billing) directly with the EDI platforms via API, so that the document is generated from the real transaction data without re-entry.

In Uzbekistan the main integration points are the state Soliq platform and EDI operators, primarily Didox, plus roaming between operators. Technically, automation looks like this: when a deal closes in your system (shipment, act, payment), the system gathers the data itself, fills in IKPU codes from the catalog, calculates VAT, generates the ESF and sends it through the operator's API. The counterparty receives a ready document, and the acceptance status flows back into your system.

What a proper integration consists of

Well-designed document-flow automation for Uzbek business includes several layers:

• IKPU and counterparty catalog. Each good or service is mapped once to an IKPU code, each counterparty to a verified TIN/PINFL. After that, the system does not make mistakes.
• Auto-generated documents. ESFs, acts, basis-contracts and invoices are generated from templates using deal data, with no copy-paste.
• API integration with Soliq and Didox. Sending, receiving statuses, digital signature, handling rejections.
• Deadline and status control. A dashboard showing which ESFs are not issued, not accepted or overdue, before the tax authority sees it.
• Reconciliation. Automatic matching of your data against counterparty data and the Soliq registry.

Who needs this first

EDI automation pays off fastest where there are many repetitive transactions: wholesale and retail trade, distribution, subscription services, marketplaces, logistics, and multi-branch food service. If accounting issues dozens of ESFs a day by hand, every month of delays and mismatches is a real risk of fines and blocked VAT credit for your clients, who then drift toward more "convenient" suppliers.

The turnover-tax regime (1%) deserves a separate note: here the entire turnover must be reflected correctly, because counterparties' counter-ESFs automatically build the picture of your revenue in the Soliq system. Manual omissions are especially dangerous here.