Purpose of Transaction

The purpose of transaction is the reason a payment is being made, such as paying a salary, supporting family members, settling an invoice for goods, paying tuition or making an investment. Banks, money transfer operators and other payment providers collect it from the sender, and sometimes the recipient, because it helps them judge whether a payment makes sense for the customer, meet reporting rules and route the payment correctly.

The idea appears in two related but different settings. In anti-money laundering, regulators expect firms to understand the purpose and intended nature of a customer relationship and to question payments that do not fit it. In cross-border payments, many countries require a specific payment-purpose code on each transfer for foreign exchange control and balance of payments statistics. Both make the purpose a standard part of a payment instruction rather than an optional note.

Providers collect the purpose of transaction for several reasons at once:

• Due diligence. Under customer due diligence rules based on the FATF recommendations, firms must understand what a customer's activity is for. A stated purpose gives a baseline against which later payments are compared.
• Transaction monitoring. A payment labelled as family support that is followed by large business-like flows, or a trade payment to a counterparty with no apparent link to the customer's business, can raise an alert in transaction monitoring.
• Sanctions and export controls. The purpose may reveal that a payment relates to restricted goods, sectors or services, which ordinary name screening would miss.
• Foreign exchange regulation. Countries with capital controls permit some purposes freely and restrict others, so the stated purpose decides whether a transfer may proceed and what documents are needed.
• Statistics and tax. Central banks use purpose data to compile the balance of payments, and tax authorities may use it to identify income such as dividends or royalties.

Many countries publish official lists of purpose codes that must accompany inbound or outbound payments. India's foreign exchange rules require a purpose code on outward remittances and on many inbound payments, distinguishing categories such as travel, education, family maintenance, imports and services. The United Arab Emirates, China, Malaysia, the Philippines and a number of other countries use their own code lists for payments in or out of the country. A payment sent without the correct code, or with a code that does not match the documents, may be held, rejected or returned by the receiving bank.

For senders, this means that a money transfer app or bank portal will often ask the customer to choose a purpose from a list, and the provider then maps that choice to the destination country's official code. Errors in this mapping are a common cause of delayed international wire transfers.

Payment message standards provide fields for the purpose. ISO 20022 messages such as the customer credit transfer contain a structured purpose element that can carry a code from an external list maintained alongside the standard, as well as a category purpose that tells banks how to process the payment, for instance as salary or a treasury transfer. Older SWIFT MT messages carried the purpose mostly as free text in the remittance or bank-to-bank information fields, which made automated checks harder. The migration of cross-border payments to ISO 20022 has made structured purpose data more widely available to banks along the payment chain.

The purpose of transaction explains where money is going and why. It is different from source of funds, which explains where the money came from, and from source of wealth, which explains how the customer built their overall assets. Firms often ask for all three on large or high-risk payments, for example when applying enhanced due diligence to a politically exposed person or a high-risk country.

The stated purpose is only as reliable as the customer's answer. Criminals can pick a plausible purpose, and honest customers often choose a code at random from a long list. For this reason providers treat purpose as one data point among many, combining it with customer profiles, documents such as invoices or contracts, and pattern analysis. Industry groups have also noted that inconsistent national code lists add cost and friction to cross-border payments, and international work on improving cross-border payments has encouraged more harmonised use of structured purpose data.