9/28/21, 5:26 PM
Cbpr/Samples
CBPR+ Sample Messages
This site provide sample test messages for the Cross Border Payments & Reporting (CBPR+) market practice. It includes two sample message sets to test:
Section 1 - Use Cases described in the CBPR+ User Handbook (res/cbpr/ISO_20022_Programme_UHB_Q4_2020_Edition_v1.0.pdf)
Section 2 - Cross-element rules in the market practice
The documentation below describes the purpose of the sample messages, and example of a use case or complex business rule and an inventory of messages. If you have any questions
you can contact SWIFT Support.
Download
CBPR+ User Handbook Sample Messages (res/cbpr/samples/UseCaseSampleMessages_2021Q2_1.zip)
Download
Cross Element Rules Sample Messages (res/cbpr/samples/CBPR_CROSS_ELEMENT_RULES_SAMPLES_2020Q4.zip)
1. CBPR+ User Handbook Sample Messages
Introduction
The purpose of the following CBPR+ sample messages is to facilitate application testing and to provide a further understanding of the structure of ISO 20022 messages. This selection of
samples is arranged in order of the Use Cases illustrated in the CBPR+ User Handbook, available from the CBPR+ landing page. Each zip file aligns to the Use Case, and contains the
message samples and a pdf document which explains the context and flow of the Use Case.
The naming convention is as follows: CBPR+ UseCaseNumber.MessageType.xxx_VersionDate.XML
Each sample message xml file is encapsulated with an envelope. The message will work “as is” in the Readiness Portal. It is essential that users remove the envelope and replace it with
their own transport header (for example for Alliance Access you would use the XML v2 headers).
The change log has been included in each sample message xml file in the comments section.
You will need an xml viewer or editor to view the xml file, such as NotePad, NotePad++ or you can use a web browser. The documentation pdf file included with each Use Case can be
read with Adobe Acrobat® or similar document reader.
This selection of messages will increase as the CBPR+ User Handbook evolves; and new samples will be added after the publication of new chapters in the Handbook.
The CBPR+ sample messages that are included cover the following message types:
Message
Title
Description
Version
camt.029
Resolution of
Investigation
The camt.029 message is sent by a case assignee to a case creator/case assigner. This message is used to inform of the
resolution of a case, and optionally provides details about;
- the corrective action undertaken by the case assignee;
- information on the return where applicable.
2021-06-30
camt.054
Bank to Customer
Debit Credit
notification
The camt.054 message is sent by the account servicer to an account owner or to a party authorised by the account owner to
receive the message. It can be used to inform the account owner, or authorised party, of single or multiple debit and/or credit
entries reported to the account.
2020-10-16
camt.056
Financial
Institution to
Financial
Institution
Payment
Cancellation
Request
The camt.056 message is sent by a case creator/case assigner to a case assignee. This message is used to request the
cancellation of an original payment instruction. The FIToFIPaymentCancellationRequest message is exchanged between the
instructing agent and the instructed agent to request the cancellation of a interbank payment message previously sent (such as
FIToFICustomerCreditTransfer, FIToFICustomerDirectDebit or FinancialInstitutionCreditTransfer).
2021-06-30
camt.057
Notification to
Receive
The camt.057 is sent by the account owner to inform the account servicer that funds will be credited into the account owner’s
account.
2020-12-08
camt.060
Account Reporting
Request
The camt.060 is sent by the account owner to request the account servicer to send a report in the form of a camt.052, camt.053
or a camt.054.
2020-12-08
pacs.002
Financial
Institution to
Financial
Institution Status
Report
The pacs.002 message is sent by an instructed agent to the previous party in the payment chain. It is used to inform this party
about the positive or negative status of an instruction (either single or file). It is also used to report on a pending instruction.
2020-10-16
pacs.004
Payment Return
The pacs.004 message is sent by an agent to the previous agent in the payment chain to undo a payment previously settled.
2020-10-16
pacs.008
Financial
Institution to
Financial
Institution
Customer Credit
Transfer
The pacs.008 message is sent by the debtor agent to the creditor agent, directly or through other agents and/or a payment
clearing and settlement system. It is used to move funds from a debtor account to a creditor.
2020-10-16
pacs.009
Financial
Institution Credit
Transfer
The pacs.009 message is sent by a debtor financial institution to a creditor financial institution, directly or through other agents
and/or a payment clearing and settlement system. It is used to move funds from a debtor account to a creditor, where both
debtor and creditor are financial institutions.
2020-10-16
pacs.009.adv
Financial
Institution Credit
Transfer
The pacs.009.adv is used to advise an agent of a fund movement. The core pacs.009 performs the settlement.
2021-06-30
pacs.009.cov
Financial
Institution Credit
Transfer
The pacs.009.cov is used to settle a pacs.008. The pacs.009.cov includes underlying customer information contained in the
pacs.008.
2021-06-30
https://www2.swift.com/mystandards/#/c/cbpr/samples
1/7
9/28/21, 5:26 PM
Cbpr/Samples
Message
Title
Description
Version
pain.001
Customer Credit
Transfer Initiation
The pain.001 message is sent by the initiating party to the forwarding agent or debtor agent. It is used to request movement of
funds from the debtor account to a creditor.
2021-06-30
pain.002
Customer
Payment Status
Report
The pain.002 message is sent by an instructed agent to the previous party in the payment chain. It is used to inform this party
about the positive or negative status of an instruction (either single or file). It is also used to report on a pending instruction.
2021-06-30
Each Use Case contains a variety of the CBPR+ messages and the Use Cases are designed to illustrate correct standards flow according to the CBPR+ rules. Where a scenario includes
payments settling across Market Infrastructure, the Market Infrastructure messages have been excluded because those MI messages are not CBPR+ messages and confirm to a different
set of rules.
Please note, real BICs have been used in the sample messages as fictitious BICs will generate an error in the Readiness Portal. The sample messages are fictitious and have been
written to illustrate the scenario.
Use Case Sample Message Illustration
The following is an illustration which is provided for guidance purposes. The Use Case is c.53.1.a. When you open the folder you will see a pdf file which contains a flow diagram of the
scenario and a table showing the participants in the flow.
From the message flow diagram you can see four messages being sent between the first and last participant. Accordingly you will see four messages in the folder, 3 pacs.008 messages
and 1 camt.053 message. Each message label contains the Use Case identification, the message type and the parties involved. In this example Use Case p.8.1.1 you will find:
Folder Name Use Case p.8.1.1
CBPR+ p.8.1.1_pacs.008_A to B
CBPR+ p.8.1.1_pacs.008_C to D
CBPR+ p.8.1.1_pacs.002_D to C
CBPR+ p.8.1.1_pacs.002_B to A
Each message begins with the comment section which includes a legal disclaimer and the Use Case identification and description. The comment section is followed by the envelope.
These messages work “as is” in the Readiness portal. However, the envelope will have to be replaced with the User’s own envelope.
List of Use Case Sample Messages
Each of the following sample messages can be found in the zip file:
Use Case
Use Case Description
Version
Use Case c.29.2.1
High Level Resolution of Investigation (camt.029) of a Customer Credit Transfers (pacs.008) where the cover is returned
2021-06-30
Use Case c.52.1.a
Bank to Customer Account Balance Report produced by the Creditor Agent
2021-06-30
Use Case c.52.1.b
Bank to Customer Account Intraday Transaction Report produced by the Creditor Agent
2021-06-30
Use Case c.52.1.b.1
Bank to Customer Account Intraday Transaction Report/s and Account Statement produced by the Credit
2021-06-30
Use Case c.52.1.c
Bank to Customer Account Intraday Transaction and Balance Report produced by the Creditor Agent
2021-06-30
Use Case c.53.1.a
Bank to Customer Statement produced by the Creditor Agent
2020-10-16
Use Case c.53.1.b
Bank to Customer Statement produced by the Debtor Agent
2020-10-16
Use Case c.53.1.c
Bank to Customer Statement produced by an Intermediary Agent
2020-10-16
Use Case c.53.2
Bank to Customer Statement sent as an additionally copy to an authorised party - Copy
2020-10-16
Use Case c.53.3
Bank to Customer Statement resents a previously sent statement/s to the Account Owner - Duplicate
2020-10-16
Use Case c.53.4
Bank to Customer Statement resents a previously sent copy statement/s to an authorised party - Copy Duplicate
2020-10-16
Use Case c.53.5
Bank to Customer Statement sent to an authorised party who forward/provides on to the Account Owner
2020-10-16
Use Case c.54.1.1
Customer Debit/Credit Notification (camt.054) of a Customer Credit Transfer (pacs.008)
2020-10-16
Use Case c.54.2.1
Customer Debit/Credit Notification (camt.054) of a FI to FI Credit Transfer (pacs.009)
2020-10-16
Use Case c.54.3.1
Customer Debit/Credit Notification (camt.054) of a payment using the cover method
2020-10-16
Use Case c.56.2.1
High Level Payment Cancelation Request (camt.056) of a Customer Credit Transfer (pacs.008) settled using a cover
2020-10-16
https://www2.swift.com/mystandards/#/c/cbpr/samples
2/7
9/28/21, 5:26 PM
Cbpr/Samples
Use Case
Use Case Description
Version
Use Case c.57.1.1
Notification to Receive (camt.057) followed by Customer Credit Transfers
2020-10-16
Use Case c.57.1.2
Notification to Receive (camt.057) followed by FI Credit Transfers (pacs.009)
2020-10-16
Use Case c.57.1.3
Notification to Receive (camt.057) where the receipt is settled by the cover method.
2020-10-16
Use Case c.57.1.4
Notification to Receive (camt.057) for a FI Credit Transfers cover (pacs.009 cov).
2020-10-16
Use Case p.9.1.2
High Level Financial Institution Credit Transfer (pacs.009) pre-advised settled using pacs.009.
2021-06-30
Use Case p.9.2.1
High Level Customer Credit Transfer (pacs.008) settled using the cover method (pacs.009 COV)
2020-10-16
Use Case p.9.2.3
High Level Customer Credit Transfer (pacs.008) settled using the cover method (pacs.009 COV) where an incorrect intermediary is used
2020-10-16
Use Case p.2.1.1
High Level Payment Status Information (pacs.002) of multiple Payment Transaction Status updates
2020-10-16
Use Case p.2.1.2
High Level Rejection of an incomplete Customer Credit Transfer (pacs.008)
2020-10-16
Use Case p.2.2.1
High Level Rejection of an incomplete Financial Institution Credit Transfer (pacs.009)
2020-10-16
Use Case p.2.3.1
High Level Rejection of an incomplete payment using the cover method
2020-10-16
Use Case p.4.1.1
Payment Return (pacs.004) of an incomplete Customer Credit Transfer (pacs.008)
2020-10-16
Use Case p.4.1.2
Payment Return (pacs.004) of a complete Customer Credit Transfer (pacs.008)
2020-10-16
Use Case p.4.1.2.a
Partial Payment Return (pacs.004) of a complete Customer Credit Transfer (pacs.008)
2020-10-16
Use Case p.4.2.1
Payment Return (pacs.004) of an incomplete Financial Institution Credit Transfer (pacs.009)
2020-10-16
Use Case p.4.2.2
Payment Return (pacs.004) of an complete Financial Institution Credit Transfer (pacs.009)
2020-10-16
Use Case p.4.3.1
Payment Return (pacs.004) of an incomplete payment using the cover method
2020-10-16
Use Case p.4.3.2
Payment Return (pacs.004) of a complete payment using the cover method
2020-10-16
Use Case p.4.3.2.a
Payment Return (pacs.004) of a complete payment using the cover method
2020-10-16
Use Case p.4.3.3
Payment Return (pacs.004) of an incomplete cover payment
2020-10-16
Use Case pn.1.1.1
High Level Relay Payment
2021-06-30
2. Cross Element Rules Sample Messages
Introduction
What is a Cross Element Rule? A Cross Element Rule is a rule defined in a market practice that describes the data required in a particular element of the ISO 20022 message, in relation
to data present in another element. Several Business rules are defined in the CBPR+ market practice to ensure the robustness of data used in the message types. It is important for
SWIFT users to adhere to the Business rules because they are enforced by the SWIFT platform. If messages do not conform to these rules messages will be rejected as part of the
message validation processing of the SWIFT platform.
The naming convention is as follows:
message type - Rule Name - POS/NEG-X.
The rule name is written by concatenating all the words in the title and capitalizing the first letter. POS/NEG indicates whether the test is positive or negative and X indicates the
number if there is more than one test.
Each xml message contains an envelope element and the business application header. The xml envelope element has been included and the element should be removed and replaced
with the user's own element. Users will be able to publish these xml messages in the Readiness Portal and gain an understanding of the purpose of each message in relation to the Use
Case.
This selection of messages will be maintained as the CBPR+ market practice evolves; and new samples will be added after the publication of any new business rule.
Element Rule Illustration
An example of a business rule is as follows:
The rule name is CBPR_ Name Any BIC Rule
The rule applies to message types which contain a Debtor and a Creditor. These messages are camt_057_001_06, camt_060_001_05, pacs.004.001.09, pacs_008_001_08 and
pacs.009.001.08.
The rule impacts Any BIC <AnyBIC> and Name <Nm> for both Debtor and Creditor.
The intention of the rule is to make the Name mandatory if Any BIC is Absent
The folder contains 2 message samples per message type:
Here below we use Pacs_008_001_08 as an example for illustration purposes:
MX_pacs_008_CBPR_STP_Debtor_NameAnyBICRule_NEG_01 (Negative use case)
The Debtor <Dbtr> appears in the CreditTransferTransactionInformation <CdtTrfTxInf>
The message is expected to fail as both the Any BIC <AnyBIC> and Name <Nm> are absent as shown in the picture below:
MX_pacs_008_CBPR_STP_Debtor_NameAnyBICRule_POS_01 (Positive use case)
The Debtor <Dbtr> appears in the CreditTransferTransactionInformation <CdtTrfTxInf>
The message is expected to pass as the Name <Nm> is present when Any BIC <AnyBIC> is absent as seen in the picture below:
https://www2.swift.com/mystandards/#/c/cbpr/samples
3/7
9/28/21, 5:26 PM
Cbpr/Samples
List of Cross Element Rules
Each of the following sample messages can be found in the zip file:
Rule Name
Definition
Message type
HeaderVersion
The test checks that AppHdr is version is urn:iso:std:iso:20022:tech:xsd:head.001.001.02.
head.001
Rule "Agent
Name Postal
Address Rule"
Name and Address must always be present together.
pacs.008
Rule "Amount
Currency
Rule"
The codes XAU, XAG, XPD and XPT are not allowed, as these are codes are only used for commodities.
camt.057
If AnyBIC is Absent Then Name is mandatory.
camt.057
camt.060
pacs.008
pacs.008
pacs.008.stp
Rule "CBPR_
Agent Name
Postal
Address Rule"
Name and Address must always be present together.
camt.052
camt.053
camt.054
camt.057
camt.060
pacs.002
pacs.004
pacs.008
pacs.009
pacs.009.COV
pacs.010
Rule "CBPR_
Expected
Value Date
Rule"
If Notification/ExpectedValueDate is absent, then item/ExpectedValueDate must be present.
camt.057
Rule "CBPR_
Name Any BIC
Rule"
If AnyBIC is Absent Then Name is mandatory.
pacs.004
pacs.009.COV
Rule "CBPR_
Party Name
Postal
Address Rule"
If Postal Address is present then Name is mandatory.
camt.052
camt.053
camt.054
camt.057
camt.060
pacs.002
pacs.004
pacs.008
pacs.008.stp
pacs.009.COV
Rule "CBPR_
Returned
Instucted __
Returned
Interbank
Settlement
Amount Rule"
If ReturnedInstructedAmount differs from the ReturnedInterbankSettlementAmount, Charge Information becomes mandatory.
pacs.004
Rule "CBPR_
Transaction
Status Reject
Effective Sett
Date Rule"
If TransactionStatus is “RJCT’ then Effective Interbank Settlement Date is not allowed.
pacs.002
Rule "CBPR_
Transaction
Status Reject
Reason Rule"
If TransactionStatus/Code equals RJCT, then “Status Reason Information/Reason” is mandatory.
pacs.002
Rule "CRED
Rule"
Charge information is mandatory if CRED is present – if no charges are taken, Zero must be used in "Amount" (any agent in the payment chain).
pacs.004
pacs.008
pacs.008.stp
Rule "DEBT
Rule"
If Charge Bearer/DEBT is used then charge information is only mandatory in case of prepaid charges (that is if interbank settlement amount is higher
than instructed amount) and in that case zero amount is not allowed. Otherwise Charge information is optional (both Agent and currency always
need to be provided).
pacs.008.stp
Rule "CBPR
Name Any BIC
Rule"
https://www2.swift.com/mystandards/#/c/cbpr/samples
4/7
9/28/21, 5:26 PM
Cbpr/Samples
Rule Name
Definition
Message type
Rule "Debtor _
Creditor _E S/
AD_ Rule"
Transactions exchanged within these country couples are considered as domestic ones. IF Creditor Agent and Debtor Agent BICs are part of
following countries: ES, AD Then: Debtor and Creditor must be identified using a Name and the Account/IBAN.
pacs.008.stp
Rule "Debtor _
Creditor _EU_
Rule"
IF Creditor Agent and Debtor Agent BICs are part of following countries: AT, BE, BG, BV, CY, CZ, DE, DK, EE, ES, FI, FR, GB, GF, GI, GP, GR, HR,
HU, IE, IS, IT, LI, LT, LU, LV, MQ (FR), MT, NL, NO, PL, PM (FR), PT, RE (FR), RO, SE, SI, SJ, SK Then: Debtor and Creditor must be identified
using a Name and the Account/IBAN.
pacs.008.stp
Rule "Debtor _
Creditor _F R/
MC_ Rule"
Transactions exchanged within these country couples are considered as domestic ones. IF Creditor Agent and Debtor Agent BICs are part of
following countries: FR, MC Then: Debtor and Creditor must be identified using a Name and the Account/IBAN.
pacs.008.stp
Rule "Debtor _
Creditor _I T/
SM_ Rule"
Transactions exchanged within these country couples are considered as domestic ones. IF Creditor Agent and Debtor Agent BICs are part of
following countries: IT, SM Then: Debtor and Creditor must be identified using a Name and the Account/IBAN.
pacs.008.stp
Rule "Debtor _
Creditor _I T/
VA_ Rule"
Transactions exchanged within these country couples are considered as domestic ones. IF Creditor Agent and Debtor Agent BICs are part of
following countries: IT, VA Then: Debtor and Creditor must be identified using a Name and the Account/IBAN.
pacs.008.stp
Rule
"Instruction
For Creditor _
Presence
Code Rule"
Each code can only be used once for element Instruction For Creditor Agent.
pacs.008
Rule
"Instruction
Identification
Rule"
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//'.
pacs.008
pacs.008.stp
pacs.009
pacs.009.COV
Rule
"Interbank
Settlement
Currency
Rule"
The codes XAU, XAG, XPD and XPT are not allowed, as these are codes are only used for commodities.
pacs.004
pacs.008
pacs.009
pacs.009.COV
Rule "Name
Postal
Address Rule"
Name and Address must always be present together.
pacs.004
pacs.008
pacs.008.stp
Rule "Original
Instruction
Identification
Rule"
This field must not start or end with a slash '/' and must not contain two consecutive slashes '//'.
camt.052
camt.053
camt.054
pacs.002
pacs.004
Rule "Original
Message
Name
Identification
Rule"
This element should be populated with either pacs.008.001.xx or pacs.009.001.xx or MT103 or MT202 or camt.053.001.xx or camt.054.001.xx when
present.
pacs.004
Rule "Original
Transaction
Reference
Creditor Agent
Rule"
If Original Message Name Identification is a pacs.009.001.xx or MT202 and if Original Transaction Reference is present, Creditor if present must be
identified as an agent.
pacs.004
Rule "Original
Transaction
Reference
Creditor Party
Rule"
If Original Message Name Identification is a pacs.008.001.xx or MT103 and if Original Transaction Reference is present, Creditor if present must be
identified as a party.
pacs.004
Rule "Original
Transaction
Reference
Debtor Agent
Rule"
If Original Message Name Identification is a pacs.009.001.xx or MT202 and if Original Transaction Reference is present, Debtor if present must be
identified as an agent.
pacs.004
Rule "Original
Transaction
Reference
Debtor Party
Rule"
If Original Message Name Identification is a pacs.008.001.xx or MT103 and if Original Transaction Reference is present, Debtor if present must be
identified as a party.
pacs.004
Rule "Original
Transaction
Reference
Ultimate
Creditor Rule"
If Original Message Name Identification is a pacs.009.001.xx or MT202 and if Original Transaction Reference is present then ultimate creditor is not
allowed.
pacs.004
Rule "Original
Transaction
Reference
Ultimate
Debtor Rule"
If Original Message Name Identification is a pacs.009.001.xx or MT202 and if Original Transaction Reference is present, then ultimate debtor is not
allowed.
pacs.004
https://www2.swift.com/mystandards/#/c/cbpr/samples
5/7
9/28/21, 5:26 PM
Cbpr/Samples
Rule Name
Definition
Message type
Rule "Related
Remit Info _
Remit Info _
Mutually
Exclusive"
In the interbank space, Related Remittance Information and Remittance Information are mutually exclusive and all may be absent.
pacs.008
pacs.008.stp
Rule
"Remittance _
Mutually
Exclusive"
For each [Full Message/Document/PaymentReturnV09], the following elements are mutually exclusive:
[PaymentReturnV09/TransactionInformation/OriginalTransactionReference/RemittanceInformation/Unstructured] ,
[PaymentReturnV09/TransactionInformation/OriginalTransactionReference/RemittanceInformation/Structured] and all may be absent
pacs.004
pacs.008
pacs.008.stp
Rule
"Remittance
Information _
Mutually
Exclusive"
For each [Full Message/Document/FinancialInstitutionCreditTransferV08], the following elements are mutually exclusive:
[FinancialInstitutionCreditTransferV08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTransfer/RemittanceInformation/Unstructured]
, [FinancialInstitutionCreditTransferV08/CreditTransferTransactionInformation/UnderlyingCustomerCreditTransfer/RemittanceInformation/Structured]
and all may be absent
pacs.009
pacs.009.COV
Rule "Return
Chain Creditor
Agent Rule"
If Original Message Name Identification is a pacs.009.001.xx or MT202, then the creditor must be identified as an agent in Return Chain.
pacs.004
Rule "Return
Chain Creditor
Party Rule"
If Original Message Name Identification is a pacs.008.001.xx or MT103, then the creditor must be identified as a party in Return Chain.
pacs.004
Rule "Return
Chain Debtor
Agent Rule"
If Original Message Name Identification is a pacs.009.001.xx or MT202, then the debtor must be identified as a agent in Return Chain.
pacs.004
Rule "Return
Chain Debtor
Party Rule"
If Original Message Name Identification is a pacs.008.001.xx or MT103, then the debtor must be identified as a party in Return Chain.
pacs.004
Rule "Return
Chain Ultimate
Creditor Agent
Rule"
If Original Message Name Identification is a pacs.009.001.xx or MT202, then ultimate creditor is not allowed in Return Chain.
pacs.004
Rule "Return
Chain Ultimate
Debtor Agent
Rule"
If Original Message Name Identification is a pacs.009.001.xx ot MT202, then ultimate debtor is not allowed in Return Chain.
pacs.004
Rule
"Returned
Interbank
Settlement
Currency
Rule"
The codes XAU, XAG, XPD and XPT are not allowed, as these are codes are only used for commodities.
pacs.004
Rule
"Structured Vs
Unstructured
Rule"
If PostalAddress is used and if AddressLine is present, then all other optional elements in PostalAddress must be absent.
camt.057
camt.060
pacs.002
pacs.004
pacs.008
pacs.008.stp
pacs.009
pacs.009.COV
pacs.010
Rule "Total
Amount
Currency
Rule"
The codes XAU, XAG, XPD and XPT are not allowed, as these are codes are only used for commodities.
camt.057
If “PostalAddress” is used, and if AddressLine is absent, then Country and Town name must be present.
camt.057
camt.060
pacs.002
pacs.004
pacs.008
pacs.008.stp
pacs.009
pacs.009.COV
pacs.010
Rule "Town
Name And
Country Rule"
Change Log
The change log has been included in each sample message xml file in the comments section.
Legal Notices
Copyright
S.W.I.F.T. SC ("SWIFT") or its licensors © 2020. All rights reserved.
Disclaimer and limitation of liability
This document depicts fictitious examples and is made available "as is" for information purposes only. SWIFT assumes no liability for any errors, inaccuracies or incompleteness contained
this document. SWIFT MAKES NO REPRESENTATIONS OR WARRANTIES, EITHER EXPRESS OR IMPLIED, OF ANY KIND RELATED TO THIS DOCUMENT OR THE
INFORMATION IN THIS DOCUMENT, AND HEREBY DISCLAIMS ALL SUCH REPRESENTATIONS AND WARRANTIES, CREATED BY LAW, CONTRACT OR OTHERWISE,
INCLUDING WITHOUT LIMITATION THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE OR NON-INFRINGEMENT. TO THE FULLEST
https://www2.swift.com/mystandards/#/c/cbpr/samples
6/7
9/28/21, 5:26 PM
Cbpr/Samples
EXTENT PERMITTED UNDER APPLICABLE LAW, SWIFT SHALL NOT BE LIABLE FOR DAMAGES OF ANY KIND ARISING FROM USE OF THIS DOCUMENT OR ANY
INFORMATION IN THIS DOCUMENT, INCLUDING WITHOUT LIMITATION ANY LIABILITY FOR DIRECT, INDIRECT, SPECIAL, CONSEQUENTIAL OR INCIDENTAL LOSS OR
DAMAGE, EVEN IF SWIFT WAS AWARE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.
Choice of law and Jurisdiction
The laws of Belgium shall govern the terms and conditions for the use of this document, and the courts of Brussels shall have exclusive jurisdiction over any disputes arising from or in
connection with the use of or any information in this document.
Trademarks
SWIFT is the trade name of S.W.I.F.T. SC. The following are registered trademarks of SWIFT: 3SKey, Innotribe, MyStandards, Sibos, SWIFT, SWIFTNet, SWIFT Institute, the Standards
Forum logo, the SWIFT logo, SWIFT gpi with logo, the SWIFT gpi logo and UETR. Other product, service, or company names in this publication are trade names, trademarks, or
registered trademarks of their respective owners.
https://www2.swift.com/mystandards/#/c/cbpr/samples
7/7