MT200 / MT202 / MT205 ↔ pacs.009
3 pairs on this page · Use case: FI transfer
MT200 ↔ pacs.009
Business purpose
Financial Institution Transfer for its Own Account — an FI moving funds between its own accounts held at another institution.
What does NOT map cleanly
pacs.009 core carries no Charge Bearer field and no Ultimate Debtor/Creditor support — matching MT200's own scope, so no functional loss on those fields, but it does mean the message can't pass through ultimate-party information the way pacs.008 can. CBPR+ restricts pacs.009 to a single transaction per message (NbOfTxs fixed at 1). Settlement Method (SttlmMtd) and Creation Date/Time are new fields added in pacs.009 with no MT200 source.
Migration notes
After FI-to-FI cross-border MT/ISO coexistence ended on 22 November 2025, MT200 is no longer delivered as MT on FIN for those flows. Qualifying MT200 instructions sent on FIN can still undergo Swift's limited contingency conversion for pacs.009 delivery on FINplus.
Sources
- BNY — Update on ISO 20022 End of Co-existence ·MT 200 is subject to contingency processing with ISO equivalent pacs.009.001.xx as of 22 November 2025 (confirmed)
- Clearstream / SWIFT MyStandards — CBPRPlus-pacs.009.001.08 Usage Guideline ·pacs.009 core carries no Charge Bearer or Ultimate Debtor/Creditor fields; CBPR+ usage guideline restricts messages to a single transaction only (NbOfTxs fixed value = 1) (confirmed)
MT202 ↔ pacs.009
Business purpose
General Financial Institution Transfer — an interbank funds transfer where both the ordering and beneficiary parties are financial institutions, executed serially (each agent in the chain instructs the next). This is the non-cover variant; MT202 COV is a separate, owned pair.
What does NOT map cleanly
Same structural caveats as MT200: no Charge Bearer or Ultimate Debtor/Creditor fields, single-transaction-only under CBPR+, structured-address preference, and new no-MT-source fields (Settlement Method, Creation Date/Time). Agent identification rules tighten under CBPR+ — BICFI takes precedence over Name and Address when both are present.
Migration notes
After FI-to-FI cross-border MT/ISO coexistence ended on 22 November 2025, MT202 is no longer delivered as MT on FIN for those flows. Qualifying MT202 instructions sent on FIN can still undergo Swift's limited, chargeable MT-to-ISO contingency conversion for pacs.009 delivery on FINplus. ISO-to-MT in-flow translation is a separate service.
Sources
- J.P. Morgan — Migration to ISO 20022 (Useful information, hints and tips) ·MT202 maps to pacs.009 core; full field-by-field mapping table (tags 20/21/32A/52A/53A/54A/56A/57A/58A/72) plus worked XML example (confirmed)
- BNY — Update on ISO 20022 End of Co-existence ·MT200, MT202, MT202 COV subject to contingency processing with ISO equivalents pacs.009.001.xx / pacs.009COV.001.xx as of 22 November 2025 (confirmed)
- Deutsche Bundesbank / T2 — Overview of messages for the future RTGS ·MT202 to pacs.009 (core, adv) design-time mapping, marked 'ISO Message (no CR needed)' (confirmed)
MT205 ↔ pacs.009
Business purpose
Financial Institution Transfer Execution — sent by the receiver of a category-2 message (MT200/201/202/203/205 or its ISO equivalent) to further transmit the transfer domestically to the beneficiary institution. It is the next-leg execution message, not the initiating order.
What does NOT map cleanly
Swift lists both MT202 and MT205 against pacs.009. That is a message-level correspondence, not proof that the two MT usage patterns or every field map identically. Confirm the purpose and participants of the next leg before converting a particular instruction; this lookup does not specify a field-level MT205 mapping.
Migration notes
After FI-to-FI cross-border MT/ISO coexistence ended on 22 November 2025, MT205 and MT205 COV are no longer delivered as MT on FIN for those flows. Qualifying instructions sent on FIN remain on Swift's limited MT-to-ISO contingency-conversion list.
Sources
- BNY — Update on ISO 20022 End of Co-existence ·MT 205 and MT 205 COV subject to contingency processing with ISO equivalents pacs.009.001.xx and pacs.009COV.001.xx as of 22 November 2025 (confirmed)
- Swift — CBPR+ roadmap beyond Standards Release 2025, September 2026 v6 ·Swift lists MT205 against pacs.009 at message level; this chart does not establish a field-level MT205 mapping (confirmed)