CBPR Plus – Collection 2.

1 FINAL

CBPR+ January 2022 1

Introduction
The following document describes Change
Requests accepted by CBPRplus. These
changes represent essential improvements to the
CBPRplus final usage guidelines, implemented in
the live FINplus service from the Standards
Release of November 2022.
The purpose of this document is to provide
detailed information on the change requests
applied to the Usage Guideline collection
published in March 2021 (often referred to as
CBPRplus collection 2.0).
CBPR+ January 2022
The updated CBPR+ Usage Guideline collection
(CBPRplus collection 2.1) have been published
within the CBPRplus MyStandards group page on
January 21st 2022. These Usage Guidelines can
be recognised with a Usage Id/Business Service
pattern end with .02 (as each Usage Guideline is
impacted by at least one of
the Change Requests described within this
document).
More information on the Usage Id and it
incrementing can be found in the CBPRplus User
HandBook, Business Application Header chapter,
Business Service element.
2
CBPR+ Maintenance 2.1 (Q1 2022) – High Level Category of Change Requests
Category Schema Schema Translation rules Editorial /
Impacted UGs Improvement Simplification Pre-Requesite Clarification
ALL CR#1, CR#2,
CR#10
ALL CR#3
(BAH/Business Service)
pacs.008 CR#4
pacs.009 Core
pacs.009 COV in CTTI and
underlying CCT
pacs.009 ADV
Pacs.008 CR#5
Pacs.008 STP
Pacs.004 CR#6

Camt.053 CR#7, CR#8

Pacs.008 and CR#9

pacs.008 STP

CBPR+ January 2022 3

 Important notice
Each CBPR plus Usage Guideline (UG) is identified using a specific value that is the “Usage identifier”.
This Usage Identifier is also used to populate the element “Business Service” in the Business Application
Header and it follows a specific format that is described in the UHB:

