The Fedwire deadline for the migration away from unstructured addresses has been pushed back to November 2027 – and is expected to align with similar deadlines for CHIPS and Swift CBPR+. This buys banks valuable time to get their ducks in a row, ensuring they have the tools to enable them and their corporate clients to action the changes effectively and efficiently. Because, say XMLdation’s Tricia Balfe, CEO, and Martin Reynolds, Business Lead North America, the scale of what’s required cannot be underestimated.
“Performing checks across the scope of a bank’s clients will be extremely challenging, time and resource consuming, and potentially unmanageable. Without the right tools.
The transition centers on updating the payee postal address information within corporates’ payment initiation files; essentially moving from a free-flowing format to specified fields. While the concept may not sound too daunting, in practice, distinguishing between building names and numbers, streets, cities and postcodes – the style and structure of which varies from country-to-country – is far from straightforward. It is therefore not simply a case of mapping data across. Every corporate will need to sift through every address and potentially obtain additional details or clarifications – especially for town name and country – in order to ensure all information in the payment initiation file is present, correct and in the correct fields.
For banks, similarly to when a new client is being onboarded, it will be their job to guide and support clients as they learn how to populate the address fields correctly – a process that for many involves reviewing test files from the client manually, line by line.
But the move to structured addresses doesn’t involve one client. It is a mass migration. Onboarding on steroids, so to speak. Performing these checks across the scope of a bank’s clients will therefore be extremely challenging, time and resource consuming, and potentially unmanageable. Without the right tools.
Now, with the Fedwire extension in place, banks have the opportunity to streamline the migration, leveraging a self-service approach, combined with automation and AI for payment initiation file validation. With XMLdation’s self-service Payment File Testing (PFT) solution, banks simply send the client a link to register. From then, the corporate is empowered to test their files in a sandbox environment. They upload their own test files and receive immediate guidance on how to populate the address fields.
Errors that will prevent payment processing are clearly flagged, with corporates able to utilize PFT’s . cutting-edge AI Explain feature, which provides additional context on the identified issues, as well as proposing fixes. Recommendations on best practices and how to prepare for long-term compliance are also available.
With this type of assistance at their fingertips, expect to see a dramatic drop in emails from clients to the bank support team looking for clarifications.
“Putting the automation tools directly into clients’ hand means clients complete their migrations fast and according to their own timeline, and bank support teams are not overwhelmed with client requests.
The solution doesn’t just provide industry guidance, it can provide precise support on a bank’s timeline and what its systems will require for hybrid and structured addresses – for Fedwire, CHIPS, Swift CBPR+ and beyond.
And the solution is not just for ISO 20022 messaging. It supports any payment format that financial institutions use for domestic wire and cross-border transactions, including CSV files and EDI820. As such, any bank, anywhere, can leverage PFT to test the full scope of payment types it supports across its market reach, all at once.
The move away from unstructured addresses marks the start of a new era of continuous payments data compliance. With future mass payments data migrations inevitable – think remittance, LEI and commercial trade names – and gifted the Fedwire extension, now is the time for banks to adopt a streamlined approach to ongoing payment file testing.
Putting the automation tools directly into clients’ hand means the overall client experience is considerably enhanced, clients complete their migrations fast and according to their own timeline, and bank support teams are not overwhelmed with client requests.