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

2. ISO 20022 The ISO recipe for all 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_v80

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_v80

4. Why ISO 20022? Convergence in the cooperative space
Competitive
Space
Cooperative Space
Competitive
Space
High Value Payments:
RTGS, EURO1 and CHIPS
Financial
Institutions
Financial
Institutions
FX and Money Markets:
Rule Books, CLS
Public
Admini-
strators
Commercial Payments:
Rule Books, Clearing Houses,
Processors
Public
Admini-
strators
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
Corporates
Corporates
Tradefacilitation:
ICC Rule Books, e-invoicing
SME’s
SME’s
Cash:
NCB rules, Industry Standards
Merchants
Merchants
Securities:
Rule Books, Exchanges, CCP’s
CSD’s, Standardisation
Consumers
Consumers
Certification & Networks:
SWIFT
Cooperative space for business rules
Cooperative space for standards
ISO_20022_SV_v80

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: BIAN, CBI Consortium, FPL, FpML, IFX Forum, TWIST, SWIFT, OAGi, ACORD, XBRL, EPASOrg, Berlin Group, ANBIMA, ASF, etc.
Market Infrastructures (MIs): DTCC, FED, China UnionPay, EBA, Target, CLS, Euroclear, Clearstream, Omgeo, T2S, NBB, etc.
International or national standards setters: ISITC, ISO WGs, UN/CEFACT, EPC, BIAN, UK Payments Council, FFI, 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 yellow’ 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 the European e-Invoicing initiative, SEPA, Target2-Securities, Giovannini and MiFID, 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, e-Invoicing
ISO_20022_SV_v80

6. ISO 20022 The registration bodies
Registration Management Group - RMG
(Overall governance)
60 senior managers from 20 countries and 9 international organisations
Standards Evaluation Groups – SEGs
(User representatives)
Securities (56 experts, 15 countries, 7 organisations)
Payments (61 experts, 17 countries, 5 organisations)
Cards and related retail financial services (30 experts, 14 countries, 3 organisations)
Trade Services (29 experts, 13 countries, 1 organisation)
Forex (25 experts, 9 countries, 3 organisations)
Technical Support Group – TSG
(ISO technical advisors)
25 experts from 12 countries and 4 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 nominated by ISO countries and international organisations in liaison with ISO. All together, they represent all sectors of the financial industry. The RMG monitors 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) are groups of industry experts nominated by ISO countries and liaison organisations, 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 nominated by ISO countries and liaison organizations, 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 last SEG and the TSG were 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_v80

7. ISO 20022 The registration process Development Process
Submitting organisation
Financial organisation or standards body
Business
justification
Business justification
RMG
Project approval & allocation to a SEG
This is an illustration of the process for development and registration of new sets of messages. There is a more detailed description of it on
The entry point of the registration process is the preparation of a ‘Business Justification’ by the organisation that wants to develop the messages (the “submitting organisation”). The Business Justification must describe the high level scope of the messages to be developed and the reason why they are expected to benefit the industry.
The Business Justification is reviewed by the SEGs and the RMG. The RMG will decide whether the proposed development fits into the ISO spectrum, does not duplicate the already existing messages and is indeed beneficial to the community. If the request is approved, the RMG decides which SEG(s) will be in charge of the evaluation of the messages, once developed.
The submitting organisation develops ISO compliant business and message models. The RA assists the submitting organisation during this phase in order to ensure that the models are compliant and use the right components from the Data Dictionary. If need be, the RA may create additional dictionary items. When the development is completed, the RA generates the ISO XML or ASN.1 schemas and prepares a comprehensive documentation for the SEG.
Based on this documentation, the SEG(s) evaluates the candidate ISO messages. The main goal of the SEG(s) is to get the buy-in of the future users from a business perspective. The submitting organisation is participating to the evaluation to help the SEG understand the proposed solution and address any question that would be raised by the SEG members.
When/if the SEG approves the messages, the RA proceeds to the official registration of the message components in the ISO Data Dictionary and publishes the new ‘ISO messages’ in the Catalogue of messages on
When messages are first piloted or implemented, first users 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.
All along, the RMG monitors the work and if need be, arbitrates any disputes.
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
Catalogue
Optional pilot testing
or first implementers
Submitter
& users
ISO_20022_SV_v80

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. The ISO maintenance process is described at The yearly maintenance cycle includes the following steps:
1) 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 new versions of the messages incorporating the approved CRs.
6) The SEG validates that the new versions indeed include the approved changes.
7) The approved new versions of messages are published by the RA.
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 ‘fast-track’ mode in case of urgent Change Requests that cannot wait for the next yearly cycle.
SEG
By October 1
SEG approval/rejection
By December 1
Submitting organisation
& RA
Development of new versions
SEG
Validation of new versions
By February 1 RA
Registration and publication
Repository
Dictionary
Catalogue
April-May
First implementers
Submitting organisation
& users
ISO_20022_SV_v80

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 and will be used in the new SEPA environment.
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).
The following business justifications have been approved by the RMG and will complement the approved messages:
two Stand-Alone Remittance Advice messages developed by by IFX and OAGi (under evaluation)
a whole suite of candidate cash management messages developed by SWIFT. They will include ‘query/answer’ messages to retrieve information about cash accounts and transaction, as well as interbank statement and advice messages
Account Switching by the Payments Council Ltd – UK.
Real Time Payments by the Payments Council Ltd – UK
The last project is not 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_v80

