BoE Delays November 2026 RTGS Standards Release: CHAPS Roadmap Reset

The Bank of England will not run its November 2026 RTGS standards release. On 27 August 2026 the Bank confirmed it is deferring that release in its entirety, including the messaging standards for CHAPS payments, after Swift announced its decision to delay the November 2026 Swift Standards Release. For any CHAPS direct participant that had a November 2026 go-live in its integration plan, that date is no longer the implementation date. No revised go-live date has been confirmed; the Bank will provide updates at its ISO 20022 implementation page as further detail on revised timelines becomes available, and it is asking organisations to monitor that page for updates.

The trigger sits upstream. Swift announced the delay to the November 2026 Swift Standards Release, with the Bank of England characterising this as Swift delaying the entire CBPR+ standards release. The BoE noted that industry had requested more time to prepare for the removal of the unstructured postal address format following concerns about global readiness. The Bank has chosen to move in step rather than press ahead alone, on the reasoning that keeping the UK aligned with the global messaging change preserves interoperability and avoids introducing fresh implementation risk at a late stage.

Related reading: G20 Cross-Border Payments Targets 2027, which sets out why harmonised ISO 20022 messaging sits at the centre of the cross-border programme this change belongs to.

The dates that moved, and the one that has not been set

This is a calendar change first and foremost, so the calendar is the place to start.

• June 2023: CHAPS moved to ISO 20022 messaging, the foundation the later enhanced-data steps build on.
• 1 May 2025: For payment-initiation channels within each CHAPS direct participant’s control, LEIs became mandatory for payments between financial institutions, and purpose codes became mandatory for payments between financial institutions and for property transactions.
• November 2025: hybrid postal addresses were enabled in CHAPS and fully structured addresses continued to be encouraged; no structured-address mandate took effect then. Structured remittance was not mandated. Separately, the Bank operates an annual change-management process for CHAPS and RTGS schemas and technical guidance, with technical changes normally implemented in November.
• 14 November 2026: the date on which Swift’s CBPR+ release would have stopped accepting fully unstructured postal addresses. This is the release now being delayed.
• November 2026: the Bank’s aligned RTGS standards release, now deferred in its entirety.
• Revised timeline: no final date has been confirmed. The Bank will provide updates at its ISO 20022 implementation page as further detail on revised timelines becomes available.

No final replacement go-live date has been confirmed. The Bank has said it will provide updates at its ISO 20022 implementation page as further detail on revised timelines becomes available; internal plans should not assume any specific date until the Bank confirms the revised schedule.

What the deferred RTGS standards release actually covered

The release in question is the Bank’s annual RTGS standards release, the vehicle through which CHAPS message schemas and technical guidance are updated each November. The 2026 edition was aligned to Swift’s CBPR+ release, the cross-border payments and reporting profile that governs how banks exchange ISO 20022 payment messages across the Swift network. Because the two were designed to land together, the Bank has deferred the whole 2026 release rather than carve out individual elements.

The Bank was explicit about that choice: separating changes at this late stage would have created risk for both the Bank and industry, so the release moves as a single package. Read that as a reason not to assume that any one component, a schema tweak here or a validation change there, might still ship on the original date. The Bank has said the release is deferred in full.

One point worth stating plainly: the Bank has paused the November 2026 release without abandoning the underlying direction of travel toward structured, enhanced ISO 20022 data. The changes are expected to return on a revised timeline the Bank will set.

Why the release moved: Swift, CBPR+ and the unstructured address

The headline change inside the November 2026 Swift release was the removal of unstructured postal addresses from CBPR+ payment messages. From the planned go-live, payment messages would have needed a fully structured or hybrid address, with town and country provided in dedicated fields at a minimum, and fully unstructured addresses would have been rejected at the network level with no contingency route.

The obstacle was readiness. Swift’s own tracking through 2026 showed that a large share of payment messages still carried unstructured address data, well short of the target of zero. Faced with that gap, Swift accepted the industry case for more time and is delaying the release rather than enforce a rejection rule against a community that is not ready. The Bank of England noted it had worked closely with Swift and other major market infrastructures to support a co-ordinated approach. European wholesale systems are sequencing their own ISO 20022 work on parallel timelines, as our coverage of the ECB T2 extended hours roadmap shows. The mechanism practitioners should register here is a simple one: a UK RTGS date slipped because a global Swift date slipped.

What stays mandatory in CHAPS while the release waits

Reading the deferral as a general pause on ISO 20022 obligations misses what the announcement actually says. The enhanced-data requirements already mandatory in CHAPS remain in force through the delay.

The live May 2025 mandates are LEIs for payments between financial institutions and purpose codes for payments between financial institutions and for property transactions, in each case for payment-initiation channels within the CHAPS direct participant’s control. Hybrid and fully structured addresses are available, but the planned technical rejection of fully unstructured CHAPS addresses was part of the deferred November 2026 release. Structured remittance is not currently mandated; CHAPS direct participants should ensure their systems can process CHAPS payments that include structured remittance data fields. A firm that reads the November 2026 delay as licence to relax data quality on live CHAPS traffic would be working against rules that are already live. The deferral touches the next release, not the current rulebook.

The Bank’s 18-month notice commitment applies to policy expansions of mandatory enhanced-data requirements, not to MyStandards schema changes. Technical schema and guidance changes follow the separate annual change-management process. For the deferred release, no revised go-live date has been confirmed; the Bank will publish updated timelines at its ISO 20022 implementation page.

What participants and vendors should do now