The current version of those Usage Guidelines (UGs) in the CBPR plus Collection 2.0 has been set
to “01” (for example, a pacs.008 has the usage identifier “swift.cbprplus.01”. The same value is to
be populated for the element “Business Service” in the BAH.

This value is incremented when the Usage Guideline is updated, therefore considering that ALL
CBPR Plus Usage Guidelines will be updated for the CBPR plus Collection 2.1, this version of the
Usage Identifier will be incremented to “02”.
CBPR+ January 2022 4
Business Application Header – Business Service
Message Definition Identifier Business Service
pain.001.001.09 swift.cbprplus.02
pain.002.001.09 swift.cbprplus.02
pacs.002.001.10 swift.cbprplus.02
pacs.004.001.09 swift.cbprplus.02
pacs.008.001.08 swift.cbprplus.02
pacs.008.001.08 (STP/STP EU) swift.cbprplus.stp.02
pacs.009.001.08 (advice) swift.cbprplus.adv.02 Usage Identifier value per CBPR plus
pacs.009.001.08 (core) swift.cbprplus.02 message type
pacs.009.001.08 (cov) swift.cbprplus.cov.02
pacs.010.001.03 swift.cbprplus.02
camt.029.001.09 swift.cbprplus.02
camt.052.001.08 swift.cbprplus.02
camt.053.001.08 swift.cbprplus.02
camt.054.001.08 swift.cbprplus.02
camt.056.001.08 swift.cbprplus.02
camt.057.001.06 swift.cbprplus.02
camt.060.001.05
CBPR+ January 2022 swift.cbprplus.02 5
 Change Requests – Usage Guidelines

CBPR+ January 2022 6

Change request impacting all Usage Guidelines (except pain.001, pain.002 and pacs.008 STP) –
Editorial Changes
CR # Impacted Element Change Description

1 Only the Description box Existing textual recommendation

(see illustration on next slide) "If BIC is absent, (Name & Postal Address) or ClearingSystemMemberIdentification must be present
and both are allowed together."

-> Should be replaced by below textual rule:

If BIC is absent, (Name & Postal Address) OR [(Name & Postal Address) and
ClearingSystemMemberIdentification] must be present.
Exception: If BIC is absent, whenever Debtor Agent, Creditor Agent and all agents in between are
located within the same country, the clearing code only may be used.

CBPR+ January 2022 7

CBPR+ January 2022 8
Change request impacting all Usage Guidelines - Editorial Changes

CR # Impacted Element Change Description

2 All rules Review ALL rules and make sure that they are correctly named (aligned with UHB
description):

Formal Rules should be suffixed with "FormalRule"

eg, CBPR_Instruction For Creditor Agent1_FormalRule

Textual Rules should be suffixed with "TextualRule"

eg CBPR_LocalInstrument_TextualRule

Guidelines should be suffixed with “Guideline”

Eg: CBPR_Purpose_Guideline

CBPR+ January 2022 9

Change request impacting all Usage Guidelines - Schema Improvement
CR # Impacted Element Change Description

3 BAH/Business Service Add a pattern for element Business Service

Illustration on next slide

+ Textual rules will be revised to reflect the increment usage identifier.

CBPR+ January 2022 10

 New Data Type will be created with below pattern and will
be applied to fields “Business Service” in BAH and
Related BAH
[a-z0-9]{1,10}\.([a-z0-9]{1,10}\.)+\d\d

CBPR+ January 2022 11

Change request impacting pacs.008, 009 Core, 009 COV and 009 ADV - Schema Improvement

CR # Impacted Element Change Description

4 Instruction for Next Agent/Instruction  Change the number of occurrences of the element “Instruction For next Agent” from (0..4)
Information -> (0..6)

 Change the Data Type of element “Instruction Information” to allow maximum max 35
characters (instead of max 140 characters)

Illustration on next slide

CBPR+ January 2022 12

CBPR+ January 2022 13
Change request impacting pacs.008 and pacs.008 STP - Schema Improvement

CR # Impacted Element Change Description

5 RemittanceLocationDetails/PostalAddress/AddressLine  Correct Data Type from "CBPR_RestrictedFINXMax35Text" to

"CBPR_RestrictedFINXMax35Text_Extended“

Illustration on next slide

CBPR+ January 2022 14

CBPR+ January 2022 15
Change request impacting pacs.008 and pacs.008 STP - Schema Improvement

CR # Impacted Element Change Description

9 Charge Bearer/DEBT Add cross element rule to limit the number of occurrences to 1 of “Charge
Charge Information Information” if Charge Bearer Code = DEBT

Illustration on next slide

CBPR+ January 2022 16

 Formal Rule:

If Charge Bearer/Debt is present,

then only one occurrence of
“Charge Information” is allowed

CBPR+ January 2022 17

Change request impacting pacs.004 - Schema simplification

CR # Impacted Element Change Description

6 Original Message Name Identification
Return Chain
Original Transaction Reference
 Remove ALL rules created for element “Original Message Name Identification”
as those rules are creating issues (in some specific scenario)
 ONLY the rule "OriginalMessageNameIdentificationRule" will be kept as that
one is correct

Illustration on next slide

CBPR+ January 2022 18

 OK

CBPR+ January 2022 19

Change request impacting camt.053 - Translation rules Pre-Requesite

CR # Impacted Element Change Description

7 Statement Pagination/Page Number and Last page Addition of Formal Rules to reflect the below:
Indicator
 IF PageNumber = 1 then there must be one and only one occurrence of
Statement/Balance/Type/CodeOrProprietary/Code Balance/Type/CodeOrProprietary/Code with value "OPBD" and if
Balance/Type/SubType/Code is present, value must be different from
Statement/Balance/Type/ "INTM“
SubType/Code
 IF PageNumber > 1 then there must be one and only one occurrence of
Balance/Type/CodeOrProprietary/Code with value "OPBD" and with
Balance/Type/SubType/Code = "INTM

Illustration on slide 22

CBPR+ January 2022 20

Change request impacting camt.053 - Translation rules Pre-Requesite

CR # Impacted Element Change Description

7 Statement Pagination/Page Number and Last page Addition of Formal Rules to reflect the below:
Indicator
 IF LastPageIndicator is "True" then there must be one and only one
Statement/Balance/Type/CodeOrProprietary/Code occurrence of Balance/Type/CodeOrProprietary/Code with value "CLBD" and
if Balance/Type/SubType/Code is present, value must be different from
Statement/Balance/Type/ "INTM“
SubType/Code
 IF LastPageIndicator is "False" then there must be one and only one
occurrence of Balance/Type/CodeOrProprietary/Code with value "CLBD" and
with Balance/Type/SubType/Code = "INTM“

 Maximum 1 occurrence of Balance/Type/CodeOrProprietary/Code with value

"CLAV" is allowed

Illustration on next slide

CBPR+ January 2022 21
 Current Formal rules will be replaced by the 5
Formal rules described on slide 20 and 21

CBPR+ January 2022 22

Change request impacting camt.053 - Translation rules Pre-Requesite

CR # Impacted Element Change Description

8 Legal Sequence Number Addition of Formal Rules to reflect the below:

Electronic sequence Number
Either “Legal Sequence Number” or “Electronic Sequence Number” must be
present for translation purposes (field 28C in MT 940)

Illustration on next slide

CBPR+ January 2022 23

 Formal Rules will be added to mandate one of the
two fields to be present (and both are allowed)

CBPR+ January 2022 24

Change request impacting ALL or some Usage Guidelines - Editorial Changes

CR # Impacted Element Change Description

10 Related BAH/ Business Service Removal of the rule “CBPR_BusinessService_Usage” since irrelevant for that field
(ALL UGs)

Cancellation Status Reason Information/Originator Removal of the rule “Rule "CBPR_Originator_Presence_Rule” as it was
(camt.029 ONLY) contradictory with the ISO definition for this element

Instruction for Creditor Agent/ Instruction Information Addition of a textual rule to provide guidance for the usage of the code /UDLC/
(pacs.009 [core] ONLY) (Underlying Creditor) in the field “Instruction for Creditor Agent/ Instruction
Information” (when the pacs.009 is used to settle of a previously sent pacs.009
Advice):

“If the pacs.009 is used to settle a pacs.009 Advice, the last available occurrence
preceded by /UDLC/ must be used to capture the /UDLC/ (Underlying Creditor)
provided in the pacs.009 ADV.”

CBPR+ January 2022 25