ISO 20022 address requirements:
what changes on 14 November 2026.
From 14 November 2026, international payments on the SWIFT network must carry the town and country of every party in dedicated structured fields. Payments whose addresses are still fully unstructured free text are rejected by the network, with no fallback mechanism. The change applies to the sender and the beneficiary alike, which is why banks are asking customers to review their details now.
This page explains the deadline in plain language: which address formats remain valid, what the minimum data is, what a rejection looks like when you track a transfer, and what to fix before the date arrives.
Trace a SWIFT transfer
See where your transfer is in the banking network right now, and get alerted when the status changes.
The November 2026 deadline at a glance
The four facts that matter, before the detail.
The requirement comes from SWIFT's removal of unstructured address data under the CBPR+ usage guidelines: from 14 November 2026, town and country must be provided in designated fields, at a minimum, for all agents and parties in cross-border payment messages. It applies to all payment types, including corporate, securities, trade, foreign exchange, and funds. Only a small set of reporting messages (admi.024, camt.025, camt.052, camt.053, camt.054, and camt.060) is exempt, and banks acting as agents may continue to identify themselves with a BIC alone.
When is ISO 20022 mandatory?
ISO 20022 has been the required format for cross-border payment messages between banks since November 2025, when SWIFT's coexistence period with the legacy MT format ended. If your bank sends an international transfer today, the bank-to-bank message is already an ISO 20022 message (a pacs.008), whatever the confirmation you receive looks like.
The address rule is the second milestone of the same programme. Migrating the message format did not automatically fix the data inside it: most payments still carried addresses as free-text lines. The November 2026 deadline closes that gap.
The final Standards Release 2026 usage guidelines, containing the formal validation that retires unstructured addresses, have been available since 20 February 2026, and the validation switches on when the release goes live on 14 November 2026.
SWIFT has been explicit that there is no contingency: address data must be corrected where it is stored, before the deadline, because the network cannot repair a payment whose address arrives incomplete.
What is the ISO 20022 address format?
Three formats exist today. From 14 November 2026, only two of them remain valid.
A fully structured address places every component in its own element: street name, building number, postal code, town name, and country each have a dedicated field, and free-text address lines are not used at all. This is the long-term target, because a machine can screen and route it without guessing which line holds the town and which holds the street.
A hybrid address is the transition format, available since November 2025. The town name and the country must sit in their structured fields, while the rest of the address may stay in up to two free-text lines of 70 characters each. Hybrid remains valid after the deadline.
An unstructured address supplies everything as free-text lines, with no dedicated town or country element. This is the format being retired: from 14 November 2026 the network refuses payment messages that carry it.
The scale of the change is easy to underestimate. In the June 2026 adoption figures SWIFT publishes on its removal of unstructured address page, roughly 60 percent of cross-border payment messages still carried unstructured addresses for the sender or the beneficiary (60.1 percent of debtor and 61.4 percent of creditor elements), five months before the deadline. A large share of everyday payments must change format in the remaining window, which is why banks are contacting customers now rather than waiting.
What the deadline means when you send or receive a transfer
Most coverage of this change is written for banks. The practical effects land on the people sending and receiving the payments.
01/ Your bank will ask you to confirm details
Expect messages from your bank asking you to review your address and your saved beneficiaries. This is not a formality: from 14 November 2026 your bank cannot send a compliant payment unless it holds your town and country, and your beneficiary's town and country, as separate data fields. Responding early costs minutes; an address gap discovered on the day you need to pay someone costs days.
02/ Payment forms will want more detail
Online banking forms and payment templates are being updated to collect town and country as separate inputs instead of one address box. If a saved beneficiary was created years ago with a single-line address, it may need to be edited once before it can be used again.
03/ Where a failed payment shows up
Most address failures are caught at submission: the bank's own systems, or the network itself, refuse the instruction before it is sent, so nothing appears in tracking because the payment never entered the chain. A payment that does get sent and is then refused by one of the banks handling it surfaces as the RJCT status. If a transfer of yours shows RJCT in late 2026, or never appears in tracking at all, incomplete address details are one of the first causes worth raising with the sending bank.
04/ The tracking reference does not change
The UETR, the 36-character reference that follows your transfer across every bank, is untouched by the address rule. Whatever format the addresses take, the UETR still identifies the payment end to end, and tracking works exactly as before.
How businesses should prepare
SWIFT's guidance to corporates is to source the beneficiary's town name and country and provide them at payment initiation; how each bank's channel collects them varies. Four steps cover most of the preparation.
Audit the addresses you store
List everyone you pay across borders: suppliers, staff, customers. For each, check whether the town and the country are recorded as separate fields rather than buried in a free-text address block.
Capture town and country as fields
Update forms, templates, and your ERP or accounting system so town name and country are always collected in their own fields. That is the minimum the network enforces from 14 November 2026.
Ask your bank what its channel expects
How the requirement reaches you varies by bank: some pass the structured format through to the files and instructions you submit, while others accept their own input format and complete the address from stored beneficiary data. Confirm what each channel you use expects, and whether it wants fully structured or hybrid addresses.
Validate with your bank before the deadline
A normal payment sent before 14 November 2026 does not prove readiness, because the new validation is not active yet. Ask your bank to validate the structured or hybrid addresses your files produce, or use its Standards Release 2026 test facility, so a formatting gap surfaces during a test rather than on payroll day.
The full requirements, including per-country guidance on how to structure unusual address formats, are published in SWIFT's ISO 20022 unstructured address FAQ and the underlying ISO 20022 standard documentation. Your bank's own onboarding team is the right contact for channel-specific file formats.
Why addresses are being structured
Free-text addresses are the single largest source of ambiguity left in cross-border payment data. When a compliance system cannot tell which line of an address is the town, it guesses, and a wrong guess produces false alarms that a person then has to review by hand. Those manual reviews are one of the main reasons an international transfer that should take hours takes days instead.
Structured addresses remove the guessing. With town and country in dedicated fields, screening systems compare like with like, fewer payments are stopped for review, and the ones that are stopped are stopped for better reasons. The same data quality goal sits behind the wider G20 programme on cross-border payments that this requirement supports: faster processing, fewer rejections, and better end-to-end transparency.
FAQ
Frequently asked questions about the ISO 20022 address requirements
When is ISO 20022 mandatory?
ISO 20022 became the required format for cross-border payment messages between banks in November 2025, when SWIFT's coexistence period with the legacy MT format ended. A second milestone follows on 14 November 2026: from that date, postal addresses inside those messages must be structured or hybrid, with town and country in dedicated fields, and payments carrying fully unstructured addresses are rejected by the network.
What changes on 14 November 2026?
From 14 November 2026, every party and agent in a cross-border payment message must have at least the town name and the country in dedicated structured fields; the exception is banks acting as agents, which may continue to be identified by a BIC alone instead of a name and address. Addresses may be fully structured or hybrid, but fully unstructured free-text addresses are no longer accepted: the SWIFT network rejects (NAK) such payment messages outright, and SWIFT provides no contingency mechanism for institutions that are not ready.
What is a structured address in ISO 20022?
A fully structured address places every address component in its own dedicated element: street name (StrtNm), building number (BldgNb), postal code (PstCd), town name (TwnNm), and country (Ctry), with no free-text address lines at all. It is the long-term target format because machines can read, screen, and route it without guessing which line holds which detail.
What is a hybrid address in ISO 20022?
A hybrid address is a transition format introduced in November 2025. The town name and the country must appear in their dedicated structured elements, and the rest of the address may stay in up to two free-text address lines of 70 characters each. Hybrid addresses remain accepted after 14 November 2026, so they are the practical route for organisations that cannot fully structure every stored address in time.
What is the minimum address information required from November 2026?
Town name and country, each in its own dedicated field, for every party and agent in the payment message. For banks acting as agents, using a BIC alone remains valid instead of providing a name and address. Everything beyond that minimum can stay in up to two free-text address lines under the hybrid format.
What happens if a payment still has an unstructured address after the deadline?
It does not go through. Messaging interfaces that validate against the standard reject the instruction before it reaches the network, and payments that do reach the network with unstructured addresses are rejected (NAK) at network level from 14 November 2026. An instruction refused at submission never leaves the bank, so there is nothing to return; a payment refused later in the chain is returned to the sender. In both cases the payment is not delivered until the sender corrects the address details and sends it again.
Why is my bank asking me to confirm my address for international payments?
Because from 14 November 2026 your bank must place your town and country, and your beneficiary's town and country, in dedicated structured fields of every cross-border payment message. Banks are contacting customers now so that stored addresses can be corrected before the deadline. Responding early is worthwhile: address gaps discovered at payment time cause delays and rejections.
Does ISO 20022 replace SWIFT?
No. SWIFT is the network that carries payment messages between banks; ISO 20022 is the message format those messages are written in. SWIFT migrated its cross-border payment messages from the legacy MT format to ISO 20022, so the network stayed the same while the language of the messages changed.
Which payments does the address requirement apply to?
All payments carried in CBPR+ payment messages on the SWIFT network, including corporate payments, securities, trade, foreign exchange, and funds. Payment systems for major currencies such as USD, EUR, GBP, AUD, CAD, and SGD are aligned with the same November 2026 deadline for their domestic legs.
Are any message types exempt from the address rule?
Yes, a small set of reporting and administrative messages: admi.024, camt.025, camt.052, camt.053, camt.054, and camt.060. Every other CBPR+ payment message must carry structured or hybrid addresses with town and country present from 14 November 2026.
Does the November 2026 change affect the UETR or payment tracking?
The UETR itself does not change: it remains the 36-character reference generated by the sending bank and carried end to end. What changes is a new way for a payment to fail. Most address failures are stopped at submission: the bank's systems or the network refuse the instruction before it is sent, so nothing appears in tracking at all. A payment that does enter the chain and is then refused by one of the banks handling it surfaces as RJCT in tracking. Either way, from late 2026 incomplete address details belong on the list of causes to raise with the sending bank.
What should a business do to prepare for the deadline?
Four practical steps: audit the addresses stored for suppliers, staff, and customers you pay across borders; make sure town and country are captured as separate fields in your systems and payment templates; ask your bank which format its channels expect, since requirements can apply to files you upload as well; and ask your bank to validate the addresses your files produce, or use its Standards Release 2026 test facility, well before November 2026. A normal payment sent before the deadline does not prove readiness, because the new validation is not active yet.
Is ISO 20022 a cryptocurrency standard?
No. ISO 20022 is an international standard for financial messaging, used for bank payments, securities, trade, and cards. Some cryptocurrency projects describe their messaging as ISO 20022 compliant, which only means their data formats align with the standard; the standard itself is about how financial messages are structured and neither endorses nor involves any specific asset.
Related guides
The concepts around the deadline: the message that carries your payment, the statuses it reports, and the reference that tracks it.
What is MT103?
The legacy SWIFT message, its pacs.008 successor, and where the UETR sits inside both.
SWIFT status codes
ACSP, ACSC, ACCC, PDNG, RJCT: what each status means and whether to wait or act.
What is a UETR?
The 36-character reference that follows your transfer across every bank in the chain.
How to track a SWIFT payment
The step-by-step guide: find the UETR, run a free check, and read the result.
How long does an international wire take?
Realistic timelines by scenario, and what to do when a transfer runs late.
Regulatory Disclosure
uetr.ai is an independent information service. We are strictly a read-only payment-monitoring tool. We never hold, move, custody, send, or process money. We are not a money transmitter or payment processor. Always consult your sending bank for the official record of any bank transfer.