Swift has confirmed that the move from unstructured to structured postal addresses for ISO 20022 payment messages will not go ahead on 14 November as originally planned. The community agreed the change back in 2023 as part of Standards Release 2026, and Swift has supported the transition since through sustained community engagement and readiness monitoring, but as the November cutover approached the picture across the network did not match the plan.
Why the extension happened
Swift’s own explanation is the part worth reading carefully. Progress across the industry remains uneven, with large parts of the market across all regions still unable to meet the requirement, and several communities formally asked Swift and their domestic payment market infrastructures, who are working to similar deadlines, for more time to comply. In consultation with those market infrastructures, Swift agreed to extend the timeline.
That is a notable statement about readiness across the network, and it comes despite more than 98% of payment instructions now being sent in the ISO 20022 format following last year’s transition from the MT standard. Format migration, in other words, is largely done. The data underneath it is not, and address remediation has turned out to be the harder half of the job for a substantial part of the industry, which is unsurprising given how much has landed on payments operations and IT teams over the same period.
What Swift has actually announced
Swift is applying a controlled extension of Standards Release 2026, which in practice splits the release rather than simply postponing it.
All payments changes are being deferred. On the structured address requirement specifically, Swift will consult over the coming weeks with banks, central banks and payment market infrastructures, alongside market practice groups and corporates, in order to define the optimal timing and approach, and it will provide an update by December at the latest as part of its governance cycle. Other payments changes originally planned for November are being phased separately.
The remaining content of Standards Release 2026 is being decoupled so that it can move faster. That covers changes supporting other business and regulatory priorities beyond payments, including the move to T+1 settlement in some markets, and those are now expected to go live in Q1 2027, with an exact date confirmed by mid September following consultation with the relevant stakeholders. Swift has also confirmed that further updates will be shared at Sibos.
An extension, not a reprieve
It would be easy to read this as breathing space, and Swift has been notably direct in discouraging that reading. Institutions that have already completed the work can benefit now, because structured addresses flow seamlessly across the Swift network today, and Swift is strongly encouraging both financial institutions and domestic payment market infrastructures to continue pressing ahead on the basis that domestic adoption of structured addresses is a critical enabler of cross-border progress.
There is a practical argument here that has nothing to do with compliance dates. Address data quality is a source problem rather than a messaging problem, and the difficulty whenever the deadline eventually lands will sit with institutions where unstructured data continues to enter the payment chain upstream, in onboarding, in client master data and in corporate payment files. None of that becomes easier by waiting, and every month of deferral compresses the same remediation work into a shorter window later on. The one certainty in the announcement is that no new date has been set, so any programme that pauses now will be restarting against a timeline it has no visibility of.
The harder question worth asking
It is also worth asking a harder question about your own estate. If a shift in a Swift timeline means reopening a project, waiting on a core vendor roadmap and rerunning a full regression cycle, then the deadline was never really the problem. Banks whose messaging platforms absorb standards changes as configuration rather than as development are far less exposed to a moving target, and this will not be the last time a date moves.
That distinction is rarely a reflection of the teams involved. Payments operations and IT teams have been carrying CBPR+, Case Management preparation, market infrastructure upgrades and business as usual simultaneously, often while depending on a core vendor whose release cadence and priorities they do not control. Where message processing sits inside the core banking application, every standards release becomes a core release with its own scoped project, vendor dependency and regression cycle across functionality that has nothing to do with payments, and no amount of effort from the team closes a gap that was structural from the start.
What we would suggest doing next
The sensible response is to carry on as though the work still needs finishing, because it does. That means continuing the upstream data work in onboarding and client records rather than treating this as a messaging layer exercise, keeping your testing and development plans intact so that readiness becomes a matter of confirming a date rather than restarting a project, and watching for the two updates Swift has committed to, the Q1 2027 date in mid September and the structured address timing by December.
Talk to us
Our team will be at Sibos Miami from 28 September to 1 October on stand DISM38 in the Discover zone, where Swift has said further updates on the revised timeline will be shared. If you would like to talk through what the extension means for your ISO 20022 programme, your securities timeline or your reconciliation processes, contact the Aqua team or come and find us there.
The full Swift statement is available here: https://www.swift.com/swift-accepts-community-request-extend-structured-address-migration-iso-20022-payment-messages
