1. The success of ISO 20022 – Universal financial Industry message scheme
ISO_20022_SV_v144

2. ISO 20022 The ISO recipe for financial messages
ISO Universal financial industry message scheme, the recipe:
syntax neutral business modelling methodology
syntax specific design rules
industry led development/registration process
financial repository on
reverse engineering approach to ease coexistence
ISO is not a suite of message standards but a recipe proposed by ISO to develop message standards for all domains of the financial industry.
The recipe contains the ingredients shown.
The most innovative characteristic of ISO is its modelling methodology which decouples the business standard from the physical message formats. The models evolve with the business, while the formats evolve with the technology to benefit from the latest innovations with regard to automation, ease of implementation, openness and cheapness of products, etc. This ISO recipe offers a better, cheaper and faster way of developing and implementing message standards.
The syntax specific design rules cover the conversion of message models to XML (eXtended Markup Language) or ASN.1 (Abstract Syntax Notation One) schemas.
The combination of the first and last ingredients (the business modelling methodology and the reverse engineering approach) makes the ISO recipe a unique development tool kit. It proposes a single target (convergence) while offering at the same time a tool to ease interoperability with other existing message sets (coexistence).
ISO_20022_SV_v144

3. Why ISO 20022? Supports convergence and co-existence
IFX
ISO 15022
MDDL
TWIST
FIX
FpML
Message
model
IFX
TWIST
When standards are developed independently of each other, ‘translating’ from one standard to another requires to map data directly from one application to another and vice-versa. This is costly, unscalable and difficult to implement and maintain. Each time you add a new standard to support, it increases the complexity and cost exponentially.
Using a single message model as a master model reduces the translation effort since each standard only needs to translate to the master to ensure a link with any other standard.
Such an approach of developing syntax-independent business models is the core of the ISO standard…
Longer term, the physical ISO messages generated from the model would become the one and only standard we are looking for. While getting there, the message model helps co-existence. Furthermore, if it is more efficient to use another syntax for a particular business area or a particular market segment, starting from the ISO message models to generate the messages in this other syntax ensures that the business information will flow smoothly from one message to another whichever the syntax used to transport this business information.
Message
model
MDDL
FpML
FIX
Long term we want one standard,
but in the interim several standards need to co-exist…
ISO_20022_SV_v144

4. Why ISO 20022? Convergence in the cooperative space
Competitive
Space
Cooperative Space
Competitive
Space
Public
Admini-
strators
SME’s
Financial
Institutions
Corporates
Merchants
Consumers
High Value Payments:
RTGS, EURO1 and CHIPS
Financial
Institutions
Public
Admini-
strators
Corporates
SME’s
Merchants
Consumers
FX and Money Markets:
Rule Books, CLS
Commercial Payments:
Rule Books, Clearing Houses,
Processors
The ISO standardisation effort takes place in the cooperative space. As such it allows all financial players to maintain their competitive edge.
Bank A
Bank B
Cards:
Rule Books, Card Schemes,
Cards Processors
Tradefacilitation:
ICC Rule Books, e-invoicing
Cash:
NCB rules, Industry Standards
Securities:
Rule Books, Exchanges, CCP’s
CSD’s, Standardisation
Certification & Networks:
SWIFT
Cooperative space for business rules
Cooperative space for standards
ISO_20022_SV_v144

