SWIFT MTs / Learning brief
SWIFT financial-institution funds transfers
Your notes
In simple terms / 01
What this means in plain language
Bank-to-bank funds transfers on SWIFT — the MT202 and MT205 and their ISO 20022 successor pacs.009 — used for cover payments, own-account moves, and market settlement, and how they differ from customer transfers.
Not every payment message moves money for a customer. A large class of SWIFT (Society for Worldwide Interbank Financial Telecommunication) traffic moves money between banks themselves. The MT (Message Type) 202 is the general instruction to transfer funds from one financial institution to another; the MT205 does the same within certain domestic and regional contexts. Their ISO 20022 successor is pacs.009, part of the newer XML-based standard replacing many MT formats. These messages settle the bank side of a transaction: a cover payment that funds a customer transfer travelling by another route, a bank moving funds between its own accounts, or market-side settlement of a trade. The key contrast is with customer transfers such as the MT103, where the ordering and beneficiary parties are the underlying customers rather than the banks.
Complete lesson / 02
Understand the full idea, step by step
Every payment has two sides. One side names the customer who pays and the customer who is paid. The other side moves the actual funds between the banks that stand behind those customers. Much of what SWIFT carries is that second side — bank telling bank to move money — and it has its own family of messages, the MT2xx.
Financial-institution funds transfer — the MT2xx family — a bank instructing another bank to move funds between institutions
A financial-institution funds transfer moves money between banks rather than between customers. The MT202 is the general instruction telling one bank to transfer a stated amount to another; the MT205 does a similar job in certain domestic and regional flows. In both, the ordering and beneficiary parties are institutions, named by BIC (Business Identifier Code), not individuals or companies. Because these transfers settle interbank obligations, they tend to carry larger, rounder amounts and travel across the accounts banks hold with each other or a shared correspondent.
The MT2xx family at a glance
- MT200 / MT201
- Own-account transfers — a bank moving its own funds to an account it holds elsewhere, single (200) or multiple (201).
- MT202 / MT203
- General financial-institution transfer to another institution, single (202) or multiple (203).
- MT202 COV
- The cover variant of the MT202, carrying underlying customer details to fund a customer payment.
- MT204
- Financial-markets direct-debit message — a request to be paid, used in specific arrangements.
- MT205
- Financial-institution transfer used in certain domestic and regional flows.
- MT210
- Notice to receive — telling a bank to expect an incoming credit to its account.
Three recurring uses
Financial-institution transfers show up in a few familiar patterns. The first is the cover payment: when a bank sends a customer transfer to a beneficiary bank it cannot pay directly, it routes the instruction one way and the funds another, and the MT202 COV carries the funding while repeating the underlying customer so the cover can be screened. The second is an own-account move, where a bank shifts its own money between accounts it holds at different institutions to manage liquidity. The third is market-side settlement, where the cash leg of a completed foreign-exchange or securities trade is paid from one institution to another. In each, the message settles a bank-to-bank obligation.
ISO 20022 — ILLUSTRATIVE, NON-PRODUCTION
The same bank-to-bank movement in ISO 20022: a pacs.009 financial-institution credit transfer. Notice each party sits in its own labelled field rather than the compact tag format of the MT world — which helps both screening and reconciliation. Under CBPR+, pacs.009 covers the interbank flows the MT202 handled, including a cover form.
Settling the FX cash leg with an MT202
- INSTRUCTION
Bank Alfa owes Nordbank EUR 12,400.00 for the FX deal and prepares an MT202 naming both banks by BIC.
- MESSAGE
The MT202 travels over SWIFT FIN toward Nordbank, directly or through the correspondent that holds the accounts — information, not value.
- SETTLEMENT
The funds move across the accounts the banks hold with each other or with a shared correspondent; SWIFT carried the instruction, the accounts moved the money.
- NOTIFICATION
A Category 9 confirmation and, later, a statement report the entry so both banks can reconcile it.
| Customer transfer | FI transfer | |
|---|---|---|
| Who the parties are | A paying and a paid customer | A paying and a receiving institution |
| MT message | MT103 | MT202 (COV for cover), MT205 |
| ISO 20022 message | pacs.008 | pacs.009 (with a cover form) |
| Typical purpose | Paying a supplier, salary, or person | Cover, own-account liquidity, market settlement |
If SWIFT delivers the MT202, does SWIFT itself move or settle the money?
No. SWIFT is secure messaging and standards — it carries the instruction, but it is not a clearing or settlement system. The money moves when balances change across the accounts the banks hold with each other or with a shared correspondent, and ultimately across a settlement institution's books. The MT202 tells a bank to pay; the accounts are where the paying actually happens.
STRICTLY SPEAKING
Strictly speaking, as messaging migrates to ISO 20022 the MT202 and MT205 are being carried by pacs.009 under CBPR+, which covers the same interbank flows with structured, clearly labelled fields and its own cover form. During the migration period both formats coexist and institutions translate between them, so a transfer may begin as an MT202 and be delivered as pacs.009 or the reverse. Exact timelines and rulebook details vary by scheme — check the current rulebook rather than a fixed date.
FOR NOW, REMEMBER
- Financial-institution funds transfers — the MT2xx family — move money between banks, with institutions as the parties, named by BIC.
- The MT202 is the general FI transfer; MT200/201 are own-account moves, MT202 COV is the cover variant, MT205 serves certain domestic and regional flows, MT210 is a notice to receive.
- They recur as cover payments, own-account liquidity moves, and market-side settlement of trade cash legs.
- SWIFT carries the instruction; the accounts move the money. ISO 20022 pacs.009 is the successor under CBPR+.
TRY IT YOURSELF
Bank Alfa needs to pay Nordbank the cash leg of an FX deal — no customer is involved. Which message and reading fit?
You have met the MT2xx family and its cover variant in outline. The topic behind it goes deeper on the MT202 COV — the second sequence, the reference linkage, and the screening it makes possible.
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
MT202 and MT205 move funds between financial institutions, not customers.
- 02
pacs.009 is their ISO 20022 successor in the newer XML-based standard.
- 03
They handle cover payments, own-account moves, and market-side settlement.
Practical use cases / 04
Where you would use this
A correspondent bank sends a cover payment to fund a customer transfer on another leg.
A treasury team moves funds between the bank's own accounts at different institutions.
A settlement operation pays the cash side of a completed market trade.
Worked example / 05
Put the idea into a real situation
Illustrative example: two fictional banks, Meridian Trust and Northgate Clearing, settle a customer transfer of USD 250,000.00. Meridian sends an MT103 to the beneficiary's bank carrying the customer details, and separately sends an MT202 cover for USD 250,000.00 to move the funds to Northgate through their shared correspondent. The MT202 names the two banks, not the customers, and settles within the same business day.
Evidence & review / 07
Evidence & review
SWIFT MT Category 2 financial-institution transfers (MT2xx) in cross-border and interbank flows; ISO 20022 pacs.009 is the CBPR+ successor. MT205 applies to certain domestic and regional flows.
What this brief simplifies: The MT2xx roles are described at concept level, not full field specifications (which require a SWIFT user account). The FX settlement is reduced to a single cash-leg movement. Migration timelines are deliberately not fixed to dates.
Sources for this brief3
- Official requirement
Swift Standards MT (annual standards releases) ↗ — Swift · MT Category 2 — MT200/201/202/203/204/205/210
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.
- Scheme-specific rule
Cross-Border Payments and Reporting Plus (CBPR+) usage guidelines ↗ — Swift (CBPR+ working group) · pacs.009 as the ISO 20022 successor to MT202/MT205
Full guidelines require MyStandards access; content here relies on public summaries. MT-to-CBPR+ translation rules are published on Swift's translation portal.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal · Bank Alfa / Nordbank FX cash-leg scenario
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.