Quick Fix Summary
Use MT103 for direct customer-to-customer international wire transfers. Use MT202 for bank-to-bank funding messages that support the MT103. Always confirm whether your payment requires MT202 COV (mandatory since 2024) to include beneficiary details. Verify field 21 references the underlying transaction before sending.
What’s really going on with these SWIFT messages?
SWIFT payment messages use “MT” followed by a three-digit code to signal the type of instruction being sent. MT103 is the direct customer credit order—it tells the receiving bank to credit the customer’s account. MT202, on the other hand, handles bank-to-bank funding and carries the MT103 data through correspondent networks. MT202 COV adds mandatory beneficiary details to prevent misrouting and delays.
By 2026, MT202 COV becomes the only accepted format for cover payments; older MT202 messages without cover details often get rejected or face delays. Field 21 in an MT202 must link to a related reference (say, an MT300 FX confirmation) so banks can track the money flow.
Here’s exactly when to use each message type
- Pinpoint your payment scenario first.
- Customer sending money directly to another customer overseas? That’s an MT103.
- Bank funding another bank to support an MT103? That’s an MT202.
- Need to include the beneficiary’s name and account? That’s MT202 COV.
- Double-check your bank’s SWIFT rules. Log in to your bank’s portal (for example, SWIFT Alliance Web Platform v8.1) and go to Messages → Create → Financial Institution Transfer. If you’re sending bank-to-bank funding, the system will automatically prompt you for MT202 fields.
- Fill in the required fields carefully. For MT202 COV, these fields are mandatory:
Field What to enter Example 21 Related Reference FX12345 32A Value Date & Amount 260501USD1500000,00 50K Ordering Institution /123456789ABC 52A Ordering Institution’s Bank CHASUS33 57A Account With Institution BNPAFRPPXXX 58A Beneficiary Institution (final receiver) DEUTDEFF 59 Beneficiary Customer /123456789XYZ John Smith - Send it and keep a copy. Check the message status under Messages → Outgoing → Sent Items. Save the MT reference for at least seven years—regulators love to ask for these during audits.
When things go wrong with your SWIFT messages
- Message rejected or stuck in limbo. Check if your bank now demands MT202 COV for cover payments. After 2026, many correspondent banks enforce this; older MT202 messages often bounce with reason code “533 – Cover details missing” Source: SWIFT Standards.
- Money never reached the beneficiary. Trace the MT103 using the bank’s SWIFT code. Ask your bank to file a Request for Trace (MT199) with the beneficiary’s bank—this is the usual fix when funds don’t arrive on time Source: ABA Compliance Tools.
- Field 21 doesn’t match. Make sure field 21 in the MT202 uses the same value as field 21 in the MT103. Banks match messages using this reference; a mismatch triggers a query and can tack on two to three extra business days to settlement.
How to steer clear of the most common mistakes
- Don’t guess—confirm MT202 vs. MT202 COV first. If the recipient is a regular customer (not another bank), you need MT202 COV. If both sides are banks, MT202 alone is fine.
- Never leave field 59 (Beneficiary Customer) blank in MT202 COV. Since 2024, this is required; leaving it empty risks misrouting your payment Source: ISO 20022.
- Run your message through SWIFT MyStandards. This free portal checks your structure in real time and flags missing or wrong fields before you hit send.
- Keep every MT reference for at least seven years. SWIFT messages are legal proof of payment; examiners routinely ask for them during reviews Source: FDIC Regulations.
