For most North American institutions ISO 20022 arrived as a deadline. Fedwire completed its move on 14 July 2025. Payments Canada’s Lynx was on the standard earlier. Swift’s structured-address milestone in November 2026 will be the next reason to reopen the ticket. Each was managed as a compliance programme, which is reasonable, and each was closed when the messages validated.

What is left on the table is the data. An ISO 20022 message carries a structured payer and payee, a purpose code, remittance information a machine can reconcile, and enough context about the parties that an exception can be resolved without a phone call. In the old formats most of that was truncated, free-text, or simply absent.

Three functions benefit at once, and none of them belongs to the payments operations team that ran the migration.

Fraud. A structured beneficiary and a purpose code are two of the strongest signals a scoring model can have. A first-time payee with a mismatched name and a purpose that does not fit the customer’s history used to be invisible. It is now in the message. The question is whether the fraud platform is receiving it.

Exceptions and investigations. Repairs, recalls and enquiries are still handled by people reading screens. Rich data lets the case be pre-populated and, increasingly, closed without a human touch. The saving is in people who can be redeployed, not in licence fees.

Reconciliation and treasury. For corporate clients, remittance data that arrives structured and complete is the difference between straight-through posting and a spreadsheet. Banks that can deliver it have something to sell.

The reason most institutions have not captured this return is architectural rather than strategic. The migration was done at the edge. A translator sits in front of a core or a legacy payments engine that still thinks in the old format, and the rich data is stripped off before any downstream system sees it. The compliance box is ticked and the value is discarded in the same step.

The fix does not require replacing the core. It requires a connector layer that carries the full ISO 20022 message through the institution, exposes it to the systems that can use it, and applies routing and policy across whichever rail the payment takes. We describe that layer in three steps: connect, orchestrate, then control and optimize. It sits alongside what the institution already runs. Our connectors for FedNow and RTP are built and certification is in progress; the same architecture is what carried India’s UPI to national scale.

A CFO does not need to understand ISO 20022 to ask the right question, which is what the migration returned. If the honest answer is “compliance”, the second question is what it would take to get the data to the fraud team, the investigators and the treasury clients. In our experience that is a quarter’s work, not another migration.

About RS Software
As the payments ecosystem transitions toward an AI-driven, real-time, and increasingly autonomous model, where TRUST is the new currency, RS Software (India) Limited's product portfolio modernizes the most critical areas across the value chain, leveraging decades of work building mission-critical payment infrastructure globally. Each product is purpose-built to address specific structural shifts in the market while collectively enabling a unified, AI-led financial ecosystem. RS IntelliEdge™ is designed to address evolving transaction-level controls and shift to continuous, identity-centric intelligence systems, protecting approximately 95% of India’s digital payment transactions and screening billions of transactions each month. RS DigitalEdge™ is designed to enable real-time routing, optimization, and decisioning across payment flows. Payabbhi® is designed to enhance the acceptance and acquiring layer, transforming it into a data-driven revenue engine. www.rssoftware.com