SWIFT Translator Mapping Libraries

Enabling ISO 20022 migrations

MICSS Tribe, Mapping Libraries Squad

Version: 2022-06-29
ISO 20022
Context

Mapping Libraries - Restricted 2

A global shift to ISO 20022

A rush to ISO 20022 Delivering next gen payments

ISO 20022 has been adopted by market ISO 20022 is the key standard in next gen
infrastructures in 70+ countries replacing payment schemes, including instant payments,
domestic or legacy formats move to 24x7, supporting open banking over
APIs, and others

Global domination Growing impact

In the next 5 years, ISO 20022 will dominate This shift is already impacting the
high-value payments, supporting over 80% of cross-border payment system; under the
transactions values worldwide Eurosystem ‘big bang’ move to ISO 20022

Mapping Libraries - Restricted 3

Planned Market Infrastructures Adoption of ISO 20022

CBPR+ (WW)

AMERICAS EMEA APAC

o TCH (US) o T2 (EU) o CHATS (HK)
o FEDWIRE (US) o E1/S1 (EU) o MEPS+ (SG)
o LVTS (CA) o CHAPS (UK) o PHILPASS (PH)
o STR (BR) o SAMOS (ZA) o RENTAS (MY)
o … o BESP (RU) o FC-RTGS (TW)
o BISS (BY) o BAHTNET (TH)
o … o …

80% of global high value payments volumes will adopt ISO

20022 by 2025
And Securities messages are also migrating…
Mapping Libraries - Restricted 4
Specific challenges linked to the ISO 20022 migrations
A theoretical framework

ISO cross border

ISO

MT counterparty
ISO

Incoming

Outgoing
Prop ISO MI guidelines
MT

MT
MT MI guidelines

Incoming Internal Outgoing

How do I handle various incoming How do I feed my different How to send the relevant format to my
formats and validate them? applications with the appropriate counterparty in accordance with the guidelines
content? and its processing capacity?

Mapping Libraries - Restricted 5

SWIFT Translator
What is it?

Mapping Libraries - Restricted 6

SWIFT Translator – Designer, Runtime and Deployment Options

1. Design 2. Build 3. Deploy

Validation

Translation Back Office Middleware Messaging

Enrichment Application Layer Interface

SWIFT
Translator
Runtime
Network

SWIFT Translator Designer SWIFT Translator Runtime SWIFT Translator is flexible and can be deployed :
 Define / maintain formats  Java-based component  As a standalone component in the back-office application or
 Define / maintain mappings exposing message middleware layer
validation, translation,
 Test and validate in U2A  As part of a SWIFT messaging interface (SIL, IPLA, AMH)
enrichment operations
 Define Runtime component  Or in multiple places for different translation purposes
 Component is configured
(business payload vs. technical header, multiple channels…)
based on where its deployed
(JAR / WAR / …)

Mapping Libraries - Restricted 7

Deployment – Standalone vs. Integrated in SWIFT Interface

Standalone component in the back-office Back Office

application or middleware layer Messaging
Middleware Network
 Flexible java-based component however it Interface
is stateless hence requires you to build all
integration logic and protocol mediation Java API Interface
around the runtime App. Server
 Integration performed by the customer
 Translation logic can be performed by
SWIFT Professional Services or by the
customer WebService Interface

Integrated component in the SWIFT interface Alliance Access

 Includes all integration logic and protocol Back Office Middleware AMH
mediation such as routing, connectivity, SWIFT
message aggregation…
SWIFT
 Translation logic and integration can be
Messaging
performed by SWIFT Professional Services
Interface
or by the customer

Mapping Libraries - Restricted 8

Predefined Libraries
What are they?

Mapping Libraries - Restricted 9

SWIFT Translator – Predefined Libraries

1. Design Cost & Time Savings

Save 100+ days of implementation
reusing predefined validation* and
mapping** libraries

Risk Reduction
Timely preparation for the ISO
migrations leveraging SWIFT
expertise

