ISO 20022 Programme

Customer Testing Guidelines

Advance information
This document is intended for the SWIFT community preparing for the payment ISO
migration. It provides customers with comprehensive testing guidelines for ISO 20022
and CBPR+ adoption. It also helps customers assess their readiness for CBPR+ go live
in November 2022.

13 April 2022
ISO 20022 Programme
Customer Testing Guidelines Table of Contents

Table of Contents
Preface .................................................................................................................................................3
Significant Changes ...........................................................................................................................4
1 Introduction ...............................................................................................................................5
2 Testing Approach .....................................................................................................................6
2.1 Business and Functional Testing ............................................................................................8
2.2 Non-Functional Testing ...........................................................................................................9
2.3 Testing Timeline ....................................................................................................................10
3 Generic Requirements for MT and ISO 20022 Customers .................................................12
3.1 Configuration Activities (for All Customers) ..........................................................................12
3.1.1 Communication Interfaces ..........................................................................................12
3.1.2 Messaging Interfaces ..................................................................................................12
3.1.3 FINplus - Configure Your Connection to SWIFTNet ...................................................13
3.1.4 Relationship Management Application .......................................................................13
3.1.5 Accessing the Test Sparring Partner ..........................................................................13
3.2 Useful ISO 20022 Resources and recommendations (for All Customers) ...........................16
3.2.1 MyStandards Readiness Portal ..................................................................................16
3.2.2 Translation Portal ........................................................................................................16
3.2.3 Financial Crime Compliance .......................................................................................16
3.2.4 Archiving of ISO 20022 or Multi-Format MX ...............................................................17
3.2.5 Validate End-of-Day Processes ..................................................................................17
3.2.6 In-Flow Translation .....................................................................................................17
3.2.7 Transaction Manager ..................................................................................................18
4 Customer Testing Journey for MT Customers ....................................................................20
4.1 Business and Functional Testing ..........................................................................................20
4.1.1 Self-Testing .................................................................................................................20
4.1.2 Testing with SWIFT ....................................................................................................22
4.1.3 Testing as a Community .............................................................................................24
4.2 Non-Functional Testing .........................................................................................................25
4.2.1 Performance Testing ..................................................................................................25
4.2.2 Business Continuity ....................................................................................................27
5 Customer Testing Journey for ISO 20022 Customers........................................................29
5.1 Business and Functional Testing ..........................................................................................29
5.1.1 Self-Testing .................................................................................................................29
5.1.2 Testing with SWIFT ....................................................................................................31
5.1.3 Testing as a Community .............................................................................................35
5.2 Non-Functional Testing .........................................................................................................36
5.2.1 Performance Testing ..................................................................................................36
5.2.2 Business Continuity ....................................................................................................38
Self-Testing – Checklist..............................................................................................39
Testing with SWIFT – Checklist .................................................................................43
Testing with a Community – Checklist .....................................................................44
CBPR+ Testing Samples ............................................................................................46
SWIFT Error Codes .....................................................................................................49
Legal Notices ....................................................................................................................................50

13 April 2022 2
ISO 20022 Programme
Customer Testing Guidelines Preface

Preface
About this document
This document is intended for the SWIFT community preparing for the payment ISO 20022
migration. It provides customers with comprehensive testing guidelines for ISO 20022 and
CBPR+ adoption. It also helps customers assess their readiness for CBPR+ go live in
November 2022.
In the context of this document, CBPR+ refers to CBPR+ 2.1 usage guidelines.
Intended audience
This document is for the following audience:
− IT and business payments specialists of all SWIFT customers sending or receiving
payments (SWIFT MT category 1, 2 and 9 and ISO 20022 pacs/camt messages)
− All SWIFT users with CBPR+ traffic flows (sent or received messages)
− Vendor community developing messaging interfaces and applications that will interact
with FINplus
Related documentation
• SWIFT platform – Connectivity Guidance
• ISO 20022 Programme Customer Adoption Guide
• ISO 20022 Programme Getting Started
• In-Flow Translation Service Overview
• Advanced Information on Transaction Manager Business Rules
• Guiding principles for screening ISO 20022 payments
• SWIFTNet Messaging Operations Guide
• Universal Confirmations Rulebook
• Details of the translation rules for ISO 20022 messages in scope of the CBPR+ market
practice in MyStandards

13 April 2022 3
ISO 20022 Programme
Customer Testing Guidelines Significant Changes

Significant Changes
This section lists the main changes since the previous publication of the document. It does
not include general edits or minor updates.

New/updated information Location

Test Sparring Partner: defining users is simplified 3.1.5 Accessing the Test Sparring Partner
with the self-service approach
Introduction to Transaction Manager release plan 3.2.7 Transaction Manager
added
Better explanation for MT users that send ISO 4.1.2.2 Use the Test Sparring Partner to
20022 messages to themselves Receive Multi-Format MX
Better explanation about the Connectivity to 4.2.1 Performance Testing
SWIFT - Connectivity Packs document
New Note about the impact of ISO on the SWIFT 5.2.1 Performance Testing
leased line bandwidth
How to access and download ISO CBPR+ Appendix D CBPR+ Testing Samples
samples from MyStandards

13 April 2022 4
ISO 20022 Programme
Customer Testing Guidelines Introduction

1 Introduction
The SWIFT community migration towards ISO 20022 for cross-border payments and the
introduction of Transaction Manager start in November 2022 and continue until 2025. They
are both critical changes to the SWIFT community.
The migration guiding principles define that any SWIFT customer can adopt ISO 20022 or
CBPR+ at their own pace, independently of the ISO 20022 capabilities of their business
counterparts. The proposed interoperability model maintains the richness of ISO 20022 or
CBPR+ transactions throughout the transaction life cycle, even if some transaction parties
are not yet ISO 20022-ready.
To achieve this level of interoperability, SWIFT introduces some key new capabilities such
as:
• In-flow Translation, which enables customers to receive payments transactions in
the format of their choice depending on their ISO 20022 readiness
• Transaction Manager, which enables the end-to-end management of the payment
transaction, thereby preserving rich data
To benefit from these new capabilities, all SWIFT customers must implement a set of changes
before November 2022. For example:
• Customer interfaces must be upgraded and configured to connect to the FINplus
service to process the payment messages in the preferred format.
• Customers adopting ISO 20022 must upgrade their payment back-office applications
to support the CBPR+ message guidelines.
For more details about the minimum readiness activities towards November 2022, see the
ISO 20022 Programme Customer Adoption Guide.

13 April 2022 5
ISO 20022 Programme
Customer Testing Guidelines Testing Approach

2 Testing Approach
Introduction
Testing will be essential to validate the changes introduced and to ensure individual customer
and SWIFT community readiness for the start of the ISO 20022 migration.

SWIFT customers must focus on their testing activities to ensure readiness to connect
to FINplus and to receive multi-format MX by November 2022.

Customer groups
The customer testing journeys will be driven by customer ISO 20022/CBPR+ readiness.
SWIFT foresees three groups of customers:
1. MT customers
These customers are not yet ready to exchange ISO 20022 messages natively in
November 2022. They will continue sending and receiving FIN MTs after November
2022 and will migrate to ISO 20022 later. Their testing activities will be focused on the
processing of multi-format MX (ISO 20022 with embedded MT)
2. ISO 20022 customers
These customers are ready to send and receive ISO 20022 messages natively as of
November 20221. The ISO 20022 customers will prepare the processing of native ISO
20022 and validate that their infrastructure can process a mix of MT and MX flows after
November 2022 (MT will still be received through the FIN channel)
The following diagram illustrates the first two customer groups and summarises their
respective customer testing journeys.

3. ISO 20022 + MT customers

These customers will send and receive a mix of MTs and ISO 20022 messages after
November 2022 as some of their branches/applications are ISO 20022-ready while
others are not. Their testing activities will be a combination of the ones described above
depending on the branch/application ISO 20022 readiness.
Customers must adopt a hybrid approach combining the two test journeys, where some
of their branches or applications remain on MT while others are ISO 20022 native. Over

1
As from August 2022, participants can start exchanging CBPR+ messages and relying on In-flow Translation over the FINplus
Live service, based on bilateral agreements with counterparts of their choice.

13 April 2022 6
ISO 20022 Programme
Customer Testing Guidelines Testing Approach

time, while more applications become ISO 20022-ready, this document continues to be
the reference to migrate the remaining applications to ISO 20022 by November 2025.
Aspects of customer testing activities
Customer testing activities must cover all or some of the following aspects:
• Business and functional testing: ensure customer functional readiness to process
their SWIFT traffic and operate their payment business after November 2022
• Non-functional testing: ensure customers can process their expected peak volumes
with their new traffic mix and can meet their business continuity objectives
The above testing activities required for November 2022 are the following:
− SWIFT interface upgrade
− Connectivity to FINplus
− Adoption of CBPR+ standards
− In-flow Translation
− gpi ISO 20022
− Universal Confirmations of pacs.008
− Financial Crime Compliance and screening
− Archiving
• Regression testing: while not explicitly mentioned in this document, regression testing
is an important step in the ISO 20022 readiness validation process. Every customer will
decide what level of regression testing is required to ensure that the current quality of
service is maintained after the ISO 20022 implementation phases.
Most testing activities can be initiated by customers with their own schedule and
completed independently from their business counterparts. This enables the SWIFT
community to ensure readiness at scale without requiring massive coordination.

Three-step approach for business and functional testing activities

SWIFT proposes a three-step approach for the testing activities:
1. Self-testing: testing activities that SWIFT customers can perform independently of
SWIFT and any business counterparties
2. Testing with SWIFT: testing activities that SWIFT customers can perform with SWIFT
through the Test Sparring Partner, independently of any business counterparties
3. Community Testing: testing activities that SWIFT customers can perform with their
business counterparties, when they have completed the two first stages

Structure of this document

This document provides, for each customer group, a comprehensive overview of the testing
activities that SWIFT recommends.
The document also aims at supporting customers in their ISO 20022 migration journey
towards 2025. As customer branches and applications become ISO 20022 native,

