Wire Transfer Purpose Codes: Country Rules and ISO 20022 Format

Wire transfer purpose codes are short alphanumeric identifiers that banks attach to international payments to classify why the money is moving. Countries like India, China, and the UAE require a specific code on every inbound or outbound remittance, and picking the wrong one can freeze your funds or bounce the payment back. Other destinations, including most of the EU and Mexico, treat the code field as optional or skip it entirely. The right code depends on where the money is going and what the payment is for.

Why Banks Ask for a Purpose Code

Every country tracks money flowing in and out through a national ledger called the balance of payments. Purpose codes feed that ledger. When you send $5,000 to a supplier in Mumbai, the code attached to the wire tells India’s central bank whether the money is a trade payment, a family remittance, or an investment return.

Banks also use the code as a screening tool. Automated systems compare the stated purpose against the sender’s history and the recipient’s profile, so a “family maintenance” code on a $500,000 transfer to a newly opened business account will trigger a manual review. The Central Bank of the UAE, for example, requires a specific code on every transaction through its clearing system for exactly this dual purpose of statistical reporting and compliance oversight.1Central Bank of the UAE. Explanatory Notes on Transaction Codes for BOP

Which Countries Actually Require Them

Enforcement varies sharply by destination. Some central banks demand granular classification on every transfer; others don’t use the field at all. Confirming the destination country’s rules before you initiate the wire saves time and fees.

India

The Reserve Bank of India maintains one of the most detailed purpose code systems anywhere. Every inward and outward remittance must carry a code from the RBI’s official list, published under its Foreign Exchange Management Act reporting requirements. The codes follow a format like P0101 or P1301, organized into broad categories:2Reserve Bank of India. Master Direction – Reporting under Foreign Exchange Management Act (FEMA)

  • P00xx — Capital account transactions (foreign direct investment, repatriation of equity)
  • P01xx — Exports of goods
  • P02xx — Transportation
  • P03xx — Travel
  • P07xx — Financial services (bank charges, brokerage, underwriting)
  • P13xx — Personal transfers (family maintenance, gifts, donations)
  • P14xx — Income (repatriated profits, dividends)

A relative in the U.S. sending money to family in India for household expenses would use P1301 (family maintenance and savings). An investor repatriating profits would use P1406. Selecting the wrong category or leaving the field blank usually leaves the funds sitting in a suspense account at the Indian bank until the recipient provides documentation to clarify the transfer’s purpose.2Reserve Bank of India. Master Direction – Reporting under Foreign Exchange Management Act (FEMA)

United Arab Emirates

The Central Bank of the UAE requires a purpose of payment code on every transaction processed through the local clearing system. The codes feed into the UAE’s Balance of Payments framework and cover trade in goods, services, income, and capital transfers.3Central Bank of the UAE. BOP Purpose of Payment Codes Table The UAE uses its own classification structure rather than India’s alphanumeric format. Confirm the exact code with the recipient’s UAE bank before sending, since it must match the transaction type precisely.

China

China’s State Administration of Foreign Exchange (SAFE) oversees all cross-border payment flows and requires purpose classification on every transaction. The system uses broad categories: goods trade (GOD), services (STR), capital transfers (CTF), and other current account transactions covering salary and investment income (OTF). Each category has subcodes with additional detail.4State Administration of Foreign Exchange. International Payment Code Guideline

Chinese banks are particularly strict about matching the code to supporting documentation. A trade payment coded as GOD needs to correspond to an invoice or contract the recipient has already submitted to their bank. Mismatches between the code and the paperwork cause the transfer to be held or returned.

European Union (SEPA)

The SEPA Credit Transfer system takes a lighter approach. The purpose code field (designated AT-T007 in the rulebook) is optional. If a sender provides one, it travels in the payment message, but banks aren’t required to reject transfers that omit it.5European Payments Council. SEPA Credit Transfer Scheme Rulebook 2025 Version 1.0 U.S. wires to European accounts generally don’t require a purpose code, though individual EU member states may impose their own requirements through domestic rules. Ask the recipient’s bank if you’re unsure.

Mexico

Mexico’s central bank operates the Directo a México service for U.S.-to-Mexico remittances and doesn’t use purpose codes. The system routes transfers through Mexico’s Interbanking Electronic Payment System (SPEI) using account identifiers: an 18-digit CLABE number, a 16-digit debit card number, or a linked 10-digit phone number. There is no maximum amount per transaction through this service.6Banco de México. Directo a México

How Codes Travel Under ISO 20022

SWIFT completed its migration to the ISO 20022 messaging format for cross-border payment instructions in November 2025. The old MT message format is no longer delivered on the SWIFT network for payment instructions.7SWIFT. ISO 20022 in Bytes for Payments – One Month to Go This matters for purpose codes because ISO 20022 carries far more structured data, so purpose information can be embedded directly in the payment message rather than crammed into free-text fields that intermediary banks might strip or misread.8SWIFT. PMPG – ISO 20022 Market Guidance

Under ISO 20022, purpose codes follow a standardized four-letter format maintained by the ISO 20022 registration authority.9ISO 20022. External Code Sets Common examples include SALA for salary payments, INVS for investment and securities transactions, and GAFA for government family allowances. These coexist with country-specific codes like India’s P-series: the four-letter codes populate structured fields in the SWIFT message, while the national code is often required separately by the receiving bank.

Picking the Right Code and Entering It Correctly

Start with the recipient. Their local bank is the one that validates the code against the transaction, so their guidance carries more weight than your own bank’s generic dropdown. This matters most for transfers to India and China, where the receiving bank will compare the code against documents the recipient has already submitted.

Cross-reference any code your bank suggests against the destination country’s central bank publications. The RBI, UAE Central Bank, and SAFE all publish their official code lists. Discrepancies between a U.S. bank’s internal list and the official regulatory list are a common cause of rejected transfers. Have the supporting paperwork ready too: invoices for trade payments, employment contracts for salary transfers, or a written explanation for personal gifts. If the receiving bank questions the code, documentation is what resolves it.

On the wire transfer form, the field is usually labeled “Purpose of Payment” or “Remittance Information” and sits near the recipient’s account number and SWIFT/BIC code. Type the exact alphanumeric string. A single transposed character can trigger an automated rejection. Save the confirmation receipt once the wire goes through; it should display the purpose code as part of the formal transaction record.

What Happens When the Code Is Wrong

A mismatched or missing purpose code produces one of three outcomes:

  • Suspense account hold. The receiving bank parks the funds until the recipient provides clarification and supporting documents. This is the most common result for transfers to India.
  • Outright rejection. The transfer bounces back to the sender. International returns can take several business days as the payment reverses through intermediary banks.
  • Documentation request. The bank contacts the sender or recipient for additional proof before processing the payment.

In all three scenarios, you’re still paying fees. Your originating bank’s wire charge won’t be refunded on a rejection, and intermediary banks may deduct their own handling charges before returning the funds. Some banks charge a separate amendment or investigation fee to correct the error and resubmit.

Repeated errors create a different problem. Banks are required to file Suspicious Activity Reports when transaction patterns look inconsistent, and a sender whose purpose codes routinely don’t match their documentation may face enhanced scrutiny, additional compliance reviews, or account restrictions.10eCFR. 12 CFR 163.180 – Suspicious Activity Reports and Other Reports and Statements A single honest mistake isn’t the issue; a pattern that makes the bank uncomfortable is.