Mapping Library Reusability and

• Mapping library to jump-start
your project leveraging Customisation
SWIFT expertise Reuse SWIFT Translator for many
• Fine-tuning possibilities migrations (CBPR+, T2, EURO1, CHAPS,
MEPS+…) and customise it based on your
needs

* Validation libraries contain message formats and business rules to validate ISO 20022 messages against the defined usage guidelines for the given market
infrastructure.
** Mapping libraries contain message formats and translation rules to convert the main messages to/from MT/ISO 20022 for the given market infrastructure.

Mapping Libraries - Restricted 10

How to Use the Library

1. Directly from the JAR 2. Import in Designer to fine-tune

Calling application JAR library (API) Import and fine-tune Build (JAR, WAR…)
Input (Envelope / MT) and deploy

C:\>

Output (MT / Envelope)

• Call the library directly from your application • Import a single* library within SWIFT
using predefined APIs Translator Designer to customise, add flows
• Quick set-up or mappings as required
• No customisation needed • Build your services and operations or use
coarse API / project JAR / WAR method
• More flexibility

* Intended as a pre-built single library or compatible mapping and validation library pair

Mapping Libraries - Restricted 11

Library Release / Version Numbering
Technical Release Version. This is the version shown in the artefact (Jar or USA)
Business Version*. This is only shown in the roadmap and release letters to indicate the business/UG version of this release

1.3.2 (2.1)
Increment
Major

Minor

Major version: Each major version is a new product, new commercial price/contract and requires a new quote & order etc.

Minor version: Will change when the scope of the mapping library changes, i.e. to reflect new business version/UGs (such as CBPR+ 2.0 to 2.1) or if additional
mappings are added/removed.

Increment version: Will change for every release under each minor version. Usually reflecting incremental changes to existing mapping such as improvement or
defect fix. This may not be sequential as releases intended for internal use may have occurred.

* This usually named after the business version of the collection published on MyStandards.

Mapping Libraries - Restricted 12

Market Initiatives

Mapping Libraries - Restricted 13

Payment MIs – Mapping Libraries on the Roadmap
Library Country Base MI Go Live Timeline Library Status

CBPR+ * WW CBPR+ Nov 2022 Released

T2 / ESMIG EMEA HVPS+ Nov 2022 Released
EURO1 EMEA HVPS+ Nov 2022 Released
CHATS HK HVPS+ Q4 2023 Planned
MEPS+ SG HVPS+ L4L Aug 2022 Released

SCRIPS SG HVPS+ Enh. Jul 2023 Planned

CHAPS GB CBPR+ Enh. Apr 2023 Released

ISO Accelerator Pack Many HVPS+ Various Planned

Payments Canada CA HVPS+ Nov 2022 Released

* Includes SWIFT GO mappings

Note: Bahtnet (Thailand) and Philpass (Philippines) may be available through SWIFT Professional Service engagement.

Mapping Libraries - Restricted 14

Mapping Libraries Roadmap & Scope

• CBPR+ • BoE CHAPS

• SWIFT GO • ISO Accelerator Pack
• ESMIG Target 2 • Payments Canada Lynx
• EBA EURO1/STEP1 • SWIFT Net
• MAS
• MEPS+ L4L
• SCRIPS
• HKMA CHATS

Mapping Libraries - Restricted 15

Mapping Libraries Roadmap Confirmed Timing TBC Scope and Timing TBC Fix Only MI Service Live Released

2021 2022 2023

Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4

CBPR+ 1.2.1 1.3.1 (2.0) 1.3.2 (2.1)

MT 2022
1.4.x (2.1)
Coexistence until Nov-25

SWIFT GO *
1.0

T2 RTGS

MT SR 2023 Updates
MT 2022
1.2.1 1.3.0 (2.2) 1.3.1 1.4.0 (2.2 Apr 22) 1.5.x

Euro1 1.0 1.1 (2.2)

