2026年 ISO 20022 対応
2026年11月14日まであと107日(2026-07-30時点)。
同日以降、完全非構造化の郵便住所は SWIFT CBPR+ の支払メッセージおよびイングランド銀行の CHAPS 検証ライブラリで受け付けられなくなります。同日には他に 2 つの変更が施行され、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日より前 | 同日以降 |
|---|---|---|---|---|---|
| 完全構造化 | あり | あり | なし | 受入 | 受入 |
| ハイブリッド | あり | あり | あり | 受入 | 受入 |
| 完全非構造化 | なし | なし | あり | 受入 | 拒否 |
番地・建物番号・郵便番号を構造化要素へ移す必要はありません。 に都市名、 に 2 文字の ISO 3166 国コードがあれば十分です。それ以外はアドレス行に残して構いません。これがハイブリッド住所であり、引き続き有効です。
Full detail, with worked examples →
今すぐデータを確認
いずれもブラウザ内で完結する 2 つのツールです。支払データが送信されることはありません。
- 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— passesCBPR-ADDR-001hybrid-valid.csv— passesCBPR-ADDR-001unstructured-invalid.csv— failsCBPR-ADDR-001missing-town-invalid.csv— failsCBPR-ADDR-002missing-country-invalid.csv— failsCBPR-ADDR-003agent-bic-only-valid.csv— passesCBPR-ADDR-005hybrid-valid.csv— passesCHAPS-ADDR-001unstructured-invalid.csv— failsCHAPS-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) | — |
役割別の確認事項
エンジニアリング
- 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-001toCBPR-ADDR-003to 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, notUnited KingdomorGBR—CBPR-ADDR-003fails 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/.