← All Insights
Payments

ISO 20022: What Banks Must Do Before the Deadline

3 min read · April 2025 · RegalWeise Consulting

ISO 20022 is the most significant change to global payment messaging in a generation. The deadline for full adoption across SWIFT's cross-border network has passed for many corridors — yet a significant number of banks remain in partial compliance, running parallel message formats and hoping the consequences stay manageable. They won't.

Here's what's actually at stake, what banks still need to do, and why the urgency is greater than most leadership teams appreciate.

What ISO 20022 Actually Changes

ISO 20022 replaces the legacy MT message standard that has dominated global payment messaging since the 1970s. The difference is not merely cosmetic. MT messages are narrow, text-based, and carry limited structured data. ISO 20022 messages — delivered in MX format — carry rich, structured, XML-based data that is far more granular, standardised, and machine-readable.

"The banks that treat ISO 20022 purely as a compliance exercise will get compliance. The banks that treat it as a data transformation opportunity will get competitive advantage."

The Truncation Trap

The most common failure mode we see is the truncation trap. A bank has technically migrated to ISO 20022 messaging — their SWIFT gateway sends and receives MX format — but internal systems still run on MT-era data models. The rich data arriving in inbound MX messages gets truncated at ingestion, stripped back to the fields legacy systems can handle.

The result: the bank appears compliant at the network level but captures none of the business value, and exposes itself to growing compliance risk as regulators begin expecting richer data to flow through to reporting systems.

What Banks Must Still Do

1. Internal Systems Uplift

Payment hubs, core banking platforms, reconciliation systems, and sanctions screening engines all need to ingest, process, and store ISO 20022 data in its full form. This is not a messaging project — it is a data architecture project.

2. Sanctions & AML Engine Reconfiguration

Existing AML and sanctions screening rules were written for MT-era data structures. ISO 20022's richer fields change the screening surface area significantly. New fields need mapping to screening logic; existing rules need validation; false positive rates need recalibration.

3. Regulatory Reporting Alignment

Several regulators — including the RBI, MAS, and ECB — are beginning to expect ISO 20022-structured data in regulatory submissions. Banks need to map their new payment data models to reporting templates before the expectation becomes a mandate.

4. Correspondent Banking Readiness

Even a fully migrated bank is only as capable as its correspondent network. Bilateral testing with correspondent partners needs to be completed and documented — including failure scenario testing for truncated or malformed messages.

The Opportunity Inside the Obligation

Banks that complete the full ISO 20022 transformation unlock real commercial capability. Rich remittance data enables straight-through processing rates of 95%+. Structured beneficiary data dramatically reduces payment investigations. Purpose-of-payment codes enable more intelligent transaction monitoring with lower false positive rates.

Our View

The deadline has not eliminated the urgency — it has changed its nature. The question is no longer whether to comply. It's whether your compliance is surface-level or substantive. Banks that invest in the full data transformation now will find themselves with a structural advantage in payment processing quality, cost, and regulatory standing.

RegalWeise Consulting

Need Help Putting This Into Practice?

Our consulting practice supports banks and financial institutions on architecture, payments, risk, digital assets and agentic AI.

Explore Consulting