MT 2022
1.2.0 (2.2 Apr 22) 1.3.x

MEPS+ L4L MT 2022

1.0 1.1 1.2.0 1.2.1 (1.1) 1.2.3 (1.1) 1.2.4 1.2.5 1.3.0

SCRIPS MT 2022
2.0 (2.3) 2.1 (2.3)

CHATS (HK) MT 2022

1.0.0

CHAPS (Enh) MT 2022 Enh

1.0 (L4L/Enh) 1.1.3 1.1.4 (1.2) L4L - cancelled 1.2.0 (1.3)

ISO Accelerator
MT 2022
Pack 1.0.0

Payments Canada MT 2022

1.0 (R2) 1.1.0 (2.1) 1.2.0 (2.1) 1.3.x (2.1)

SWIFTNet MT 2022
1.0 1.1.0 1.2.x
Notes:
• Versioning legend – 1.3.1 (2.0): technical version (MI business version)
• * Included in CBPR+ library

1. Availability dates on SWIFT Translator Standalone, IPLA & SIL deployment models. For availability dates on AMH, please contact your account manager.
2. Black outlined diamonds indicate tentative, placeholder defect fixes if required and as priorities permit.

Mapping Libraries - Restricted 16

Mapping Library Pricing Scheme

Financial Institutions can opt for Mapping Libraries which come as a one-off price and a 20% yearly maintenance fee. A
mapping library will usually include the corresponding validation library.

The maintenance fee includes:

• Bug corrections, minor enhancements or minor additions of new message validations or mappings.
• Enhancements and additions are assessed by SWIFT on a case-by case basis and are either triggering a minor
or major version release of the library.
• Major releases are not part of the maintenance fee and will require the customer to purchase a new version of
the product (one-off price and yearly maintenance fee).

Important Notes:

1. Mapping libraries require a SWIFT Translator licence (bundle or runtime) or appropriate SWIFT interface product licence. They cannot be
used with 3rd party software translators.
2. The scope of each mapping library is carefully considered to cover the main use cases and high priority or high-volume messages. A
library will not contain full coverage of mappings for all messages in use by the market infrastructure.
3. These are core product libraries and will not contain mappings for messages that are not used by the given market infrastructure.
4. Try & Buy option for mapping libraries is not available. A limited, sample mapping library is available for demonstration purposes.

Mapping Libraries - Restricted 17

CBPR+

Mapping Libraries - Restricted 18

Mapping Library for CBPR+ - Messages in Scope
including Business Application Header

MT ISO 20022 CBPR+ Direction Version Availability Date

MT 103 * pacs.008 MT  ISO

MT 202 CORE / COV * pacs.009 CORE / COV MT  ISO
MT 103 RETURN / MT 202 RETURN * pacs.004 ISO  MT
November 2020
MT 199 / 299 REJT * pacs.002 Negative ISO  MT V1.2.1
(March 2021 V1.2.1)
MT 210 camt.057 ISO  MT
MT 900 camt.054 MT  ISO
MT 910 camt.054 MT  ISO

* These mappings will be updated, superseded or expanded in v1.3.0

Mapping Libraries - Restricted 19

Mapping Library for CBPR+ - Messages in Scope
including Business Application Header
MT ISO 20022 CBPR+ Direction Notes Version Availability Date

Supersedes V1.0. Supports:

pacs.008 CORE <> MT 103 CORE
MT 103 pacs.008 MT  ISO
pacs.008 STP > MT 103 CORE
MT 103 STP > pacs.008 CORE
pacs.009 CORE / COV / Supersedes V1.0. Added pacs.009 ADVICE >
MT 202 CORE / COV MT  ISO
ADV MT 202 CORE
MT 205 CORE / COV pacs.009 CORE / COV MT  ISO
MT 103 / 202 (CORE & COV) / 205
pacs.004 MT  ISO Field 72. Supersedes V1.0 103 / 202 RETURN
(CORE & COV) RETN
MT 103 / 202 (CORE & COV) / 205 1.3.1
pacs.002 Negative MT  ISO (Business August 2021
(CORE & COV) REJT
Mt 199 / 299 pacs.002 Negative ISO  MT version 2.0)