13 April 2022 7
ISO 20022 Programme
Customer Testing Guidelines Testing Approach

customers will also use this guide to validate their readiness, applying the testing activities
for ISO 20022–ready applications.

2.1 Business and Functional Testing

The business and functional testing are following a three-step approach:

The main testing activities that are part of each phase are summarised below:

The following table describes each of these phases:

Phase Sub-phase Objective Testing activities

MT customers ISO 20022 customers

Self- Standards Validate Validate reception and Validate the structure of CBPR+
Testing readiness of processing of multi-format messages:
back-office MX.
application to • Readiness portal for CBPR+
process ISO • Verify the In-flow format validation
20022 Translation result code
• Translation Portal to test
messages • Define the appropriate alignment with CBPR+
operations to deal with translation rules
potential truncations
Messaging Validate • Interface upgrade
interface Interface
upgrade and • FINplus connectivity configuration
configuration • Routing and back-office configuration
• Validate your requirement for the Relationship Management
Application (RMA) on FINplus
FINplus Validate • Ensure definition of queues (if needed beyond the default
connectivity to configuration)
the FINplus
pilot service • In-flow Translation configuration2
• Send an ISO 20022 format message to your own BIC (see
details below in the Testing with SWIFT section)
FCC (com- Validate • Ensure appropriate • Ensure appropriate screening of
pliance) screening screening of multi- ISO 20022 messages
and end-of- processes format MX messages
day • (for customers using SWIFT in-
processes • (for customers using flow screening services) Verify
SWIFT in-flow that both the messaging
screening services, interface and the back-office
that is, SWIFT route the rejected messages as
Transaction Screening per the Screening return code
and SWIFT Sanctions and they process correctly the
Screening) Verify that abort notifications
the messaging

2
SWIFT recommends keeping In-flow Translation enabled for testing since messaging interfaces are able to handle and deliver the
various formats to back-office applications. Customers who are willing to configure in-flow differently are requested to contact
SWIFT Support.

13 April 2022 8
ISO 20022 Programme
Customer Testing Guidelines Testing Approach

Phase Sub-phase Objective Testing activities

MT customers ISO 20022 customers

interface and back-
office route received
messages as per
Screening return code
Validate • Ensure archiving of ISO 20022 data
archiving
processes

Validate end- • Adapt all end-of-day and reporting processes to ISO 20022
of-day data including processing of the multi-format MX
processes

Testing Test with Validate Test Sparring Partner Test Sparring Partner testing
with the Test functional testing scenarios: scenarios:
SWIFT Sparring integration
Partner with internal • Reception of ISO • CBPR+ catalogue
applications 20022 format with
embedded MT • gpi ISO 20022 test catalogues3
using the Test
Sparring including as well
Partner truncation scenarios
(In-flow Translation
only. No Transaction
Manager involved)
Testing Self- Validate Select counterparties that Select counterparties that are
as a organised business and are planning to adopt ISO planning to adopt ISO 20022. They
com- community technical 20022. They will send you will send you ISO 20022 messages
munity testing. interoperability ISO 20022 messages and and you will receive ISO messages
with selected you receive multi-format. and the opposite way. ISO 20022
counterparties. message relay can also be tested.
Your interface will route
either the ISO 20022
message or the MT based
on updated routing rules.
The counterparties
sending MT remain
delivered by means of FIN
(as today), unless for
transactions4 already
known by Transaction
Manager

2.2 Non-Functional Testing

Performance and business continuity testing are specific activities that must be planned
enough in advance of go-live to have enough buffer to tune the infrastructure according to
the test results.
Recommendations:
• Performance testing
− Strongly recommended for high volume on-premises customers
− Optional for the other customers

3
gpi customers: Optional payable onboarding service is available. A selected list of specific gpi test cases has been selected to test
the gpi ISO readiness against the 2021 gpi ISO rulebook.
4
Transaction known by Transaction Manager: transaction starting with an ISO leg is stored in Transaction Manager and
subsequent MT legs are also processed by Transaction Manager. MT recipient receives an ISO multi-format and their interface
extracts the MT to be delivered to back-office (see SWIFT platform – Connectivity Guidance for details).

13 April 2022 9
ISO 20022 Programme
Customer Testing Guidelines Testing Approach

• Business continuity testing

− Recommended for all customers
The various testing activities for MT and ISO 20022 customers are summarised in the table
below:

Phase Objective Testing activities

MT customers ISO 20022 customers

Performance Validate that

Testing the customer
SWIFT
infrastructure
and
configuration Customers can simulate their peak Customers can simulate their peak
can process traffic by*: traffic by*:
their traffic
volumes ▪ Before the test, sending ISO ▪ Before the test, sending MTs to
20022 to themselves to build a themselves to build a queue of
queue at SWIFT of ISO 20022 MTs
with embedded MT (using the ▪ During the test, sending ISO
Test Sparring Partner) 20022 to themselves and
▪ During the test, sending MT to retrieving the previously
themselves and retrieving the generated MTs
previously generated ISO 20022 *Requires coordination with SWIFT
with embedded MT (See Knowledge Base article
*Requires coordination with SWIFT 2008531)
(See Knowledge Base article
2008531)

Business Validate that

Continuity the customer
Testing SWIFT
infrastructure
and
configuration
can meet Based on their business continuity Based on their business continuity
their objectives and resilience set-up, objectives and resilience set-up,
business customers will simulate failure in customers will simulate failure in
continuity their SWIFT infrastructure and their SWIFT infrastructure and
objectives. exercise their business continuity exercise their business continuity
procedures to ensure that the multi- procedures to ensure that the ISO
format MX flow is properly recovered 20022 flows are properly recovered
and that any potential message gap and that any potential message gap
can be recovered using SWIFTNet can be recovered using SWIFTNet
retrievals. retrievals.

2.3 Testing Timeline

The below figure summarises the overall customer testing readiness plan and covers key
activities that must be conducted as listed in the above tables.
For each test category, the blue cross-hatched time window is indicative of the maximum
timeline to complete the related readiness test, keeping a contingency window before the
November go-live activation.

13 April 2022 10
ISO 20022 Programme
Customer Testing Guidelines Testing Approach

Customer testing activities planning 1

If you are using a third-party SWIFT interface, then validate with the vendor the version
that must be implemented to support multi-format message handling and recognise the
signature from FINplus or Transaction Manager. Perform end-to-end testing to ensure
successful straight-through processing from the interface to the back-office applications.
A list of compatible FINplus interfaces was published in March 2022 (see swift.com). If
you are using a service bureau, then work with the vendor to ensure that you receive
and process the output from the service bureau. A list of compliant service bureaux will
be published by the end of June 2022.

13 April 2022 11
ISO 20022 Programme
Customer Testing Guidelines Generic Requirements for MT and ISO 20022 Customers

3 Generic Requirements for MT and ISO 20022

Customers
Introduction
This chapter covers the requirements that apply to all customers, whether they stay on MT
or they support ISO 20022 natively.
Out of scope
The following items are out of scope of this document and must be procured directly by the
customer.
• consulting services and impact analysis for the ISO 20022 migration
• infrastructure to support processing of ISO 20022 and CBPR+ messages (that is,
hardware, network, storage requirements internal to customers’ premises)
• design of translation solutions and mapping rules to convert existing customer flows to
CBPR+
• analysis of vendor proposal to support translation or ISO 20022-ready payment engine
• ISO 20022 domestic initiative driven by local Payment Market Infrastructures (PMI):
requirements are typically managed by the PMI itself and its customer community

3.1 Configuration Activities (for All Customers)

Tip Many items of this section are similar to some chapters of the ISO 20022
Customer Adoption Guide

3.1.1 Communication Interfaces

This section documents the impact of adopting ISO 20022 and FINplus on the
communication interface layer of your SWIFT stack.
Intended Audience: all staff operating and configuring SWIFTNet interfaces
Note Always consult the Release Timeline on swift.com for product end of support and
upgrade requirements.
3.1.1.1 SWIFTNet Link
There is no specific impact other than the upgrade to SWIFTNet Link 7.6 for the exchange
of CBPR+ messages over FINplus.
3.1.1.2 Alliance Gateway
There is no specific impact other than the upgrade to Alliance Gateway 7.6 for the exchange
of CBPR+ messages over FINplus.
3.1.1.3 Alliance Remote Gateway
There is no specific impact other than the upgrade to Alliance Remote Gateway 7.6 for the
exchange of CBPR+ messages over FINplus.
3.1.1.4 Third-Party Products
If you are using third-party products, then make sure that they are updated to correctly
handle the new format.

3.1.2 Messaging Interfaces

The upgrade to a compliant messaging interface is mandatory before November 2022
for all customers to connect to FINplus and process the multi-format MX messages.

13 April 2022 12
ISO 20022 Programme
Customer Testing Guidelines Generic Requirements for MT and ISO 20022 Customers

This section documents the impact of adopting ISO 20022 and FINplus on the messaging
interface layer of your SWIFT stack.
Intended Audience: all staff operating and configuring SWIFTNet interfaces.
Related information
See the ISO 20022 Customer Adoption Guide > Messaging Interfaces.
Alliance Access/Entry customers: the modules are gathered in a dedicated SWIFTSmart
curriculum.

3.1.3 FINplus - Configure Your Connection to SWIFTNet

SWIFT has deployed FINplus, which brings the following features:
• To enable the exchange of ISO 20022-formatted request types over SWIFTNet, the
FINplus many-to-many InterAct service supports ISO 20022 messages for payments
and delivers to recipients the multi-format MX.
• It offers an equivalent level of features as FIN and includes the validation of industry
usage guidelines such as CBPR+.
• It will be one of the channels to interact with Transaction Manager. The SWIFT platform
– Connectivity Guidance provides information about the different implementation
options available during the coexistence period, starting November 2022.
All customers with FIN BICs5 were automatically provisioned for FINplus pilot future
during Q1 2022. Any new eligible BIC joining FIN will also be provisioned for FINplus.

Related information
ISO 20022 Customer Adoption Guide > FINplus and SWIFTNet Store-and-Forward.

