Business Automation CRM Automation and Follow-Up for Sales Teams in Uzbekistan
A practical guide for Uzbek sales teams: how to eliminate manual entry, stop losing leads, and build automated follow-up...
In Uzbekistan, private-sector employees can receive salaries, bonuses, and other corporate payments on a bank card or e-wallet of their choice. The employer does not need to set up a separate payroll arrangement with every bank. Its job is to prepare a single register correctly and monitor the payment outcome.
Do not treat this as simply “writing down a new card number.” HR, accounting, and IT need to review together how consent is obtained, payment details are validated, errors are returned, and payments are reconciled.
On November 18, 2026, the Central Bank of Uzbekistan announced the procedure for sending payments through the Funds Distribution Center. The employer submits a consolidated payroll register, authenticated with an electronic digital signature, to its servicing bank. The Center then routes the funds to the bank or e-wallet selected by each employee.
The card or e-wallet must belong to the employee. If the payment details are incorrect or fail central validation, the entry is returned for correction. That is why “the money was sent to the bank” cannot be treated as “the employee received the money.”
Earlier reports about the launch date are inconsistent. Spot.uz reported that the planned launch was delayed because some banks were not technically ready. It is therefore risky to assume that every bank is ready for the system. Companies should obtain written confirmation from their servicing bank about the register format, submission cut-off time, fees, and the procedure for correcting returned entries.
Portability does not change the company’s bank. The employer continues to send funds through the bank servicing its account. The difference is that employees listed in a single register can now choose different banks or e-wallets.
This arrangement does not override labor requirements. Under Articles 253 and 256 of the Labor Code, salaries must be paid on the established dates at least twice a month. Bank transfers require the employee’s written consent, while the employer covers the costs associated with banking services.
In many cases, the costliest problem is not the fee but the manual work required to correct a failed payment. An accountant identifies the error, HR asks the employee to resubmit the payment details, and a manager approves the second attempt. If this is not recorded separately in 1C or the ERP, the same error may appear again in the next register.
Collecting card details in a shared Telegram group or an HR manager’s personal chat is also risky. Telegram can be used to send reminders. Payment details, however, should be collected through a secure form, with access limited to HR and authorized accounting staff.

Public sources do not specify an official company-wide migration deadline, a final list of participating banks, or a standard employer fee. For that reason, do not start collecting applications from employees at scale until your bank confirms that its system is ready to process real payments.
Use the following checklist to prepare:
First, test the full cycle with a limited group of employees: generate the register, send it to the bank, receive the outcome, and compare it with the accounting entry. If the bank cannot provide a return file or clear error codes, do not move the entire company to the new process at once.
At many companies, errors occur not in the bank transfer itself but in the manual work before and after it. HR enters the payment details into a spreadsheet, and an accountant copies them into 1C. Meanwhile, the failed-payment notice gets buried in email or Telegram.
Celion can design a secure employee form, an approval workflow, and integration with 1C or Odoo for this process. If payment details change, the system retains the previous value and includes only the approved entry in the register. The status returned by the bank is then linked to the relevant employee profile.
Automation should begin only after the bank’s official format and return mechanism are clear. Otherwise, the company will encode a process that is still changing and will have to rework the integration when the bank updates its requirements.
The decision rule is simple. If your bank confirms the register format, fee, submission cut-off time, and rejection procedure in writing, start the test cycle. If even one of those four answers is missing, clarify the process first.

Celion’s business process automation and 1C/Odoo integration service combines secure collection of employee payment details, register approval, and payment reconciliation in one controlled workflow.
Callback
Leave your details and we will contact you shortly.
Become a Partner
Leave your contact details and we will get back to you shortly.
Order Service
Leave your phone number and we will contact you shortly.