Home Features Cross-Border Payments Face Key SWIFT Deadline
Author: Deborah Ritchie | Photos: Shutterstock
With SWIFT’s ISO 20022 compliance deadline looming in November, several banks are behind schedule.
This article appears in the September 2026 issue of Global Finance Magazine.
Cross-border payments are approaching a hard deadline in November, when SWIFT stops accepting unstructured address data under ISO 20022 . The global messaging standard that replaced the old SWIFT MT format, ISO 20022 was designed to give every country’s banks a common baseline, and November’s structured-address requirement is the next phase of that migration.
SWIFT data from April showed that 61.2% of payments still carried unstructured debtor addresses, and 62.9% unstructured creditor data. This matters; once fully unstructured addresses are removed, noncompliant payments risk rejection or delay, with no fallback transition layer for missing address data.
A March survey of senior payments professionals across Europe and North America by RedCompass Labs found that 44% of banks were behind schedule on readiness for SWIFT’s removal of unstructured addresses. Pratiksha Pathak, RedCompass senior vice president and head of payments, attributed that figure to years of treating the wider ISO 20022 migration as a message-format exercise rather than the data quality overhaul it was always meant to be.
Anxiety about readiness was clear but uneven, with 20% of the very largest banks deeming the deadline “unrealistic,” compared with 5% of smaller banks, indicating that scale and legacy systems are part of the problem. This was not for lack of trying; most banks are spending around $20 million on the requirements, with larger institutions spending over $30 million.
Bank readiness has shifted since March, Pathak noted. Some trailblazers have rolled out “brilliant” programs, she said, while laggards still hope SWIFT will push back the clock. That won’t happen, Pathak said: “They’re not moving the deadline.”
Lloyds is among the banks that recognized the central issue early, building its solutions around structured data from the outset. API-based channels natively support the required fields, backed by validation controls and proactive client outreach, including a ramp-up in dedicated resources as November approaches.
“The biggest challenge isn’t usually the payment message itself,” said Surath Sengupta, head of transaction banking products at Lloyds. “It’s the readiness of the underlying data. Many organizations already hold most of the required information, but it’s often stored inconsistently across ERP and treasury systems.”
Early movers aren’t aiming just to meet the deadline, he said. They are positioning themselves to capture the broader gains from automation that follow, “from increasing automation and reducing friction to laying the foundations for the next generation of cross-border payments.”
Industry estimates suggest that 5% to 10% of payments currently generate sanctions screening alerts requiring manual review, a friction that richer structured data should directly ease.
Not every treasurer is equally confident in the guidance they receive, however. Some have faced practical challenges with the availability of detailed technical specifications and implementation guidance from banking partners, said Marianna Polykrati, group treasurer at aquaculture producer Avramar: “Many corporates are still waiting for this information.”
Ownership of payment pro…