No Swift deadline. Same problems.
Yesterday, 27 August 2026, Swift announced that it will defer the payments changes planned for Standards Release 2026, including the structured postal address requirement. A new timeline will be defined over the coming months.
Announcement: Swift accepts community request to extend structured address migration
The decision reflects a familiar reality in payments and banking: industry-wide change takes time, especially for standardization groundwork, and readiness remains uneven across institutions and infrastructures.
But the purpose of ISO 20022 and its improvements was never to meet a Standards Release.
It was to reduce friction.
Inject intelligence into the data → That’s strategic.
Extract intelligence from the data → That’s tactical.
Business problems
- Poor address quality still creates friction in sanctions screening and payment processing.
- Payment investigations still depend on fragmented, incomplete and inconsistent data.
So the absence of a November deadline can actually be useful: less energy spent racing toward a date, more time to improve the underlying data and processes, reap the benefits now, and be ready for future Standards Releases almost as a by-product.
Where we are focusing
🔍 At Alpina Analytics we’re focusing on two contributions.
- TxFlow structures and enriches payment addresses, with potential gains in sanctions screening and operational data quality today.
- TxAgent uses AI to investigate payments across messy and evolving data, while helping raise the quality of the evidence and resolution process.
No deadline does not mean no friction.
It means we can focus on the friction itself.