1C:Payroll & HR is a powerful tool — but it was built around the Russian legal framework. In Uzbekistan the gaps show up fast: the tax-authority reports don’t match, USD contracts aren’t calculated correctly, and payslips aren’t in Uzbek. Below are the 5 customizations we build most often.
1. Social payment and personified reporting for the tax authority
Out-of-the-box Payroll doesn’t have the forms the State Tax Committee of Uzbekistan accepts: social payment calculation, individual-level details, Pension Fund certificates. Accountants assemble these by hand in Excel, at constant risk of reference-number mistakes.
What we build: a dedicated “Uzbekistan Tax Reports” module with current XML templates and direct upload to the taxpayer portal. Updated whenever the forms change.
Outcome. Our clients cut monthly filing from 1–2 days to 1–2 hours.
2. USD contracts and conversion at the Central Bank rate
Employees paid in USD (common in IT and foreign-trade firms) are poorly supported in standard Payroll: the exchange rate isn’t pulled in automatically, conversion history isn’t kept, and the payslip has no currency columns.
What we build:
- an information register “CBU Exchange Rates” with daily auto-update via API;
- a calculation type “Salary in foreign currency” with auto-conversion on the accrual date;
- a two-column payslip (USD + som).
// example formula for "Salary USD → som"
CurrencySalary * RateOnAccrualDate * DaysWorked / NormDays3. Leave and sick days under the Uzbek Labour Code
The Uzbek Labour Code differs from the Russian one: 24 calendar days of annual leave (not 28), its own sick-day calculation logic, and different rules for hazardous-work leave and multi-child mothers.
What we build: an “Uzbekistan Leave & Sick Days” module that replaces the standard calculations with its own calculation-type registers. Formulas are transparent — the accountant can see exactly where each number comes from.
4. Payroll upload to Humo and Uzcard
Standard Payroll only handles uploads for Russian banks. In Uzbekistan, payroll cards run through Humo and Uzcard in XML/CSV formats specific to each bank (Ipoteka Bank, Asia Alliance, Kapitalbank, and others).
What we build: a “Card Upload” processor with bank selection, automatic employee card-number validation, and file generation in the required format. We support 8 banks today and add new ones on request.
A common trap. Some companies export through the generic 1C format and then edit the file in Notepad. Banks often reject these — half a day gone.
5. Bilingual payslips and HR orders
Uzbek law requires payslips to be issued in the state language (Uzbek), while some staff prefer Russian. Standard Payroll can’t switch between them.
What we build: a print form with dynamic language (ru/uz) picked either from employee settings or department type. Same approach for hiring, transfer, and leave orders.
Case snapshot
“Zamonaviy Pharma,” a Tashkent pharmaceutical distributor with 180 staff.
Before: monthly payroll close — 5 working days. Three separate Excel files for social payment, leave, and bank upload.
What we did: all five modules above in 6 weeks.
After: monthly close — 4 hours. Calculation errors — gone (zero in the last 3 months per the accountant’s log).
Frequently asked
Is there a “1C:Payroll for Uzbekistan” we can just buy? Not in the standard 1C lineup — partner localizations cover 40–60% of the need, and the rest still gets customized.
Will standard Payroll updates break your customization? No — we write everything as configuration extensions. When the base configuration updates, your extension stays intact. We regression-test on every major version.
How much do all five modules cost together? It depends on your Payroll version and headcount. See our 1C customization pricing guide.
What if we’re on Payroll 3.1 and you build on 3.2? We support both. Also 3.0, but we strongly recommend migrating off it.
Free Payroll audit. In 30 minutes we’ll show which of the 5 tasks apply to you and which one pays back first.
Also read: Custom 1C development in Uzbekistan: when the boxed version isn’t enough.
