BRIDGE Intelligence
BRIDGEIntelligence
[ BACK_TO_REPORTS ]
RESEARCH

ISO 20022 Is Now Mandatory — What Banks Need to Know

SWIFT's November 2025 deadline has passed. Every bank processing cross-border payments must now support ISO 20022 messaging. Here's what changed and why it matters for settlement infrastructure.

PUBLISHED

June 15, 2025

AUTHOR

Bridge Research Team

READ_TIME

7 min read

CATEGORY

Research

ISO-20022SWIFTcross-border-paymentsbanking-infrastructuresettlementcompliance

The Deadline Has Passed

On November 22, 2025, SWIFT completed its migration to ISO 20022 messaging for cross-border payments. The MT message format that banks relied on for decades is being phased out. Every institution processing international payments must now support the new standard.

This isn't a minor protocol change. ISO 20022 fundamentally restructures how payment data is transmitted — from free-text fields to structured, machine-readable data elements. The implications for settlement infrastructure are significant.

What Changed

From MT to MX

The legacy MT (Message Type) format used fixed-length fields with limited character sets. A typical cross-border payment carried minimal structured data — often just enough to route the payment, with critical details buried in free-text fields that required manual parsing.

ISO 20022's MX format replaces this with rich, structured XML/JSON messages carrying:

  • Complete originator and beneficiary information — full legal names, addresses, and identifiers
  • Purpose codes — standardized transaction purpose categories
  • Regulatory reporting fields — jurisdiction-specific compliance data
  • Remittance information — structured invoice and reference data
  • End-to-end transaction tracking — unique identifiers from initiation to settlement

What This Means for Banks

Compliance teams now receive structured data instead of parsing free-text fields. Sanctions screening accuracy improves because names and addresses are in dedicated fields, not embedded in narrative text.

Operations teams benefit from automated straight-through processing. The structured format reduces the manual intervention rate — currently averaging 40% for cross-border payments — by eliminating ambiguity in payment instructions.

Treasury teams gain real-time visibility into payment status and expected settlement times, replacing the opacity of correspondent banking chains.

The Infrastructure Gap

Many banks have updated their SWIFT connectivity to support ISO 20022 messaging. But the underlying settlement infrastructure hasn't changed. Payments still traverse 3-5 correspondent banks, each adding latency and cost. The message format is modern; the rails are not.

This creates an opportunity. Banks that combine ISO 20022 messaging with modern settlement infrastructure — distributed ledger technology, real-time gross settlement, direct corridor connectivity — can deliver the full promise of the new standard: faster, cheaper, more transparent cross-border payments.

What We're Seeing

The institutions moving fastest are those that treat ISO 20022 not as a compliance checkbox, but as an infrastructure upgrade opportunity. They're using the migration as a catalyst to:

  • Deploy real-time settlement alongside existing core banking systems
  • Automate compliance screening using structured data fields
  • Reduce correspondent banking dependencies with direct settlement corridors
  • Offer clients end-to-end transaction visibility

Looking Ahead

ISO 20022 is the messaging standard. The settlement infrastructure beneath it determines whether banks can deliver on the standard's promise. The gap between modern messaging and legacy rails is where the next generation of payment infrastructure lives.


Bridge Intelligence builds ISO 20022-native settlement infrastructure for banks and financial institutions. Learn more about our settlement capabilities.