The November 2026 changes that could stop your cross-border payments

From 14 November 2026, fully unstructured postal addresses will no longer be supported in cross-border payment messages sent through Swift's CBPR+ framework. At a minimum, the town and country for relevant parties must appear in designated fields. Instructions that don't meet the rules may be rejected before entering the network or returned at network level.

Whilst this sounds like a technical change, it’s actually a data problem that starts inside the business.

What's actually changing?

Until now, an address could be entered as several lines of free text. A person could understand it, even if the individual components weren't labelled.

From November, businesses will need either a fully structured or hybrid address. Both require the town and two-letter country code to be held in dedicated fields. A hybrid address can retain some information in free-text lines, while a fully structured address separates components such as the street name, building number and postcode.

The requirements apply across corporate, securities, trade, FX and fund payments. They also matter regardless of whether a business uses ISO 20022 files, MT101 messages or a provider's proprietary channel. The bank or payment provider still needs the required information to execute the transaction. Swift's guidance explains the formats and affected payment channels in more detail.

Why this isn't just your bank's problem

The address attached to a payment usually originates in an ERP system, treasury platform, payroll database or saved beneficiary template. If that source record doesn't contain a separate town and country field, the instruction may be incomplete before it reaches the provider.

This is where I think some businesses could be caught out. An address may look perfectly clear on screen but still fail validation because it's stored as one block of text.

Businesses also shouldn't assume their bank can repair the information downstream. Swift says address data must be sourced at origin and there's no network-level contingency for organisations that miss the deadline. Invalid instructions could be rejected by validating interfaces or returned at network level.

Where the bad data may be hiding

Active suppliers and regular beneficiaries are the obvious place to start. But the higher-risk records may be those that receive less attention.

These could include old payment templates, payroll records, suppliers inherited through an acquisition, accounts created before the current ERP system was introduced and dormant suppliers that suddenly become active again. Bulk-payment files and spreadsheets maintained outside the main finance system also deserve attention.

For businesses operating across several markets, local teams may record addresses differently. Towns may appear within general address fields, while country names may use inconsistent abbreviations rather than the required two-letter codes.

Don't leave testing until November

Start by identifying every system and channel that can originate an international payment. Check whether the required address fields exist, whether they're mandatory and whether the information flows correctly into the final instruction.

Records without a town or valid country code will need to be cleansed or enriched. In some cases, that will mean contacting suppliers, employees or other beneficiaries to confirm their details.

Onboarding forms should also be updated so the business doesn't keep creating records that will need fixing later. Once the data and system changes are complete, test sample files with each banking and payment partner. Formats and validation processes may differ, so passing a check through one channel doesn't guarantee that every channel is ready.

Better data should mean better payments

Structured addresses should give screening systems more precise information, reduce false matches and support more straight-through processing. Over time, that should mean fewer investigations, repairs and delays.

APA works with businesses making payments across multiple currencies, markets and routes. We can help clients understand the information required when submitting payments through APA and test their processes before the change.

If you're unsure whether your beneficiary records and payment files will meet the November requirements, speak to the APA team now. Finding the gaps before a time-sensitive payment fails will be much easier than fixing them afterwards.