3.1.4 Relationship Management Application

Like with the FIN messaging service, Relationship Management Application (RMA) is a
mandatory prerequisite to exchange Live traffic with your counterparties with the FINplus
messaging service. Authorisations are set up and maintained separately for each service.
For Test and Training traffic (pilot service), the use of RMA is optional.
Related information
ISO 20022 Programme Customer Adoption Guide > Relationship Management Application
(RMA)

3.1.5 Accessing the Test Sparring Partner

SWIFT Test Sparring Partner (TSP) is a platform that takes non-user roles in test message
flows. It is available to customers that are registered for the FINplus service with SWIFT.
Two versions are available:
• a free Universal version of the platform that uses pre-defined test cases
• a paid Premium version that includes customisable test cases and reference data.
The prerequisites for testing with SWIFT Test Sparring Partner are as follows:
• a FINplus subscription.
All eligible BICs are automatically subscribed and provisioned for the pilot future
version..
• FINplus connectivity

5
See details in the KB article 5025106.

13 April 2022 13
ISO 20022 Programme
Customer Testing Guidelines Generic Requirements for MT and ISO 20022 Customers

SWIFT Test Sparring Partner for CBPR+ operates in bypass mode, so no Relationship
Management Application (RMA) exchange is required.
There are two steps to start using SWIFT Test Sparring Partner. The first part of the process
provides secure access to SWIFT Test Sparring Partner. The second part informs SWIFT
Test Sparring Partner about what the user is permitted to do for which BICs and testing
services.
Access at swift.com level – Your swift.com administrator approves user’s access to the
TSP
SWIFT Test Sparring Partner is accessed through a portal on swift.com. To access the
portal, you must belong to an institution subscribed to the SWIFT Test Sparring Partner
service and your user profile must be validated by your institution's swift.com administrator.
This is done to ensure secured access to the TSP application, controlled by your swift.com
administrator.
Note All institutions provisioned for FINplus pilot are automatically subscribed to TSP
Universal access
Prerequisite: How to enroll a user to the Test Sparring Partner
1. Make sure that you are connected to the Internet or a multi-vendor secure IP network
(MV-SIPN)
2. Make sure that you have Google Chrome, Microsoft Edge, or Firefox installed.
3. Open swift.com in one of these browsers and log in to your mySWIFT account.
If you do not have a mySWIFT account, then you must create one. Information about
how to create a mySWIFT account is available on the login screen.
Procedure
1. Click My tools at the top of your screen.
2. Select My profile and account.
3. On the following page, click Request Accesses.
This tab lists all available SWIFT applications.
4. Click Edit at the top-right corner of the list and scroll down to the Licenses section,
where the Test Sparring Partner - Pilot is located.
5. Click to change and select the appropriate user role (Administrator or User).
User roles are explained further in the Test Sparring Partner for CBPR+ guide > Access
Management.

6. Click OK.
7. Scroll to the bottom of the page and click Save.
This sends your request to your swift.com administrator, who must approve the request
for you to access the Test Sparring Partner.

13 April 2022 14
ISO 20022 Programme
Customer Testing Guidelines Generic Requirements for MT and ISO 20022 Customers

Access at TSP level – Manage user access in the TSP workspace

A user that has a TSP access approved on swift.com can log in to TSP. However, the user’s
credentials on TSP are managed by the TSP administrator. This is done to control user
access rights related to the role, BICs, and testing services.
The basic steps to start working with TSP are as follows:
1. Request access at swift.com level as explained above: request role(s) for your
swift.com account through the swift.com portal, with at least one user requesting the
TSP administrator role through swift.com.
2. Once approved, the TSP administrator accesses the TSP. A TSP workspace (linked to
the administrator’s swift.com profile BIC) is automatically and immediately created.
With that, the TSP administrator can manage BICs and user role and access for other
users of the institution that share the same swift.com profile BIC.
3. Other users must request TSP roles (Tester or Viewer) through swift.com. Once
granted, they log in to the TSP to activate the access and, at the same time, work with
their TSP administrator to confirm the role and type of accesses they need within the
TSP application.
Note The self-service model is applicable to Universal services only. Customers
that want Premium services must request them through their Account Manager.
TSP administrators and TSP users start working with the Test Sparring Partner
When their request is approved by the swift.com administrator, the Test Sparring Partner
appears under Licenses on the Applications tab of their mySWIFT profile. Login to TSP is
granted and users must liaise with their TSP administrator to define and validate their TSP
roles, as explained above.

Test Sparring Partner URL: you can now access the Test Sparring Partner through your
mySWIFT profile or by using the direct link: www2.swift.com/tsp.

13 April 2022 15
ISO 20022 Programme
Customer Testing Guidelines Generic Requirements for MT and ISO 20022 Customers

3.2 Useful ISO 20022 Resources and recommendations

(for All Customers)
3.2.1 MyStandards Readiness Portal
Purpose
The MyStandards Readines Portal enables customers to support them in their initial steps of
internal testing activities:
• to test messages against CBPR+ usage guidelines and eliminate syntactical and
semantic errors before connectivity to the FINplus pilot service is in place
• (applicable to MT customers) to test CBPR+ messages for screening or archiving
purposes
Timeline
Available
Description
Inject manually / application-generated messages (ISO 20022) in the Readiness Portal to
test validity against the CBPR+ Usage Guidelines
Prerequisites
Access to Readiness Portal. The service is available to the community.
Related information
MyStandards Readiness Portal

3.2.2 Translation Portal

Purpose
The Translation Portal enables customers to test the mapping rules between the MT and
ISO 20022 formats and ensure downstream applications can be shielded from format
changes, where relevant.
The portal helps validate the structure of CBPR+ messages before connectivity to the
FINplus pilot service is in place.
Timeline
Available
Description
Inject manually / application-generated messages (ISO 20022 or MT) in the Translation
Portal to test alignment with CBPR+ translation rules
Prerequisites
Access to the Translation Portal. The service is available to the community.
Related information
Translation Portal Online Help.

3.2.3 Financial Crime Compliance

As ISO 20022 provides more granular, more structured and additional data elements,
compliance departments must revisit their screening environments to identify the impact and
opportunities ISO 20022 will bring. The compliance departments must also determine how
these additional data structures in ISO 20022 may be used by sanction screening
applications to support a more efficient and effective screening process.

13 April 2022 16
ISO 20022 Programme
Customer Testing Guidelines Generic Requirements for MT and ISO 20022 Customers

SWIFT recommends that customers go through the following check points and start
discussions with their compliance departments and compliance vendors early enough
before November 2022.
❑ Make sure your compliance department is aware about ISO 20022 and the
migration timelines
❑ Check with your compliance application vendor, if, how, and when they will support
ISO 20022 flows
❑ Consult the Guiding principles for screening ISO 20022 payments document on
swift.com which proposes guidelines for effective and efficient screening of ISO
20022 payments
❑ If you consider:
o using ISO 20022, check the impacts of additional data elements compared
to MT
o continuing using MT during the co-existence phase, be aware of possible
data truncation impacting the effectiveness of your controls
❑ Check with your compliance department how this may impact your compliance
processes and compliance policies
Related information about SWIFT products and services
If you are using a hosted screening or fraud solution from SWIFT, such as Payment
Controls or Transaction Screening, ISO 20022 is supported directly within the application.
For more information about SWIFT’s screening and fraud solutions, see www.swift.com >
Financial crime compliance.
If you want to know as of when the various ISO 20022 services (Market Infrastructure
migrations and CBPR+) will be supported by Payment Controls and Transaction Screening,
for Test and Training and Live, then see the Knowledge Base article 5025241.

3.2.4 Archiving of ISO 20022 or Multi-Format MX

All customers must prepare their archiving process to archive the ISO 20022 messages or,
alternatively, the multi-format MX messages.

3.2.5 Validate End-of-Day Processes

All customers must evaluate the impact and adapt their end-of-day and reporting processes
to the multi-format MX.

3.2.6 In-Flow Translation

Purpose
As part of the migration of cross-border payments towards ISO 20022 MX, SWIFT will
provide an In-flow Translation service. In-flow translation means that the translation
happens during the processing of the message at SWIFT. The service enables customers to
receive the translated MT embedded in the ISO 20022 MX over FINplus.
This approach aims at facilitating the integration in the receiver's application environment in
case not all applications can (yet) support the ISO 20022 format by November 2022. It helps
validate connectivity to the FINplus pilot service (reception, internal routing, and processing
of multi-format MX messages).
This following diagram describes the scope of the tests with ISO 20022 data sent on
FINplus and received as multi-format MX (ISO 20022 with embedded MT) after processing
by the In-flow Translation:

13 April 2022 17
ISO 20022 Programme
Customer Testing Guidelines Generic Requirements for MT and ISO 20022 Customers

Note In-flow Translation is independent of Transaction Manager. All eligible CBPR+

messages exchanged through FINplus go through In-Flow Translation by default,
whether these messages have been processed by Transaction Manager
(Transaction Manager does not contain any MX to MT translation module).
Timeline
The FINplus pilot future service with provisioned CBPR+ messages is available.
The In-flow Translation capability is available.
Description
Send ISO 20022 CBPR+ messages to oneself over the FINplus pilot future service to:
• test the reception, routing, and processing of inbound traffic (including multi-format
messages through In-flow Translation)
• test the validity of outbound traffic against Usage Guidelines based on the service
validation engine
Prerequisites
All eligible customers are automatically provisioned for the FINplus pilot future service. See
Appendix A Self-Testing – Checklist > footnote.
Related information
In-flow Translation Service Overview

3.2.7 Transaction Manager

