14 November 2026: the Swift address rule, from a corporate treasury view

What changes

From 14 November 2026, cross-border payment messages on Swift (the CBPR+ ISO 20022 messages banks exchange) accept only structured or hybrid postal addresses. Messages with free-text-only addresses can be rejected or delayed. The rule also reaches domestic payments with a cross-border leg.

A hybrid address is the minimum:

Element	Requirement
Town name (TwnNm)	Mandatory, in its own field
Country (Ctry)	Mandatory, in its own field (ISO country code)
Address lines (AdrLine)	At most two, up to 70 characters each

Placeholders such as NOTPROVIDED in town or country are not acceptable. Banks have been able to send hybrid addresses since 22 November 2025, so many are already asking clients for the data.

Why this lands on corporate treasury

The rule binds banks, not companies. But a bank can only send a compliant address if you give it one. Whatever format you use to instruct payments (pain.001, MT101, a bank’s own CSV layout or a portal upload), the beneficiary’s town and country have to come from somewhere. That somewhere is usually your ERP’s vendor master data.

In our view, that’s where most of the work is. Payment-file mapping changes are small once the data exists. Cleaning addresses for hundreds or thousands of overseas vendors is not.

A short checklist

1. Ask each bank directly. What will happen from 14 November to an instruction with an unstructured beneficiary address: reject, repair, or pass through? Do they want structured fields in your file now?
2. Pull a vendor extract. Filter to vendors you pay cross-border and check that town and country are in separate fields, not buried in an address line.
3. Check one real payment file. If you send pain.001, look at Cdtr/PstlAdr. Address lines alone, without TwnNm and Ctry, are the pattern to fix. Our free file checker flags it in your browser, with nothing uploaded.
4. Watch the agent fields too. For banks identified by BIC, a BIC alone remains valid; the address rule bites on parties identified by name and address.
5. Test before the date. Send a test file through each bank’s test channel before mid-November.

The bigger picture

This is one step in the ISO 20022 migration. Swift’s coexistence period for cross-border payment instructions between banks ended in November 2025. Corporates were not forced to change formats on the same day, and many treasury teams are still unsure what the migration means for them. J.P. Morgan also notes that 14 November 2026 ends the coexistence of MT101 over Swift CBPR+ for financial institutions. If your company instructs payments by MT101, ask your bank what that means for you.

Rules like this are why we argue for bank-agnostic payment processes: clean, standard data in your systems, so a change at one bank or network is a mapping exercise, not a project.