Preparação ISO 20022 para 2026

107 dias até 14 de novembro de 2026, em 2026-07-30.

Nessa data, os endereços postais totalmente não estruturados deixam de ser aceites nas mensagens de pagamento SWIFT CBPR+ e pela biblioteca de validação CHAPS do Banco de Inglaterra. No mesmo dia entram em vigor outras duas alterações, e em novembro de 2027 segue-se um conjunto maior.

Cada regra abaixo tem um identificador, uma data de entrada em vigor, uma fonte autorizada e um ficheiro de teste — nada aqui exige confiança cega.

Isto afeta-o?

Está abrangido se enviar pagamentos CBPR+ ou CHAPS que contenham um endereço postal para qualquer parte.

O que muda realmente

O requisito é um mínimo, não um máximo. É a parte do mandato mais frequentemente mal interpretada.

Formato	TwnNm	Ctry	AdrLine	Antes de 14 nov 2026	A partir dessa data
Totalmente estruturado	Presente	Presente	Ausente	Aceite	Aceite
Híbrido	Presente	Presente	Presente	Aceite	Aceite
Totalmente não estruturado	Ausente	Ausente	Presente	Aceite	Rejeitado

Não é necessário mover a rua, o número do edifício e o código postal para elementos estruturados. Bastam a localidade em e o país em como código ISO 3166 de duas letras. O restante pode permanecer nas linhas de endereço: isso é um endereço híbrido e continua válido.

Full detail, with worked examples →

Verifique os seus dados agora

Duas ferramentas, executadas inteiramente no seu navegador. Nenhum dado de pagamento é transmitido.

• 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.

Ficheiros de teste

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

Todos os marcos, não apenas este

Novembro de 2026 não é o fim das alterações ISO 20022. A partir dessa data a Swift adota um ciclo anual de Standards Release, pelo que as guias de utilização mudarão todos os anos.

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 →

O que verificar, por função

Engenharia

• 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.

Dados

• 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.

Testes

• 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.

Operações

• 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.

Gestão

• 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.

Diferenças entre esquemas

	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

Fontes

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.

Fonte	Editor	Documento	Verificado
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/.