SWIFT MTs / Learning brief
The SWIFT message categories
Your notes
In simple terms / 01
What this means in plain language
Swift MT (Message Type) messages are grouped into numbered categories by business area, from customer payments to securities and cash management, so each message carries a predictable purpose and structure across the network.
Swift is a messaging network banks use to exchange structured instructions. Its older format is the MT (Message Type) standard, and every MT message has a three-digit number. The first digit is the category, and it tells the reader the business area the message belongs to. Category 1 covers customer payments and cheques, category 2 covers transfers between financial institutions, category 3 covers treasury business such as foreign exchange and money markets, category 4 covers collections and cash letters, category 5 covers securities, category 6 covers commodities and syndications, category 7 covers documentary credits and guarantees, category 8 covers travellers cheques, and category 9 covers cash management and status reporting. A common group, written as category n, holds messages shared across all areas. Knowing the category lets an operator predict what a message means before reading its contents.
Complete lesson / 02
Understand the full idea, step by step
Walk into a large library and the shelves are not random: a number on the spine tells you the subject before you open the book. SWIFT MT messages are shelved the same way. The three-digit number is not a serial code — its first digit sorts every message into a business area, so you can guess a message's purpose before you read a single field.
The first digit is the category
An MT type is three digits, and the first digit is the category — the business area. The second digit groups related messages inside that area; the third names the specific message. Because the scheme is consistent everywhere on the network, an institution in one country and one in another share the same understanding of what a given type is: an MT103 is a single customer credit transfer, an MT202 a general financial-institution transfer. That shared meaning is the whole point of a standard — it removes ambiguity and lets validation rules attach to each type.
| Category | Business area | Example |
|---|---|---|
| 0 | System messages — the network talking to itself (acknowledgements, service) | ACK / NAK |
| 1 | Customer payments and cheques — a party is not a bank | MT103 |
| 2 | Financial-institution transfers — movements between the institutions themselves | MT202 / MT202 COV |
| 3 | Treasury markets — foreign exchange, money markets, derivatives | FX confirmation |
| 4 | Collections and cash letters | Documentary collection |
| 5 | Securities — trade, settlement, corporate actions | Settlement instruction |
| 6 | Commodities and syndications | Precious-metals trade |
| 7 | Documentary credits and guarantees (trade finance) | Letter of credit |
| 8 | Travellers cheques | Travellers cheque message |
| 9 | Cash management and customer status — balances and statements | MT940 statement |
The common group (category n) — the letter n stands in for any category digit
Beyond the numbered categories, SWIFT defines a common group written as category n, where n stands for any category digit. These messages do jobs needed across every business area — acknowledging receipt, requesting cancellation, or reporting that a message could not be processed. A common-group message can query or recall an earlier instruction no matter which category that instruction belonged to, which is why you meet the same handling messages everywhere.
Does every bank support every category?
No — and it would be wasteful to. A bank supports the categories that match its business lines. A retail-focused bank may live almost entirely in categories 1, 2, and 9 (customer payments, interbank transfers, and statements) and never touch category 6 commodities or category 7 trade finance. The category map is the full menu; each institution builds focused processing for the areas it actually uses, and routes the rest away or rejects it.
COMMON CONFUSION
“The category number alone tells you exactly what a message means.”
The category is a strong first hint, not the final word. The same type can appear in different operational situations, and direction, sender and receiver roles, and the actual fields still decide meaning — the point you met when reading option letters and cover payments. Read the number to sort and route; read the fields to be sure.
STRICTLY SPEAKING
Strictly speaking, many institutions now also exchange ISO 20022 MX messages alongside MT, and those are named by a different scheme (like pacs.008) rather than a category digit. The category concept is an MT idea and remains a clear mental model, but it does not map one-to-one onto the MX naming you will meet elsewhere.
FOR NOW, REMEMBER
- An MT type is three digits: the first is the category (business area), the second a group, the third the specific message.
- Categories run 0-9: 0 system, 1 customer payments, 2 FI transfers, 3 treasury, 4 collections, 5 securities, 6 commodities, 7 trade finance, 8 travellers cheques, 9 cash management.
- The common group (category n) carries cross-cutting functions like acknowledgement, cancellation, and non-delivery reports.
- Banks support only the categories their business needs, and the category digit drives routing and controls.
TRY IT YOURSELF
An incoming message is an MT940. Before reading its fields, which team's queue should Bank Alfa's routing send it to, based on its category?
You know how messages are organised today. Last question in this series: these standards are not frozen — how and why do they change, once a year, without breaking the shared language?
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
The first digit of a Swift MT number identifies the business category.
- 02
Categories 1 through 9 each map to a distinct area of banking activity.
- 03
The common group, category n, holds messages used across all categories.
Practical use cases / 04
Where you would use this
An operations analyst routes an incoming message to the correct team by reading its category digit.
A systems team maps each supported category to a processing queue and validation ruleset.
A trainer teaches new staff to recognise message purpose from the number before opening the body.
Worked example / 05
Put the idea into a real situation
Illustrative example: an operator at a fictional bank, Meridian Trust, receives three messages numbered MT103, MT202, and MT300. The leading digits 1, 2, and 3 tell the operator, before reading any field, that the first is a customer credit transfer, the second a financial-institution transfer, and the third a foreign-exchange confirmation. The operator routes all 3 to their respective teams in under 60 seconds using only the category digit.
Evidence & review / 07
Evidence & review
SWIFT FIN MT category system (categories 0-9 and common group n).
What this brief simplifies: Gives one representative example per category; real message sets and usage rules are more detailed and governed by SWIFT's standards and market practice.
Sources for this brief2
- Official requirement
Swift Standards MT (annual standards releases) ↗ — Swift · MT message categories and common group
Full field-level specifications live in the Swift Knowledge Centre User Handbook behind a swift.com login; content here relies on public summaries. Swift ended MT-to-ISO 20022 coexistence for in-scope cross-border payment instructions (for example MT103 and MT202) in November 2025; MT statement messages are being phased out on a separate timeline.
- 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.