Serial versus cover routing
Two ways to route the same payment: pass the MT103 bank to bank, or send it direct and move the money separately with an MT202 COV.
L0 Explain simply
An everyday analogy: you need to get a valuable package and its delivery note to someone abroad. The serial method is a relay: you hand both to a courier, who hands both to the next courier, until the last one delivers. Nothing arrives until everything arrives, but everyone in the chain sees exactly what they are carrying. The cover method splits them: you post the delivery note straight to the recipient's local depot — "a package is coming, here is everything about it" — while the package itself travels separately through the freight network. The depot can prepare in advance, but it should not hand anything over until the package actually lands. Most cross-border payment problems trace back to which of these two choices was made.
L1 Core concepts
Serial and cover are the two classic ways to route a cross-border customer payment through correspondent banks. In the serial method, one MT103 travels the whole way: the ordering bank sends it to its correspondent, which sends it on, hop by hop, until it reaches the beneficiary's bank; each hop settles across the accounts the two banks hold with each other. In the cover method, the MT103 goes directly from the ordering bank to the beneficiary bank — fast, and complete with all customer detail — while the money moves separately through the correspondent chain as an MT202 COV. The beneficiary bank holds the instruction early but should only credit its customer once the covering funds have actually arrived on its account.
L2 Practitioner view
The choice is driven by relationships and currency. If the ordering bank has no direct relationship with the beneficiary bank, serial keeps instruction and money together — at the cost of every intermediary handling the customer payment, each applying its own screening, possible deductions, and cut-offs. Cover gets the full instruction to the beneficiary bank sooner and keeps intermediaries off the MT103 entirely, which is precisely why the funding leg must be an MT202 COV carrying the underlying parties. The failure modes differ accordingly. Serial: charges eroding the amount, and any bank in the chain missing its cut-off and pushing value a day. Cover: the mismatch-and-timing family — MT103 in hand but cover late, absent, or inconsistent, leaving the beneficiary bank holding an instruction it cannot safely act on.
L3 Technical details
The routing shows up in the fields. A serial MT103 uses :56a: (intermediary institution) and :57a: (account with institution) to spell out the remaining chain, and each bank re-issues the message with the path shortened by one. In a cover arrangement, the direct MT103 signals how funds will travel through :53a: (sender's correspondent) and :54a: (receiver's correspondent), telling the beneficiary bank where to expect the money. The MT202 COV then links back through :21:, quoting the MT103's :20: reference, and repeats the underlying customers in its sequence B. Under SWIFT gpi practice, both legs carry the same UETR in block 3 field 121, so a tracker can join instruction and cover into one journey. Matching engines at the beneficiary bank pair arriving covers with waiting MT103s on reference, amount, and value date.
L4 Standards & sources
Two kinds of source govern this topic. The SWIFT Standards MT documentation (Categories 1 and 2) defines the messages themselves: the MT103 and MT202 COV formats, the related-reference linkage, and the rule that a financial institution transfer covering an underlying customer payment must use the COV variant with the underlying parties present. It is published on swift.com and requires a SWIFT user account, so public descriptions — ours included — are summaries. The transparency expectations behind the COV variant are articulated as market practice in the Wolfsberg Group's payment transparency standards, which set out why intermediary banks should be able to see and screen the parties to payments they help move. Institutions differ in how they operationalise cover matching, so verify local practice before assuming a universal rule.
Sources & standards2
- Official requirement
Swift Standards MT (annual standards releases) ↗ — Swift · Categories 1 and 2 — MT103 and MT202 COV usage rules
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 and screensBank Alfa (ordering bank)
Format and balance checks plus sanctions screening. Cross-border payments face stricter screening because more jurisdictions are involved.
Screening checkpoint: Outbound cross-border screening — Ordering and beneficiary parties, banks, and remittance text are screened before the payment leaves.
- 03PostingThe customer's account is debitedBank Alfa (ordering bank)
Bank Alfa books the debit and, per the charge option, any fees.
- DR Ordering customer's account at Bank Alfa — USD 250,000.00
- 05ProcessingMeridian validates and screens in the middleMeridian Bank (correspondent)
Every bank in the chain screens independently. Meridian also checks that Bank Alfa's account has cover for the debit.
- 06SettlementMoney moves across the books of MeridianMeridian Bank (correspondent)
Both Bank Alfa and Cassia hold USD accounts at Meridian. Settlement here is a book transfer in commercial bank money: Meridian debits one account it holds and credits the other.
No clearing house is involved — the correspondent's ledger is the settlement venue. This is settlement in commercial bank money, not central bank money.
- 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
- 09ProcessingCassia validates the incoming paymentCassia Bank (beneficiary bank)
Account checks and inbound screening. Only when funds are confirmed on the nostro and checks pass is the beneficiary credited.
- 10PostingThe beneficiary is creditedCassia Bank (beneficiary bank)
Cassia credits its customer, net of any beneficiary-side charges the charge option allows.
- CR Beneficiary's account at Cassia — USD 250,000.00
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 · Categories 1 and 2 — MT103 and MT202 COV usage rules
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 serial and cover flow diagrams use fictional banks, a fixed number of intermediaries, and clean happy paths; real chains vary in length, and matching, screening, and liquidity steps are compressed. The courier analogy treats funds as a physical object, which understates how settlement actually works across accounts.
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.