The SWIFT platform mediates between institutions using different communication channels
and formats, ensuring interoperability amongst all members of the community.
Institutions can continue to use the MT format with the platform until the ISO 20022
migration deadline for cross-border payments and reporting in November 2025. They can
adopt new services (such as those provided through APIs) at their own pace.
The first release of the enhanced platform’s transaction management functionality, referred
to as Transaction Manager, will go live in November 2022 and will focus on cross-border
payments. Traffic build-up phases are planned after November 2022 to enable gradual
onboarding of ISO 20022 messages in Transaction Manager.
Transaction Manager is referenced in various test cases in this document. The most
important priority is that all customers are ready to receive multi-format MX from FINplus.
Your SWIFT messaging interface will indicate which transaction was processed by
Transaction Manager.
A Transaction Manager GUI will be made available. This GUI will be fully integrated in the
gpi Tracker GUI and the Basic Tracker GUI and will enable customers to visualise the
Transaction Copy. More details will be provided in subsequent releases of this document.
Transaction Manager will be released in the live environment in November 2022 and will be
generally available for community testing in September 2022.

13 April 2022 18
ISO 20022 Programme
Customer Testing Guidelines Generic Requirements for MT and ISO 20022 Customers

For details about Transaction Manager, see the SWIFT platform – Connectivity Guidance
document.

SWIFT customers must focus on their testing activities to ensure readiness to connect
to FINplus and to receive multi-format MX by November 2022.

Disclaimer
The Transaction Manager information provided in this document is provisional. Transaction
Manager is still under development. It is subject to community consultation through the
Platform User Group. Consequently, certain features and functions, including the ones
reflected in this document, may be subject to change based on further customer feedback
that may lead to updates to this document in the future.

13 April 2022 19
ISO 20022 Programme
Customer Testing Guidelines Customer Testing Journey for MT Customers

4 Customer Testing Journey for MT Customers

4.1 Business and Functional Testing
This chapter explains the various options for the customers to validate their functional
readiness to process their SWIFT traffic and operate their payment business after
November 2022.
The following diagram describes the journey that is documented in this chapter:

The main challenge for the MT customers is to be able to receive ISO 20022 messages and to
generate ISO 20022 CBPR+ test messages to send to themselves to simulate their daily
operations after November 2022.
To do so, they must:
• be ready ahead of the November 2022 deadline with the upgrade of their SWIFT
interface
• train their operations on the reception of multi-format MX that they will receive from
counterparties that will start sending live ISO 20022

4.1.1 Self-Testing
Purpose
MT customers must prepare the processing of their SWIFT traffic with multi-format MX and
operate their payment business after November 2022:
• FIN traffic is unchanged and remains on FIN
• ISO 20022 CBPR+ traffic sent by their counterparties (or sent by themselves) is
received on FINplus in multi-format MX – customers must:
− complete connectivity to the FINplus pilot service
− confirm their ability to handle the received multi-format MX messages
See 4.1.2.2 Use the Test Sparring Partner to Receive Multi-Format MX for more
information.
Timeline
Available. Phase recommended at the latest in Q1 2022. SWIFT strongly advises not to
delay this task beyond July/August 2022. This would not give you the time to be fully
prepared to receive multi-format MX messages.
Description
• Messaging interface: upgrade explained in the section Configuration Activities
• Preparation for multi-format MX processing: explained in the section In-Flow
Translation

13 April 2022 20
ISO 20022 Programme
Customer Testing Guidelines Customer Testing Journey for MT Customers

• Standards Testing: SWIFT recommends that customers that want to send and receive
ISO 20022 format messages validate these messages using the MyStandards
Readiness Portal
• Standards testing with internal applications and processes:

• Archiving solution: customers must test it if they decide to keep the multi-format MX
• FCC processes: customers must review them as explained in the section Financial
Crime Compliance
Prerequisites
Access to Readiness Portal. The service is available to the community.
Related information
Section MyStandards Readiness Portal
Section Translation Portal
MyStandards Readiness Portal
4.1.1.1 SWIFT gpi and ISO 20022
For gpi MT customers, the SR 2021 SWIFT gpi rulebook has been applicable since
November 2021 for gpi MT, ISO 20022, and confirmations processing.
MT customers must consult the gpi ISO Summary Of Impacts gCCT gCOV gFIT Services.
4.1.1.2 Universal Confirmations of pacs.008
Not applicable to MT customers who will not process pacs.008 in their back-offices.
MT customers will continue to receive MT payments over FIN. When an ISO leg is initiated
by the debtor bank by means of a pacs.008, the MT customer will receive a multi-format MX
on FINplus and the interface will extract the embedded MT 103 to be delivered to the back-
office.

13 April 2022 21
ISO 20022 Programme
Customer Testing Guidelines Customer Testing Journey for MT Customers

4.1.2 Testing with SWIFT

Test Sparring Partner
The Test Sparring Partner (TSP) enables MT customers to access tools to generate ISO
20022 messages that they can send to themselves. It also enables the customers with the
premium service level to customise test cases leading to field truncation in the translated
MT.
The Test Sparring Partner is used to validate functional integration with internal applications
to ensure functional readiness to process SWIFT traffic and operate payments business.

This section provides information about how to:

• access the Test Sparring Partner
• use the TSP to receive multi-format MX
• use the TSP for value-added services
4.1.2.1 Access the Test Sparring Partner
See 3.1.5 Accessing the Test Sparring Partner.
4.1.2.2 Use the Test Sparring Partner to Receive Multi-Format MX
The main purpose of TSP is to send ISO 20022 messages and simulate the role of the bank
in different business roles.
As an MT customer, you must validate that you can receive and process multi-format MX
messages. You can use the TSP to send to yourself an ISO 20022 and validate the
reception of multi-format MX over FINplus. This enables you to test the functional integration
with internal applications and ensure functional readiness to process multi-format MX (ISO
20022 with embedded MT).
Prerequisites
• All eligible FINplus pilot future customers are already registered for the FINplus service
with SWIFT (specifically for testing of inbound scenarios) and are eligible to access
TSP.
• A swift.com account is required to access the TSP. For more information about
swift.com accounts, see the swift.com Registration User Guide.

13 April 2022 22
ISO 20022 Programme
Customer Testing Guidelines Customer Testing Journey for MT Customers

• Access to the TSP must be set up as per 3.1.5 Accessing the Test Sparring Partner
• Users are assigned to the TSP by their institution's swift.com administrator. Within the
TSP, a user may be assigned the role of administrator, tester, or viewer. User roles are
explained further in the Test Sparring Partner for CBPR+ guide > How to Manage
Users.
• Two versions of the TSP platform are available:
− A free Universal version of the TSP platform for CBPR+ that uses pre-defined test
cases. This version is self-service.
− A paid Premium version that includes customisable test cases and reference data.
This version requires the assistance of SWIFT Professional Services.
Test cases
In the current version of the Test Sparring Partner you can validate the reception of the
multi-format MX (ISO 20022 format with embedded MT) by using inbound CBPR+ test
cases which are part of the general CBPR+ test catalogue.
The CBPR+ test catalogues are gradually enriched and will cover most of the CBPR+
message in the course of Q2 2022.
A dedicated Quick Start CBPR+ Test Catalogue will be created in the course of Q2 2022 to
cover a minimum, essential set of test scenarios, including the truncation scenarios.
4.1.2.3 Use the Test Sparring Partner for Value Added Services
Purpose
You can use the Test Sparring Partner (TSP) for Value Added Services to validate
functional integration with internal applications.
gpi business flows
You can test gpi flows using the TSP (gpi Customer Automated Testing - gCAT).
During the testing phase, gpi customers validate their gpi message flows in test mode, with
SWIFT acting as a business counterparty through the TSP gpi Customer Automated
Testing. gCAT interacts as a gpi counterparty in an automated manner based on pre-
defined test cases.
The test cases allowed with gCAT are communicated to the gpi customers as part of their
onboarding service pack.
The following services are covered in the current version of the Test Sparring Partner:
• Mandatory gpi services
− gCCT
− gCOV
− gSRP
• Optional gpi services
− gFIT
− g4C
− gpi Instant
− gCASE
− Pre-validation Data User
Additional test catalogues will be incrementally added to the TSP in the course of 2022. The
following ones are expected in Q2:
− Pre-Validation Data User

13 April 2022 23
ISO 20022 Programme
Customer Testing Guidelines Customer Testing Journey for MT Customers

− SWIFT Go
Prerequisites
• The Test Sparring Partner for the gCCT, gCOV, gSRP, gFIT, g4C, gpi instant, gCASE
is available to customers that are registered for the dedicated service. Order of an
onboarding package may be required for testing supported by gpi Customer Automated
Testing (gCAT).
• A swift.com account is required to access the Test Sparring Partner. For more
information about swift.com accounts, see the swift.com Registration User Guide.
• Access to the TSP must be set up as in per 3.1.5 Accessing the Test Sparring Partner
• Users are assigned to the TSP by their institution's swift.com administrator. Within the
TSP, a user may be assigned the role of administrator, tester, or viewer. For
information about the user roles, see the Test Sparring Partner for CBPR+ > Access
Management.
Test cases
In a future version of the TSP, the test catalogue will continue to be enriched and this
document will be updated accordingly.
• Pre-validation
− Around 100 test cases
− Grouped by role (Pre-validation Data User, Pre-validation Data Provider) and
Business Scenario (4 scenarios possible)
• SWIFT Go
− 17 test cases
− Grouped by role (originating agent; intermediary agent, creditor agent)
• Case Management for non-gpi customers
− 17 cases for Stop and Recall for non-gpi customers, grouped by role
− 20 cases for Case Investigation for non-gpi customers, grouped by assignment role
Related information
For more information about how to access the Test Sparring Partner and information about
how to manage other users' access to the Test Sparring Partner and configure Business
Identifier Codes (BICs), see the Test Sparring Partner for CBPR+.
SWIFTSmart module: Introduction to the Test Sparring Partner for CBPR+

4.1.3 Testing as a Community

Purpose
The objective is to validate business and technical interoperability, including In-flow
Translation, with selected counterparties and Payment Market Infrastructures (PMI).
Amongst the counterparties and PMIs, some are still using MTs while others are planning to
adopt ISO 20022.
This diagram shows the applications triggered by these tests.

13 April 2022 24
ISO 20022 Programme
Customer Testing Guidelines Customer Testing Journey for MT Customers

