CBPR+: ISO 20022 for cross-border payments

L0 Explain simply

Analogy: ISO 20022 is a language with an enormous vocabulary — rich enough to describe almost any financial event. If every bank used it freely, messages would be grammatically correct but wildly inconsistent, like essays written in completely different styles. CBPR+ is the agreed house style for one specific readership: banks sending payments to each other across borders. It says which words to use, which to avoid, and how long each section may be, so any correspondent can process any other correspondent's message without a phrasebook. High-value payment systems wrote a matching house style, called HVPS+, so a payment crossing both worlds does not need rewriting at the border.

ISO 20022

L1 Core concepts

CBPR+ stands for Cross-Border Payments and Reporting Plus: a set of usage guidelines that take base ISO 20022 messages and restrict them for correspondent banking traffic exchanged over the SWIFT network. A usage guideline works by subtraction: it removes optional elements, tightens lengths and code lists, and pins the exact message versions in scope. HVPS+ (High Value Payments Plus) is the sister initiative for market infrastructures — the RTGS and other high-value systems — so that domestic settlement legs and correspondent legs stay aligned. Both routing models are covered: serial routing with pacs.008 passing hop by hop, and cover routing with a pacs.008 travelling directly while a pacs.009 COV carries the funding between correspondents.

CBPR+HVPS+Serial paymentCover payment

L2 Practitioner view

For the MT generation, this is the replacement world: the MT–MX coexistence period for cross-border payment instructions on SWIFT ended in November 2025, and the MT payment categories were retired from that traffic in favour of the CBPR+ messages. Working under CBPR+ means version discipline (the guideline names the exact message versions in force), element discipline (data your channel captured may have no compliant home if the guideline excludes it), and route awareness: one payment often traverses both CBPR+ correspondent legs and HVPS+-aligned market infrastructure legs. The two guideline families are deliberately close but not identical, so the interesting defects live in the gaps — an element one leg carries that the other constrains more tightly.

MT messageRTGS

L3 Technical details

Details that surface in real work: the Business Application Header's business service element declares which CBPR+ guideline a message claims to follow, and gateways validate against it. Character set rules are tighter than generic XML for many elements, so names in other scripts must be transliterated before they enter the message. The UETR is mandatory end to end, which is what makes cross-border tracking workable. For sanctions screening, CBPR+ structure is a genuine gain — a debtor's country sits in a labelled element rather than a free-text address line — but only where originators actually populate structured fields, and the guidelines have been tightening address rules over time to force that. Screening systems, in turn, had to be re-tuned from MT line numbers to XML paths, a migration many institutions found harder than the format change itself.

Business Application HeaderUETRTransliterationScreening

L4 Standards & sources

The normative texts are the CBPR+ usage guidelines themselves, published and versioned on SWIFT's MyStandards platform: element-level rules, code lists, and the in-force version schedule live there, not in summaries like this one. The HVPS+ guidelines are maintained by a task force of high-value payment system operators and published as market practice that individual infrastructures adapt to their own rules. Two verification habits follow. First, confirm which guideline version is currently in force before relying on any element-level rule, because versions change with the annual standards release cycle. Second, remember that an individual market infrastructure may deviate from HVPS+ in documented ways, so the infrastructure's own specification wins on its leg. Our description simplifies both families to their shared intent.