Central Bank Policy and Payments: BoE Delays November RTGS Release

Central banks make some of their most consequential choices about plumbing, not prices. The systems that move money between banks do not attract the attention given to a rate decision, but a change to the format of a payment message can affect thousands of institutions at once. On August 27, 2026, the Bank of England published a short statement that falls into this category: it is delaying what would have been its November 2026 release of standards for the Real-Time Gross Settlement (RTGS) system, a decision that covers the messaging standards for CHAPS payments. The statement is brief, and the reasoning in it is a useful example of central bank policy applied to infrastructure.

What was announced

The statement begins with Swift. On the same day, August 27, Swift announced a decision to delay its November 2026 Standards Release. The reason it gave, as the Bank describes it, was a request from industry for more time to prepare for the removal of the unstructured postal address format, following concerns about global readiness.

After what it called careful consideration, the Bank said it would also delay its own November release. The deferral is complete: the Bank said the November 2026 RTGS standards release will be postponed in its entirety. It noted that this matches Swift’s decision to delay the entire CBPR+ standards release, which is the set of rules for cross-border payments messaging. The Bank said splitting the changes at such a late stage would create challenges and risks for the Bank and for industry.

No new date has been set. The Bank said it will keep talking with Swift, other market infrastructures and RTGS participants about next steps, and will provide broader updates on its web page about implementing ISO 20022, the global payments messaging standard, within CHAPS and RTGS. Those updates will allow organizations to amend their own planning once more detail on revised timelines is available.

The address issue

The change at the center of the delay concerns how a postal address is written into a payment message. An unstructured address places the details in free-text lines, in whatever order and style the sender chooses. A structured address assigns each element, such as town and country, to a defined field. Structured data is easier for systems to validate and screen, and removing the unstructured format is part of the wider move to richer, more consistent payment messages under ISO 20022.

The difficulty is practical. Many customer records store addresses as free text. Converting them to structured form requires changes to systems and, in some cases, to the data itself. The Swift decision, as the Bank reports it, followed concerns about readiness on a global scale.

Why the Bank followed Swift

The Bank’s explanation is built around one principle: global alignment. It said maintaining alignment is important to preserving interoperability and to avoiding new implementation risks, and that it worked closely with Swift and other major market infrastructures to support a coordinated approach.

The logic is straightforward. A payment sent from one jurisdiction to another passes through several systems, each of which must read and write messages in a compatible format. If one system adopts a new standard in November and another does not, institutions must support both versions or risk messages being rejected. A domestic system that moves on its own schedule can strand its participants when their correspondents abroad have not yet changed. By keeping its RTGS release in step with Swift’s, the Bank avoids creating a gap that participants would have to bridge at their own expense.

The Bank also chose to defer everything, not to carry out a partial release. Separating the address change from other items in the release would have required participants to prepare for a revised package close to the planned date. A clean postponement is simpler to explain and to plan around. The statement says as much when it refers to the challenges and risks of trying to separate changes at this late stage.

The episode also shows the dependence of a national system on a private messaging network. Swift’s release calendar sets the rhythm for many of the systems that connect to it. When industry asks Swift for more time, a central bank that operates a connected system has to decide whether to follow, and the Bank’s statement shows it weighed the interoperability benefits of moving together above the benefit of keeping its original date.

What it means for central bank policy

It is easy to treat statements like this as administrative notes. They are better read as a record of how a central bank balances two objectives. One is to modernize payment infrastructure on a predictable timetable, which gives banks and vendors the certainty to invest. The other is to avoid imposing a deadline the industry cannot meet. A credible schedule is one the central bank will move when conditions require, and the Bank has done so here, at a point where proceeding alone would have carried more risk than waiting.

The statement is also a reminder that central bank policy extends to the operation of the settlement system, which the Bank runs. Decisions about RTGS standards apply directly to the Bank’s own infrastructure and to the participants that rely on it. The Bank’s choice to follow, rather than lead, a global message-standard deadline reflects the interdependence of payment systems.

What to watch

Three developments will tell the story from here. The first is the new date for the postponed RTGS release, which the Bank has said it will communicate once the picture is clearer. The second is whether Swift’s revised timetable keeps the same scope or splits the changes into stages. The third is how banks respond to the extra time. If firms use it to clean address data, the delay may produce a smoother transition. If they treat it as a reason to wait, the readiness problem that prompted the postponement will return with the next deadline.

For now, the Bank’s message to participants is to continue planning but to adjust assumptions. The November release is off the calendar, and the replacement date has yet to be set.