Note This is a self-organised community testing, that is, customers select their
counterparties and PMIs for the tests.
Timeline
CBPR+: SWIFT recommends doing these tests once they have tested with the Test
Sparring Partner.
The FINplus pilot future service with provisioned CBPR+ messages has been available
since November 2021 with In-flow Translation.
Description
• Simulate real-life traffic over the FINplus pilot service with selected counterparties.
Selection is based on, for example, volumes, criticality of flows.
• Inbound flows could be multi-format messages through FINplus In-flow Translation or
FIN with the FIN PMIs.
• Functional testing: tests are carried out based on pre-agreed scenarios and patterns.
• Testing with domestic PMIs is highly recommended prior to go-live.
Customers must validate the reception of inbound cross-border payments on FINplus,
translate internally these payments into PMI format and Usage Guidelines (MT, HVPS+,
proprietary), and relay the payment to the PMI on SWIFT or another channel. Typically
PMIs operate on a SWIFTNet service different from FINplus.
Details are available in the MI Adoption Guide.
• Reception of MT or domestic ISO 20022 from the PMI (outside FINplus) must also be
tested, as these payments are either relayed as MT messages and forwarded to the
next agent on FIN or converted to CBPR+ and forwarded to the next agent on FINplus.
• Messages rejected by the PMI and re-sent must also be tested.
Prerequisites
All eligible customers are automatically provisioned for the FINplus pilot future service. See
the footnote in Appendix A Self-Testing – Checklist.
Related information
Appendix C Testing with a Community – Checklist

4.2 Non-Functional Testing

4.2.1 Performance Testing
Purpose
Note Performance testing is optional for most users. It is, however, recommended for
high-volume customers with on-premises connectivity.

13 April 2022 25
ISO 20022 Programme
Customer Testing Guidelines Customer Testing Journey for MT Customers

Compared to the 2021 operations, MT customers expect to receive a percentage of their

inbound volume as multi-format MX, replacing the same amount of today’s MT volume.
Such percentage depends on the number of counterparties that will send ISO 20022 to
FINplus as of November 2022 and the volume sent by counterparties to individual MT
customers.
It is crucial that customers validate that their SWIFT infrastructure configuration can process
mixed-traffic volumes after November 2022.

SWIFT recommends that customers contact their counterparties and build traffic tables of
the volume expected to be sent as ISO 20022 as of November 2022.
The following figure illustrates the components that are included in this test:
Performance and Continuity 1

-
Timeline
Available since November 2021.

The testing dates must be agreed with SWIFT (see Knowledge Base Article 2008531)

Description
Based on their volumes, customers will send and receive their peak traffic using their test
SWIFT infrastructure to validate that the processing time is in line with their business SLAs.
The traffic will be composed of a mix of MT messages sent and received over FIN and multi-
format MX messages received on FINplus using InterAct store-and-forward.
Customers can simulate their peak traffic by:
• before the test, sending ISO 20022 to themselves to build a queue of multi-format MX
(see section 4.1.2.2 Use the Test Sparring Partner to Receive Multi-Format MX). TSP
cannot be used to generate large volumes of data. However, it is designed to issue a
variety of test scenarios that you can batch and send to yourself to prepare the test.
• during the test, sending MT to themselves and retrieving the previously generated
multi-format MX
Prerequisites
• SWIFT messaging interface must be updated to support multi-format MX.
• SWIFTNet configuration and provisioning must be completed.
Execution
These tests require a coordination with SWIFT (see Knowledge Base Article 2008531).

13 April 2022 26
ISO 20022 Programme
Customer Testing Guidelines Customer Testing Journey for MT Customers

Related information
Connectivity to SWIFT - Connectivity Packs for on-premises customers only: this
document has been updated to include the calculation of the required line bandwidth when
the traffic switches from MT to ISO 20022 or multi-format MX. ISO 20022 or multi-format MX
messages are larger than their corresponding MTs.
Note For the vast majority of the SWIFT community, the estimated additional line
required will be absorbed inside the current line capacity, so such customers do
not take any action. Customers may consult their individual leased line use report
at https://www2.swift.com/llurw/admin. Contact SWIFT Support for further
assistance.
ISO 20022 Customer Adoption Guide > Capacity Planning.

4.2.2 Business Continuity

Purpose
SWIFT recommends business continuity testing for all users.

The purpose is to validate that the customer SWIFT infrastructure and configuration can
meet their business continuity objectives.

The components that are included in this test are the same as in 4.2.1 Performance Testing:

Timeline
Available since November 2021.
Description
Based on their business continuity objectives and resilience set-up, customers will simulate
a failure in their SWIFT infrastructure and exercise their business continuity procedures to
ensure that the multi-format MX flows are properly recovered and that any potential
message gap can be recovered using SWIFTNet retrievals. In addition, customers applying
cold start procedures should re-test them.
Execution
Align your operations with the SWIFT schedule available here.
Related information
Introduction to Business Continuity Planning (SWIFTSmart module)
Business Continuity Planning and Alliance Infrastructure Resilience (SWIFTSmart module)
Business Continuity Planning and Alliance Lite2 Infrastructure Resilience (SWIFTSmart
module)

13 April 2022 27
ISO 20022 Programme
Customer Testing Guidelines Customer Testing Journey for MT Customers

Connectivity to SWIFT – Resilience Guide

13 April 2022 28
ISO 20022 Programme
Customer Testing Guidelines Customer Testing Journey for ISO 20022 Customers

5 Customer Testing Journey for ISO 20022

Customers
5.1 Business and Functional Testing
This chapter explains the various options for the customers to validate their functional
readiness to process their SWIFT traffic and operate their payment business after
November 2022.
The following diagram describes the step-by-step journey that is explained in this chapter.

5.1.1 Self-Testing
Purpose
The main objective of ISO 20022 customers is to get prepared for the processing of their
SWIFT traffic.
They must be able to:
• send ISO 20022 messages
• receive multi-format MX messages
The ISO 20022 traffic sent by their counterparties is received on FINplus in multi-format
MX. As a result, they must complete the connectivity to the FINplus pilot service and
confirm their ability to handle the received multi-format MX message.
• operate their payment business after November 2022.
FIN traffic remains unchanged and remains on FIN.
Timeline
Available. Phase recommended by the latest in Q1 2022.
Description
• Upgrade the messaging interface as explained in the section 3.1 Configuration
Activities (for All Customers)
• Prepare for multi-format MX processing as explained in the section In-Flow Translation

13 April 2022 29
ISO 20022 Programme
Customer Testing Guidelines Customer Testing Journey for ISO 20022 Customers

• Standards testing: customers that want to send and receive ISO 20022-format
messages must validate these messages using the MyStandards Readiness Portal.
• Scope of Standards testing with internal applications:

• test their archiving solution if they decide to keep the multi-format MX.
• prepare their FCC operating model as explained in the section Financial Crime
Compliance.
Prerequisites
Access to the MyStandards Readiness Portal. The service is available to the community.
Related information
Section MyStandards Readiness Portal
Section Translation Portal
MyStandards Readiness Portal
5.1.1.1 SWIFT gpi and ISO 20022
Purpose
The adoption of gpi traffic sent has been remarkable since the launch of gpi.
With the migration to ISO 20022, gpi customers are expected to send gpi-enabled
pacs.008 and pacs.009 payments (that is, with the Service Level element in the Payment
Type Information block of pacs.008 and pacs.009 set to the appropriate value) as they are
doing today with MTs 103, MTs 202, and MTs 202 COV.
Timeline
The SR 2021 SWIFT gpi rulebook has been applicable since November 2021 for gpi MT,
ISO 20022, and confirmations processing.
SWIFT recommends that ISO 20022 customers consult the gpi ISO Summary of Impacts
gCCT gCOV gFIT Services and webinar recordings (Knowledge Base article 5024984).
Deliverables for the gpi ISO 20022 adoption
There are four main deliverables for the gpi ISO 20022 adoption:
• Tracking of domestic and cross-border payment messages (pacs)
• Introduction of ISO 20022-based messages for interactions with the Tracker, as
equivalents to MTs and APIs:
− trck.001 – Tracker Payment Status Update
− trck.002 – Tracker Payment Status Information
− trck.003 – Tracker Alert Notification
− trck.004 – Payment Status Customer Tracker Report (g4C)
• Upgrade to Tracker API services v5 to cater for ISO 20022 data model

13 April 2022 30
ISO 20022 Programme
Customer Testing Guidelines Customer Testing Journey for ISO 20022 Customers

• Keep supporting Tracker confirmations in the current format/channels

Related information
For more information about SWIFT gpi ISO 20022 adoption features, see the following
resources:
- SWIFT gpi on the Knowledge Centre
- gpi Support Page
- Universal Confirmations Support Page
5.1.1.2 Universal Confirmations of pacs.008
As of 20 November 2022, SWIFT will extend the obligation to confirm inbound payments to
pacs.008.
The SWIFT users of categories Supervised Institutions (SUPE) and Payment System
Participants (PSPA) must confirm to the Tracker the outcome of the processing of all
pacs.008 received on SWIFTNet services enabled with InterAct6.
The Basic Tracker GUI is enhanced to support the manual confirmation of pacs.008.
Related information
Universal Confirmations Rulebook and SWIFTNet Service Description

5.1.2 Testing with SWIFT

Test Sparring Partner
The Test Sparring Partner can be used to validate the functional integration with internal
applications to ensure functional readiness to process SWIFT traffic and operate payments
business.
The following diagram describes the application landscape that can be triggered through the
TSP:

This section provides information about how to:

• access the Test Sparring Partner
• use the Test Sparring Partner for CBPR+ to trigger ISO 20022 CBPR+ message format
and business flows
• use the Test Sparring Partner for gpi ISO to test the gpi flows in ISO 20022 message
format
• use the Test Sparring Partner for Value Added Services to validate functional
integration of added-value services

6
pacs.008 received on SWIFTNet FINplus or from a SWIFTNet MUG managed by a Payment Market Infrastructure, of which
Usage Guidelines support the minimum Tracker requirement, must be confirmed to the Tracker.

13 April 2022 31
ISO 20022 Programme
Customer Testing Guidelines Customer Testing Journey for ISO 20022 Customers

