MT202 and MT202 COV
MT202 moves money between banks; MT202 COV is the variant that funds a customer payment and must show whose payment it is.
L0 Explain simply
An everyday analogy: banks move money between themselves the way warehouses move stock — big consolidated shipments, not individual parcels. An MT202 is the paperwork for one of those bank-to-bank shipments. The COV version is the same paperwork with a manifest stapled to it: this shipment exists to fund one specific customer parcel, and here is who sent that parcel and who is due to receive it. The manifest exists so that every warehouse the shipment passes through can check the parcel's sender and receiver — not just the other warehouses — against its lists before letting it move on. Without the manifest, the middlemen would only ever see bank names, never the people behind the payment.
L1 Core concepts
The MT202 is the general financial institution transfer: one bank instructing another to move funds between institutions. Banks use it to settle their own obligations — funding a nostro account, settling the bank leg of a foreign exchange deal, or moving cover for a customer payment. The MT202 COV is a distinct variant reserved for that last purpose. When a customer payment is routed by the cover method — MT103 sent directly to the beneficiary's bank, funds routed separately through correspondents — the funding message must be an MT202 COV, and it must carry the underlying ordering customer and beneficiary in a dedicated second sequence. That requirement exists for transparency: the intermediary banks moving the money can see, and screen, whose payment it ultimately is.
L2 Practitioner view
For operations and compliance teams the COV variant is about two disciplines. First, consistency: the customer details in the COV's underlying sequence must match the MT103 it covers. A mismatch — a different beneficiary name, an inconsistent amount, a missing underlying party — is a classic investigation trigger, and at worst looks like an attempt to hide a party from screening. Second, linkage: the COV points at the MT103 it funds through its related reference, and if that chain breaks, the beneficiary bank may sit on an MT103 it cannot safely credit because the cover cannot be identified. Screening teams treat the underlying sequence as first-class input: an intermediary that only ever sees the MT202 COV relies on it entirely for visibility of the customers. Using a plain MT202 where a COV was required is a recognised transparency failure.
L3 Technical details
The MT202 carries :20: transaction reference, :21: related reference, :32A: value date, currency, and amount, optional routing fields :52a:, :56a:, :57a:, and :58a: the beneficiary institution. In an MT202 COV those fields form sequence A, and a mandatory sequence B carries the underlying customer credit transfer details: :50a: the ordering customer and :59a: the beneficiary customer, with optional fields such as :70: remittance information and :33B: the instructed amount. The linkage works through :21:: the COV's related reference quotes the field 20 reference of the MT103 it covers, which is how receiving systems and investigators pair the two messages. Field specifications and the rules on when the COV variant must be used are in the SWIFT Standards MT Category 2 documentation on swift.com (account required).
Sources & standards1
- Official requirement
Swift Standards MT (annual standards releases) ↗ — Swift · Category 2 — MT202 / 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.
L4 Standards & sources
Two layers of rules govern cover-payment transparency. The message layer is the SWIFT Standards MT Category 2 documentation on swift.com (account required), which defines the MT202 COV as the required format for the funding leg of a cover payment, specifies sequence B, and network-validates that the underlying ordering customer and beneficiary fields are present. The policy layer is the Wolfsberg Group's Payment Transparency Standards, market practice from an association of correspondent banks. They articulate why sequence B exists: no institution in a cover chain should be asked to move value blind to the parties behind it. They expect originating banks to populate underlying party details accurately, intermediaries to screen what sequence B shows them, and each bank's controls to detect a plain MT202 used where a COV was required — the transparency failure this design guards against.
Sources & standards2
- Official requirement
Swift Standards MT (annual standards releases) ↗ — Swift · Category 2 — MT202 COV usage rules and sequence B
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
The 2023 standards replace the 2017 version and are supplemented by separate Wolfsberg guidance on roles and responsibilities in payment chains.
SEE THE PAYMENT MOVE
Read the steps as text
- 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.
- 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
- 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
Sources for this topic3
- Official requirement
Swift Standards MT (annual standards releases) ↗ — Swift · Category 2 — MT202 / 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
The 2023 standards replace the 2017 version and are supplemented by separate Wolfsberg guidance on roles and responsibilities in payment chains.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
What this simplifies: The linked cover flow shows a short correspondent chain with fictional banks; real chains can be longer, and the timing gap between the MT103 and the arrival of cover varies. The warehouse analogy compresses interbank settlement into physical shipment.
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.
Deepest material on this page: L4 — Standards & sources. Where a topic stops short of implementation depth, that is a deliberate coverage decision, not an oversight — see coverage.