MT 192 / 292 camt.056 MT  ISO

MT 196 / 296 camt.029 MT  ISO
MT 940 camt.053 ISO  MT
MT 942 camt.052 ISO  MT
MT 900 / 910 camt.054 MT  ISO
MT 210 camt.057 ISO  MT

Notes:
1. V1.3.1 includes mapping from previous release unless stated.
2. Mappings remain subject to review with the introduction of the Transaction Management Platform.
3. This Mapping library is a commercial “on-premises” library which may differ in scope from the CBPR+ in-flow or TM translation products.
Mapping Libraries - Restricted 20
Mapping Library for CBPR+ - Messages in Scope
including Business Application Header
MT ISO 20022 CBPR+ Direction Notes Version Availability Date

MT 103 pacs.008 MT  ISO InstForNxtAgt change

pacs.009 CORE / COV /
MT 202 CORE / COV MT  ISO InstForNxtAgt change
ADV
MT 205 CORE / COV pacs.009 CORE / COV MT  ISO InstForNxtAgt change
MT 103 / 202 (CORE & COV) / 205
pacs.004 MT  ISO
(CORE & COV) RETN
MT 103 / 202 (CORE & COV) / 205
pacs.002 Negative MT  ISO
(CORE & COV) REJT
Mt 199 / 299 pacs.002 Negative ISO  MT
1.3.2 onwards
January 2022
MT 192 / 292 camt.056 MT  ISO (Business version 2.1)
MT 196 / 296 camt.029 MT  ISO
MT 940 camt.053 ISO  MT
MT 942 camt.052 ISO  MT
MT 900 / 910 camt.054 MT  ISO
MT 210 camt.057 ISO  MT

CRs, defect fixes, MT SR 2021

CRs, defect fixes, MT SR 2022 1.4.0 (Business version 2.1) August 2022

Notes:
1. V1.3.2 includes mapping from previous release unless stated.
2. Mappings remain subject to review with the introduction of the Transaction Management Platform.

Mapping Libraries - Restricted 21

SWIFT GO

Mapping Libraries - Restricted 22

Mapping Library for SWIFT GO - Messages in Scope
including Business Application Header
Input Output Direction Version Availability Date

MT 103 (SWIFT GO STP) pacs.008.001.08 MT > ISO

1.0.0 Q1 2022
pacs.008.001.08 MT 103 (SWIFT GO STP) ISO > MT

Note: SWIFT GO mappings are included in the CBPR+ library and not in a separate library. Validation library is separate from CBPR+.

Mapping Libraries - Restricted 23

ESMIG Target 2

Mapping Libraries - Restricted 24

Mapping Library for T2 RTGS - Messages in Scope
including Business Application Header
MT ISO 20022 T2 RTGS Direction Version Availability Date
MT 103 pacs.008 MT <> MX
MT 202 / MT 202 COV pacs.009 MT <> MX V1.0
August 2020
MT 900 camt.054 MX > MT (UDFS2.1 Feb. Addendum)

MT 910 camt.054 MX > MT

MT 940 camt.053 MX > MT V1.1
September 2020
MT 950 camt.053 MX > MT (UDFS2.1 Apr. Addendum)

MT 012 pacs.002 Positive MX > MT

MT 019 pacs.002 Negative MX > MT V1.2
(Based on UDFS2.1 Apr. March 2021
MT 204 pacs.010 MT <> MX Addendum)
MT 103 RETURN / MT 202 RETURN pacs.004 ISO > MX
UDFS 2.2 Updates
V1.3.x
Multi-Addressee Feature September 2021
(Based on UDFS2.2)
MT SR2021 Updates
MT 103 RETURN / MT 202 RETURN pacs.004 MT > MX
V1.4.0 (Based on 2.2 Apr 22) May 2022
UDFS 2.2 Apr 22 / SWP 4.1 Updates
Defect fixes, MT SR 2022 1.5.0 (Business version 2.2 Apr 22) July 2022