The practical work is roadmap hygiene alongside continued readiness work; the practical action is to watch the Bank’s ISO 20022 pages and keep readiness work in flight given the direction of travel is unchanged. Firms already managing other fixed market-infrastructure deadlines, such as the UK move to T+1 settlement, can treat this as one fewer competing November date for the moment. A short set of actions covers most CHAPS direct participants and the vendors who supply their payment engines.

• Remove the November 2026 RTGS release from live delivery plans and reclassify it as pending a Bank-confirmed date, so downstream dependencies do not silently assume the old go-live.
• Keep any structured-address and CBPR+ readiness work already in flight, since the direction has not changed and the readiness gap is exactly what caused the delay.
• Continue testing and vendor-readiness work for structured and hybrid addresses.
• Monitor the Bank’s ISO 20022 pages for CHAPS and RTGS, where it has said revised timelines and next steps will be published.

The one thing to avoid is building delivery plans around an assumed date before the Bank confirms the revised schedule. Watch the Bank’s ISO 20022 pages for the confirmed revised go-live.

Frequently Asked Questions

Does the delay change the enhanced data already mandatory in CHAPS?

The May 2025 LEI and purpose-code mandates remain in force for payment-initiation channels within the CHAPS direct participant’s control. Structured addresses and structured remittance are not currently mandatory CHAPS requirements: the planned rejection of fully unstructured addresses was part of the deferred November 2026 release, and structured remittance is not currently mandatory in CHAPS; the Bank’s published policy on expanded enhanced-data requirements is set out at its ISO 20022 implementation page.

Is there a new go-live date for the RTGS standards release?

No final date has been confirmed. The Bank has said it will provide updates at its ISO 20022 implementation page as further detail on revised timelines becomes available. Internal plans should not lock in any specific date until the Bank publishes a confirmed replacement go-live.

Can we still ship part of the release, such as a schema or validation change, on the original date?

The Bank has deferred the release as a single package and stated that separating changes at this late stage would create risk for the Bank and industry. On that basis a partial November 2026 go-live is not the intended path; the components move together on the revised timeline.

Related Articles

• G20 Cross-Border Payments Targets 2027: why ISO 20022 harmonisation underpins the cross-border payments programme this release sits within.
• ECB T2 Extended Hours Roadmap for European Banks: an adjacent wholesale settlement-infrastructure change and how banks sequence the operational work.
• UK T+1 Settlement 2027 and FCA Readiness: managing a fixed market-infrastructure go-live and the readiness milestones that surround it.
• SEPA Instant Payments Regulation: another jurisdiction’s push toward structured data and payee verification in ISO 20022 messaging.
• Payments Vision Delivery Committee and UK Retail Payments Infrastructure: the wider UK payments strategy that frames RTGS and CHAPS modernisation.

Key Takeaways

• The Bank of England is deferring its November 2026 RTGS standards release in its entirety, including CHAPS messaging standards, as confirmed on 27 August 2026.
• The trigger is Swift’s decision to delay the November 2026 Swift Standards Release, which the Bank characterises as the entire CBPR+ standards release being deferred, including the structured-address change scheduled for 14 November 2026.
• No final revised go-live date has been confirmed; the Bank will publish updates on revised timelines at its ISO 20022 implementation page.
• The release is deferred as one package, so no component should be assumed to ship on the original date.
• The May 2025 LEI and purpose-code mandates remain in force for payment-initiation channels within CHAPS direct participants’ control. The November 2026 rejection of fully unstructured addresses is deferred, and structured remittance is not currently mandated.
• Practitioners should keep structured-address readiness work moving and watch the Bank’s CHAPS and RTGS ISO 20022 pages for the revised schedule.

Sources and References

• Bank of England, “Delay to the November 2026 RTGS standards release” (statement, published 27 August 2026): bankofengland.co.uk/news/2026/august/delay-to-the-november-2026-rtgs-standards-release
• Bank of England, “Expanding mandatory ISO 20022 enhanced data in CHAPS from 2027” (policy statement, 2025): bankofengland.co.uk/paper/2025/ps/expanding-mandatory-iso-20022-enhanced-data-in-chaps-from-2027
• Swift, Standards Release 2026 delay announcement (August 2026), referenced via Bank of England statement of 27 August 2026; Swift announcement not independently fetched at time of writing (host timeout).
• Swift, “ISO 20022 milestone for November 2026: Unstructured addresses to be removed”: swift.com/news-events/news/iso-20022-milestone-november-2026-unstructured-addresses-be-removed
• Swift, “Unstructured address data is being removed. Are you ready?”: swift.com/standards/iso-20022/removal-unstructured-address
• Bank of England, “Mandating ISO 20022 enhanced data in CHAPS” (policy statement, 2024): bankofengland.co.uk/paper/2024/policy-statement/mandating-iso-20022-enhanced-data-in-chaps
• Bank of England, “CHAPS transitions to latest global financial messaging standard” (June 2023): bankofengland.co.uk/news/2023/june/chaps-transitions-to-latest-global-financial-messaging-standard

Holding the November date open

The safe read of this announcement is narrow and specific: one annual release has slipped so the UK stays aligned with a global Swift change, while everything already mandatory in CHAPS keeps running. The action it demands is equally specific. Remove November 2026 as the implementation date, keep structured-address readiness moving, and watch the Bank’s ISO 20022 pages for the confirmed revised go-live date.

Disclaimer: The information on RegReportingDesk.com is for educational and informational purposes only. It does not constitute legal, regulatory, tax, or compliance advice. Always consult your compliance officer, legal counsel, or the relevant supervisory authority for guidance specific to your institution.