Swift delays ISO 20022 structured address deadline

So the rumours were true. Swift has extended the ISO 20022 structured address deadline and deferred the entire Standards Release (SR 2026). 

A partial SR 2026 package is expected in Q1 2027 for non-payment items. Swift is expected to confirm the exact date in mid-September 2026. In the meantime, SR 2025 will remain in effect until its replacement is live.  

The delay follows a request from large community banks and domestic payments market infrastructures in August, with readiness data from April showing around 61% of payments were still carrying unstructured addresses.  

It also echoes our own research in February this year. We found that nearly half (44%) of global banks weren’t on track to meet the ISO 20022 structured address deadline. On top of that, a fifth (20%) of the largest banks (with assets of $250bn or greater) described the November deadline as unrealistic. 

Swift’s announcement backs up our findings, which underlined the scale of the challenge banks were facing to be ready for the deadline.  

So, what does this mean for banks preparing for SR 2026? 

6 things you need to know

1. Structured addresses are still supported

The first thing to say about this news is that it shouldn’t hold up the work you’re already doing. The timeline has been relaxed, but that doesn’t mean banks should. 

While anything tied to SR 2026’s development or deployment is on hold, SR 2025 still supports structured and hybrid addresses. Any work you’ve done on address migration is still deployable today with SR 2025 baseline; you don’t need to wait for the future release.

2. The MT 101 pressure is off

Unstructured addresses will continue in MT 101, and the ‘request-for-transfer’ message remains supported in FI-to-FI (financial institution) single and multiple instructions. This also means that the MT101 and pain.001 coexistence period gets an extension beyond November. 

Additionally, the 3 October 2026 RMA bootstrap will be cancelled. Swift may introduce a new one in early 2027 based on the Payment Initiation Rulebook adherence.  

3. Inbound validations should be relaxed

Banks who were ready for SR 2026, with tightened validations that would reject unstructured addresses need to be ready to accept them again. With SR 2025 still in place addresses in all three formats (unstructured, hybrid and structured) are valid. 

If the tightened inbound validations go live, then unstructured addresses arriving from other participants or correspondent banks get rejected. This means payments stop for processing and someone will have to manually intervene to fix them.

4. Cross-border payments change requests are postponed

MT Category 1, CBPR+, SCORE+ and SwiftGo have been lifted out of the release entirely. This includes the removal of unstructured postal addresses.  

They won’t be part of the partial release in Q1 2027 and an announcement on a timeline for this is expected in December 2026.

5. SR 2027 will still go ahead

Despite these delays, the scheduled 2027 Standards Release isn’t affected by today’s news. Swift is reviewing its content though, which makes sense given that a slot still needs to be found for elements pulled from SR 2026. 

6. Fedwire Funds Service release has been postponed

As a result of Swift’s annoucement, the Federal Reserve Financial Services (FRFS) has annouced it will reschedule its release from November 2026 to November 2027.

Further details of the scope of the release will be shared later in the year.

What you need to do

There are still lots of unanswered questions. Swift hasn’t confirmed the new structured address timeline, contents of SR 2027 or the exact date in Q1 2027 for the partial release of today’s deferred package. 

We would advise that you shouldn’t expect any further delays. It’s not just structured address migration impacted by this because other market infrastructures are aligning to Swift and CBPR+ guidelines. So a firm date matters to the wider ecosystem, and if address changes slip to November 2027 that adds a lot more elements to an already heavy release.  

Your immediate tasks

• Put SR 2026 development and deployment on hold: You also shouldn’t activate SR 2026 for processing either. There’s no issue installing the packages under Swift or vendor’s guidance, but nothing can be activated while SR 2025 active.
• Audit what’s deployed and what’s active: Focus vendor’s and partner’s systems as well as your own, because we’re still waiting on rollback guidelines.
• Confirm SR 2025 can be maintained: If you had planned to retire SR 2025 support that plan has to change because any new go-live must comply with last year’s release.
• Build a PMI matrix: Create one row per scheme, listing direct and indirect participants, what the scheme has actually published and who owns confirmation. This should cover the EPC and SEPA positions, CHAPS, T2, Fedwire, CHIPS, SIC and any regional infrastructure you clear through.   

Don’t stand anything down 

Migration doesn’t depend on the new release because structured and hybrid addresses are accepted on SR 2025, so you don’t need a deadline deploy them. It’s also important to keep cleaning customer data, it’s the longest job and won’t be easy to fix in a rush no matter when the new release date is.  

We’d also advise continuing with client outreach, because once an engagement program stops, it can take six to nine months to restart. Keep the same momentum with pushing corporates towards pain.001. With the postponement announced, you may need to use a commercial or relationship-focused motive to ensure the work doesn’t slip.  

Protect the work you’ve already done

If your systems are set up to reject unstructured addresses, then loosen them but don’t delete the rules. Just change what happens when one arrives. This way you get a data point each time a message arrives in the old format.  

Re-baseline your regression testing to SR 2025, because that’s the rules you’ll be working under for the foreseeable future. Any release you put live will have to comply with them.

Get answers from your vendors

Four questions worth asking today: 

1. Can we install without activating, and does that leave SR 2025 behaviour untouched? Have you tested that?
2. What is your rollback guidance?
3. Can you support us on SR 2025 all the way through to the deferred release, and beyond?
4. How will you handle two releases inside 12 months?

Speak to your corporate clients  

Give them your own deadline rather than wait for Swift to provide one. Also reassure clients that the work they’ve already done isn’t wasted. Structured and hybrid addresses are still accepted so nothing is lost and SR 2026 hasn’t gone away, it’s just delayed.

Where RedCompass Labs can help

The request to postpone SR 2026 is a reflection of the volume of work involved. There were too many addresses to convert, too many defects to clear and not enough capacity to carry out work. 

If you’re still running late, our Payments Expert Agent can help. Our AI solution puts over two decades of payments modernization expertise inside your project. It can help support your migration in a fraction of the time and cost.  

Get in touch if you’d like to know more.