Articles / Learning brief
Purpose codes in payments
Your notes
In simple terms / 01
What this means in plain language
Purpose codes and category-purpose codes are standard ISO 20022 external code lists that state why a payment is being made. They can influence routing, regulatory reporting, and screening, but a code is self-declared context, not proof.
A purpose code is a short standard value that states why a payment is being made, for example a salary, a tax payment, or a supplier invoice. ISO 20022 (International Organization for Standardization standard 20022) carries two related fields. The purpose code describes the reason for the payment for the benefit of the end parties, the payer and the payee. The category-purpose code describes the reason at a higher level and is meant for the banks handling the payment, so they can apply any special processing the category needs. Both values come from standard external code lists that ISO 20022 publishes and updates on a regular schedule, so every institution reads the same code the same way. The codes help route a payment, support regulatory reporting, and give screening teams useful context. One caution matters throughout: a purpose code is declared by the sender and is not independently verified, so it is a hint about intent, not proof of it.
Complete lesson / 02
Understand the full idea, step by step
When you send a bank transfer, you often type a note — "rent", "July salary", "invoice 1001". That note is for a human. Payments carry a second kind of note too, one written for machines and controls, in a fixed vocabulary both banks already agree on. That is the purpose code.
Purpose code — a coded reason for the payment, carried on behalf of the payer and payee
The purpose code states why a payment is being made, on behalf of the end parties. It travels through to the beneficiary and their bank as information about what the payment is for — a salary, a supplier payment, a tax payment, a pension, a dividend, rent, a charitable donation. It speaks to the parties: it tells Asha Traders' staff member, and Nordbank, that this credit is wages.
Category-purpose code — a higher-level reason addressed to the banks handling the payment
The category-purpose code answers the same question — why — but at a category level, and it is addressed to the financial institutions moving the payment, not the parties. It lets an agent apply any special handling a category needs, such as treating a whole batch as salaries or requesting same-day value. The same short value, such as the one for salaries, can appear in both fields; what differs is the audience.
| Purpose code | Category-purpose code | |
|---|---|---|
| Answers | Why, for the end parties | Why, at a category level |
| Written for | The payer, payee, and payee's bank | The banks handling the payment |
| Typical use | Context that travels to the beneficiary | Special processing, e.g. salary batch, same-day value |
| Where it sits | Transaction-level purpose element | Payment-information / category element |
The values come from a shared, versioned list
Neither code is invented freely by each sender. Both draw from standard ISO 20022 (International Organization for Standardization standard 20022) external code lists — lists published alongside the message schema rather than inside it, so they can be revised on their own timetable without changing the message definition. The registration authority publishes updates on a regular schedule, adding and occasionally retiring values as business needs change. Because both banks read from the same published list, a code entered by one means exactly the same thing to another — which is what lets a purpose travel between institutions with no separate bilateral agreement. Teams keep their code tables current with each published update rather than freezing one set and forgetting it.
ISO 20022 — ILLUSTRATIVE, NON-PRODUCTION
<PmtTpInf>
<CtgyPurp><Cd>SALA</Cd></CtgyPurp>
</PmtTpInf>
<Purp><Cd>SALA</Cd></Purp>SYNTHETIC — TRAINING ONLY. Here the same value SALA (salary) appears twice: once as a category-purpose for the banks, once as a purpose for the parties. Reading which element a code sits in tells you who it was written for.
You may be wondering: if the sender just picks the code, can a bank trust what it says?
Only so far. A purpose code is declared by the sender and not independently verified — it describes what the payment is said to be for, not what it provably is. That does not make it useless; it makes it context. A control treats the code as one signal among many, confirming the underlying facts from documents and counterparty records rather than relying on the code alone. An honest code sharpens judgement; it never replaces the check.
COMMON CONFUSION
“A payment coded as a charitable donation has been verified as a charitable donation, so it needs less scrutiny.”
The code is self-declared context, not proof. A payment described as a donation to a higher-risk region may in fact warrant a closer look, not a lighter one. Controls use the stated purpose to inform judgement and then confirm the facts independently — the code is where a review starts, never where it ends.
STRICTLY SPEAKING
Strictly speaking, purpose information also feeds regulatory reporting. Several jurisdictions use it to compile balance-of-payments statistics or to meet local rules on cross-border flows, and some markets require a purpose to be stated before a payment can be sent at all. The exact code lists, mandatory-or-not rules, and reporting obligations vary by country, so check the local requirement rather than assuming one rule everywhere.
FOR NOW, REMEMBER
- A purpose code states why a payment is made, for the parties; a category-purpose code states it at a category level, for the banks.
- Both draw from ISO 20022 external code lists — published beside the schema and updated on a schedule, so a code means the same to every reader.
- A code enables routing, special handling, and regulatory reporting — but it is self-declared context, not verified proof.
- Controls treat the stated purpose as one signal and confirm the facts independently.
TRY IT YOURSELF
A payment arrives at Meridian Bank carrying a purpose code that reads as a charitable donation, sent to a higher-risk region. How should the screening team treat that code?
A code can say why a payment is sent. Two other codes say who is involved and where it goes — the BIC that routes to a bank, and the LEI that identifies a legal entity. They are often confused; next we separate them.
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
The purpose code states why a payment is made for the end parties; the category-purpose code states the reason at a higher level for the banks handling it.
- 02
Both values are drawn from standard ISO 20022 external code lists that are published and updated on a regular schedule.
- 03
A purpose code is declared by the sender and not independently verified, so controls treat it as context, not proof.
Practical use cases / 04
Where you would use this
A payroll provider sets the category-purpose code to the salary value so receiving banks can apply any special handling salaries require.
A central bank or regulator uses purpose codes on cross-border payments to compile balance-of-payments statistics.
A screening analyst reads the purpose code as context when reviewing an alert, while confirming the facts from other evidence.
Worked example / 05
Put the idea into a real situation
Illustrative example: a fictional employer, Rowan Textiles Ltd, pays monthly salaries to 42 staff through its bank, a fictional institution called Meridian Trust. On the batch, Rowan Textiles sets the category-purpose code SALA, which signals salaries, and each individual payment carries the purpose code SALA as well. One payment of EUR 3,180.00 to an employee is routed and reported as a salary, and because the category is known, Meridian Trust applies its standard same-day salary handling. When a separate payment of EUR 120,000.00 later carries the purpose code SUPP for a supplier invoice, a screening analyst notes the stated purpose but still verifies the counterparty and invoice from independent records before releasing it.
Evidence & review / 07
Evidence & review
ISO 20022 purpose and category-purpose codes generally; regulatory reporting obligations vary by jurisdiction.
What this brief simplifies: Uses SALA as an illustrative value and describes the code-list update cadence without version-specific dates; local reporting mandates are summarised, not enumerated.
Sources for this brief3
- Official requirement
ISO 20022 External code sets ↗ — ISO 20022 Registration Authority · Purpose and CategoryPurpose code lists
Updated quarterly (end of February, May, August, and November) in XLSX, XSD, and JSON formats; always check the latest published version for valid codes.
- Market practice
Wolfsberg Group Sanctions Screening Guidance ↗ — The Wolfsberg Group
Wolfsberg guidance is industry market practice, not law; institutions vary in how they apply it.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.