Banks that successfully navigated the end of Swift’s coexistence period in November 2025 can’t relax just yet. By November 2026, the use of fully unstructured postal addresses in payment messages will come to an end.
To manage evolving ISO 20022 requirements, many institutions have turned to translation tools to bridge the gap between legacy systems and new messaging standards. Our recent research shows 65% of banks are still relying on these tools as part of their compliance approach.
However, translation tools were never designed to deliver the level of data quality and structural precision that November’s rules demand. With the deadline only six months away and Swift offering no fallback for institutions that miss the mark, the cost of inaction is rising by the day.
The bigger picture
The move to structured addresses is not an isolated change. It reflects a wider industry shift towards higher-quality, standardised payment data, aligned with initiatives such as the G20 Cross-Border Payments Roadmap and FATF Recommendation 16.
For years, free-text address fields have introduced friction across payments processing. Variations in formatting, missing fields and inconsistent inputs make it harder to process transactions efficiently and to perform accurate sanctions, AML and fraud screening.
Structured data removes that variability. By enforcing defined fields for core address components, Swift is building a more consistent foundation for payments processing, supporting:
- Greater straight-through processing, reducing manual intervention across the payments chain
- More accurate compliance screening, improving sanctions and AML detection
- Enhanced transparency, giving all parties clearer visibility of payment data
- Increased automation, removing a key constraint on operational efficiency
The gap between readiness and reality
Despite the benefits, moving to structured addresses presents a significant challenge for banks.
To reconcile legacy systems with ISO 20022 requirements, many banks have turned to translation tools as a workable short-term solution. However, these tools won’t be enough for the next phase of the transition.
Translation tools convert data from one format to another, but they do not improve the underlying data itself. If address data is stored in legacy systems as free text with missing or inconsistent information, that structure remains unchanged when it is carried into ISO 20022 messages.
Until now, banks could absorb the consequences. Payments with flawed address data could be caught and corrected through repair and exception handling further down the line. But under the new rules, payments with unstructured addresses will face rejection at validation stage, removing the ability to fix issues later in the process.
The cost of inaction
For banks that fail to act before the deadline, the consequences will be felt fast. Failed payments, growing exception queues and regulatory penalties will follow – at a moment when most operations teams can least afford it.
Meanwhile, any corporate relying on their banking partner to access and process Swift payments faces the same exposure. If a bank’s payment messages fail validation, its customers’ transactions fail too – making this a conversation banks need to be having with their corporate clients now, not in October.
Modernising the payment data layer
Meeting Swift’s requirement is not about just patching over existing issues. It demands a more fundamental shift, moving address data out of free-text legacy systems and ensuring it is validated and structured before it ever reaches Swift messaging.
This is where Aquila, Aqua Global’s payments orchestration hub, can help. Instead of simply passing data through unchanged, Aquila sits in the payment flow and applies validation, enrichment and standardisation rules before messages are created.
Through Aquila, banks can:
- Validate and enrich before submission: Address data is checked and improved before reaching Swift, reducing the risk of failures linked to unstructured inputs
- Structure data earlier in the flow: Address information is standardised before messaging, rather than relying on post-processing or translation tools
- Identify issues in real time: Incomplete or inconsistent data is identified at the point of processing, enabling earlier correction
- Integrate without replacing core systems: Connects to existing banking and compliance infrastructure via API, allowing banks to improve control over payment data without major system change
The window is closing
The move away from unstructured addresses marks the final step away from legacy free-text formats and towards fully structured, ISO 20022-aligned data. But with many banks still reliant on translation tools, readiness remains uneven.
Those that act soon will avoid disruption and build stronger, more resilient payment operations. Those that don’t risk entering November 2026 with processes that simply won’t hold up. To learn more about how those in the industry are tackling ISO 20022 migration, with insights form a survey of 150 UK and European banking leaders, read our industry report: From Compliance Burden to Competitive Advantage.
