Preparación ISO 20022 para 2026
107 días hasta el 14 de noviembre de 2026, a 2026-07-30.
En esa fecha, las direcciones postales totalmente no estructuradas dejarán de aceptarse en los mensajes de pago SWIFT CBPR+ y en la biblioteca de validación CHAPS del Banco de Inglaterra. Ese mismo día entran en vigor otros dos cambios, y en noviembre de 2027 llega un conjunto mayor.
Cada regla siguiente lleva un identificador, una fecha de entrada en vigor, una fuente autorizada y un juego de pruebas: nada aquí exige confianza.
¿Le afecta?
Le afecta si envía pagos CBPR+ o CHAPS que contengan una dirección postal para cualquier parte.
| Mensajes | pacs.008, pacs.009, pacs.004, pacs.003 |
| Partes | Debtor, creditor, ultimate debtor, ultimate creditor, and agents that carry an address |
| Fuera del alcance | admi.024, camt.025, camt.052, camt.053, camt.054, camt.060 |
| Exentos | Agents identified by BIC alone need no postal address (CBPR-ADDR-005) |
Qué cambia realmente
El requisito es un mínimo, no un máximo. Es la parte del mandato que más se malinterpreta.
| Formato | TwnNm | Ctry | AdrLine | Antes del 14 nov 2026 | A partir de esa fecha |
|---|---|---|---|---|---|
| Totalmente estructurada | Presente | Presente | Ausente | Aceptada | Aceptada |
| Híbrida | Presente | Presente | Presente | Aceptada | Aceptada |
| Totalmente no estructurada | Ausente | Ausente | Presente | Aceptada | Rechazada |
No es necesario trasladar la calle, el número de edificio ni el código postal a elementos estructurados. Basta con la localidad en y el país en como código ISO 3166 de dos letras. El resto puede permanecer en las líneas de dirección: eso es una dirección híbrida y sigue siendo válida.
Full detail, with worked examples →
Compruebe sus datos ahora
Dos herramientas, ejecutadas íntegramente en su navegador. No se transmite ningún dato de pago.
- 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.
Juegos de prueba
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
Todos los hitos, no solo este
Noviembre de 2026 no es el final de los cambios de ISO 20022. Swift adopta un ciclo anual de Standards Release a partir de esa fecha, por lo que las guías de uso cambiarán cada año.
| 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) | — |
Qué comprobar, por función
Ingeniería
- 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.
Datos
- 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.
Pruebas
- 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.
Operaciones
- 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.
Dirección
- 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.
Diferencias 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 |
Fuentes
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.
| Fuente | 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/.