SWIFT has postponed the November 2026 structured address deadline. What happens now?

What did SWIFT announce?

On 27 August 2026, SWIFT said it had accepted a request from the financial community to extend the migration to structured addresses in ISO 20022 payment messages. Under the plan in force until then, from November 2026 postal addresses in cross-border payment messages had to be either fully structured or “hybrid” (town and country in their own fields), and payments with fully unstructured addresses could be rejected or delayed. SWIFT had also said there would be no contingency measure to process non-compliant messages.

SWIFT’s reason, as reported by The Paypers and Finextra, was that progress remained uneven, with large parts of the industry across all regions not yet able to meet the requirement. SWIFT deferred all payments-related changes in its Standards Release 2026 and said it would consult banks, central banks, payment market infrastructures, market practice groups and corporates on “the optimal timing and approach”, with an update by December 2026 at the latest, as part of its governance cycle.

Who else changed their plans?

Large domestic high-value payment systems had aligned their own address rules with SWIFT’s date, so the deferral rippled outwards within hours:

The Bank of England said it expects to publish an updated list of changes in December 2026 and a final list in April 2027. It also reminded firms that hybrid and structured address formats are already available, so there is no need to wait. Separately, the Bank had already said in July 2026 that it would not mandate structured remittance data from November 2026.

Why does a postal address matter so much?

Every international payment is screened by each bank it passes through: against sanctions lists, for fraud and for anti-money-laundering rules. In the old MT103, addresses were a few lines of free text, so a bank’s software had to guess where the town and the country were. ISO 20022 gives each part its own field. A town and a country in tagged fields make screening faster and more accurate, cut false matches and reduce the number of payments a person has to stop and look at. That is why regulators and SWIFT want unstructured addresses gone, and why the change touches every bank, payment company and corporate that creates payment instructions. Our explainer on the SWIFT ISO 20022 migration has the background.

Is this a reprieve for banks, or a delay for everyone?

Mostly the second. Structured addresses are still the destination; only the date moved. The deferral spares payments that would otherwise have been rejected because one bank in the chain, or one corporate system, was not ready. That is a real risk for payments that pass through several correspondents, where a single non-compliant hop can stop the whole transfer. But it also means the screening and automation benefits arrive later.

It is also part of a wider pattern. In its October 2025 progress report, the Financial Stability Board judged it unlikely that the G20’s 2027 targets for faster, cheaper cross-border payments would be met, citing long lead times for infrastructure changes and different rates of adoption. See the G20 roadmap and its 2027 targets.

Companies are affected too, not only banks. A corporate that sends payment files to its bank still in the older MT101 format was told by SWIFT to use the structured option (option F) for the ordering customer and beneficiary fields when it gives an address. Treasury and ERP teams that had planned their upgrades around November 2026 now have more time, but the work is the same.

What should an Indian exporter do?

Nothing changes for you overnight, and payments that used to arrive will keep arriving. But the direction is fixed, so it is worth getting ahead:

1. Put a full, structured address on your invoices: building and street, town or city, PIN code and country, each on its own line, matching your bank records.
2. Ask overseas clients to copy it exactly into their bank’s payee form, rather than squeezing everything into one line.
3. Check your own bank profile. If your bank holds an old or partial address for you, update it; the address on file and the address the payer sends should agree.
4. Keep the payment reference and the UETR for every incoming wire, so a held payment can be traced quickly. See SWIFT gpi tracking.

If clients pay you over their local rails into a receiving account instead of by wire, the address data still matters, but it is captured once when the account is set up. More on the options in how to receive international payments in India.

What is not yet known

As of 30 October 2026, SWIFT has not published the new date for removing unstructured addresses from CBPR+ messages; it has committed to doing so by December 2026. The Bank of England describes its 12-month deferral as an expectation that remains subject to confirmation. We will update this post when the dates are final.