What does CBPR+ stand for?

Cross-Border Payments and Reporting Plus: the ISO 20022 usage guidelines for cross-border payments and cash reporting between banks on the Swift network.

When did CBPR+ go live?

In March 2023. MT and ISO 20022 then coexisted until 22 November 2025, when payment instructions between banks moved to ISO 20022 only.

Is CBPR+ the same as ISO 20022?

No. ISO 20022 is the standard that defines the messages. CBPR+ is a usage guideline that restricts those messages for cross-border payments on Swift. A message can be valid ISO 20022 but not valid CBPR+.

Which message replaces the MT103 in CBPR+?

The pacs.008 FI to FI Customer Credit Transfer, sent with a head.001 business application header.

How is a CBPR+ payment rejected?

With a pacs.002 that has transaction status RJCT and a status reason code such as AC01, AC04, AM04 or RC01. After settlement the funds are returned with a pacs.004 instead.

What is the difference between CBPR+ and HVPS+?

CBPR+ covers cross-border payments between banks on Swift. HVPS+ covers payments in high-value payment systems such as real-time gross settlement systems. Both use the same pacs and camt messages with different rules. See the HVPS+ guide.

CBPR+: cross-border payments and reporting on ISO 20022

Written and maintained by ZagTrader. Last reviewed 21 October 2026. How this page is sourced and checked

CBPR+ (Cross-Border Payments and Reporting Plus) is the set of usage guidelines that defines how banks use ISO 20022 messages for cross-border payments and cash reporting on the Swift network. It went live in March 2023, and since 22 November 2025 payment instructions between banks on Swift are sent in CBPR+ ISO 20022 messages rather than MT.

What CBPR+ is

ISO 20022 defines messages with many optional elements so that one message can serve many markets. A usage guideline narrows a message down for one community: which elements are allowed, which become mandatory, which code values may be used and how long text may be. CBPR+ is the usage guideline for the cross-border correspondent banking community on Swift. The guidelines are published in Swift MyStandards.

In practice "a CBPR+ message" means an ISO 20022 message with a business application header (pacs.008 or pacs.009, for example) that follows the CBPR+ rules and travels over Swift. A message can be valid against the ISO 20022 schema and still be rejected because it breaks a CBPR+ rule.

The messages CBPR+ covers

Main CBPR+ messages and the MT messages they replace
ISO 20022	Use	MT it replaces
pacs.008	Customer credit transfer between banks	MT103
pacs.009	Bank-to-bank transfer; the COV form covers a customer payment	MT202, MT202COV
pacs.002	Payment status report, used for rejects	Reject via MT199 or field 72 codes
pacs.004	Payment return	Return via MT103 or MT202 with /RETN/
camt.056	Request to cancel a payment	MT192
camt.029	Answer to a cancellation request or investigation	MT196
camt.053	Statement of account	MT940, MT950
camt.052	Intraday account report	MT942
camt.054	Debit and credit notification	MT900, MT910
head.001	Business application header that travels with every message	Blocks 1 to 3 of the MT header

CBPR+ rules that catch people out

One transaction per message. CBPR+ allows a single transaction in each pacs.008, pacs.009, pacs.002 and pacs.004, so batches of payments are sent as separate messages.
The UETR is mandatory in CdtTrfTxInf/PmtId/UETR and must be passed on unchanged by every bank. Rejects, returns and cancellations refer to it in OrgnlUETR. Check one with the UETR checker.
Rejects are sent as a pacs.002 with status RJCT and a reason code from the status reason code set, for example AC04 or RC01. Returns after settlement use a pacs.004 with a return reason.
Party data is richer than in MT: names, structured postal addresses, account and party identifiers have their own elements. A hybrid postal address (structured town and country plus up to two address lines) was introduced in November 2025. Unstructured addresses were to be removed in November 2026; that change was postponed and unstructured addresses may be used until at least November 2027.
Character set and lengths differ from MT. CBPR+ text can be longer than the MT field it replaces, which is why data can be lost when a CBPR+ message is translated to an MT for a bank that cannot yet read ISO 20022. See truncation in MT translation.

Timeline

Reporting (camt.052, camt.053, camt.054) and the related MT statements are not part of the November 2025 cut-over and continue in both formats for now. See what changed in November 2025.

Key CBPR+ dates
Date	What happened
March 2023	CBPR+ goes live: banks must be able to receive ISO 20022 payment messages; MT and MX coexist.
22 November 2025	End of coexistence for payment instructions: FI-to-FI payment instructions on Swift are delivered only as ISO 20022 messages.
1 January 2026	Swift starts charging for contingency processing, which converts MT103, MT202 and MT202COV sent on FIN into ISO 20022.
Q1 2027 (planned)	Mandate to receive camt.110 for enquiries and investigations, deferred from the November 2026 standards release.
November 2027 (at least)	Unstructured postal addresses and MT101 between banks may continue until at least this date.

A CBPR+ customer payment

The parser on this site has a complete example: a business application header and a pacs.008.001.08 for a USD payment from Dubai to London, the same payment as the MT103 example. Open the pacs.008 page to see it element by element, or paste your own message into the parser.

Questions

What does CBPR+ stand for?: Cross-Border Payments and Reporting Plus: the ISO 20022 usage guidelines for cross-border payments and cash reporting between banks on the Swift network.
When did CBPR+ go live?: In March 2023. MT and ISO 20022 then coexisted until 22 November 2025, when payment instructions between banks moved to ISO 20022 only.
Is CBPR+ the same as ISO 20022?: No. ISO 20022 is the standard that defines the messages. CBPR+ is a usage guideline that restricts those messages for cross-border payments on Swift. A message can be valid ISO 20022 but not valid CBPR+.
Which message replaces the MT103 in CBPR+?: The pacs.008 FI to FI Customer Credit Transfer, sent with a head.001 business application header.
How is a CBPR+ payment rejected?: With a pacs.002 that has transaction status RJCT and a status reason code such as AC01, AC04, AM04 or RC01. After settlement the funds are returned with a pacs.004 instead.
What is the difference between CBPR+ and HVPS+?: CBPR+ covers cross-border payments between banks on Swift. HVPS+ covers payments in high-value payment systems such as real-time gross settlement systems. Both use the same pacs and camt messages with different rules. See the HVPS+ guide.

Messages in this guide

All guides · Troubleshooting