10. The ISO 20022 recipe is used! (2/11) Payments message portfolio is growing!
62 ISO messages approved:
Customer payment initiation
Interbank payment clearing and settlement
Payments exceptions & investigations
Bank-to-customer cash management
Mandates
Change/verify account identification
Bank account management
Creditor payment activation request
Cash account reporting request & notification messages
Bank services billing
Authorities financial investigations
Candidate ISO messages under evaluation
Stand-alone remittance advice messages
Candidate ISO messages approved for development:
Cash management
Real time payments
Account switching
ISO_20022_SV_v80

11. The ISO 20022 recipe is used! (3/11) Card message portfolio is growing
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) messages developed by 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 messages developed by EPASOrg to cover POI Terminal Management, including status report, management plan and acceptor parameters. In January 2013, it approved a fourth Terminal Management message submitted by EPASOrg.
EPASOrg will develop additional candidate messages to cover the Sale Management at the retailer (Sale to POI).
Three other business justifications were approved by the RMG:
Acquirer to issuer card messages (ATICA) proposed by ISO TC68/SC7/TG1 as a reverse engineering of ISO 8583 card messages in ISO
ATM interface for transaction processing and ATM management messages proposed jointly by the IFX Forum and EPASOrg.
- Dispute resolution in cards fee collection proposed by China UnionPay.
The Cards SEG approved the development of a new version of the 19 Card Payments Exchanges (CAPE) messages at the occasion of the 2013/2014 maintenance cycle.
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_v80

12. The ISO 20022 recipe is used! (4/11) Cards and related retail financial services
19 ISO messages approved:
Card payments exchanges (CAPE) – Acceptor to Acquirer and Terminal Management
Candidate ISO messages approved for development:
ATM interface for transaction processing and ATM management
Acquirer to issuer card messages (ATICA)
Card Payments Exchanges (CAPE) - Sale-to-POI management
Dispute Resolution in Cards Fee Collection
New development proposal:
None
ISO_20022_SV_v80

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
Transaction Regulatory Reporting (SWIFT)
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 (four messages developed by SWIFT)
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 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.
SWIFT, Omgeo, FPL, FpML, ISITC and the 4CB have also started development of candidate ISO messages in a series of specific areas.
NB: the slide doesn’t show all the approved business justifications.
The Securities SEG approved the development of new versions of existing Securities messages at the occasion of the 2013/2014 maintenance cycle:
21 new versions of Settlement and Reconciliation messages,
2 new versions of Post Trade Matching messages and,
9 new versions of Corporate Actions messages.
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_v80

14. The ISO 20022 recipe is used! (6/11) Securities - investment funds (CIV)
PEP/ISA/Portfolio Transfers
Old plan manager
Fund
accountant
New plan manager
Price Report
Order & Confirmation & Status
A full set of 66 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.
SWIFT has developed 8 candidate messages for Alternative Funds (hedge funds) that are piloted before registration.
ANBIMA intends to develop 4 candidate Investment Fund Prospectus messages.
Clearstream will develop two candidate messages to offer a ‘Transparency of Holdings’ statement mechanism primarily intended for holdings of shares in investment funds.
The Securities SEG approved the development of 18 new versions of existing Investment Funds messages at the occasion of the 2013/2014 maintenance cycle.
Alternative Funds Order, Confirm & Status
Transfer
agent
Transfer & Confirmation & Status
Institutional
investor
Statements
Account Management
Fund Cash Forecast Report
Request for Fund Report
Prospectus or FPP report user, e.g. Fund distributor
FPP Report
Fund Prospectus
Investment
manager
Prospectus or FPP report provider, e.g. Fund manager
ISO 20022
Candidate ISO (in development)
ISO_20022_SV_v80

