Swift delays structured address mandate as corporate data gaps persist

Swift has postponed the next major milestone in the ISO 20022 modernisation process, extending the timetable for eliminating fully unstructured postal addresses from payment messages. The decision follows widespread reports from the industry that many participants across all regions were unable to meet the original November requirement. The global payments messaging network deferred all payments changes scheduled for Standards Release 2026 and has not yet set a replacement date for the structured address requirement. Swift stated that it will consult with banks, central banks, payment infrastructures, market practice groups and corporates, with an update expected by December.

The postponement comes after the industry largely completed its underlying migration to the ISO 20022 standard. Swift announced that more than 98% of payment instructions are now sent in this format following the end of coexistence with the older MT standard last year. However, the transition to richer, standardized and machine-readable data remains incomplete. The primary objective of this phase is to ensure information is immediately usable by machines, reducing the need for systems or people farther along the payment chain to interpret free-form text. This shift aims to support greater automation, more effective compliance screening and better straight-through processing.

Recent readiness data released in August indicates that unstructured addresses still dominate Cross-Border Payments and Reporting Plus traffic. In July, 58.3% of debtor addresses and 59.3% of creditor addresses were unstructured. In comparison, only 36.9% and 27% of these addresses, respectively, were structured or hybrid. This disparity highlights the difficulty of converting legacy data formats into the discrete fields required by the new standard. A supplier address stored as a line of free-form text may be sufficient for an invoice or a human reviewing a vendor record, but it does not automatically provide the specific town and country fields necessary for transmission through an ISO 20022 message.

The delay places significant emphasis on enterprise integration, as banks now depend on ERP and treasury systems to supply structured information at payment initiation. Swift’s guidance for corporate customers states that businesses must source creditor address information through their own channels, store it in their ERP or treasury applications, and provide it to their bank when the payment is initiated. This positions ERP platforms, treasury management systems and bank payment channels at the centre of the next phase of implementation. The quality of data within these systems is now a critical constraint on payment efficiency, as automated workflows can still fail if the beneficiary information feeding them remains inconsistent or incomplete.

The Federal Reserve’s response to the Swift delay reinforces that the work is not limited to cross-border messaging. Federal Reserve Financial Services moved its planned November 2026 release of the Fedwire Funds Service to November 2027 following the announcement. Although Fedwire has already migrated to ISO 20022, the Fed stated it will announce the final scope of the November 2027 release this fall. Current implementation guidance instructs financial institutions to continue preparing for the removal of unstructured postal addresses and to involve their software vendors or processors.

Corporate customers are receiving similar instructions from financial institutions. U.S. Bank stated that it and payment networks will not begin rejecting wires for address formatting in November. Instead, the bank encouraged customers to continue updating systems, files, templates, repeat codes and processes. It also directed ERP users to their software vendors for information about supporting the requirements. PYMNTS Intelligence found that demand for better ERP, treasury and accounting integration rises from 22% of businesses overall to 29% of larger firms, identifying integration as a leading barrier to real-time payment adoption.