Payment-Purpose Code

A payment-purpose code is a standardized code attached to a payment that identifies its commercial or regulatory reason, for example payment for imported goods, fees for services, salary, family support or an investment. Purpose codes allow banks and central banks to classify cross-border flows for statistics, foreign exchange control and compliance, and allow companies to pass structured information to their counterparties.

In many countries a purpose code is mandatory for international transfers, and an inaccurate or missing code can cause a payment to be delayed, rejected or reported incorrectly. A code that does not match the supporting documents can also raise questions in anti-money laundering reviews.

• Balance of payments statistics: central banks use purpose codes to compile the balance of payments, distinguishing trade, services, income and transfers.
• Foreign exchange control: where capital controls apply, a current account transaction such as an import payment may be freely allowed while a capital account transaction such as a foreign investment needs approval. The code tells the bank which rules apply.
• Tax and reporting: some flows, such as dividends or royalties, attract withholding tax or specific reports.
• Compliance: the stated purpose gives banks a reference point for checking whether a payment fits the customer's profile and documents.

There is no single global list; codes are set nationally or by message standards.

• ISO 20022 defines an external Purpose code list used in ISO 20022 messages, with four-letter codes such as SALA (salary), SUPP (supplier payment), GDDS (purchase or sale of goods) and TAXS (tax payment).
• India: the Reserve Bank of India publishes purpose codes for foreign exchange transactions, with separate series for inward and outward remittances.
• United Arab Emirates: the Central Bank of the UAE requires a three-letter purpose of payment code on many transfers, for example for salaries and family support.
• China: cross-border receipts and payments are reported under balance of payments transaction codes administered by the State Administration of Foreign Exchange (SAFE).

Many other countries in Asia, the Middle East and Africa apply similar requirements, particularly those with limited currency convertibility.

In legacy SWIFT messages, the code is often placed in a free-text field, such as the remittance information or sender-to-receiver information of an MT103, in the format required by the destination country. In ISO 20022 messages it can be carried in dedicated structured fields, either as an ISO code or as a local regulatory reporting code. The originating bank or remittance provider collects the purpose from its customer, and the receiving bank uses it to complete its own reporting.

A wrong or missing purpose code can lead to:

• the payment being held by the beneficiary bank pending clarification, opening a payment investigation;
• rejection and a returned payment, sometimes after fees and exchange losses;
• problems for exporters required to evidence export proceeds repatriation;
• a mismatch with the commercial invoice or contract, which may prompt enhanced checks under trade payment compliance procedures;
• in serious cases, regulatory penalties for misreporting.

Deliberately misstating the purpose, for example labelling a capital transfer as a payment for services to avoid exchange controls, may breach foreign exchange law and is a known red flag for trade-based money laundering. Senders are therefore advised to choose the code that reflects the real transaction and to keep the documents that support it.