15. The ISO 20022 recipe is used! (7/11) Securities message portfolio is growing!
154 ISO messages approved and published:
Investment funds distribution
Securities transaction regulatory reporting
Proxy voting
Issuers’ agents communication
Fund processing passport report
Securities settlement and reconciliation
Securities corporate actions
Securities post-trade
Total portfolio valuation report
Candidate ISO messages under evaluation:
Securities pre-trade/trade
CCP Clearing
Collateral management
Candidate ISO messages approved for development:
Alternative funds
TARGET2-Securities
Investment fund prospectus
SSI for Securities, Payments & FX
Transparency of holdings
New development proposal:
none
ISO_20022_SV_v80

16. The ISO 20022 recipe is used! (8/11) Forex
Ordering
party
ISO 20022
MTs
FpML CUG (Trade Notifications)
FX order
Interest rate swaps
Trading
party
Foreign exchange and currency options
In March 2007, the FX SEG approved 15 Forex Notifications messages submitted by CLS. There are no additional candidate ISO messages in development in FX. The SWIFT MT and FpML messages shown on the slide are for information only.
A proposal for the development of new Post Trade FX messages has been submitted by CLS on 1 July 2013.
Loans and deposits
Trading
party
FX & Loan/Deposit Advice & Allocations
NDF Opening and Valuation Notifications and
Foreign Exchange Option Premium Notifications
Settlement
party
custodian
NDF and Foreign Exchange Option Notifications
NDF and Foreign Exchange Option Notifications
Central Settlement System
ISO_20022_SV_v80

17. The ISO 20022 recipe is used! (9/11) FX message portfolio is growing!
15 ISO messages approved and published:
Forex notifications
Candidate ISO messages under evaluation:
none
Candidate ISO messages approved for development:
Post Trade FX messages
New development proposals:
FX Post-Trade Confirmation, FX Post-Trade Capture
ISO_20022_SV_v80

18. The ISO 20022 recipe is used! (10/11) Trade Services
Buyer’s
bank
Seller’s
bank
Financial Invoice
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.
In October 2010, it approved a Financial Invoice message developed by UN/CEFACT that can be used to trigger payment initiation (EBPP) and for other financial purposes.
In December 2012, the SEG approved 20 messages developed by SWIFT to support Demand Guarantees and Standby Letters of Credit (this is not represented on the slide).
In October 2011, the RMG approved a business justification from the Association Française des Sociétés Financières (ASF) for the development of a message set to support Factoring Services introduced by.
In October 2012, the RMG approved a business justification from the Federation of Finnish Financial Services (FFI) and Tieto for the development of a message to support the provision of Invoice Tax Report to Tax Authorities.
The Trade SEG approved 9 new versions of the Trade Services Management messages to be published at the occasion of the 2013/2014 maintenance cycle.
ISO 20022
Financial Invoice
Candidate ISO 20022
(in development)
Factoring Services
Invoice Financing Request
Factoring Services
Financial Invoice
Tax
Authority
Invoice Tax Report
Financial Invoice
Buyer
Seller
ISO_20022_SV_v80

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

20. Who is interested by ISO 20022?
Country
Visits % 1
France
30,287
13% 2
Germany
28,089
12% 3
United States
20,694 9% 4
United Kingdom
19,504 5
Netherlands
11,719 5% 6
India
11,469 7
Spain
10,230 4% 8
Belgium
9,397 9
Italy
8,418 10
Switzerland
5,953 3% 11
Japan
4,503 2% 12
Sweden
4,064 13
Singapore
3,469 14
Australia
3,183 1% 15
Austria
2,970 16
Canada
2,597 17
Brazil
2,562 18
Ireland
2,379 19
Poland
2,339 20
Finland
2,296 21
Portugal
2,225 22
Denmark
2,202 23
Russia
2,102 24
Norway
1,913
194,564
85%
From 26 April 2013 to 26 October 2013, had 229,204 visits from 135,400 visitors from 175 countries
- The continents are sorted on the number of visits to the ISO website.
- The countries listed in the table (right) are the ones representing 85 % of the ISO website visits.
26 Apr 13 – 25 Oct 13
Continent
Number of Visits %
Europe
160,153
70.8%
Asia
30,939
13.7%
Americas
28,565
12.7%
Oceania
3,520
1.6%
Africa
2,897
1.3%
ISO_20022_SV_v80

21. & 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_v80