Notes:
1. The introduction of ISO 20022 brings some new workflows / use cases which did not exist for MT use cases and are therefore not in scope for mappings to/from MT.
2. T2 CLM is a new, ISO native system therefore no mapping library is available for this.
Mapping Libraries - Restricted 25
EBA Clearing EURO1/STEP1

Mapping Libraries - Restricted 26

Mapping Library for Euro1 - Messages in Scope
including Business Application Header
MT ISO 20022 Euro1 Direction Version Availability Date

MT 103 pacs.008 MT  ISO

MT 202 / MT 202 COV pacs.009 MT  ISO
MT 970 camt.053 ISO  MT
MT 900 camt.054 ISO  MT
MT 910 camt.054 ISO  MT
MT 012 pacs.002 Positive ISO  MT

MT 019 pacs.002 Negative ISO  MT V1.0

July 2021
(Based on tech version v20)
MT 204 pacs.010 MT  ISO

MT 103 RETURN / MT 202 RETURN pacs.004 ISO  MT

MT 198 / MT 298 camt.056 MT  ISO

MT 998 camt.029 ISO  MT

MT 972 camt.052 ISO  MT

MT SR2021 Updates V1.1.x
December 2021
UDFS 2.2 Updates (T2 UDFS 2.2 – April 2021)
UDFS 2.2 Apr 2022 Updates V1.2.x (Based on 2.2 Apr 2022) April 2022
Defect fixes, MT SR 2022 1.3.0 (Business version 2.2 Apr 2022) July 2022
Note: The introduction of ISO 20022 brings some new workflows / use cases which did not exist for MT use cases and are therefore not in scope for mappings to/from MT.

Mapping Libraries - Restricted 27

MAS

− MEPS+ Like-For-Like
− SCRIPS

Mapping Libraries - Restricted 28

Mapping Library for MEPS+ - Messages in Scope
including Business Application Header
MT ISO 20022 MEPS + Direction Version Availability Date

MT 103 / MT 103+ pacs.008 MT  ISO

MT 202 CORE / COV pacs.009 MT  ISO
MT 900 / MT 910 camt.054 ISO  MT
MT 940 / MT 950 camt.053 ISO  MT
V1.0 (L4L) January 2021
MT 192 / MT 292 camt.056 MT  ISO
MT 196 / MT 296 camt.029 ISO  MT
MT 010 xsys.010 ISO  MT
MT 011 xsys.011 ISO  MT
MT 290 camt.077 ISO  MT
MT 298 camt.998/021 ISO  MT
MT 920 camt.060 MT  ISO
V1.1 (L4L) May 2021
MT 941 / MT 942 camt.052 ISO  MT
MT 996 camt.029 ISO  MT
MT 990 camt.077 ISO  MT
Remove xsys.010/011 V1.2 (L4L) onwards
October 2021
MT SR2021 Updates (Based on tech version 12)

Defect fixes 1.2.5 (Business version 1.1) Early July 2022

Defect fixes & MT SR 2022 1.3.0 (Business version 1.1) August 2022

Mapping Libraries - Restricted 29

Mapping Library for SCRIPS Enhanced - Messages in Scope
including Business Application Header
MT ISO 20022 SCRIPS Direction Version Availability Date

MT 103 pacs.008.001.08 MT > MX

