Skip to content

🇺🇿 Sending to Uzbekistan

UZ · UZB

UZS

National format   SWIFT BIC required

← Back to Country-specific guides

Required information

  • Account number

    20 digits exactly. First 5 digits encode balance-sheet/account-type per CBU chart of accounts; embedded MFO (5 digits) identifies the bank branch.

  • SWIFT BIC

    Beneficiary bank BIC (8 or 11 characters).

  • MFO

    5-digit numeric bank/branch code (e.g. 00440) assigned by Central Bank of Uzbekistan. Required for domestic UZS settlement; cross-border requires BIC (e.g. NBFAUZ2X).

  • Purpose-of-payment code (mandatory)

    Free-text detailed purpose plus contract/invoice reference; the Uzbek bank assigns the 5-digit currency operation code locally

  • Beneficiary address

    Match the address template — partial addresses cause holds.

For your end users

Double-check the beneficiary's full name (no initials), account number, and bank SWIFT/BIC against what their bank has on file. International wires can take 1-5 business days and may be delayed by sanctions screening.

Last reviewed by GIB compliance on 2026-05-21. Reference material only.

  • Currency

    UZS

  • Typical settlement

    1-2 business days typical; longer for cross-border with FX or compliance review.

  • SWIFT BIC

    Required

  • Local clearing

    RTGS (Central Bank of Uzbekistan)

Account format

How beneficiary account numbers are structured for Uzbekistan. Failure to match this format is the single most common reason wires are rejected at the destination.

Field Value
Format tier National format
Length 20 digits exactly. First 5 digits encode balance-sheet/account-type per CBU chart of accounts; embedded MFO (5 digits) identifies the bank branch.
Validation regex ^[0-9]{20}$
Example 20208000900123456001

Routing identifiers

Which routing codes the wire-creation API call must include for Uzbekistan.

Field Value
SWIFT BIC Required
MFO Required
Format 5-digit numeric bank/branch code (e.g. 00440) assigned by Central Bank of Uzbekistan. Required for domestic UZS settlement; cross-border requires BIC (e.g. NBFAUZ2X).
Directory ↗ Source
Local clearing RTGS (Central Bank of Uzbekistan)

Address format

How Uzbekistan expects the beneficiary address to appear on the wire. Free-form variations frequently trigger compliance holds.

  1. Recipient Full Name
  2. Street + Building + Apartment
  3. District/Tuman
  4. 6-digit Postal Code, City
  5. Region/Viloyat
  6. UZBEKISTAN
Field Value
Postal code Optional — validated against the format below when provided
Postal code regex ^[0-9]{6}$
Example Bekzod Alimov, Chilanzar 11-2-38, 100123 Tashkent, UZBEKISTAN

Purpose of payment

Put the purpose in the remittance information (<RmtInf><Ustrd>) of the ISO 20022 wire-creation request, as the code format below describes. Requirement: Mandatory (confirmed) GIB check: a missing or unexpected purpose is reported as a validation warning; the wire is not held.

Non-standard element

For Uzbekistan, the purpose is placed in <RmtInf> (remittance info), not the standard <Purp> element.

Field Value
Code format Free-text detailed purpose plus contract/invoice reference; the Uzbek bank assigns the 5-digit currency operation code locally
Source ↗ Cabinet Resolution 283

Operational notes

Field Value
Currencies accepted UZS
Typical settlement 1-2 business days typical; longer for cross-border with FX or compliance review.
Banking holidays ↗ Calendar

Known issues:

  • 20-digit account number is structured per CBU chart of accounts; first digits indicate account type (current, card, settlement) and getting them wrong causes hard rejects.
  • Several banks consolidated to a single MFO in recent years (e.g. Trustbank, Asia Alliance) — branch-level MFOs are deprecated; validate against current CBU MFO directory.
  • UZS is not freely convertible offshore; inbound wires arrive in USD/EUR and are converted at the bank's rate per CBU FX rules.
  • Currency-control declaration required for inbound transfers above thresholds; beneficiary may need to provide contract/invoice copy to the bank.

Common rejection reasons

Documented patterns that cause this country's banks to return wires. Universal reasons (sanctions holds, missing BIC) aren't repeated here.

Beneficiary name mismatch (initials, abbreviations, punctuation, or transliteration differences from what the beneficiary bank has on file).
Account number format error (wrong length, wrong check digits, or non-standard characters).
Missing or invalid SWIFT/BIC code.
Insufficient remittance information (unclear economic reason for the payment).
Sanctions or compliance hold (OFAC / EU / UN / local screening).
Missing or invalid MFO (5-digit bank code) — the most common rejection reason.
Missing INN/TIN (taxpayer ID) of beneficiary; required on all UZS payments.
Missing purpose-of-payment code (CBU dictionary).
Cyrillic/Latin transliteration mismatch on beneficiary name.

Validate before you send

Check identifiers before you submit. The IBAN check runs in your browser (format plus the ISO 13616 MOD-97 check digit). GIB's API checks the IBAN format for countries where an IBAN is required. The BIC lookup searches GIB's BIC directory and needs a dashboard login.

BIC lookup

Loading…

References

First-party sources — central banks, FX regulators, ISO registries. Always re-verify against these before pushing volume to a new corridor.

Disclaimer

These country guides aggregate information from central banks, regulators, and industry-standard references. Global Innovations Bank reviews them on a rolling cadence and notes the verification date on each page. Payment-corridor rules change between releases, so we cannot guarantee continued accuracy.

Always verify against the primary sources linked in the References section before going live in a new corridor. Re-check applicable sanctions lists (OFAC, EU, UK, UN consolidated, and any state-level requirements) at the time of payment, since designations shift between our refreshes.

For fintech partners on GIB's sponsor-bank rails, these guides do not replace your BSA/AML, KYC, sanctions-screening, or transaction-monitoring obligations under your program agreement with GIB.

Nothing in this material constitutes legal, tax, or regulatory advice, and wire-acceptance decisions remain at the discretion of GIB Compliance and the destination bank.

← Back to Country-specific guides