On 27 August 2026, Swift announced that the November 2026 Standards Release would not go ahead as planned. Much of the early coverage framed this as an extension of the structured address deadline. That description understates what happened, and what it means for banks mid-migration.
Here is what actually changed, and what it should change in your roadmap.
What Swift announced
Three things happened at once:
The entire payments scope of SR 2026 has been deferred. A standards release is built, tested and deployed as a single package, so Swift did not pull the address rule alone; all payments changes moved with it. SR 2025 remains the active rulebook until a replacement release goes live.
Non-payments items were decoupled and will go live in Q1 2027. These include changes supporting the move to T+1 settlement in some markets. Swift is expected to confirm the exact date in September 2026.
CBPR+ changes, including the removal of unstructured postal addresses, were lifted out of the release entirely. They will not be part of the Q1 2027 package. Swift is expected to announce a new timeline in December 2026. Until then, the structured address mandate has no date.
The ripple effects are already visible. The Bank of England deferred its November 2026 RTGS standards release in its entirety, including CHAPS messaging standards, to preserve alignment with Swift and avoid the risk of separating changes late in the cycle. Other market infrastructures are making the same calculation.
Why it happened
The delay followed an industry request, and the readiness data explains it: as of April 2026, roughly 61% of cross-border payments were still carrying unstructured addresses. With the deadline seven months out, a majority of payment flows would have failed the new validation. The mandate did not become less important. The industry simply was not ready.
That distinction matters. Swift has been consistent that structured data is the destination for ISO 20022; richer, machine-readable address data is what enables precise sanctions screening, higher straight-through processing and lower manual repair volumes. The delay is a statement about timing, not direction.
What it means for your roadmap
If you were ready for SR 2026, you now have a rollback problem. Institutions that tightened validations to reject unstructured addresses must be able to accept them again. Under SR 2025, all three formats – unstructured, hybrid and structured, remain valid. If tightened inbound validations go live prematurely, compliant payments from correspondents get rejected, stopping payments for manual intervention. Audit what is deployed versus what is active, and confirm SR 2025 support can be maintained for longer than planned.
If you were behind, the reprieve is smaller than it looks. The address mandate lost its date, not its certainty. And address data problems compound: every new account opened with free-text addresses, every corporate payment file ingested without validation, adds to the remediation backlog. When the new date lands in December, the scope will be larger and the runway shorter – and every affected institution will be competing for the same implementation capacity at once.
Either way, the budget conversation changes. Programmes justified against a November 2026 deadline now need a business case anchored in the underlying drivers: data quality, screening precision, straight-through processing and operational cost. Those drivers did not move. Funding decisions made in the next budget cycle should rest on them, not on a date that no longer exists.
The work the delay did not change
Structured address data cannot be patched in at the point of sending. It depends on how data is captured at account opening, in corporate payment files, and across online channels and branches often in systems that have stored free-text addresses for decades. Fixing it means:
- Assessing where addresses actually enter. Most banks find more origination points than they expected.
- Prioritising by exposure. High-volume corridors and correspondent-facing flows first, so effort maps to payment risk.
- Fixing capture, not just records. Cleansing legacy data without validating new entries simply refills the backlog.
- Retiring the workarounds. Once structured data flows from the source, translation layers and manual repair queues stop being load-bearing.
Banks that use this window to do that work properly will read December’s announcement as a date on work already underway. Banks that treat the delay as breathing room will be back where they were in August: preparing for a hard deadline, under time pressure, with a bigger backlog.
The deadline moved. The work didn’t.
Author Bio
Author Bio
Altimetrik helps
banks and their corporate clients become ISO-native through
engineering-led remediation and its
ISO 20022 Migration Accelerator, which converts legacy payment formats into
bank-accepted, CBPR+-validated ISO 20022 messages without replacing existing systems.
Explore the Accelerator →