MT 103 STP pacs.008.001.08 MT > MX
MT 202 pacs.009.001.08 MT > MX
MT 202 COV pacs.009.001.08 MT > MX
MT 192 camt.056.001.08 MT > MX
MT 292 camt.056.001.08 MT > MX
MT 920 camt.060.001.05 MT > MX
2.0
MT 298 camt.021.001.06 MX > MT (Business version 2.3, tech June 2022
MT 196 / 296 / 996 camt.029.001.09 MX > MT version 8)
MT 941 / 942 camt.052.001.08 MX > MT
MT 940 / 950 camt.053.001.08 MX > MT
MT 900 / 910 camt.054.001.08 MX > MT
MT 290 / 990 DRAFT6camt.077.001.01 MX > MT
MT 298 camt.998.001.02 MX > MT
MT 103 / 103 STP pacs.008.001.08 MX > MT
MT 202 / 202 COV pacs.009.001.08 MX > MT
MT 320 camt.050.001.05 (extensions tbc) MT > MX
2.1
Q3 2022
MT 398 camt.025.001.05 MX > MT (Business version 2.3, tech
TBC
version 8)
Defect fixes, MT SR 2022

Notes
1. MAS is renaming MEPS+ to SCRIPS for this enhanced go live in July 2023.
2. SCRIPS will be a major release for MEPS+ Enhanced and therefore a new product. Pricing aligned with MEPS+.
Mapping Libraries - Restricted 30
HKMA CHATS

Mapping Libraries - Restricted 31

Mapping Library for CHATS HK - Messages in Scope
including Business Application Header

MT ISO 20022 CHATS Direction Version Availability

Date
MT 103 pacs.008 ISO > MT
MT 103 RETN pacs.004 ISO > MT
MT 202 pacs.009 ISO > MT
MT 202 COV pacs.009 COV ISO > MT
2022
MT 202 RETN pacs.004 ISO > MT TBC
TBC
MT 012 / 019 pacs.002 (pos/neg) ISO > MT
MT 900 / 910 camt.054 ISO > MT
MT 940 camt.053 ISO > MT
MT 950 (TBC) camt.053 ISO > MT
MT 103 pacs.008 MT > ISO
MT 103 RETN pacs.004 MT > ISO
MT 202 pacs.009 MT > ISO
MT 202 COV pacs.009 COV MT > ISO
MT 202 RETN pacs.004 MT > ISO
camt.029 (TBC)
camt.056 (TBC)

DRAFT – TO BE CONFIRMED
Mapping Libraries - Restricted 32
BoE CHAPS

Mapping Libraries - Restricted 33

Mapping Library for CHAPS UK - Messages in Scope (1 of 2)
including Business Application Header
Input Output Direction Notes Version Availability Date

MT 103 pacs.008.001.08 MT > ISO L4L & Enh UG

MT 202 pacs.009.001.08 MT > ISO L4L & Enh UG
MT 202 COV pacs.009.001.08 MT > ISO L4L & Enh UG
MT 103 RETURN pacs.004.001.09 MT > ISO Enh UG
MT 202 RETURN pacs.004.001.09 MT > ISO L4L & Enh UG
pacs.008.001.08 MT 103 ISO > MT L4L & Enh UG
V1.0 June 2021
pacs.009.001.08 MT 202 ISO > MT L4L & Enh UG
pacs.009.001.08 MT 202 COV ISO > MT L4L & Enh UG
pacs.004.001.09 MT 103 RETURN ISO > MT Enh UG
pacs.004.001.09 MT 202 RETURN ISO > MT L4L & Enh UG
xsys.010 MT 010 ISO > MT
xsys.011 MT 011 ISO > MT

Mapping Libraries - Restricted 34

Mapping Library for CHAPS UK - Messages in Scope (2 of 2)
including Business Application Header
Input Output Direction Version Availability Date

pacs.002.001.10 (NEG) MT 019 ISO > MT

