2026 ISO 20022 readiness

107 days to 14 November 2026, as at 2026-07-30.

On that date, fully unstructured postal addresses stop being accepted in SWIFT CBPR+ payment messages and by the Bank of England's CHAPS validation library. Two other changes land the same day, and a larger set follows in November 2027.

Every rule below carries an identifier, an effective date, an authoritative source and a test fixture, so nothing here has to be taken on trust.

Are you affected?

You are in scope if you send CBPR+ or CHAPS payments containing a postal address for any party.

What actually changes

The requirement is a minimum, not a maximum. This is the most commonly misread part of the mandate.

Format	TwnNm	Ctry	AdrLine	Before 14 Nov 2026	On or after
Fully structured	Present	Present	Absent	Accepted	Accepted
Hybrid	Present	Present	Present	Accepted	Accepted
Fully unstructured	Absent	Absent	Present	Accepted	Rejected

You do not have to move street, building number and post code into structured elements. Town Name in and Country in as a two-letter ISO 3166 code is sufficient. Everything else may stay in address lines. That combination is a hybrid address and it remains valid.

Full detail, with worked examples →

Check your data now

Two tools, both running entirely in your browser. No payment data is uploaded.

• Batch address scan — upload a CSV of party addresses and get a readiness score, a breakdown by party, and a downloadable remediation list of the records that would fail.
• XSD validation — check an existing message against the official schema for element order, cardinality and datatypes.

Test fixtures

Run these through the workbench, the CLI or the API. Each maps to the rule it exercises, so you can confirm your pipeline reacts the way you expect.

• structured-valid.csv — passes CBPR-ADDR-001
• hybrid-valid.csv — passes CBPR-ADDR-001
• unstructured-invalid.csv — fails CBPR-ADDR-001
• missing-town-invalid.csv — fails CBPR-ADDR-002
• missing-country-invalid.csv — fails CBPR-ADDR-003
• agent-bic-only-valid.csv — passes CBPR-ADDR-005
• hybrid-valid.csv — passes CHAPS-ADDR-001
• unstructured-invalid.csv — fails CHAPS-ADDR-001

Every milestone, not just this one

November 2026 is not the end of ISO 20022 change. Swift moves to an annual Standards Release cycle from that date, so usage guidelines will change every year.

Date	Scheme	Change	Rule
2025-11-22	CBPR+	Hybrid postal address option available	CBPR-ADDR-004
2025-11-22	CBPR+	MT/MX coexistence for payment instructions ends	—
2026-11-14	CBPR+	Fully unstructured postal address rejected	CBPR-ADDR-001
2026-11-14	CHAPS	CHAPS validation library rejects unstructured addresses	CHAPS-ADDR-001
2026-11-14	CBPR+	MT101 interbank coexistence ends; contingency relays to pain.001	—
2026-11-14	Swift	camt.110 investigation requests must be receivable	—
2026-11-14	Swift	Annual Standards Release cycle begins	—
2027-11	CHAPS	Purpose codes mandatory on all payments (announced)	CHAPS-PURP-001
2027-11	CHAPS	Structured remittance information mandatory (announced)	CHAPS-RMT-001
2027-11	Swift	camt.110 and camt.111 both mandatory (announced)	—

Dated change log and feed →

What to check, by role

Engineering

• Find every place an address is concatenated into a single line before it reaches the message. That is usually where the problem is.
• Model town and country as separate fields end to end, not just at the boundary.
• Add CBPR-ADDR-001 to CBPR-ADDR-003 to your pre-submission validation, with the effective date, so failures surface before 14 November rather than on it.
• Add a negative test that a fully unstructured address is rejected. A rule you have never seen fire is a rule you cannot rely on.

Data

• Measure how many records are missing a structured town or country now, so the remediation effort is a number rather than a guess. The batch scan produces exactly this.
• Identify the authoritative source per field. Addresses often arrive from several systems with different conventions.
• Country must be a two-letter ISO 3166 code. GB, not United Kingdom or GBR — CBPR-ADDR-003 fails on the latter two.

Testing

• Test the day before, the day of, and the day after the effective date. Effective-date logic is where date-boundary bugs live.
• Test CBPR+ and CHAPS separately. They are modelled as distinct rules here for a reason.
• Include a hybrid address in the passing set. A test suite that only accepts fully structured addresses will reject valid traffic.

Operations

• Know what a rejection for this reason will look like in your monitoring, and who triages it.
• Confirm your counterparties' readiness, not only your own. A compliant message can still fail if the receiving side is not ready.

Management

• The exposure is the count of records that would fail today, not the count of systems. Ask for the number.
• Note the 2027 obligations below. Teams that treat November 2026 as the finish line will repeat this work in twelve months.

Scheme differences

	SWIFT CBPR+	Bank of England CHAPS
Unstructured rejected	14 November 2026	14 November 2026
Minimum acceptable	Hybrid	Hybrid
Enforced by	CBPR+ usage guidelines	CHAPS validation library
Purpose codes	Not mandated by this change	Mandatory for all payments from November 2027
Structured remittance	Not mandated by this change	Mandatory from November 2027
Rules here	CBPR-ADDR-001 – 006	CHAPS-ADDR-001, CHAPS-PURP-001, CHAPS-RMT-001

Sources

Every rule on this page derives from one of these. Rules marked announced are published intentions whose exact date should be re-verified before you rely on them.

Source	Publisher	Document	Verified
SWIFT-ADDR-2026	S.W.I.F.T. SC	SWIFT CBPR+ Removal of Unstructured Address Guidelines	2026-07-28
BOE-CHAPS-2026	Bank of England	Policy Statement — Mandating ISO 20022 Enhanced Data in CHAPS	2026-07-28
ISO-20022-PACS008-13	ISO 20022 Registration Authority	Financial Innovation & Transfer — pacs.008.001.13 Message Definition	2026-07-28

pacs008.com is not the official ISO 20022 website. The sole source of up-to-date materials and information on ISO 20022 message standards and the Repository is https://www.iso20022.org/.