Presentation will begin at 12:00GMT

If you cannot hear us via WebEx / computer audio

you may need to dial-in using a phone

Global Vendor Webinar

Transaction Management

Partner Programme / Vendor Readiness

January 2022
Admin notices

▪ This presentation is being recorded

▪ The content will be published on SWIFT.com (https://www.swift.com/transaction-management-
vendors)
▪ Global vendor webinars occur the last Thursday of every month and you can register for future
events on SWIFT.com here: Transaction Management Global Vendor Webinar
▪ Please email any questions to transaction.mgmt.vendor.support@swift.com
▪ To ensure you receive communications from us while we remain GDPR compliant please update
your preferences here (you will need to login to / create your free SWIFT account) to include the
interests ‘Payments’ and/or ‘Standards’ and we will ensure we keep you informed about:
▪ Global Vendor Webinar Invitations
▪ Relevant developments on ISO 20022 and Transaction Management
▪ Updates from SWIFT’s Market Practice team
▪ The latest info on adoption enabling tools and support

Transaction Management - Global Vendor Webinar 2

Agenda

1. Recap: where to go for everything you need to know

2. Key updates re: transaction management, in-flow translation, and ISO 20022
3. ISO 20022 CBPR+ usage guidelines v2.1
4. Close

Transaction Management - Global Vendor Webinar 3

Transaction Management for Vendors Webpage

Dedicated page on SWIFT.com detailing all the

important information, links, tools, and support

https://www.swift.com/transaction-management-vendors

Transaction Management - Global Vendor Webinar 4

SWIFT Platform Evolution Support Page

Comprehensive Knowledge Centre

page detailing everything you need to
know about Transaction Management,
in-flow translation, and much more…

https://www2.swift.com/knowledgecentr
e/subjects/swift_platform/index.html

Transaction Management - Global Vendor Webinar 5

ISO 20022 Adoption Support Page

Comprehensive Knowledge Centre

page detailing everything you need to
adopt ISO 20022 and FINplus.

https://www2.swift.com/knowledgecentr
e/subjects/iso_20022_adoption/index.ht
ml?src=sw_platform_sp

Transaction Management - Global Vendor Webinar 6

− Key updates re: transaction management,
in-flow translation, and ISO 20022

Transaction Management - Global Vendor Webinar 7

ISO 20022 CBPR+ v2.1

• At the end of January 2022, the CBPR+ v2.1 usage guidelines will be
published on the MyStandards CBPR+ landing page
• CBPR+ v2.1 will be deployed on the Integration Testbed and FINplus pilot
services on 28th February 2022
• All third-party providers must adhere to the latest version (v2.1) for go-live
on FINplus Live in November 2022

Connectivity pack

The Connectivity Pack has been updated to include FINplus bandwidth analysis

Transaction Management - Global Vendor Webinar 8

Bank and FI BIC Mass provisioning

All eligible BICs are being provisioned on FINplus. For more information, including which BICs are eligible,
there is a Knowledge Base Tip: Centrally administered mass provisioning exercise on the FINplus Pilot
Future service. For further detailed information please see the ISO 20022 Customer Adoption (swift.com)
page.

