Swift defers SR2026 and the end of unstructured addresses
Expected
Affects you
Swift postponed all payment changes of its 2026 standards release, including the November 2026 end of unstructured postal addresses in cross-border ISO 20022 payment messages (CBPR+, Cross-Border Payments and Reporting Plus). It plans a new address date by December 2026, so that date is expected. The rest of the release, for non-payment messages, goes live on 12 June 2027.
What it is
Swift (network) is the messaging network that banks use to send payment instructions across borders. Its cross-border payment messages follow ISO 20022, a data-rich message standard, under the usage rules called CBPR+ (Cross-Border Payments and Reporting Plus) (Swift news (external site)).
Each message carries the postal addresses of the payer and the payee. Swift planned to stop accepting unstructured addresses, written as free lines of text, from 14 November 2026, and has now postponed that step (Swift news (external site)).
What changes
A structured postal address puts each part in its own field: street, building number, postcode, town and country. A fully structured address needs at least a country and a town name (Swift on the removal of unstructured addresses (external site)).
As an illustrative example only: the free line "10 Market Street, Lyon, France" becomes separate fields for street name, building number, town and country. A hybrid address keeps town and country in fields and allows up to two free lines for the rest (hybrid postal address guidance (external site)).
Swift will defer all payments changes of its Standards Release 2026 (SR2026) and will give an update on the structured address timing by December 2026 at the latest (Swift news (external site)). Until then, unstructured addresses stay accepted.
The non-payment part of SR2026 goes ahead on 12 June 2027. It covers MT messages except Category 1, ISO 20022 securities and funds messages, tracker messages, and exceptions and investigations messages (Swift news (external site)).
Who it affects
The change concerns banks, payment institutions and market infrastructures that send or receive cross-border payment messages over Swift (Swift news (external site)).
- Payments Messaging Specialist (SWIFT): replans the address changes and the testing of the deferred release.
- Payments Operations Analyst: repairs or returns payments whose address data fails the new rules.
- Sanctions Analyst: screens names against towns and countries held in separate fields.
- Data Governance Analyst: sets quality rules for client address data at its source.
- Corporate Onboarding Analyst (KYC): captures client addresses in structured form at onboarding.
- Trade Finance Operations Specialist: plans for the trade message changes in the June 2027 release.
Timeline
- Standards Release 2025: the hybrid address option was introduced, with a one-year transition (Swift CBPR+ roadmap (external site)).
- 14 November 2026: original end of unstructured addresses, now postponed (Swift milestone news (external site)).
- By December 2026: Swift update on the new address date (expected).
- 12 June 2027: deferred SR2026 for non-payment messages (confirmed).
The Eurosystem shifted its own November 2026 releases to 28 November 2026 and allowed unstructured addresses in T2 for a limited period (ECB (external site)).
Background
Swift links structured address data to Recommendation 16 of the Financial Action Task Force, which sets the payer and payee information that travels with a transfer (Swift questions and answers on the removal (external site)).
Structured fields let banks along the payment chain read the town and country of each party automatically. Swift accepted a request from its community for more time before making them mandatory (Swift news (external site)).
Dates
- Swift update on the structured address timeline (by December)Expected
- Deferred Standards Release 2026 goes liveConfirmed
Who must comply
Cities where it applies
Processes
Roles affected
28 roles are directly affected: they run one of these processes.
- Agency Operations Analyst
- Cash Management Product Manager
- Chargeback & Disputes Analyst
- Corporate Banking Analyst
- Corporate Onboarding Analyst (KYC)
- Data Analyst
- Data Governance Analyst
- Data Protection Specialist
and 20 more
- Finance Transformation Consultant
- IBOR & Investment Data Analyst
- KYC Analyst
- Loan Operations Analyst
- Master Data Specialist
- Merchant Acquiring Sales Executive
- Payments & Cash Management Sales (Financial Institutions)
- Payments Messaging Specialist (SWIFT)
- Payments Operations Analyst
- Payments Partnerships Manager (Acquiring & Gateways)
- Periodic Review Analyst (KYC)
- Privacy Specialist (Technology)
- Reference & Security Master Data Analyst
- Relationship Manager (Corporate & Business Banking)
- Sanctions Analyst
- Trade Finance Analyst
- Trade Finance Operations Specialist
- Transaction Banking Analyst
- Transaction Banking Sales (Cash Management)
- Treasury Operations Analyst
Also relevant: 18 roles
- AML Analyst
- BI Analyst (Banking)
- Business Intelligence Analyst
- Company Secretary (Listed Companies)
- Company Secretary / Corporate Secretarial Associate
- Compliance Officer
- Conduct Risk Analyst
- Corporate Actions Analyst
- Corporate Treasury Analyst
- Custody Operations Analyst
- Cyber Risk Consultant (Banking)
- Cybersecurity GRC Consultant
- Fraud Analyst
- Legal Counsel
- Regulatory Change Analyst
- Retail Banking Advisor
- Settlements Analyst
- Treasury Analyst
What to prepare
- Keep cleaning client address data into town, country and the other structured fields.
- Replan testing of payment messages around the deferred release of 12 June 2027 and the address date due by December 2026.
General information, not advice