Timeline
Available. Phase recommended by the latest in Q1 or Q2 2022.
Related information
How to access the TSP, manage other users' access to the Test Sparring Partner, and
configure Business Identifier Codes (BICs) is explained in the Test Sparring Partner for
CBPR+
SWIFTSmart module: Introduction to the Test Sparring Partner for CBPR+
5.1.2.1 Accessing the Test Sparring Partner
See 3.1.5 Accessing the Test Sparring Partner.
5.1.2.2 Use the Test Sparring Partner for CBPR+
Purpose
The objective of testing with SWIFT, using the Test Sparring Partner (TSP), is to validate
the functional integration with internal applications: sending, relaying, and receiving ISO
20022 format messages.
Using the Test Sparring Partner, you can exchange ISO 20022 CBPR+ messages with a
fictitious counterparty (that is, the BICs managed by TSP) over the FINplus pilot service to
test the processing of inbound and outbound traffic.
Timeline
Available
Prerequisites
• Customers must be registered for the FINplus service to use the Test Sparring Partner
for CBPR+.
• A swift.com account is required to access the TSP services. For more information
about swift.com accounts, see the swift.com Registration User Guide.
• Access to the TSP must be configured as per section 3.1.5 Accessing the Test
Sparring Partner.
• Users are assigned to the TSP by their institution's swift.com administrator. Within the
TSP, a user may be assigned the role of TSP administrator, tester, or viewer. User
roles are explained further in the Test Sparring Partner for CBPR+ guide > Access
Management.
• Two versions of the TSP platform are available:
− A free Universal version of the TSP platform for CBPR+ that uses pre-defined test
cases. This version is self-service.
− A paid Premium version that includes customisable test cases and reference data.
This version requires the assistance of SWIFT Professional Services.
Premium access
Users subscribed to the Premium version of the Test Sparring Partner can customise
reference data and test cases to meet their needs.
Most of the elements of CBPR+ messages can be configured as per the user testing needs
(for example, settlement method, priority, and remittance information).
Execution
For more information about test execution and report, see the Test Sparring Partner for
CBPR+ guide > Test Execution and Results.

13 April 2022 32
ISO 20022 Programme
Customer Testing Guidelines Customer Testing Journey for ISO 20022 Customers

Test cases
The Test Sparring Partner CBPR+ test catalogue contains a list of test cases accompanied
by the following information:
• test scenario
• direction of the test
• associated BICs
• date on which the test case was last updated
• status of the test case
The direction of a test may be:
Incoming: your institution receives a test message sent by the Test Sparring Partner
Outgoing: your institution sends a test message to the Test Sparring Partner
Relay: your institution both sends and receives test messages with the Test Sparring
Partner as the counterparty
Currently, test cases are available for the following messages:

Message type Inbound Outbound Relay

pacs.008 – incl. pacs.002 ✓ ✓ ✓
pacs.009 CORE – incl. pacs.002 ✓ ✓ ✓
pacs.009 COV – incl. pacs.002 ✓ ✓ ✓
pacs.004 – pacs.008 ✓ ✓ ✓
pacs.004 – pacs.009 ✓ ✓ ✓
camt.054 (Debit/Credit Notif ~MT 900/910) ✓ ✓ ✓
camt.053 (Statement ~MT 940/950) ✓ ✓ ✓
camt.052 (Account Report ~MT 941/942) ✓ ✓ ✓

Further test cases and additional messages (camt.054, camt.053, camt.052, camt.56,
camt.29, camt.57, camt.60, pacs.009.ADV, pacs.010, pain.001, pain.002, pacs.008
EEA/STP) will be available in a later version of the platform (by the end of Q2 2022).
You can view, download, and print test results in the form of a report. For more information
about test execution and report, see the Test Sparring Partner for CBPR+ guide > Test
Execution and Results.
Related information
For more explanations about how to prepare and execute a test with the Test Sparring
Partner, how to get a report, how to troubleshoot, and how premium users can customise
reference data and test cases, see the Test Sparring Partner for CBPR+ guide > Testing
Message Flows and Text Execution and Results.
5.1.2.3 Testing Using the Test Sparring Partner for gpi ISO
Purpose
Using the Test Sparring Partner, you can exchange ISO 20022 CBPR+ messages with a
fictitious counterparty over the FINplus pilot service to test the processing of inbound and
outbound traffic.
The objective of testing with SWIFT, using theTSP, is to validate the functional integration
with internal applications: sending, relaying and receiving gpi ISO 20022 messages

13 April 2022 33
ISO 20022 Programme
Customer Testing Guidelines Customer Testing Journey for ISO 20022 Customers

To execute the test cases, the gpi customers must exchange payment messages using test
data with test BICs and update the Tracker. The test cases allowed with gCAT are
communicated to the gpi customers as part of their onboarding service pack.
Timeline
Availability in Q2 2022.
Prerequisites
• Customers must be registered for the gpi service with SWIFT.
• Customer must be registered for the FINplus service with SWIFT.
• A swift.com account is required to access the TSP services. For more information
about swift.com accounts, see the swift.com Registration User Guide.
• Access to the TSP must be configured as per 3.1.5 Accessing the Test Sparring
Partner.
• Users are assigned to the TSP by their institution's swift.com administrator. Within the
TSP, a user may be assigned the role of administrator, tester, or viewer. User roles are
explained further in the Test Sparring Partner for CBPR+ guide > Access Management.
• gpi test cases’ execution is part of a SWIFT Professional Services package.
Test cases
The test cases allowed for gpi ISO 20022 will be communicated to the gpi customers as part
of their onboarding service pack.
The TSP for gpi ISO may only be used in the scope of a SWIFT Professional Services
agreement, except in case of a change to the SWIFT Standards or the SWIFT gpi Rulebook
for Mandatory Services, or additional rulebooks for optional services, where the gpi
community must validate new or existing gpi message flows. In that case, SWIFT will
organise a customer adoption programme, and will allow the gpi customer community to
temporarily use the Test Sparring Partner for gpi ISO.

The Test Sparring Partner for gpi ISO does not offer the same confidentiality
protection as the production environment. Consequently, gpi customers may
only test gpi message flows in the Test Sparring Partner for gpi ISO with test
data, and not with real transaction data. SWIFT disclaims any liability for
damages due to a gpi customer's use of real transaction data in the Test
Sparring Partner for gpi ISO.

The TSP for gpi ISO catalogue will contain a list of test cases accompanied with the
following information:
• test scenario
• direction of the test
• associated BICs
• date on which the test case was last updated
• status of the test case
Currently, the test cases are foreseen for the following services (the expected number of
cases is indicated between brackets):
• gCCT (38)
• gCOV (25)
• gFIT (23)
Supported messages: pacs.008, pacs.009 CORE, pacs.009 COVE, trck.001, trck.002,
pacs.002 (pending full implementation of reject by the Tracker).

Outbound Relay Inbound

gCCT 15 15 9

13 April 2022 34
ISO 20022 Programme
Customer Testing Guidelines Customer Testing Journey for ISO 20022 Customers

gCOV 7 12 6
gFIT 3 12 8

gFIT cover flow services will be available in a later version of the platform (end of Q2,
beginning of Q3 2022).
5.1.2.4 Testing Using the Test Sparring Partner for Value Added Services
Purpose
You can use the TSP for Value Added Services to validate functional integration with
internal applications.
In future versions of the TSP platform, dedicated test catalogues for the following value-
added services will be added in the Test Sparring Partner. This document will be updated
accordingly:
• Pre-validation (Bank is Pre-validation Data Provider role is available and planned
availability is end Q2 for Bank is Pre-Validation Data User role)
• SWIFT Go (planned availability Q2 2022)
• Case Management (gSRP and gCASE) for non-gpi customers (planned availability
Q2/Q3 2022)
Prerequisites
• A swift.com account is required to access the Test Sparring Partner. For more
information about swift.com accounts, see the swift.com Registration User Guide.
• Access to the TSP must be configured as per 3.1.5 Accessing the Test Sparring
Partner.
• Users are assigned to the TSP by their institution's swift.com administrator. Within the
TSP, a user may be assigned the role of administrator, tester, or viewer. User roles are
explained further in the Test Sparring Partner for CBPR+ guide > Access Management.
Test cases
In a future version of the TSP, dedicated catalogues will be available and this document will
be updated accordingly.
• Pre-validation
− Around 100 test cases
− Grouped by role (Pre-validation Data User, Pre-validation Data Provider) and
Business Scenario (4 scenarios possible)
• SWIFT Go
− 17 test cases
− Grouped by role (originating agent; intermediary agent, creditor agent)
• Case Management for non-gpi customers
− 17 cases for Stop and Recall for non-gpi customers, grouped by role
− 20 cases for Case Investigation for non-gpi customers, grouped by Assignment role

5.1.3 Testing as a Community

The objective is to validate business and technical interoperability, including In-flow
Translation, with selected counterparties that are planning to adopt ISO 20022.
Note This is a self-organised community testing, that is, customers select their
counterparties and Payment Market Infrastructures (PMIs) for the tests.
The following diagram shows the applications triggered by these tests:

13 April 2022 35
ISO 20022 Programme
Customer Testing Guidelines Customer Testing Journey for ISO 20022 Customers

Timeline
CBPR+: SWIFT recommends that customers do this testing after having tested with the Test
Sparring Partner.
The FINplus pilot service with provisioned CBPR+ messages has been available since
November 2021 with In-flow Translation.
Description
• Simulate real-life traffic over the FINplus pilot service with selected counterparties.
Selection is based on, for example, volumes, criticality of flows.
• Inbound flows will be multi-format messages through In-flow Translation.
• Functional testing: tests are carried out based on pre-agreed scenarios and patterns.
• Testing with domestic PMIs is highly recommended prior to go-live.
Customers must:
a. validate the reception of inbound cross-border payments on FINplus
b. translate internally these payments into PMI’s format and Usage Guidelines (MT,
HVPS+, proprietary)
c. relay the payment to the PMI on SWIFT or another channel. Typically PMIs operate
on a SWIFTNet service different from FINplus.
Details are available in the MI Adoption Guide.
• Reception of payments from the PMI must also be tested, as these payments are
typically converted to CBPR+ and forwarded to the next agent on FINplus.
Prerequisites
All eligible FINplus pilot future customers are already provisioned for the FINplus pilot future
service with SWIFT.
Related information
Appendix C Testing with a Community – Checklist
ISO 20022 Readiness Directory: a new SWIFTRef product that indicates whether a
participant is already sending ISO 20022 messages over FINplus. The directory is available
in the download area of the SWIFTRef data portal > Download area).

