ISO 20022 Address Requirements:
Deadline Update
SWIFT has deferred the November 2026 structured-address deadline. It will provide an update on revised timing and approach by December 2026 at the latest. Keep preparing town and country as separate fields and confirm the address format your bank requires for international payments.
Understand the available address formats, the timetable update, and practical steps for sending and receiving international payments.
Trace a SWIFT transfer
See what the banks have reported about your transfer, and get alerted when the payment reaches a further stage.
The address deadline at a glance
The four facts that matter, before the detail.
In its August 2026 announcement, SWIFT deferred the payments changes planned for Standards Release 2026, including the removal of unstructured addresses. It will consult on revised timing and approach, with an update by December 2026 at the latest.
When is ISO 20022 mandatory?
ISO 20022 has been the required format for CBPR+ cross-border payment instructions between financial institutions since November 2025, when coexistence with legacy MT instructions ended. The address extension does not reverse that migration.
Address preparation is a separate step. Structured and hybrid addresses are already available, and SWIFT encourages banks and payment systems to continue improving address data.
The planned 14 November 2026 cutover has been deferred. SWIFT will consult with banks, central banks, payment systems, market practice groups, and corporates on the revised timing and approach.
SWIFT will provide an update by December 2026 at the latest. That is the timing for an announcement. Confirm your bank's own preparation schedule and the requirements of the payment systems it uses.
What is the ISO 20022 address format?
Three formats exist today. SWIFT has deferred the planned removal of unstructured addresses.
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. This format is already available for CBPR+ payments.
An unstructured address supplies everything as free-text lines, with no dedicated town or country element. SWIFT has deferred its planned removal from CBPR+ payment messages.
SWIFT recommends continuing to improve address data. Its address-format guidance describes the structured and hybrid formats. Use the August extension announcement for the timetable.
What this 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/ Confirm your details with your bank
Your bank may still ask you to review your address and saved beneficiaries. Keep town and country in separate fields where requested, and confirm the bank's preparation schedule. Updating stored details helps avoid repairs when you next pay.
02/ Check your payment templates
Check whether your online banking forms and payment templates collect town and country separately. If a saved beneficiary uses a single free-text address, ask your bank whether it needs updating for the channel you use.
03/ Where a failed payment shows up
Missing or incorrect address details can cause delays or rejection under existing checks. A network refusal (NAK) is distinct from an RJCT status reporting a rejected instruction. An empty tracking result does not establish an address failure. Ask the sending bank to confirm the reason and next step.
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. These fields are the minimum for the structured and hybrid CBPR+ address formats.
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 addresses with your bank
Ask your bank to validate the structured or hybrid addresses your files produce and confirm its available test facilities. Agree a preparation schedule for each channel so formatting gaps are found before you need to send a payment.
For address-format details, see SWIFT's structured and hybrid address guidance. Your bank can confirm channel-specific file formats and testing. Payment systems have their own schedules: the Bank of England deferred its RTGS release, including CHAPS messaging changes, while Fedwire rescheduled its release to November 2027. The Fedwire date is not a confirmed SWIFT deadline.
Why addresses are being structured
Free-text addresses can make automated screening harder because address components are not identified consistently. Clear town and country fields help banks identify parties and reduce manual repairs that can delay a transfer.
SWIFT describes structured data as a foundation for more effective compliance screening, greater automation, and better payment transparency. Preparing accurate addresses supports those improvements while the migration timetable is revised.
FAQ
Frequently asked questions about the ISO 20022 address requirements
When is ISO 20022 mandatory?
ISO 20022 became the required format for CBPR+ cross-border payment instructions between financial institutions in November 2025, when coexistence with legacy MT instructions ended. SWIFT has deferred the separate November 2026 structured-address deadline and will provide an update on revised timing and approach by December 2026 at the latest.
Has the ISO 20022 address deadline been extended?
Yes. In August 2026, SWIFT deferred the payments changes planned for Standards Release 2026, including the removal of unstructured addresses. The planned 14 November 2026 cutover no longer applies. SWIFT will consult on the revised timing and approach and provide an update by December 2026 at the latest.
What is a structured address in ISO 20022?
A fully structured address places each supplied component in its own dedicated element, such as street name (StrtNm), building number (BldgNb), postal code (PstCd), town name (TwnNm), and country (Ctry). It uses no free-text address lines. For CBPR+, town name and country are the minimum address elements in this format.
What is a hybrid address in ISO 20022?
A hybrid address combines structured elements with free text. Introduced for CBPR+ in November 2025, it requires town name and country in dedicated fields and allows up to two free-text address lines of 70 characters each. It is already available for banks preparing their address data.
What is the minimum information in a structured or hybrid address?
Town name and country, each in its own dedicated field. SWIFT planned this minimum for every party and agent in the affected CBPR+ messages, except banks acting as agents may use a BIC alone instead of a name and address. The November 2026 rollout was deferred; confirm your bank's current requirements.
Can incomplete address details cause a payment to be rejected?
Yes. Missing or incorrect address details can cause delays or rejection under a bank's existing checks. A network refusal (NAK) means the message failed validation; an RJCT status reports rejection of the payment instruction. Neither confirms a refund. Ask the sending bank for the reason and the correction needed.
Why is my bank asking me to confirm my address for international payments?
Banks can continue preparing structured address data while SWIFT revises the migration timetable. Your bank may ask for your town and country and the same details for beneficiaries. Confirm the format and timing it requires for your payment channel and update saved details when requested.
Does ISO 20022 replace SWIFT?
No. SWIFT provides financial messaging services; ISO 20022 is a standard for financial messages. SWIFT migrated CBPR+ payment instructions from the legacy MT format to ISO 20022. The address-timing extension does not reverse that migration.
Do all payment systems have the same address deadline?
No. SWIFT is consulting on revised CBPR+ timing. The Bank of England has deferred its November 2026 RTGS standards release, including CHAPS messaging changes. The Fedwire Funds Service has rescheduled its release to November 2027. That Fedwire date is not a confirmed SWIFT deadline.
Which messages were covered by the planned address rule?
The planned rule covered parties and agents in CBPR+ payment messages, with exceptions for admi.024, camt.025, camt.052, camt.053, camt.054, and camt.060. Banks acting as agents could use a BIC alone. SWIFT is consulting on revised timing and approach following the deferral.
Does the address change affect the UETR or payment tracking?
The UETR remains the 36-character reference used to track the payment end to end. The address extension does not change it. An empty tracking result does not establish an address problem; for a delayed or rejected payment, ask the sending bank to confirm the reason.
What should a business do to prepare?
Check stored beneficiary addresses, capture town and country as separate fields, confirm each bank's input format, and arrange address-validation testing with the bank. SWIFT encourages continued preparation while it consults on revised timing. Follow your bank's requirements for each channel.
Is ISO 20022 a cryptocurrency standard?
No. ISO 20022 is an international standard for financial messaging across payments, securities, trade, cards, and foreign exchange. It does not certify or endorse cryptocurrencies.
Related guides
Related payment concepts: 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.