5. The ISO 20022 recipe - For whom? Potential users and developers
Communities of users looking for interoperability and more cost-effective communications
Message development organisations: ACORD, ANBIMA, ASF, Berlin Group, BIAN, CBI Consortium, Early Warning Services, FPL, FpML, IFX Forum, nexo, OAGi, SWIFT, Tieto, TWIST, XBRL, etc.
Market Infrastructures (MIs): Bank of England, China Foreign Exchange Trade System, China UnionPay, Clearstream, CLS, DTCC, EBA, European Central Bank, Banque de France, Banca de España, Deutsche Bundesbank, Banca d’Italia, Euroclear, FED, Omgeo, Target, T2S, ESMA, ASX etc.
International or national standards setters: EPC, Federation of Finnish Financial Services (FFI), ISITC, ISO WGs, NPSO, Russian Corporate Market Practice Group (RU-CMPG), UN/CEFACT, South African Bureau of Standards (SABS), SPRING, SMPG etc.
To whom is the ISO recipe targeted?
The ISO platform is available to all developers of message standards (they don’t need to be affiliated to ISO). And the ISO message standards are freely and publicly available to all communities of users.
The goal is to attract all developers of financial message standards. They will continue to focus on their domain of expertise and keep their Intellectual Property Rights (IPR) on the ISO compliant messages they develop while all together offering the community a range of messages in the same language, as if they were developed by a single body.
The organisations ‘in blue’ on the slide have already engaged in ISO message development.
Market infrastructures (ACHs, RTGS, [I]CSDs, etc.) are adopting and pushing developers to embrace the ISO standard for the benefit of their common customers.
Industry initiatives and regulatory requirements, such as SEPA, Target2-Securities, Giovannini and MiFID, MiFIR, EMIR, SFTR which all look for open standards to support their harmonisation of business practices, are all recommending adoption of ISO 20022…
There are also catalysts for interoperability and convergence, such as SEPA, T2S, Giovannini, MiFID, MiFIR, EMIR
ISO_20022_SV_v144