5.2 Non-Functional Testing

5.2.1 Performance Testing
Purpose
Note Performance testing is optional for most users. It is, however, recommended for
high-volume customers with on-premises connectivity.

13 April 2022 36
ISO 20022 Programme
Customer Testing Guidelines Customer Testing Journey for ISO 20022 Customers

Compared to the 2021 operations, ISO 20022 customers will expect to receive a percentage
of their inbound volume as ISO 20022 (or multi-format MX if In-flow Translation is activated),
replacing the same amount of today’s MT volume. Such percentage depends on the number
of counterparties that will send ISO 20022 to FINplus as of November 2022 and the volume
sent to these customers.
The purpose of the tests is to validate that the customer SWIFT infrastructure and
configuration can process their mixed traffic volumes after November 2022.
SWIFT recommends that customers contact their counterparties and build traffic tables of
the volume expected to be sent as ISO 20022 as of November 2022.
The following figure illustrates the components that are included in this test:
Performance and Continuity 1

Timeline
Available since November 2021.

The testing dates must be agreed with SWIFT (see Knowledge Base article 2008531).

Description
Based on their volumes, customers will send and receive their peak traffic using their test
SWIFT infrastructure to validate that the processing time is in line with their business SLAs.
The traffic will be composed of a mix of MT messages sent and received over FIN and ISO
20022 (or multi-format MX) messages sent and received using InterAct store-and-forward,
depending on their ISO 20022 readiness.
Customers can simulate their peak sent and received traffic by:
• before the test, sending ISO 20022 to themselves to build a queue of ISO 20022 (or
multi-format MX)
• during the test, sending ISO 20022 to themselves and retrieving the previously
generated ISO 20022 (or multi-format MX)
Prerequisites
• The SWIFT infrastructure must be updated to support ISO 20022 (or multi-format MX).
• The SWIFTNet configuration and provisioning must be completed.
Execution
The tests require coordination with SWIFT (see Knowledge Base Article 2008531)
Related information
Connectivity to SWIFT - Connectivity Packs for on-premises customers only: this
document has been updated to include the calculation of the required line bandwidth when
the traffic switches from MT to ISO 20022 or multi-format MX. ISO 20022 or multi-format MX
messages are larger than their corresponding MTs.

13 April 2022 37
ISO 20022 Programme
Customer Testing Guidelines Customer Testing Journey for ISO 20022 Customers

Note For the vast majority of the SWIFT community, the estimated additional line
required will be absorbed inside the current line capacity, so such customers
must not take any action. Customers may consult their individual leased line use
report at https://www2.swift.com/llurw/admin. Contact SWIFT Support for further
assistance.

5.2.2 Business Continuity

Note Business Continuity testing is recommended for all users.
The purpose of this testing is to validate that the customer SWIFT infrastructure and
configuration meet their business continuity objectives:

The following figure illustrates the components that are included in this test:
Performance and Continuity 2

Timeline
Available since November 2021
Description
Based on their business continuity objectives and resilience set-up, customers will simulate
failure in their SWIFT infrastructure and exercise their business continuity procedures to
ensure that the ISO 20022 flows are properly recovered and that any potential message gap
can be recovered using SWIFTNet retrievals. In addition, customers applying cold-start
procedures should re-test them.
Execution
Align your operations with the SWIFT schedule available here.
Related information
Introduction to Business Continuity Planning (SWIFTSmart module)
Business Continuity Planning and Alliance Infrastructure Resilience (SWIFTSmart module)
Business Continuity Planning and Alliance Lite2 Infrastructure Resilience (SWIFTSmart
module)
Connectivity to SWIFT - Resilience Guide

13 April 2022 38
ISO 20022 Programme
Customer Testing Guidelines Self-Testing – Checklist

Self-Testing – Checklist
To prepare your organisation for ISO 20022 and CBPR+, see the ISO 20022 Programme
Getting Started > Your Readiness Journey.
See also the diagram Customer testing activities planning 1 to align with the optimal
completion readiness timeline.
First checklist: Configuration steps
The first checklist enumerates the configuration steps that a customer must perform to
successfully connect to FINplus and analyse the compliance requirements.

Phase Sub-phase Objective Team Planned Done

involved by

Configuration Communication SWIFT products: there is no impact on

Interfaces SWIFTNet Link, Alliance (Remote) Gateway.
Check compliance with the SWIFT Release
Timeline.
Third-party products: Make sure it is updated
to correctly handle the new multi-format.
Messaging Configuring Alliance Access and Alliance
Interfaces Entry for FINplus Messaging
See the ISO 20022 Customer Adoption Guide >
Alliance Access and Alliance Entry.
Note: Alliance Access/Alliance Entry 7.6.x is
required for FINplus.
A dedicated SWIFTSmart curriculum provides
detailed information.
Alliance Messaging Hub
See the ISO 20022 Customer Adoption Guide
> Alliance Messaging Hub.
Note: AMH 4.1.6 does receive the multi-format
MX and passes it as-is to middleware.
AMH 4.2.x is required to extract the MX or MT
from the multi-format MX.
Alliance Lite2
See the Alliance Lite2 User Guide.
Third-party products: Make sure it is updated
to correctly handle the new multi-format
Alliance Cloud
See the ISO 20022 Programme Customer
Adoption Guide > Alliance Cloud.
FINplus and All eligible customers are automatically
SWIFTNet store- provisioned for the FINplus pilot future service7.
and-forward See details in the Knowledge Base article
5025106.
All the steps are described in the ISO 20022
Customer Adoption Guide > Configure your

7
See details in the KB article 5025106.

13 April 2022 39
ISO 20022 Programme
Customer Testing Guidelines Self-Testing – Checklist

Connection to SWIFTNet and FINplus Service

Subscription.
Send and Receive Traffic on FINplus
See the ISO 20022 Customer Adoption Guide >
Send Traffic on FINplus.
All the steps are already described.
Set up your Relationship Management (RMA)
See the ISO 20022 Programme Customer
Adoption Guide > Relationship Management
Application (RMA).
Note: For Test and Training traffic, the use of
RMA is optional and RMA filtering will not be
used by default.
To enable the RMA check on your interface, you
can activate the trial filtering option for the
swift.finplus!pc and swift.finplus!pf pilot services.
Compliance Validate Ensure appropriate screening of multi-format
screening MX or ISO 20022 messages
processes For customers using SWIFT in-flow screening
services: check that the messaging interface
and back-office route reject messages as per
Screening return code and correctly process
abort notifications.

Second checklist: Standards and Translation

The second checklist enumerates the Standards and Translation learning steps that a
customer must perform to successfully comprehend ISO 20022 and CBPR+.
See the detailed section ISO 20022 and CBPR+ in the ISO 20022 Customer Adoption
Guide, with the relevant checklists.

Phase Sub-phase Objective Team Planned Done

involved by

Standards and ISO 20022 Familiarise your teams with ISO 20022 with
business SWIFTSmart modules and read The ISO 20022
impact Adoption FAQ
CBPR+ Read the CBPR+ User Handbook and Usage
Guidelines.
All information is available on MyStandards and
gathered in a dedicated SWIFTSmart curriculum.

Message Use the MyStandards Readiness Portal to test

validation and messages against CBPR+ Usage Guidelines and
translation eliminate syntactical and semantic errors.
validation Inject manually application-generated messages
(ISO 20022 or MT) in the Readiness Portal or the
Translation Portal to test the alignment with CBPR+
translation rules.
Refer to the MyStandards CBPR+ Translation Portal
for the list of supported mappings MX to MT and MT
to MX
SWIFT Certified Increase your knowledge and motivate your teams
Expert through the Certification Tracks on swift.com.
ISO message When moving to ISO 20022, you must map your
flows and existing payments, reporting flows to ISO 20022,
translation and CBPR+ counterparts.

13 April 2022 40
ISO 20022 Programme
Customer Testing Guidelines Self-Testing – Checklist

Involve your vendor if you have deployed a payment

engine from a supplier.
Decide with your architects whether you want to
translate to ISO 20022 locally in your institution and
evaluate the tools required to define and deploy
translation rules efficiently.
See the ISO 20022 Customer Adoption Guide >
Translations.
Alternatively, rely on the SWIFT’s In-flow Translation
service. It always delivers inbound multi-format MX
(ISO 20022 with embedded MT), enabling your
systems to consume either ISO 20022 MX or MT.
See the In-flow Translation Service Overview and
the SWIFT platform – Connectivity Guidance.

Third checklist: reception from In-flow Translation

The third checklist enumerates the steps to validate the reception of In-flow Translation
results. These steps are valid once the customer has decided to use SWIFT’s in-flow
functionality.

In-flow Translation is activated by default to all BICs on FINplus. Customers that do

not want this functionality must contact SWIFT Support.

The following diagram illustrates (like in the Connectivity Guidance) potential set-up of
routing the multi-format MX to internal applications:

Phase Sub-phase Objective Team Planned Done

involved by

In-flow Self-test in-flow Select some CBPR+ sample messages and adapt
Translation them to your addresses (sender and receiver
DNs). See the list of supported messages in the In-
flow Translation Service Overview > Appendix A.
Send these messages to yourself on FINplus.

13 April 2022 41
ISO 20022 Programme
Customer Testing Guidelines Self-Testing – Checklist

Configure your interface to extract the MT format

from the received multi-format MX.
Route the MT to your payment engine and validate
successful processing.
Send ISO 20022 MT customers looking for options to send ISO
messages to 20022 messages to themselves must refer the
yourself sections Use the Test Sparring Partner to Receive
Multi-Format MX and Appendix B of this document.