pacs.002.001.10 (POS) MT 012 ISO > MT
camt.053.001.08 MT 950 ISO > MT
admi.004.001.02 MT 298 / 003 ISO > MT
admi.004.001.02 MT 298 / 004 ISO > MT
camt.052.001.08 MT 298 / 010 ISO > MT 1.1
(Business version 1.2, tech version 3 (L4L) & November 2021
camt.054.001.08 MT298 / 011 ISO > MT 4 (Enh))
camt.054.001.08 MT298 / 012 ISO > MT
camt.054.001.08 MT298 / 013 ISO > MT
camt.054.001.08 MT298 / 014 ISO > MT
Remove xsys.010/011
MT SR2021 Updates
L4L Removed / Renamed V1.1.4 (Business version 1.2 Enhanced) March 2022
UG updates, defect fixes, MT SR 2022 V1.2.0 (Business version 1.3, tech version 6) August 2022

Notes
1. As of 17 Jan 2022 – BoE announced change to RTGS migration, cancelling L4L phase and now a single, big bang (enhanced) go live in Apr 2023
2. V1.1.4 removed or renamed L4L mappings.

Mapping Libraries - Restricted 35

ISO Accelerator Pack

Mapping Libraries - Restricted 36

Mapping Library for ISO Accelerator Pack - Messages in Scope
including Business Application Header

MT ISO 20022 Direction Notes Version &

Availability Date
MT 103 pacs.008 MT  ISO Core only, no specific STP mapping. No Remit.
MT 202 / MT 202 COV pacs.009 MT  ISO
MT 103 / 202 RETN pacs.004 MT  ISO
MT 103 / 202 RJCT pacs.002 Negative MT  ISO
MT 204 pacs.010 MT  ISO
MT 192 / MT 292 camt.056 MT  ISO
1.0.0
MT 196 / MT 296 camt.029 MT  ISO (Business version 1.0,
MT 940 camt.053 MT  ISO tech version 4)

MT 950 camt.053 MT  ISO

MT 900 camt.054 MT  ISO Q4 2022 TBC
MT 910 camt.054 MT  ISO
MT 941 camt.052 MT  ISO
MT 942 camt.052 MT  ISO
MT 920 camt.060 MT  ISO
MT 012 pacs.002 Positive ISO  MT
MT 019 pacs.002 Negative ISO  MT

Mapping Libraries - Restricted 37

Payments Canada Lynx

Mapping Libraries - Restricted 38

Mapping Library for Payments Canada - Messages in Scope
including Business Application Header
Input Output Direction Version Availability Date

MT 103 pacs.008.001.08 MT > ISO

MT 205 pacs.009.001.08 MT > ISO
MT 205 COV pacs.009.001.08 MT > ISO
MT 103 RETURN pacs.004.001.09 MT > ISO
MT 205 RETURN pacs.004.001.09 MT > ISO 1.0.0
pacs.008.001.08 MT 103 ISO > MT UG Release Two
February 2022
pacs.009.001.08 MT 205 ISO > MT
pacs.009.001.08 MT 205 COV ISO > MT
pacs.004.001.09 MT 103 RETURN ISO > MT
pacs.004.001.09 MT 205 RETURN ISO > MT
xsys.002 MT 012 XML > MT
1.0.0 (UG N/A)
xsys.003 MT 019 XML > MT
UG / CBPR+ 2.1 Updates 1.1.0 (Core Messages 2.1) Apr 2022
camt.053 MT 940 ISO > MT
1.2.0 (Reporting Messages 2.1) June 2022
Defect fixes
Defect fixes, MT SR 2022 1.3.0 (Business version 2.1) July 2022

Mapping Libraries - Restricted 39

SWIFT Net

Mapping Libraries - Restricted 40

Mapping Library for SWIFTNet - Messages in Scope

MT XML Direction Version Availability Date

MT 010 xsys.010.001.02 XML > MT

1.0.0 Q4 2021
MT 011 xsys.011.001.02 XML > MT
MT 010 xsys.010.001.01 XML > MT
1.1.0 May 2022
MT 011 xsys.011.001.01 XML > MT
MT SR 2022 1.2.0 July 2022

Mapping Libraries - Restricted 41

 www.swift.com

Mapping Libraries - Restricted 42