6. ISO 20022 registration bodies
Registration Management Group - RMG
(Overall governance)
80 senior managers from 21 countries and 16 international organisations
Standards Evaluation Groups – SEGs
(User representatives)
Securities (80 experts, 19 countries, 9 organisations) and Derivatives SubSEG (54 experts, 8 countries, 10 organisations)
Payments (65 experts, 20 countries, 7 organisations)
Cards and related retail financial services (33 experts, 17 countries, 5 organisations)
Trade Services (18 experts, 10 countries, 1 organisation)
Forex (18 experts, 9 countries, 3 organisations)
Technical Support Group – TSG
(ISO technical advisors)
33 experts from 9 countries and 10 international organisations
Registration Authority – RA
(Maintaining ISO repository)
The industry is directly involved in the acceptance, review and evaluation of candidate ISO messages submitted by the submitting organisations.
The Registration Management Group (RMG) is the highest registration body. It is made up of senior industry experts representing countries and international organisations. All together, they represent all sectors of the financial industry. The role of the RMG is to promote and support the involvement of financial service actors to facilitate the registration and maintenance of high quality globally relevant ISO compliant business models for exchange of information for financial services. Its mission is to ensure that ISO is a trusted standard providing high quality business models for exchange of information for financial services.
The RMG supervises the overall registration process. It approves the business justifications introduced by submitting organisations that want to develop new ISO messages. It also initiates the creation of the Standards Evaluation Groups (SEGs).
The Standards Evaluation Groups (SEGs) and SubSEGs are groups of industry experts, which each represents the future users of ISO messages in a particular financial domain. Their role is to ensure that the candidate ISO messages actually address the needs of the future users.
The Technical Support Group (TSG) is composed of technical experts, who can advise the submitting organizations and the other ISO registration bodies on technical matters related to the use of the ISO recipe, e.g., modelling guidelines, usage of XML or ASN.1, repository management, impact of innovations, etc.
The Registration Authority (RA) is the guardian of the ISO financial repository. SWIFT has been nominated by ISO to provide the RA services. The RA supports the submitting organisations in their development effort, ensures compliance of the developed models and performs the transformation of message models into compliant ASN.1 or XML schemas. The RA is also responsible for the maintenance of the ISO website ( which contains detailed information on the ISO message portfolio and the status of all ISO projects.
The RMG and the first two SEGs were initiated in 2005 and the next two SEGs in 2006, while the fifth SEG and the TSG were created in The Derivatives SubSEG was created in As you can see from the figures on the slide, ISO is quite successful in attracting the interest of the industry worldwide.
ISO_20022_SV_v144

7. ISO 20022 The registration process Development Process
Submitting
organisation
Financial industry group or standards body
Business
justification
Business justification
RMG
Project approval & allocation to a SEG
Once the Business Justification is approved by the RMG, and as long as the messages have not been approved by the SEG, the messages are called ‘candidate ISO messages’. Once they are approved by the SEG for publication, the messages are called ‘ISO messages’ or ‘ISO compliant messages’.
Candidate ISO messages
Submitting organisation
& RA
Development & provisional registration
SEG
Business validation
ISO messages
Official registration
and publication RA
Repository
Dictionary
Optional pilot testing
or first implementers
Submitting organisation
& users
Catalogue
ISO_20022_SV_v144

8. ISO 20022 registration process Yearly maintenance process
Timing
By June 1
Users introduce Change Requests to the RA
Users CRs
SEG
SEG screens Change Requests (CRs)
By July 7
Submitting organisation prepares ‘Maintenance Change Request’ with each CR implementation
By August 21
Submitting
organisation
Once approved, the ISO messages can be maintained upon request of the users or submitting organisations. There are several kinds of maintenance processes, to adapt to the needs and urgency of each community of users.
The ISO maintenance processes are described at The most common maintenance process is the yearly maintenance cycle that is described below.
The yearly maintenance cycle includes the following steps:
All Change Requests (CRs) are to be sent to the RA by June 1 using a “Change Request Template” . Anybody can introduce a CR. All received CRs are published in the Catalogue of Change Requests (
2) Valid CRs received prior to June 1 are evaluated by the SEG(s) that approved the initial version of the messages. Purpose of this initial evaluation is to eliminate the CRs that are not worth investigating further and to decide whether CRs that are worth considering should be implemented in the upcoming yearly maintenance cycle or can wait for another year.
3) Selected CRs for the upcoming cycle are forwarded to the submitting organisation in charge of the maintenance of the messages for investigation. This results in a “Maintenance Change Request” document describing how each change request could be implemented. The Maintenance Change Requests are published in the Status of Submissions (
4) The SEG reviews the Maintenance Change Request and approves or rejects each of the CRs.
5) The submitting organisation develops candidate new versions of the messages incorporating the approved CRs. The RA verifies the compliance of the candidate new versions and generates the evaluation documentation for the SEG. This draft documentation is also published as advance information.
6) The SEG validates that the candidate new versions indeed include the approved changes as agreed in the Maintenance Change Request.
7) The approved new versions of messages are published by the RA. This generally happens in February, if the new versions presented to the SEG are valid. It may happen later if the SEG requires changes before publication.
8) The first implementers of the new versions are invited to comment on the ‘technical implementability’ of the messages and the accuracy of the documentation published on the website. Possible changes or corrections requested by first implementers will be evaluated by the SEG, the RA and the submitting organisation and may lead to changes to the messages and/or documentation.
If approved by the SEG, this maintenance cycle can be used in a ‘urgent unscheduled’ mode in case of urgent Change Requests that cannot wait for the next yearly cycle.
There is also a ‘Fast Track maintenance process’ that can be initiated any time but is restricted to submitting organisations that can develop themselves the new versions of the messages (see
SEG
By October 1
SEG approval/rejection
Development of candidate new versions
Provisional publication
By December 1
Submitting organisation
& RA
SEG
By February 1
Validation of new versions RA
Registration and publication
By February - May
Submitting organisation
& users
First implementers
ISO_20022_SV_v144

9. The ISO 20022 recipe is used (1/11) Payments
Credit Transfers / Direct Debits / Mandates
Financial
Investigations
Exceptions & Investigations
Change/Verify Account Identification
Creditor Payment Activation Request
Authorities
Debtor’s
bank
Cash Management
Creditor’s
bank
Account Switching
This is an overview of the current ISO offering to support the Payments market. The picture shows the various flows of information exchanged by the parties to initiate, execute and report the execution of a payment. The yellow arrows are already covered by approved ISO messages, while the blue arrows are still candidate ISO messages.
In September 2005, the Payments SEG approved the very first set of ISO messages covering the area of ‘customer to bank credit transfer initiation’, which included the so-called ‘core payment kernel’ developed jointly by SWIFT, TWIST, IFX and OAGi.
In June 2006, the SEG approved a new version of the payment initiation messages, including direct debits as well as the interbank direct debit and credit transfer messages. The interbank messages were developed by SWIFT.
In July 2006, the SEG approved a set of messages developed by SWIFT to cover exceptions and investigations in the payments area.
In March 2007, the SEG approved 3 bank to customer advice and statement messages developed jointly by SWIFT, TWIST, IFX, OAGi and ISITC.
In March 2009, the SEG approved a new version of the whole ISO Payments message set, to accommodate change requests received from the user base.
In August 2009, the SEG approved four Mandate messages developed by SWIFT to initiate and maintain payment mandates.
In December 2009, the SEG approved a set of 3 messages developed by the the French SWIFT Users Group to inform payment initiators of a change in the account identification of their counterpart or verify the account of the beneficiary before instructing a payment.
In March 2010, the SEG approved 15 Bank Account Management messages developed by SWIFT to enable corporate clients to open a bank account with their bank and maintain related data.
In September 2010, the SEG approved a set of 2 messages developed by the CBI Consortium to enable creditors to request debtors to initiate a credit transfer in their favour.
In November 2010, the SEG approved a set of 4 Cash Account Reporting Request and Notification to Receive messages developed by SWIFT.
In May 2012, the SEG approved a Bank Services Billing message developed by TWIST and SWIFT.
In October 2012, the SEG approved 3 Authorities Financial Investigations messages developed by the Federation of Finnish Financial Services (FFI) (not represented on the slide).
In April 2014, the SEG approved two Stand-Alone Remittance Advice messages developed by IFX and OAGi.
-In March 2016, the SEG approved ten candidate Cross-border Transactions Currency Control Reporting (CTCCR) messages submitted by the Russian Corporate Market Practice Group (not represented on the slide) and one candidate interbank Financial Institution Direct Debit message contributed by SWIFT to complement the ‘Payments Clearing and Settlement’ message set.
- In January 2017, the SEG approved an additional two Mandate messages developed by SWIFT in cooperation with the South African Bureau of Standards (SABS); and an additional Payment Clearing and Settlement message developed by SWIFT and the European Payments Council (EPC).
The SEG is reviewing 11 candidate Account Switching messages developed by Payments UK and 31 candidate cash management messages developed by SWIFT.
The following business justifications have been approved by the RMG and will complement the approved messages:
Payment Pre-Authorization (PaPA) by Early Warning Services.
Proxy for Bank Account Numbers by SPRING.
Not all projects are represented on the slide.
Account Switching
Exceptions & Investigations
ISO 20022
Advice & Statement
Change/Verify Account Identification
Bank Account Management
Creditor Payment Activation Request
Account Reporting Request
Notification to Receive
Mandates
Credit Transfer Initiation
Advice & Statement
Exceptions & Investigations
Creditor Payment Activation Request
Stand-Alone Remittance Advice
Direct Debit Initiation
Stand-Alone Remittance Advice
Candidate ISO (in development)
Bank Services Billing
Bank Services Billing
Debtor
Creditor
ISO_20022_SV_v144

10. The ISO 20022 recipe is used (2/11) Payments message portfolio
120 ISO messages approved:
Customer payment initiation
Interbank payment clearing and settlement
Payments exceptions & investigations
Bank-to-customer cash management
Payments mandates
Change/verify account identification
Bank account management
Creditor payment activation request
Cash account reporting request & notification messages
Bank services billing
Authorities financial investigations
Stand-alone remittance advice messages
Cross-border transactions currency control reporting (CTCCR)
Account Switching
Cash Management
candidate ISO messages under evaluation:
None
Candidate ISO messages approved for development:
Payment pre-authorization (PaPA)
Proxy for banking account numbers
EMIP (Deutsche Bundesbank, Banca D’Italia & SWIFT)
New development proposal: None
ISO_20022_SV_v144

11. The ISO 20022 recipe is used (3/11) Card message portfolio
Authorisation (ATICA)
Acquirer
Issuer
In October 2010, the Cards and Related Retail Financial Services SEG approved a first set of 15 Card Payments Exchange (CAPE) Acceptor to Acquirer messages developed by nexo A.I.S.B.L (formerly EPASOrg) to support Acceptor to Acquirer POI activities, including authorisation, completion, batch transfer, cancellation, reconciliation, diagnostic and rejection.
In April 2011, the SEG approved an additional three CAPE messages developed by nexo to cover POI Terminal Management, including status report, management plan and acceptor parameters. In January 2013, it approved a fourth CAPE - Terminal Management message submitted by nexo. In January 2014, the Cards and Related Retail Financial Services SEG approved two new CAPE – Acceptor to Acquirer messages developed by nexo. In January 2015, the SEG approved an additional two CAPE - Terminal Management messages developed by nexo. In August 2015, the SEG approved 21 ATM interface for transaction processing and ATM management messages developed jointly by the IFX Forum and nexo. In February 2016, a first set of 13 Acquirer to issuer card messages (ATICA), developed by ISO TC68/SC9/TG1 as a reverse engineering of ISO 8583 card messages in ISO 20022, were published as a proof of concept. In February 2016, the SEG also approved two additional CAPE – Terminal Management messages developed by nexo. In May 2016, the SEG approved 8 additional ATM interface for transaction processing and ATM management messages developed jointly by the IFX Forum and nexo. In May 2017, the SEG approved 2 additional CAPE – Acceptor to Acquirer messages developed by nexo.
ISO TC68/SC9/TG1 is expected to deliver a new, more comprehensive version of the ATICA messages by the end of 2017.
nexo A.I.S.B.L will develop additional candidate messages to cover the Sale Management at the retailer (Sale to POI).
Two other business justifications were approved by the RMG:
- Dispute resolution in cards fee collection proposed by China UnionPay. 15 candidate messages were submitted to the SEG for review in July 2016, but an attempt to merge the requirements into the ATICA message set is currently undertaken.
- Payment Tokens Management Exchanges (a.k.a. TOKE) by ISO/TC68/SC9/TG1 and nexo A.I.S.B.L.
ATMI transaction authorisation
POI transaction authorisation (CAPE)
POI Terminal Management (CAPE)
ATM terminal Management
ISO 20022
Candidate ISO (in development)
Acceptor
Sale Management (CAPE)
ISO_20022_SV_v144

12. The ISO 20022 recipe is used (4/11) Cards & retail financial services
69 ISO messages approved:
Card payments exchanges (CAPE) – Acceptor to Acquirer and Terminal Management
ATM interface for transaction processing and ATM management
Acquirer to issuer card messages (ATICA – first version)
17 Candidate ISO messages under evaluation
CASP - Card Sale to POI ISO Protocol
Candidate ISO messages approved for development:
Card Payments Exchanges (CAPE) - Sale-to-POI management
Payment Tokens Management Exchanges (TOKE)
Acquirer to issuer card messages (ATICA – second version)
ISO_20022_SV_v144

13. The ISO 20022 recipe is used (5/11) Securities - equities and fixed income
Buyer
Seller
Pre-trade / Trade (FIX/SWIFT)
Post-Trade (Omgeo/SWIFT)
CCP Clearing (FPL/SWIFT)
Regulators
Financial Instruments and Transactions Regulatory Reporting (ESMA)
Corporate
Actions
(SWIFT)
Settlement
(SWIFT)
Settlement
(SWIFT)
Corporate
Actions
(SWIFT)
On the traditional fixed income and equities markets, the securities industry is using ISO 15022, the precursor of ISO ISO (illustrated in red/orange on the slide) covers a large part of the securities business from trade to settlement and reconciliation, and corporate actions.
ISO developments initially focused on areas not (well) covered by ISO such as:
the pre-trade and trade space (29 candidate messages submitted by FIX and SWIFT)
the transaction regulatory reporting required to address MiFID I (four messages developed by SWIFT and archived in 2017 when MiFID II/MiFIR messages were registered by ESMA)
the proxy voting process (eight messages developed by SWIFT)
the issuer’s agent communication for corporate actions (22 messages developed by Euroclear)
the investment funds distribution (see next slide).
However, under the pressure of
the firms who have not invested in ISO and would prefer to invest directly in ISO 20022
the industry initiatives (Giovannini, MiFID, T2S) recommending ISO 20022
the other financial industry sectors which are moving to ISO (eg, payments/SEPA),
the RMG approved the development of ISO equivalent messages in the ‘core’ areas of settlement and reconciliation (29 messages approved in December 2009) and corporate actions (13 messages approved in December 2009), which are covered by ISO
An initial set of 5 Post-trade matching messages developed by SWIFT and Omgeo was approved by the Securities SEG on 3 August 2011.
On 7 October 2011, the SEG approved a Total Portfolio Valuation Statement report submitted by SWIFT on behalf of ISITC and 4 additional Settlement and Reconciliation messages developed by SWIFT, including an Audit Trail to be used by T2S.
On 22 January 2015, the SEG approved 10 CCP Clearing messages submitted by SWIFT and FPL as well as 14 Collateral Management messages submitted by SWIFT, FPL, FpML and ISITC.
On 25 January 2016, the SEG approved 5 Money Market Statistical Reporting (MMSR) messages submitted by the ECB, Banque de France, Deutsche Bundesbank and Banco de Espana.
SWIFT, Omgeo, FPL, FpML, ISITC , ECB and the 4CB have also started development of candidate ISO messages in a series of specific areas.
In February 2016, the ISO variants of the Settlement and Reconciliation messages and the Corporate Actions messages, developed by SWIFT, were published as Variant “002” of the corresponding global messages.
In May 2016, the SEG approved 4 Standing Settlement Instructions for Securities, Payments and FX messages submitted jointly by Omgeo, ISITC and FPL.
In July 2016, the Derivatives SubSEG received the evaluation documentation of 3 candidate Financial Instruments and Transactions Regulatory Reporting messages submitted by ESMA to cover EMIR reporting by Trade Repositories.
In October 2016, the RMG approved a business justification submitted by ESMA for the development of ISO messages to support the Securities Financing Transactions Regulatory Reporting (SFTR).
In May 2017, the RMG approved a first version of 18 candidate Financial Instruments and Transactions Regulatory Reporting messages submitted by ESMA to cover MiFID II/MiFIR reporting. The Securities SEG is however still reviewing these messages in the spirit of making them more generic in a second version. The 4 Transaction Regulatory Reporting messages developed by SWIFT in 2007 to support MiFID I were archived.
In November 2017, the SEG received the evaluation documentation of a set of 16 candidate CCP Supervisory reporting messages developed by Bank of England and a first set of 12 candidate T2S messages.
NB: the slide doesn’t show all the approved message sets/business justifications.
ISO 20022
Reconciliation
TPV Statement
(ISITC/SWIFT)
Candidate ISO (in development)
Reconciliation
(SWIFT)
ISO 15022
I/CSD
Settlement & Reconciliation (SWIFT)
Settlement & Reconciliation (SWIFT)
Custodian
Issuers’ Agent Communication
(Euroclear)
Clearing
agent
Corporate
Actions
(SWIFT)
Issuers’ Agent
ISO_20022_SV_v144

14. The ISO 20022 recipe is used (6/11) Securities - investment funds (CIV)
Portfolio Transfers
Old plan manager
Fund
accountant
New plan manager
Price Report
Order & Confirmation & Status
A full set of ISO messages was developed by SWIFT in the area of Collective Investment Vehicle (CIV). 45 of them were approved in December A second release, including 22 additional messages, was approved in April Two Fund Processing Passport Report messages from SWIFT were approved in November 2009.
In January 2017, the SEG approved the withdrawal of 5 Investment Funds messages in the framework of the 2016/2017 maintenance cycle.
Clearstream has developed two messages, approved in March 2016, to offer a ‘Transparency of Holdings’ statement mechanism primarily intended for holdings of shares in investment funds, but also of use for other types of instruments.
Transfer & Confirmation & Status
Transfer
agent
Transparency of Holdings
Institutional
investor
Statements
Account Management
Fund Cash Forecast Report
Request for Fund Report
Prospectus or FPP report user, e.g. Fund distributor
FPP Report
Investment
manager
Prospectus or FPP report provider, e.g. Fund manager
ISO 20022
Candidate ISO (in development)
ISO_20022_SV_v144

15. The ISO 20022 recipe is used (7/11) Securities message portfolio
213 ISO messages approved and published:
Investment funds
Proxy voting
Issuers’ agents communication
Securities settlement and reconciliation, including ISO variants
Securities corporate actions, including ISO variants
Securities post-trade
Total portfolio valuation report
CCP Clearing
Collateral management
Money Market Statistical Reporting (MMSR)
Transparency of holdings
SSI for Securities, Payments & FX
Financial instruments and transactions regulatory reporting (MiFID II / MiFIR) v1 and v2
CSDR-Settlement Internaliser Report
TARGET2-Securities
Securities markets regulatory reporting message sets - Benchmark Reporting
59 candidate ISO messages under evaluation:
CCP supervisory reporting
Securities Financing Transactions Regulatory Reporting (SFTR)
Target2-Securities (Account Reference Data, Collateral, Intra-Balance)
Financial instruments and transactions regulatory reporting (EMIR)
Candidate ISO messages approved for development:
ASX CHESS Replacement
Triparty Collateral Management (Banca de Espana/SWIFT)
Shareholder Identity Disclosure (SMPG/SWIFT)
New development proposals: none
ISO_20022_SV_v144

16. The ISO 20022 recipe is used (8/11) Forex
Trading
system
ISO 20022
Candidate ISO 20022
(in development)
Ordering
party
MTs
FpML CUG (Trade Notifications)
FX order
Interest rate swaps
Trade capture
Trading
party
In March 2007, the FX SEG approved 15 Forex Notifications messages submitted by CLS. In September 2015, the SEG approved a set of 13 ‘Post Trade Foreign Exchange’ message definitions developed by CLS. This message set was complemented with two message definitions from the Forex Notifications message set, the rest of the latter message set was archived.
The SWIFT MT and FpML messages shown on the slide are for information only.
In February 2016, the FX SEG approved two candidate message sets: FX Post-Trade Trade Capture and FX Post-Trade Confirmation, submitted by China Foreign Exchange Trade System (CFETS).
In March 2017, the SEG approved 4 new Post Trade Foreign Exchange message definitions developed by CLS.
Foreign exchange instruments
Loans and deposits
Trading
party
FX & Loan/Deposit Advice & Allocations
Deriv-atives
FX Spot, Forward & Swap instructions
NDF and FX Option instructions (archived)
Settlement
party
custodian
Status notifications and payment and position information
Status notifications and payment and position information
Central Settlement or Netting System
ISO_20022_SV_v144

17. The ISO 20022 recipe is used (9/11) FX message portfolio
27 ISO messages approved and published:
Post Trade FX messages
FX Post-Trade Confirmation
FX Post-Trade Trade Capture
Candidate ISO messages under evaluation:
None
New development proposals
ISO_20022_SV_v144

18. The ISO 20022 recipe is used (10/11) Trade Services
Buyer’s
bank
Seller’s
bank
Trade Services
Management
Trade Services
Management
TSU
Invoice Tax Report
The Trade Services SEG approved:
3 Invoice Financing Request messages submitted by the CBI Consortium in October 2007,
50 Trade Services Management (TSU) messages submitted by SWIFT in April 2008.
20 messages developed by SWIFT to support Demand Guarantees and Standby Letters of Credit (this is not represented on the slide) in December 2012
11 Factoring Services messages developed by the Association Française des Sociétés Financières (ASF) in March 2015.
2 Invoice Tax Report messages developed by the Federation of Finnish Financial Services (FFI) & Tieto Corporation in October 2016.
ISO 20022
Factoring Services
Invoice Financing Request
Factoring Services
Tax
Authority
Invoice Tax Report
Buyer
Seller
ISO_20022_SV_v144

19. The ISO 20022 recipe is used (11/11) Trade message portfolio
88 ISO messages approved:
Invoice financing request
Trade services management
Demand guarantees and standby letters of credit
Factoring services
Invoice Tax Report
Candidate ISO messages under evaluation:
None
Candidate ISO messages approved for development:
New development proposals:
ISO_20022_SV_v144

20. & Answers uestions www.iso20022.org iso20022ra@iso20022.org
We have reached the end of this presentation.
Remember, a lot of information is available on the ISO website ( which is updated on an ongoing basis, but questions and comments can also be sent to the RA:
&
Answers
ISO_20022_SV_v144