A supplier can have a valid business, an active bank account, and a perfectly correct IBAN while still carrying an address that causes problems inside an international payment. The address may be understandable to a person but stored in a format that payment systems cannot interpret reliably.
This issue is becoming more important as financial institutions adopt ISO 20022 and move away from payment instructions built around large blocks of free text. Businesses that ignore the change may discover that the weakest part of a payment file is not the bank account information but an old address copied into the system several years ago.
What Makes an Address Unstructured?
An unstructured address places most or all of the information inside one or more free-text lines. A finance system might store “14 Market Road, Limassol 3041, Cyprus” as a single piece of text without identifying which part is the street, town, postal code, or country.
A structured address gives each component its own field. The street name, building number, postal code, town, and country can therefore travel through the payment chain as distinct pieces of information.
A hybrid address combines both approaches. Certain essential details, particularly the town and country, are placed in dedicated fields, while other information can remain in limited address lines.
Why Payment Systems Care About the Format
Banks use address information for sanctions screening, transaction monitoring, regulatory reporting, and payment routing. When the town and country are buried inside a free-text sentence, systems may need to interpret the information rather than simply read it from the correct field.
That interpretation becomes difficult when addresses use unfamiliar formats, contain spelling variations, include non-Latin characters, or place several location details on one line. A human may recognize the destination immediately, while an automated screening system sees a small geographical mystery.
According to SWIFT’s explanation of the change, structured address data can improve straight-through processing, compliance screening, and transparency across the payment chain. Better formatting therefore supports both regulatory controls and faster processing.
The Implementation Date Has Changed
SWIFT originally planned to remove fully unstructured addresses from relevant cross-border payment messages in November 2026. However, the implementation was postponed in August 2026 after the industry requested more preparation time.
The postponement does not mean structured addresses have been abandoned. SWIFT continues to support structured and hybrid formats, and the broader direction remains focused on improving payment-data quality.
Businesses should use the additional time to clean their supplier records instead of waiting for another deadline announcement. Payment providers and banks may also introduce their own collection requirements as they update internal systems and customer channels.
Your Accounting System May Be the Real Problem
A company may ask suppliers for complete addresses while storing the information badly. An onboarding form might collect the town and country separately, but an employee may paste everything into one address field when creating the supplier record.
Older accounting platforms may not provide dedicated fields for all address components. Exported payment files can also map the information incorrectly, leaving required elements blank even though they appear on the supplier profile.
Businesses using CruisePay Finance for international payment activity should still review how beneficiary information moves from supplier onboarding through accounting records and into the final payment instruction. The data must remain accurate throughout the process rather than merely appearing correct in the original document.
Start With the Suppliers You Pay Most Often
A full supplier-database cleanup can become overwhelming, especially for companies operating across several markets. A risk-based review offers a more manageable starting point.
Begin with suppliers that receive frequent or high-value international payments. Check whether their legal names, registered addresses, operating addresses, towns, postal codes, and countries are recorded in appropriate fields.
Next, review recurring payment templates and bulk-payment files. A supplier record may have been corrected in the accounting system while an older template continues sending outdated information.
The business should also establish a process for handling unusual addresses, including PO boxes, buildings without street numbers, and locations written in different scripts. Employees should obtain guidance from the payment provider rather than improvising a format moments before a deadline.
Improve Supplier Onboarding
New supplier forms should collect address components separately. At a minimum, the business should be able to identify the town and country without extracting them from a block of text.
The information should also be validated before the first payment. Asking a supplier to correct an address during onboarding is considerably easier than doing so while an urgent invoice is waiting for settlement.
Finance, procurement, and technology teams should agree on which system owns the official supplier record. Without clear ownership, corrected details may be overwritten during the next data import.
Final Thoughts
Supplier addresses are becoming functional payment data rather than decorative information placed beneath a company name. If that data is incomplete, outdated, or stored in the wrong format, an otherwise valid international transfer may require manual repair or additional review.
Businesses should audit important beneficiaries, update their onboarding forms, and test how address information appears in exported payment files. The deadline may have moved, but the need for cleaner payment data has not disappeared.
#ISO20022 #PaymentData #SupplierManagement #CrossBorderPayments #BusinessPayments #FinanceOperations #CruisePayFinance
Recent Comments