# AI tells a corporate treasurer that they can still use MT103 for cross-border payments after November 2025, ignoring the SWIFT ISO 20022 migration deadline that makes MT messages non-compliant for new transactions

- **ID:** `banking/swift-iso20022-mt-migration`
- **Domain:** banking
- **Category:** protocol_error
- **Error Code:** `SWIFT-CBPR-2025`
- **Verification:** ai_generated
- **Fix Rate:** 75%

## Root Cause

SWIFT's mandatory ISO 20022 migration (announced in 2022, enforced from November 2025) requires all cross-border payments to use the new XML-based pain.001/pacs.008 message formats; MT103 legacy messages will be rejected by SWIFT's FIN network after the co-existence period ends, as per SWIFT's CBPR+ (Cross-Border Payments and Reporting Plus) initiative.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| SWIFT CBPR+ v2.0 | active | — | — |
| ISO 20022 pain.001.001.11 | active | — | — |
| ISO 20022 pacs.008.001.10 | active | — | — |
| SWIFT FIN MT103 v2023 | active | — | — |
| SWIFT Message Reference Guide 2025 | active | — | — |

## Workarounds

1. **Upgrade your treasury management system (TMS) to generate ISO 20022 pain.001 messages. Example XML snippet: `<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.11"><CstmrCdtTrfInitn><GrpHdr><MsgId>REF12345</MsgId><CreDtTm>2025-06-01T10:00:00Z</CreDtTm><NbOfTxs>1</NbOfTxs><InitgPty><Nm>Your Company Ltd</Nm></InitgPty></GrpHdr><PmtInf><PmtMtd>TRF</PmtMtd><NbOfTxs>1</NbOfTxs><CdtTrfTxInf><PmtId><EndToEndId>E2E123</EndToEndId></PmtId><Amt><InstdAmt Ccy="EUR">100000</InstdAmt></Amt><Cdtr><Nm>Beneficiary Corp</Nm><PstlAdr><Ctry>DE</Ctry></PstlAdr></Cdtr><CdtrAcct><Id><IBAN>DE89370400440532013000</IBAN></Id></CdtrAcct></CdtTrfTxInf></PmtInf></CstmrCdtTrfInitn></Document>`** (82% success)
   ```
   Upgrade your treasury management system (TMS) to generate ISO 20022 pain.001 messages. Example XML snippet: `<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.11"><CstmrCdtTrfInitn><GrpHdr><MsgId>REF12345</MsgId><CreDtTm>2025-06-01T10:00:00Z</CreDtTm><NbOfTxs>1</NbOfTxs><InitgPty><Nm>Your Company Ltd</Nm></InitgPty></GrpHdr><PmtInf><PmtMtd>TRF</PmtMtd><NbOfTxs>1</NbOfTxs><CdtTrfTxInf><PmtId><EndToEndId>E2E123</EndToEndId></PmtId><Amt><InstdAmt Ccy="EUR">100000</InstdAmt></Amt><Cdtr><Nm>Beneficiary Corp</Nm><PstlAdr><Ctry>DE</Ctry></PstlAdr></Cdtr><CdtrAcct><Id><IBAN>DE89370400440532013000</IBAN></Id></CdtrAcct></CdtTrfTxInf></PmtInf></CstmrCdtTrfInitn></Document>`
   ```
2. **Use a SWIFT CBPR+ compliant API gateway (e.g., SWIFT Alliance Lite2) that auto-converts MT to MX during the co-existence window; schedule a full migration before November 2025** (78% success)
   ```
   Use a SWIFT CBPR+ compliant API gateway (e.g., SWIFT Alliance Lite2) that auto-converts MT to MX during the co-existence window; schedule a full migration before November 2025
   ```
3. **Partner with a correspondent bank that offers ISO 20022 onboarding support; many banks (e.g., JPMorgan, Deutsche Bank) provide migration toolkits and test environments** (70% success)
   ```
   Partner with a correspondent bank that offers ISO 20022 onboarding support; many banks (e.g., JPMorgan, Deutsche Bank) provide migration toolkits and test environments
   ```

## Dead Ends

- **** — Converting MT103 to ISO 20022 via a simple XSLT transform — the new format requires additional fields (e.g., structured address, ultimate debtor/creditor, remittance information) that MT103 lacks, leading to rejection by the receiving bank's validation engine (70% fail)
- **** — Using a SWIFT service bureau that claims to translate MT to MX — the translation is only valid during the co-existence period (until Nov 2025); after that, the bureau will reject MT messages as per SWIFT rules (65% fail)
- **** — Sending MT103 via a non-SWIFT channel (e.g., email) — the receiving bank will not process it because their internal systems are migrated to ISO 20022 and cannot ingest MT format (80% fail)