Implementing 1C in Uzbekistan: Where to Start and How to Avoid Overpaying

Why businesses in Uzbekistan choose 1C

1C: Enterprise 8 remains the accounting standard for mid-sized and large businesses in Uzbekistan for a simple reason: an entire ecosystem has grown around it. There are localized configurations built for the national chart of accounts, ready-made integrations with Soliq and Didox, a clear talent market, and predictable total cost of ownership. Alternatives such as custom-built systems or foreign ERPs almost always run into the same wall: they have to be adapted to Uzbek tax and currency legislation from scratch.

The 1C platform is not a single program but an engine that runs different applied solutions called configurations. That is why the phrase "implement 1C" means very little on its own. The key questions are which configuration you are deploying, who localized it, and who will support it.

Choosing a configuration: Trade Management, accounting, or a complete solution

The most common starting point for trading and distribution companies is 1C: Trade Management (UT). It covers purchasing, warehouse, sales, pricing, settlements with counterparties, and basic analytics. For manufacturing and service companies the logic differs; they more often look toward complete solutions or ERP-level products.

It is important not to confuse the managerial and the regulated (accounting, tax) circuits. Trade Management is primarily operational accounting for running the business. Accounting reporting for Soliq is kept in a localized accounting configuration. In practice, companies in Uzbekistan often work in tandem: operational accounting in UT plus data exchange with the accounting block.

Localization for Uzbekistan: Soliq, Didox, VAT, and currency

This is the point that separates a successful project from endless rework. The Uzbek realities a configuration must handle include:

• the national chart of accounts and regulated reporting forms for Soliq;
• electronic invoices (EHF) and document flow through Didox or similar EDI operators;
• correct calculation of VAT and tax regimes, including turnover tax;
• accounting in the national currency and foreign-currency transactions with exchange-rate differences based on the Central Bank of Uzbekistan rate;
• HR and payroll accounting under local labor law, if it falls within the project scope.

Before buying, always confirm whether you are dealing with a localized version and who is responsible for updating it when legislation changes. Tax rules in Uzbekistan change regularly, and supporting the localization is not a one-time service but an ongoing process.

Implementation stages: how a healthy project should run

A proper implementation is not "installed and good to go." A minimally healthy project passes through these stages:

• Pre-project assessment. Describing business processes, current pain points, and requirements. Without it, you are buying a pig in a poke.
• Technical specification and estimate. Scope, timeline, and budget are fixed. This is where you decide what is delivered with standard functionality and what needs customization.
• Configuration and customization. Installing the platform and configuration, tailoring it to processes, and developing the required customizations and integrations.
• Data migration. Reference data, balances, counterparties, open documents. One of the most underestimated stages in terms of effort.
• User training. Without it, even a perfectly configured system will not take root.
• Pilot operation and support. The first weeks of work under supervision, fixing errors, fine-tuning.

The more thoroughly the assessment and specification stages are done, the fewer unpleasant surprises and overpayments arise in later stages, where changes cost several times more.

Where companies in Uzbekistan most often overpay

Overpayment rarely looks like one big line item. It is usually the sum of small decisions made without analysis:

• buying an excessive configuration or surplus licenses "for growth" that are never used;
• endless customizations to fit staff habits instead of adapting processes to standard functionality;
• no technical specification, working on a "as we go" basis where the vendor bills for every clarification;
• cutting corners on training, so the system is used at 20% of its capability;
• buying from one contractor and getting support from another without handing over documentation.

Support and maintenance: what to treat as mandatory

Implementation is the beginning, not the end. After go-live you will need configuration updates (especially the regulated part for Soliq changes), user consultations, bug fixes, and system development as the business grows. Agree on the support format in advance: response time, who keeps the source code of customizations, whether documentation is handed over. Dependence on a single irreplaceable specialist is a risk worth closing at the contract stage.