ISO 20022 and the Intraday Liquidity Gap: Is Your Treasury Ready?

The Payments Migration Most Treasuries Are Not Ready For

The global payments industry is in the middle of a structural shift. ISO 20022 — the new international messaging standard for financial transactions — is being adopted by SWIFT, central banks, and major payment schemes worldwide. By the time full migration completes, virtually every significant payment flow will carry richer, more structured data than the legacy MT message formats it replaces.

For most corporate treasury teams, the practical implications are still underestimated. This is not simply an IT infrastructure change. It is a fundamental shift in how treasury can — and should — see cash moving in real time.

What ISO 20022 Actually Changes

Legacy SWIFT MT messages carry limited, unstructured data. A payment arrives with a reference number, an amount, and perhaps a remittance field that has been manually truncated to fit the format. Matching that payment to an invoice, a receivable, or a treasury position requires manual reconciliation — or costly middleware to parse and interpret what the message actually means.

ISO 20022 MX messages change this. They carry structured, machine-readable data: full remittance information, counterparty details, purpose codes, and LEI identifiers. A payment arriving in ISO 20022 format can, in principle, be automatically matched, reconciled, and posted to the correct position — without human intervention.

For treasury teams, this means intraday cash visibility can become genuinely real-time rather than an estimate based on yesterday's closing position. Intraday liquidity management — currently a manual, estimate-driven process for most corporate treasuries — becomes data-driven.

The TMS Gap

The challenge is that most treasury management systems — even those deployed within the last five years — were built around the assumption that payment data arrives in MT format. They process payments in batches, reconcile at end of day, and generate cash positions that are, by definition, retrospective.

As banks and payment platforms migrate to ISO 20022, the enriched data those systems generate cannot be properly consumed by a TMS that was not designed for it. The result is a growing gap: payment flows carry more information than ever before, but treasury systems cannot use it. Reconciliation remains manual. Intraday positions remain estimates.

What Treasuries Should Be Doing Now

The organisations that will benefit most from ISO 20022 are those that use the migration as a trigger to modernise their treasury infrastructure — not those that treat it as a connectivity upgrade to be managed by IT alone.

Practically, this means: assessing whether your current TMS can ingest and process ISO 20022 data natively; understanding which of your banking partners have already migrated and what data they are now sending; and designing a roadmap that takes advantage of enriched payment data to improve reconciliation, forecasting, and intraday liquidity management.

How RG Treasury Can Help

RG Treasury provides senior interim treasury and payments specialists who have worked through ISO 20022 migrations and TMS modernisation programmes at global financial institutions. If your organisation is assessing its readiness — or is mid-migration and needs specialist support — contact us at Sales@rgtreasury.com to discuss your programme.