2026 年 ISO 20022 就绪

距 2026 年 11 月 14 日 还有 107 天（截至 2026-07-30）。

自该日起，完全非结构化的邮政地址将不再被 SWIFT CBPR+ 支付报文以及英格兰银行的 CHAPS 校验库接受。同一天还有另外两项变更生效，2027 年 11 月将有更大范围的变更。

下列每条规则都带有标识符、生效日期、权威来源和测试文件——无需仅凭信任。

这是否影响到您

如果您发送的 CBPR+ 或 CHAPS 支付中包含任一当事方的邮政地址，即属适用范围。


报文	`pacs.008`, `pacs.009`, `pacs.004`, `pacs.003`
当事方	Debtor, creditor, ultimate debtor, ultimate creditor, and agents that carry an address
不在范围内	`admi.024`, `camt.025`, `camt.052`, `camt.053`, `camt.054`, `camt.060`
豁免	Agents identified by BIC alone need no postal address (`CBPR-ADDR-005`)

实际改变了什么

该要求是下限而非上限。这是该强制要求中最常被误读的部分。

格式	`TwnNm`	`Ctry`	`AdrLine`	2026 年 11 月 14 日之前	自该日起
完全结构化	有	有	无	接受	接受
混合	有	有	有	接受	接受
完全非结构化	无	无	有	接受	拒绝

您无需把街道、门牌号和邮政编码迁入结构化元素。在中填写城市、在中填写两位 ISO 3166 国家代码即可。其余内容可保留在地址行中：这属于混合地址，依然有效。

Full detail, with worked examples →

立即检查您的数据

两个工具，均完全在您的浏览器中运行。不会发送任何支付数据。

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.

测试文件

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

所有节点，而不只是这一个

2026 年 11 月并非 ISO 20022 变更的终点。自该日起 Swift 转为年度 Standards Release 周期，使用指南将逐年变化。

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 →

按角色需要检查的事项

工程

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.

数据

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.

测试

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.

运营

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.

管理层

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.

各方案之间的差异

	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`

来源

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.

来源	发布方	文件	核实
`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/.