Swift Moved the Structured Address Deadline. The Real Problem Is Data
Swift has given banks more time to stop sending addresses as free text. The bigger job is fixing the customer data behind them.
If you work in cross-border payments, 14 November 2026 has been on your calendar for two years. From that date, cross-border payment messages on Swift were meant to stop carrying addresses as loose lines of free text, the way banks have written them for decades. Only structured or “hybrid” addresses, with at least the town and country in their own fields, would get through.
That date has now moved. On 27 August 2026, Swift agreed to a request from its users for more time. It will ask banks, central banks, market infrastructures, market practice groups and companies how and when to make the change, and says it will give an update by December at the latest. Some other changes planned for this year have moved to 12 June 2027.
The reason is that many banks aren’t ready. Swift’s own figures from April 2026 showed that about six in ten payments still gave the payer’s address as free text. Plenty of banks had switched to the new ISO 20022 messages but were still filling them with old data.
That’s the real issue. A structured address is only as good as the customer record it comes from.
In many core banking systems, addresses were typed in decades ago as two or three lines of free text. Sometimes the town is missing, the country is shortened, or the postcode is in the wrong place. Splitting those lines into street, building number, postcode, town and country is a data clean-up job, and a big one.
This matters for more than tidy formatting. Clear addresses help sanctions checks tell apart people and firms with similar names, so fewer good payments get stopped by mistake. They support FATF Recommendation 16 on payment transparency, and let more payments go through without manual work. Every cut-off or misread address can mean a manual fix, a late payment or a compliance question.
With the extra time, I’d treat this as a data project. Check your customer address data and see how much of it a system can split up automatically. Fix it at the source, when customers sign up and in the core system, instead of patching it in the payment hub. Agree rules for hybrid addresses and the odd cases, and test from end to end with your partner banks.
Swift has moved the deadline, but the data still needs fixing. Banks that use the extra time to clean up will be ready whenever Swift sets the new date.
Photo: Dead Letter Office, Bain News Service / Library of Congress (public domain).
This article first appeared in Payment Samachar, Edition 3 (November 2026).