Testing
• Vendors are recommended to further prepare for the SWIFT platform
evolution with their customers by reviewing the Customer Testing Guidelines,
published on swift.com. This document is intended for the SWIFT community
preparing for ISO 20022 adoption and aims at providing comprehensive
customer testing guidelines for ISO 20022 CBPR+, and for assessing customer
readiness for the SWIFT platform evolution in November 2022. More info can
be found on the SWIFT Platform Evolution Support Page
• Vendors can continue to apply for provisioning on the FINplus Future
Integration Testbed (ITB) to test in-flow translation using the e-forms on the
ITB ordering page
Transaction Management - Global Vendor Webinar 9
Messaging interface specifications
All messaging interface providers must adhere to the vendor specifications shared in vendor letters VL/032021 & VL/082021. These include, but are not limited to,
the specifications for:
I. Receiving messages from SWIFT's transaction manager i.e.:
i. There is no change in the requirements for creating signatures or sending traffic, where the messaging interface must make sure that an HSM
certificate with the appropriate CertPolicyId is used. Those requirements can be found in the Service Design Guide.
ii. For Signatures received there are no mandatory requirements, unless the messaging interface implements additional checks during the
verification of a Signature. In this case the following requirements apply in case of a Signature containing a DigestRef equal to "TRD" and a
SignDN ending on "o=swift, o=swift":
• No check on the DigestValue of the Reference with DigestRef equal to "TRD"
• No validation on the SignDN
• No validation on the CertPolicyId
II. SWIFTNet Messaging In-flow Translation Integration i.e.: the mandatory features to be implemented when receiving an ISO 20022 message including a
translated MT are:
i. Validate the "Translated MT" DigestValue to be the same as the digest on the translation as per the specifications
ii. Pass the translation result code together with the translated MT whenever this is provided outside of the messaging interface. An alternative
option to provide the translation result is to be able to route traffic flows based on the translation result, so that the application may be
protected from unacceptable translation results. The recommended approach is to both passing the translation result when possible, and the
ability to route on the translation result code.
Important note: Messaging interface providers must refer to Vendor Letters (VL/032021 & VL/082021) for the full specifications

Transaction Management - Global Vendor Webinar 10

Compliance timelines

• By March 2022, messaging interfaces must be compliant with the latest SWIFT Compatible Interface
specifications, which includes being able to receive and process multi-format MX messages.
• By June 2022, service bureaux must comply with the latest Shared Infrastructure Programme, and
security controls framework, terms and conditions. This includes upgrading their SWIFT messaging
interface to a compliant version that supports multi-format MX handling.

Transaction Management - Global Vendor Webinar 11

CBPR Plus – Collection 2.1 FINAL

CBPR+ December 2021 12

Introduction

The following document describes Change The updated CBPR+ Usage Guideline collection
Request accepted by CBPRplus. These changes (CBPRplus collection 2.1) will be published within
represent essential improvements to the the CBPRplus MyStandards group page by the
CBPRplus final usage guidelines, implemented in end of January 2022. These Usage Guidelines
the live FINplus service from the Standards can be recognised with a Usage Id/Business
Release of November 2022. Service pattern end with .02 (as each Usage
The purpose of this document is to provide Guideline is impacted by at least one of
advance notice of an updated collection of the Change Requests described within this
CBPR+ Usage Guideline allowing the industry to document).
analyse the details and plan for the changes More information on the Usage Id and it
applied on top of the Usage Guideline collection incrementing can be found in the CBPRplus User
published in March 2021 (often referred to as HandBook, Business Application Header chapter,
CBPRplus collection 2.0). Business Service element.

CBPR+ December 2021 13

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+ December 2021 14

 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+ December 2021 15
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+ December 2021 swift.cbprplus.02 16
 Change Requests – Usage Guidelines

CBPR+ December 2021 17

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+ December 2021 18

CBPR+ December 2021 19
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+ December 2021 20

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+ December 2021 21

 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+ December 2021 22

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
Information (0..4) -> (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+ December 2021 23

CBPR+ December 2021 24
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+ December 2021 25

CBPR+ December 2021 26
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+ December 2021 27

 Formal Rule:

If Charge Bearer/Debt is present,

then only one occurrence of
“Charge Information” is allowed

CBPR+ December 2021 28

Change request impacting pacs.004 - Schema simplification

CR # Impacted Element Change Description

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

Illustration on next slide

CBPR+ December 2021 29

 OK

CBPR+ December 2021 30

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+ December 2021 31

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
Statement/Balance/Type/ from "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+ December 2021 32
 Current Formal rules will be replaced by the 5
Formal rules described on slide 20 and 21

CBPR+ December 2021 33

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+ December 2021 34

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

CBPR+ December 2021 35

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
(ALL UGs) field

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+ December 2021 36

If you have any questions, please contact your account manager
www.swift.com

or contact us at transaction.mgmt.vendor.support@swift.com