Screening of The customers must evaluate whether they have

multi-format MX any requirements to access and process full ISO
20022 data to comply with local regulations on
Sanctions Screening.
If yes, then the full MX must be sent to the local
screening engine.
If no, then the MT data is screened.
Archiving of The customers must evaluate whether they have
multi-format MX any requirements to archive full ISO 20022 data to
comply with local regulations on content and
duration of data archiving.
If yes, then the full MX must be sent to the
archiving engine.
If no, then the MT data is archived.

13 April 2022 42
ISO 20022 Programme
Customer Testing Guidelines Testing with SWIFT – Checklist

Testing with SWIFT – Checklist

This checklist covers the preparation of tests using the Test Sparring Partner (TSP).
Pre-requisite: the ISO 20022 customer has done self-testing with In-flow Translation.

Phase Sub-phase Objective Team Planned Done

involved by

Testing with Consult the SWIFTSmart module: TSP Access

SWIFT Accessing the Guide for Customers
TSP
Swift.com access swift.com Registration User Guide

Assigning the TSP roles in swift.com. See the Test

Sparring Partner for CBPR+ User Guide > How to
Manage Users.

Accessing the Test Sparring Partner through

mySWIFT profile or through www2.swift.com/tsp.
Assign the relevant TSP roles (administrator, tester,
or viewer).
User roles are explained in the Test Sparring
Partner for CBPR+ User Guide > How to Manage
Users.
Consult the SWIFTSmart module: Introduction to the
Testing using the Test Sparring Partner for CBPR+
TSP Register for the FINplus service: FINplus | SWIFT -
- for reception of The global provider of secure financial messaging
multi-format MX services
- for CBPR+ For the paid premium version that includes
customisable test cases and reference data, order
implementation through SWIFT Professional
Services:
https://www.swift.com/myswift/ordering/order-
products-services/consulting-service
Note; the free-of-charge version of the TSP platform
exposes predefined test cases that cannot be
customised
Testing using the Register for the relevant service:
TSP for Value Pre-validation
Added services
(see timeline in https://www.swift.com/our-solutions/swift-gpi/pre-
Testing Using the validation-gpi-payments
Test Sparring
Partner for Value https://www.swift.com/myswift/ordering/order-
Added Services) products-services/payment-pre-validation

SWIFT Go
https://www.swift.com/myswift/ordering/order-
products-services/swift-go

Case Management
https://www.swift.com/myswift/ordering/order-
products-services/gpi-case-resolution

13 April 2022 43
ISO 20022 Programme
Customer Testing Guidelines Testing with a Community – Checklist

Testing with a Community – Checklist

This checklist enumerates the steps that a customer must perform to prepare for ISO 20022
or multi-format community testing.
Prerequisite: The customer must have performed self-testing with In-flow Translation or in-
house translation and testing with the Test Sparring Partner (TSP).

Phase Sub-phase Objective Team Planned Done

involved by

Test as a Select Select the counterparties you want to test with,

community counterparties based on (1) their readiness plan (same execution
Use the dates than yourself), (2) correspondent banking
SWIFTRef ISO relationship, (3) existing volume (consult Watch or
20022 Readiness Observer Analytics), (4) direct participant to the
Directory same Payment Market Infrastructure (PMI), (5)
presence in the ISO 20022 Readiness Directory
Elaborate a test strategy and define test plans.
Define how you will measure success
For more information about the ISO 20022
Readiness Directory, see the SWIFTRefdata portal.
Select PMIs Select the PMIs you want to test with, based on (1)
their plan to support ISO 20022, (2) you are a direct
participant, (3) how many of your correspondents
are also direct participants
For more details, see the ISO 20022 Programme -
MI Adoption Guide > Appendix A Checklists.

Understand the Consult the HVPS+ Usage Guidelines or other

PMI guidelines defined by the Market Infrastructure
requirements and Adapt your systems to process inbound and
assess impacts outbound messages compliant with PMI’s
guidelines.
Test your generated messages in MyStandards
portal.
See details in the MyStandards Readiness Portal -
User Guide
Define test cases Define outbound messages with each PMI and
with PMIs validate that cross-border inbound flows are properly
translated to these PMI outbound messages.
Define inbound messages with each PMI and
validate that domestic inbound flows are properly
either processed internally if you are creditor agent
or relayed to the next agent in CBPR+ format on
FINplus.
Identify the happy path scenario and the negative
test cases resulting from a reject from the PMI
RTGS.
Transaction Prepare your operations to receive transactions
Manager processed by Transaction Manager (that is, all the
ones initiated with a rich ISO 20022 pacs message
on FINplus).
As creditor agent, you will receive from Transaction
Manager the most complete data, even if a party in
the chain has processed with a less rich format (MT
or proprietary or HVPS+).
These tests are linked to the Transaction Manager
traffic build-up phases. See details in the SWIFT
platform Connectivity Guidance document.

13 April 2022 44
ISO 20022 Programme
Customer Testing Guidelines Testing with a Community – Checklist

Validate end-to- Agree on test timelines with your counterparties

end processing Execute the tests and share validation results with
your counterparties

13 April 2022 45
ISO 20022 Programme
Customer Testing Guidelines CBPR+ Testing Samples

CBPR+ Testing Samples

The MyStandards Cross-Border Payments and Reporting Plus page give access to CBPR+
samples that are ready for download and do work “as is” in the Readiness portal.
Access the samples
1. From the MyStandards Cross-Border Payments and Reporting Plus page > MT/ISO
20022 Translation, click Samples Library.

4. Click CBPR+ User Handbook Sample Messages.

5. Read the page information.

6. Click Download CBPR+ User Handbook Sample Messages to download the
samples.

13 April 2022 46
ISO 20022 Programme
Customer Testing Guidelines CBPR+ Testing Samples

7. Send a CBPR+ sample message to yourself.

The following diagram shows the structure of a pacs.008 downloaded from
MyStandards:

In order to use these messages and send them to yourself in loopback mode, you have
the following two options:
− Manually, through your SWIFT interface message entry GUI:

13 April 2022 47
ISO 20022 Programme
Customer Testing Guidelines CBPR+ Testing Samples

Prerequisites: your interface must be configured for FINplus, CBPR+ and have valid
routing rules for ISO 20022 processing in place
o SWIFTNet Technical Header: (not shown in the diagram above)
i. Define the addressing parties: add your Level3 Requestor DN (Sender) and
Level3 Responder DN (Receiver)8.
ii. Define the SWIFTNet service you will send this message to: add the
FINplus pilot future service swift.finplus!pf
o Application Header
i. Copy and paste the Application Header of the message (starting with
<AppHdr …> and closing with </AppHdr>) as text in the GUI.
ii. Validate (if required).
o Business Payload
i. Copy and paste the payload of the message (starting with <Document …>
and closing with </Document>) as text in the GUI.
ii. Validate (if required).
o When these steps are validated by your interface, send the message to yourself.
o Remove the envelope (starting with <Envelope xsi:schemaLocation …>).
In case of questions, contact your Supplier’s Support.
− Through file upload into your SWIFT interface using InterAct Store and Forward
(not FileAct). These steps may vary depending on your interface. See the product
documentation.
Prerequisites: your interface must be configured for FINplus, CBPR+ and have valid
routing rules for ISO 20022 processing in place.
o Define a file adapter:
i. Configure your interface to accept an XML ISO 20022 file from a directory.
ii. Define the routing to send the file content through SWIFTNet InterAct Store
and Forward.
o Create the file from the provided sample:
i. The envelope (starting with <Envelope xsi:schemaLocation …>) must be
replaced with the User’s own envelope (your interface accepts a specific
header for file transfer like XMLv2 for Access/Entry or AMP for AMH)
ii. SWIFTNet Technical Header: Add in your specific header, in the respective
fields, the Level3 Requestor DN (Sender) and Level3 Responder DN
(Receiver), and the FINplus pilot future service swift.finplus!pf
iii. Application Header and Business Payload: Copy and paste the
Application Header and the business payload of the message (starting with
<AppHdr …> and closing with </Document>) in the payload section of your
file envelope.
iv. Save your sample file.
o Load the file in your interface.
In case of questions, contact your Supplier’s Support.

8
Level3 Requestor DN (Sender) and Level3 Responder DN (Receiver) have the form ou=xxx,o=<your live BIC8>,o=swift

13 April 2022 48
ISO 20022 Programme
Customer Testing Guidelines SWIFT Error Codes

SWIFT Error Codes

Network Validation Rules for See SWIFTNet - Network Validation Rules for ISO 20022 and
ISO 20022 SWIFTNet Link 7.6 - Error Codes
In-flow Translation See details in the In-flow Translation Service Overview > Translation Reporting.
MyStandards Usage The CBPR+ Usage Guidelines for each CBPR+ message can be generated by
Guidelines Validation Rules using the Export function, either to pdf (full pdf) or excel (Rules tab). The
validation rules for each field are exported to the chosen format.
This diagram shows the view for pacs.008 Release 2.0:

13 April 2022 49
ISO 20022 Programme
Customer Testing Guidelines Legal Notices

Legal Notices
Copyright
SWIFT © 2022. All rights reserved.
You may copy this publication within your organisation. Any such copy must include these legal
notices.

Confidentiality
This publication contains SWIFT or third-party confidential information. Do not disclose this
publication outside your organisation without SWIFT’s prior written consent.

Disclaimer
SWIFT supplies this publication for information purposes only. The information in this publication
may change from time to time. You must always refer to the latest version available on
www.swift.com.

Translations
The English version of SWIFT documentation is the only official and binding version.

Trademarks
SWIFT is the trade name of S.W.I.F.T. SCRL. The following are registered trademarks of SWIFT:
3SKey, Innotribe, MyStandards, Sibos, SWIFT, SWIFTNet, SWIFT Institute, the Standards Forum
logo, the SWIFT logo and UETR. Other product, service, or company names in this publication are
trade names, trademarks, or registered trademarks of their respective owners.

13 April 2022 50