MT201 / MT203 ↔ No ISO 20022 message

Business purpose

MT201 (Multiple Financial Institution Transfer for its Own Account) and MT203 (Multiple General Financial Institution Transfer) batched several FI-to-FI debits or credits into a single message.

What does NOT map cleanly

SWIFT's own end-of-coexistence bulletin places MT201 and MT203 on the 'Payment Messages Withdrawn' list, effective 22 November 2025: these message types are 'not substituted with ISO 20022 messages' and are simply rejected by the FIN network after the cutover — there is no designated ISO 20022 successor at all. This is a real gap, not an oversight: CBPR+'s pacs.009 usage guideline restricts messages to a single transaction only (NbOfTxs fixed at 1), so there is no mechanical way to carry a batch of FI transfers in one ISO 20022 message the way MT201/MT203 did. A sender must decompose the batch into N separate pacs.009 messages at the application layer — a workflow change, not a format translation. Several third-party mapping tables incorrectly present 'MT201/MT203 to pacs.009' as a clean 1:1 mapping; SWIFT's own primary migration bulletin says otherwise.

Migration notes

Withdrawn outright as of the 22 November 2025 cutover, with no SWIFT-provided contingency conversion service (unlike MT200/202/205, which do get temporary MT-to-MX conversion). Institutions still sending MT201/MT203 after the cutover are rejected by the FIN network.