in
← Back to newsroom
In Focus

When 98% adoption is not enough

Swift’s decision to delay its next payment-message changes despite near-universal ISO 20022 adoption exposes a recurring constraint on financial-market infrastructure: a system is not ready when its technology is ready, but when the critical chain around it is ready too.

More than 98 per cent of payment instructions carried by Swift now use ISO 20022. That should look like mission accomplished.

It is not.

Swift has postponed the payment changes planned for November after banks and domestic payment infrastructures asked for more time to prepare for structured address data. The Bank of England followed by delaying its own November Real-Time Gross Settlement standards release. The Eurosystem is reassessing the corresponding TARGET Services changes.

The problem is not ISO 20022 itself. It is what happens around it.

A messaging network can provide the standard. It cannot ensure that a corporate customer entered the right data, that a bank captured it properly, that screening systems recognise it, that domestic infrastructures process it cleanly or that counterparties can do so without manual intervention.

That is what the 98 per cent figure misses.

Financial-market infrastructure is increasingly constrained not by the capability of the central platform, but by the readiness of the chain connected to it.

The same pattern appeared in the move to T+1 settlement in North America. The Depository Trust & Clearing Corporation could shorten its processing window, but the market still needed years of preparation, repeated testing and coordinated changes across brokers, custodians, asset managers and infrastructures before the switch could work.

Extended-hours trading in US options offers another example. NYSE American may have its exchange framework approved, but launch still depends on the Options Clearing Corporation being ready to clear those trades.

Trading, clearing, settlement, messaging: different businesses, same problem.

For infrastructure operators, this changes the meaning of execution capability. The competitive advantage is no longer simply building the new system first. It is being able to move a market with it.

That requires something less glamorous than technology but arguably more valuable: knowing which dependencies matter, forcing the right testing, identifying where participants are genuinely unready and separating those problems from ordinary resistance to change.

There is a danger here. “The market is not ready” can become a convenient argument for delay. Large participants can be slow, legacy systems can linger and the least-prepared institution should not acquire a permanent veto over modernisation.

The answer is not endless postponement. It is better evidence of readiness.

Adoption percentages are useful, but they are not enough. Infrastructure operators need to know whether data arrives correctly, whether exceptions are falling, whether counterparties can process the new standard without workarounds and whether the whole chain has been tested under realistic conditions.

That is a much harder measure than saying 98 per cent.

It is also a more useful one.

The next infrastructure advantage will not belong simply to the operator that can change fastest, but to the one that can make a complex market move together without allowing its weakest critical dependency to become either a source of systemic risk or a permanent brake on progress.

Sources — Swift; Bank of England; European Central Bank; Depository Trust & Clearing Corporation; United States Securities and Exchange Commission; NYSE American; Options Clearing Corporation.