SWIFT MTs / Learning brief
SWIFT MT2xx Financial Institution Messages
Your notes
In simple terms / 01
What this means in plain language
SWIFT Financial Application (FIN) Category 2 covers transfers where banks are the parties. This guide separates own-account from third-party transfers, single from multiple, and explains the notice nature of MT210 and the MT202 COV cover message.
The Society for Worldwide Interbank Financial Telecommunication (SWIFT) Financial Application (FIN) Category 2, the MT2xx range, is for financial-institution transfers. Here the parties to the message are banks moving funds, not end customers. Some of these transfers move a bank's own money between its accounts, and others move funds on behalf of a third party. A few messages carry no money at all and simply give notice that funds are coming. This guide sorts the main MT2xx types by whether they are own-account or general, single or multiple, and instruction or notice, and it explains the widely used MT202 COV cover message.
Complete lesson / 02
Understand the full idea, step by step
A customer payment gets announced in one message — but the banks behind it are now out of pocket to each other, and that has to be squared with a message of its own. Category 2 is the bank-to-bank set: the messages banks use to move their own money.
MT2xx and MT202 COV — Category 2 — financial-institution transfers; COV is the cover variant
Category 2 (the MT2xx range) covers financial-institution transfers: the named parties are banks, not end customers. The plain MT202 is a single general FI transfer. The MT202 COV (cover) is an MT202 that accompanies an underlying customer credit transfer, repeating that customer's details so the cover leg can be checked against the payment it funds.
| Message | What it does | Whose funds / nature |
|---|---|---|
| MT200 | Single FI transfer for the bank's own account | Own funds, single |
| MT201 | Multiple FI transfer for the bank's own account | Own funds, multiple |
| MT202 | Single general FI transfer | On behalf of another party |
| MT203 | Multiple general FI transfer | On behalf, multiple |
| MT202 COV | Cover for an underlying customer credit transfer | Funds a customer payment |
| MT204 | Financial markets direct debit | Pull between institutions |
| MT205 | FI transfer execution — pass a received payment onward | Onward leg in a chain |
| MT210 | Notice to receive — expect an incoming credit | Information only, no funds |
Serial and cover: announcement versus funding
There are two ways to route a cross-border customer payment. In the serial method, the MT103 itself passes bank to bank down the chain, funding and announcement together. In the cover method, Bank Alfa sends the MT103 announcement straight to Nordbank, and *separately* sends an MT202 COV to move the money through the correspondent. Same payment, two legs: one tells the beneficiary's bank what is coming, the other funds it.
Read the steps as text
- 01MessageThe customer orders a USD transfer abroadOrdering customer → Bank Alfa (ordering bank)
Same starting point as the serial method — the difference is how Bank Alfa chooses to route instruction and money.
- 02ProcessingBank Alfa validates, screens, and debitsBank Alfa (ordering bank)
After checks and screening, the customer's account is debited and the bank decides on the cover method: announce directly, pay through correspondents.
- DR Ordering customer's account at Bank Alfa — USD 250,000.00
Screening checkpoint: Outbound cross-border screening — Both the announcement and the cover leg will be screened by every bank that touches them.
- 03MessageThe MT103 goes directly to CassiaBank Alfa (ordering bank) → Cassia Bank (beneficiary bank) · MT103
The beneficiary bank learns the full payment details immediately — who is paying whom, how much, and why. But this message alone brings no money.
- 04MessageThe cover transfer goes to the correspondentBank Alfa (ordering bank) → Meridian Bank (correspondent) · MT202 COV
The MT202 COV moves the money along the account chain. Its sequence B repeats the underlying customer details so every bank in the chain can screen the real parties.
- 05SettlementMeridian settles the cover across its booksMeridian Bank (correspondent)
As in the serial flow, settlement is a book transfer between the two banks' USD accounts held at Meridian.
- DR Bank Alfa's USD account at Meridian (vostro) — USD 250,000.00
- CR Cassia's USD account at Meridian (vostro) — USD 250,000.00
- 06MessageCassia sees the cover arrive on its nostroMeridian Bank (correspondent) → Cassia Bank (beneficiary bank) · MT910
The credit advice tells Cassia the money side is complete. Now it has both halves: instruction and funds.
- 07ProcessingCassia matches the announcement against the coverCassia Bank (beneficiary bank)
The beneficiary bank pairs the MT103 with the incoming cover by references and amount. Crediting on the MT103 alone would be paying before being paid.
- 08PostingThe beneficiary is creditedCassia Bank (beneficiary bank)
With instruction and funds matched, Cassia credits its customer. The cover method can be faster for the beneficiary bank's information, but credit still waits for money.
- CR Beneficiary's account at Cassia — USD 250,000.00
SWIFT MT — ILLUSTRATIVE, NON-PRODUCTION
The cover leg for the supplier payment. Its sequence B (:50K: ordering customer, :59: beneficiary) repeats the underlying customer details from the MT103 — deliberately, so every bank in the chain, including the correspondent, can screen the same parties. :32A: carries the interbank settlement amount.
| Account | Dr | Cr |
|---|---|---|
| Bank Alfa vostro account | EUR 1,250.00 | |
| Settlement owed toward Nordbank | EUR 1,250.00 |
Illustrative two-entry view on the correspondent's books. A real posting includes value dating, fees, and control accounts, and the exact account structure varies by institution.
COMMON CONFUSION
“The MT202 COV is a second, separate payment — so the supplier gets paid twice.”
No. The MT103 and the MT202 COV are two legs of one payment: the MT103 announces it to Nordbank, the MT202 COV funds it through the correspondent. Nordbank credits the supplier once, matching the two together. Announcement and funding are separated on purpose — never doubled.
WHAT IF — An MT210 arrives instead of a funds transfer
What happens: No money moves. An MT210 is a notice to receive — a pre-advice telling a bank to expect an incoming credit.
How it is handled: Reconciliation treats it as information: it warms up the expectation, and the actual credit still has to arrive and settle. Maya's team at Bank Alfa reads a stray MT210 as a heads-up, not as a completed payment.
STRICTLY SPEAKING
Strictly speaking, the cover variant exists to keep the underlying customer visible to every bank in the chain — a payment-transparency expectation, not a routing convenience. In ISO 20022 the FI transfer maps to pacs.009, with a cover flavour that likewise carries the underlying customer block. The idea is the same across MT and MX: the institutional leg must not hide who is really paying whom.
FOR NOW, REMEMBER
- Category 2 (MT2xx) messages move banks' own funds — the parties named are institutions.
- MT200/201 move a bank's own money; MT202/203 move funds on behalf; MT204 pulls; MT205 passes a payment onward.
- MT202 COV funds an underlying customer payment and repeats its details so every bank can screen them.
- MT210 is a notice to receive — information about an incoming credit, moving no money itself.
TRY IT YOURSELF
Nordbank receives an MT103 for the supplier payment and, shortly after, an MT202 COV that repeats the same customer names and amount. What should Nordbank conclude?
Customer and institutional messages both assume the network delivered them. But a perfectly valid payment can still fail before it reaches the other bank. Next: the system messages that report acceptance and delivery.
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
SWIFT Financial Application (FIN) Category 2 messages are financial-institution transfers: the banks themselves are the parties, distinguishing them from the customer payments of Category 1.
- 02
MT200 and MT201 move a bank's own funds between its own accounts (single and multiple), while MT202 and MT203 are general institution transfers (single and multiple); MT202 COV is the cover version that accompanies an underlying customer payment.
- 03
MT210 is a notice to receive, a pre-advice that no funds move on its own; MT204 is a financial markets direct debit and MT205 is a transfer execution passing the payment onward.
Practical use cases / 04
Where you would use this
A nostro reconciliation team recognises an MT210 notice to receive as a pre-advice and expects a matching credit, without treating the notice itself as a settlement.
A correspondent bank processing an MT202 COV links the cover payment to the underlying customer transfer so both legs can be screened consistently.
A treasury operations analyst uses MT200 to sweep the bank's own funds between two of its own accounts held at different correspondents.
Worked example / 05
Put the idea into a real situation
Illustrative example: Meridian Bank owes 5,000,000.00 USD to Cedar Bank as cover for a customer payment. Meridian sends an MT202 COV whose cover fields reference the underlying customer transfer. Separately, Meridian sweeps 750,000.00 USD of its own money between two of its nostro accounts using an MT200. Cedar Bank, expecting an unrelated incoming credit, has already received an MT210 notice to receive, which moved no funds by itself but told operations to watch for the arriving payment.
Evidence & review / 07
Evidence & review
SWIFT FIN MT standard, Category 2 financial-institution messages; correspondent-banking cover routing
What this brief simplifies: Shows a two-entry correspondent posting and separates the customer announcement (MT103) from the cover funding (MT202 COV). Real postings, value dating, and screening rules are more detailed and institution-specific.
Sources for this brief4
- Official requirement
Swift Standards MT (annual standards releases) ↗ — Swift · FIN Category 2; MT200-210 and MT202 COV
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.
- Market practice
Wolfsberg Group Payment Transparency Standards ↗ — The Wolfsberg Group · Cover payment transparency
The 2023 standards replace the 2017 version and are supplemented by separate Wolfsberg guidance on roles and responsibilities in payment chains.
- Market practice
ISO 20022 Standards (Swift ISO 20022 adoption programme) ↗ — Swift · pacs.009 FI transfer and cover
Programme milestones change over time; the coexistence period for in-scope cross-border payment instructions ended in November 2025. Check swift.com for the current timeline.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal · Cover scenario and correspondent ledger
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.