Delay to the November 2026 RTGS standards release
AI Analysis
On 2026-08-27, the Bank of England deferred the entire November 2026 RTGS standards release, including CHAPS messaging standards, following Swift’s decision to delay its corresponding Standards Release 2026. The immediate reason is industry concern about global readiness for removing fully unstructured postal addresses; the revised timetable has not been announced, so firms must replan while preserving interoperability and avoiding parallel implementation risks.
Key dates
- 2026-08-27
- The Bank of England announced deferral of the entire November 2026 RTGS standards release, including CHAPS messaging standards; Swift announced the corresponding Standards Release delay on the same date.
- 2026-12-31
- Swift has indicated that it will provide an update on the optimal timing and approach for the structured-address change by December 2026 at the latest; this is an expected communications milestone, not a confirmed implementation deadline.
Suggested considerations
- Firms should update regulatory-change inventories and project plans to record that the November 2026 RTGS and CHAPS standards release has been deferred, without assuming that the change has been cancelled.
- CHAPS and RTGS participants should obtain the BoE’s revised implementation timetable and monitor the BoE ISO 20022 implementation page, participant communications and Swift governance updates, including the expected update by December 2026 at the latest.
- Compliance and payments teams may wish to preserve completed analysis and technical preparations for structured or hybrid postal addresses, while reassessing sequencing, testing windows, release dependencies and vendor delivery dates against the revised timetable.
- Firms should distinguish the deferred BoE/CHAPS release from any other payment-system or bilateral requirements that may continue on their original schedules, and should confirm the treatment of address validation, message rejection, exception handling and operational support with relevant counterparties and vendors.
- Technology and operations teams should maintain regression-test environments and data-quality remediation plans so that implementation can resume without restarting discovery or delaying future mandatory testing.
- Firms using both CHAPS/RTGS and Swift CBPR+ should assess whether the coordinated deferral changes their customer communications, correspondent-bank testing, operational-resilience scenarios, payment-routing controls and incident-management assumptions.
- Governance committees may wish to record the deferral as a schedule and dependency change rather than as a reduction in scope, because the BoE states that the November release is deferred in its entirety and provides no indication that the underlying standards work is withdrawn.
What changed
The November 2026 RTGS standards release will not proceed as originally planned and has been deferred in its entirety rather than being split into separate changes. This includes the RTGS messaging standards applicable to CHAPS payments. The decision maintains alignment with Swift’s deferred CBPR+ release and means that the previously expected 2026-11-14 removal of fully unstructured postal addresses should not be treated as the operative BoE/Swift implementation date; Swift has indicated that it will consult market participants and provide an update by December 2026 at the latest. No replacement RTGS or CHAPS release date, new mandatory address date, or revised implementation specification has yet been published by the BoE.
Compliance impact
The publication does not create a new binding obligation or enforcement deadline; it changes the implementation timetable for a major payment-message standard and reduces the immediate risk of incompatible or prematurely separated BoE and Swift changes. The practical impact remains material for CHAPS and cross-border payment operations because industry commentary indicates that fully unstructured
Who is affected
Related regulations
References
AI-generated analysis. May contain errors or omissions — verify with the original BoE source before acting. Full disclaimer.
What the BoE said
Bank of England statement
Published by BoE . Read the full notice at the source for the authoritative text.