ISO 20022-2:2013

INTERNATIONAL ISO
STANDARD 20022-2
Third edition
2013-05-01

Financial services — Universal financial
industry message scheme —
Part 2:
UML profile
Services financiers — Schéma universel de messages pour l'industrie
financière —
Partie 2: Profil UML




Reference number
ISO 20022-2:2013(E)
©
ISO 2013

---------------------- Page: 1 ----------------------
ISO 20022-2:2013(E)

COPYRIGHT PROTECTED DOCUMENT


©  ISO 2013
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56  CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland

ii © ISO 2013 – All rights reserved

---------------------- Page: 2 ----------------------
ISO 20022-2:2013(E)
Contents Page
Foreword . v
Introduction . vii
1  Scope . 1
2  Normative references . 1
3  Terms and definitions . 1
4  How the Profile is specified . 2
4.1  General . 2
4.2  Package structure of the Profile . 2
4.3  Basic organization of the Profile specification . 2
4.4  Properties of the Metamodel and UML — Tag Definitions . 3
4.5  Properties of the Metamodel that correspond to existing UML Properties . 3
4.6  AssociationEnds . 3
4.7  Constraints . 3
4.8  Figures . 3
4.9  How modellers choose which UML Diagrams to create . 3
5  Mapping the Metamodel’s elements to UML . 4
5.1  General . 4
5.2  UML realization of ISO20022::Metamodel . 4
5.2.1  General . 4
5.2.2  Metaclass: BusinessProcessCatalogue . 4
5.2.3  Metaclass: CodeSet . 4
5.2.4  Metaclass: Code . 5
5.2.5  Metaclass: Constraint . 5
5.2.6  Metaclass: DataDictionary . 5
5.2.7  Metaclass: IdentifierSet . 5
5.2.8  Metaclass: Repository . 5
5.2.9  Metaclass: RepositoryConcept . 6
5.2.10  Metaclass: TopLevelCatalogueEntry . 6
5.2.11  Metaclass: TopLevelDictionaryEntry . 6
5.2.12  Metaclass: Trace . 6
5.2.13  DataType: Cardinality . 6
5.3  UML realization of ISO20022::Metamodel::ScopeLevel . 7
5.3.1  General . 7
5.3.2  Metaclass: BusinessProcess . 7
5.3.3  Metaclass: BusinessRole . 7
5.4  UML realization of ISO20022::Metamodel::ScopeToConceptualTransformation . 8
5.4.1  General . 8
5.4.2  Metaclass: BusinessProcessTrace . 8
5.4.3  Metaclass: BusinessRoleTrace . 8
5.5  UML realization of ISO20022::Metamodel::ConceptualLevel::Dynamic . 8
5.5.1  General . 8
5.5.2  Metaclass: BusinessTransaction . 9
5.5.3  Metaclass: MessageTransmission . 9
5.5.4  Metaclass: MessageTransportMode . 10
5.5.5  Metaclass: Participant . 10
5.5.6  Metaclass: Receive . 11
5.5.7  Metaclass: Send . 11
5.6  UML realization of ISO20022::Metamodel::ConceptualLevel::Static . 11
5.6.1  General . 11
© ISO 2013 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO 20022-2:2013(E)
5.6.2  Metaclass: BusinessAssociation .11
5.6.3  Metaclass: BusinessAssociationEnd .12
5.6.4  Metaclass: BusinessAttribute .12
5.6.5  Metaclass: BusinessComponent .12
5.6.6  Metaclass: BusinessElement .13
5.7  UML realization of ISO20022::Metamodel::ConceptualToLogicalTransformation .13
5.7.1  General .13
5.7.2  Metaclass: BusinessComponentTrace .13
5.7.3  Metaclass: BusinessElementTrace .14
5.7.4  Metaclass: CodeSetTrace .14
5.7.5  Metaclass: MessageTypeTrace .14
5.8  UML realization of ISO20022::Metamodel::LogicalLevel .15
5.8.1  General .15
5.8.2  Metaclass::BusinessArea .15
5.8.3  Metaclass: ChoiceComponent .15
5.8.4  Metaclass: ExternalSchema .15
5.8.5  Metaclass: MessageAssociation .15
5.8.6  Metaclass: MessageAssociationEnd .15
5.8.7  Metaclass: MessageAttribute .16
5.8.8  Metaclass: MessageBuildingBlock .16
5.8.9  Metaclass: MessageComponent .16
5.8.10  Metaclass: MessageComponentType .17
5.8.11  Metaclass: MessageDefinition .17
5.8.12  Metaclass: MessageDefinitionIdentifier .18
5.8.13  Metaclass: MessageElement .18
5.8.14  Metaclass: MessageSet .19
5.9  UML realization of ISO20022::Metamodel::DataTypes .19
5.9.1  General .19
5.9.2  DataType: Amount .19
5.9.3  DataType: Indicator .19
5.9.4  DataType: Quantity .19
5.9.5  DataType: Rate .19
5.9.6  DataType: Text .20
5.10  UML realization of ISO20022::TypeLibrary::XMLSchema .20
5.11  UML realization of ISO20022::TypeLibrary::Enumerations .21
5.11.1  Enumeration: Aggregation .21
Annex A (normative) Definitions of Stereotypes and Tags .22
Bibliography .71

iv © ISO 2013 – All rights reserved

---------------------- Page: 4 ----------------------
ISO 20022-2:2013(E)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies
(ISO member bodies). The work of preparing International Standards is normally carried out through ISO
technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO 20022-2 was prepared by Technical Committee ISO/TC 68, Financial services.
This third edition cancels and replaces the second edition (ISO 20022-2:2007) which has been technically
revised.
ISO 20022 consists of the following parts, under the general title Financial services — Universal financial
industry message scheme:
 Part 1: Metamodel
 Part 2: UML profile
 Part 3: Modelling
 Part 4: XML Schema generation
 Part 5: Reverse engineering
 Part 6: Message transport characteristics
 Part 7: Registration
 Part 8: ASN.1 generation
ISO 20022-1:2013, ISO 20022-2:2013, ISO 20022-3:2013, ISO 20022-4:2013, ISO 20022-5:2013,
ISO 20022-6:2013, ISO 20022-7:2013 and ISO 20022-8:2013 will be implemented by the Registration
Authority by no later than the end of May 2013, at which time support for the concepts set out within them will
be effective. Users and potential users of the ISO 20022 series are encouraged to familiarize themselves with
the 2013 editions as soon as possible, in order to understand their impact and take advantage of their content
as soon as they are implemented by the Registration Authority. For further guidance, please contact the
Registration Authority.
© ISO 2013 – All rights reserved v

---------------------- Page: 5 ----------------------
ISO 20022-2:2013(E)
For the purposes of research on financial industry message standards, users are encouraged to
share their views on ISO 20022:2013 and their priorities for changes to future editions of the
document. Click on the link below to take part in the online survey:
http://www.surveymonkey.com/s/20022_2013

vi © ISO 2013 – All rights reserved

---------------------- Page: 6 ----------------------
ISO 20022-2:2013(E)
Introduction
This International Standard defines a scalable, methodical process to ensure consistent descriptions of
messages throughout the financial services industry.
The purpose of this International Standard is to describe precisely and completely the externally observable
aspects of financial services messaging in a way that can be verified independently against operational
messaging.
The trigger for the creation of this International Standard was the rapid growth in the scale and sophistication
of messaging within financial services during the 1990s using ISO 15022. The financial services industry (from
here on referred to as "the industry") created the first version of this International Standard as the successor to
ISO 15022 in response to that trigger. Since ISO 15022, the industry has broadened the scope from securities
to the entire industry for this International Standard.
This International Standard is based on open technology standards, which historically have evolved more
rapidly than the industry itself. Consequently, this International Standard adopted a model-driven approach
where the model of the industry's messaging can evolve separately from the evolution of the messaging
technology standards. The period during which this International Standard has emerged followed the
widespread adoption of the World Wide Web (the Web) for business. XML (eXtensible Mark-up Language)
emerged as the de facto standard for document representation on the Web and it became the first syntax for
ISO 20022.
The modelling process is further refined into three levels which, in addition to the messaging technology
standard, is why this International Standard is based on four levels: the Scope level, the Conceptual level, the
Logical level and the Physical level.
This four-level approach is based on the first four levels of the Zachman Framework. The remaining two levels
of the Zachman Framework are equivalent to the implementations and the operational levels, respectively.
In ISO 20022-1, the first, second and third levels are described in UML (Unified Modelling Language) because
it is widely supported and supports multiple levels of abstraction. The models created in accordance with this
International Standard are technology independent in that they do not require any particular physical
expression or implementation. Such models aim to describe all parts of the message exchange. The models
form the definition of the protocol between participants exchanging messages. This International Standard
defines a method that describes a process by which these models can be created and maintained by the
modellers.
The models and the Physical level artefacts are stored in a central repository, serviced by a Registration
Authority. This International Standard's repository is available on the World Wide Web and offers public
access for browsing.
The Repository is organized into two areas:
 A DataDictionary containing the industry model elements likely to have further or repeated use.
 A BusinessProcessCatalogue that contains models describing specific message definitions and business
processes, and physical syntax implementations.
This International Standard is organized into the following parts.
 ISO 20022-1 describes in MOF (Meta-Object Facility) the metamodel of all the models and the Repository.
© ISO 2013 – All rights reserved vii

---------------------- Page: 7 ----------------------
ISO 20022-2:2013(E)
 This part of ISO 20022 covers the UML profile, a grounding of general UML into a specific subset defined
for this International Standard (to be used when UML is selected to define the models).
 ISO 20022-3 describes a modelling method to produce models for this International Standard.
 ISO 20022-4 covers XML schema generation rules to transform a Logical level model into a Physical level
description in the syntaxes.
 ISO 20022-5 covers logical model alignment and reverse engineering of existing message syntaxes.
 ISO 20022-6 covers message transport characteristics that define the quality of service required by the
business process definitions so that they can operate successfully.
 ISO 20022-7 describes the process of managing the registration of models and physical syntax
implementations.
 ISO 20022-8 gives ASN.1 syntax generation rules to transform a Logical level model into a Physical level
description in ASN.1.

viii © ISO 2013 – All rights reserved

---------------------- Page: 8 ----------------------
INTERNATIONAL STANDARD ISO 20022-2:2013(E)

Financial services — Universal financial industry message
scheme —
Part 2:
UML profile
1 Scope
This part of ISO 20022 defines the UML Profile for this International Standard. In essence, it defines how to
use UML to create models that conform to the ISO 20022 Metamodel, which is defined in ISO 20022-1. In so
doing, it defines a UML-based concrete syntax for the Metamodel. It does not preclude the specification of
additional concrete syntaxes for the Metamodel, such as a textual concrete syntax.
The Profile defines how to represent in UML each of the Metamodel’s Scope Level Elements (Level 1),
Business Level Elements (Level 2) and Message Level Elements (Level 3), as well as Metamodel Elements
that are scoped across the levels.
Therefore, the Profile covers all of the Metamodel’s Packages, except for the following:
 ISO20022::Metamodel::ConceptualLevel::MessageTransport
 ISO20022::Metamodel::LogicalLevel::Reversing
 ISO20022::Metamodel::LogicalToPhysicalTransformation
 ISO20022::Metamodel::PhysicalLevel

The Profile also covers the ISO20022::TypeLibrary Package, upon which the Metamodel has some
dependencies.

This part of ISO 20022 is only applicable when UML is used.
2 Normative references
ISO 20022-1, Financial services — Universal financial industry message scheme — Part 1: Metamodel
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 20022-1 and the following apply.
3.1
1)
Metamodel
the ISO 20022 metamodel

1) The reason that the defined term is “the metamodel” rather than “metamodel” is that sometimes the term “UML
Metamodel” is used, and it would be incorrect in such cases to substitute “ISO 20022 metamodel” for “metamodel,” since
the result of the substitution would be “UML ISO 20022 metamodel.”
© ISO 2013 – All rights reserved 1

---------------------- Page: 9 ----------------------
ISO 20022-2:2013(E)
3.2
Profile
the UML profile for ISO 20022
3.3
UML metamodel
OMG's metamodel of UML
4 How the Profile is specified
4.1 General
This clause explains the technique used to specify the Profile.
4.2 Package structure of the Profile
The internal Package structure of the Profile is similar to the internal Package structure of the Metamodel.
Whereas the Metamodel’s top-level Package is ISO20022::Metamodel, the Profile’s top-level Package is
ISO20022::Profile. The following are the top-level Packages within the ISO20022::Profile Package:
1) ISO20022::Profile::ScopeLevel;
2) ISO20022::Profile::DataTypes;
3) ISO20022::Profile::ConceptualLevel;
4) ISO20022::Profile::LogicalLevel;
5) ISO20022::Profile::ConceptualToLogicalTransformation.

The ISO20022::Profile::Conceptual Package contains two Packages:
ISO20022::Profile::Conceptual::Dynamic;
ISO20022::Profile::Conceptual::Static.

The ISO20022::Profile Package imports two Packages:
ISO20022::TypeLibrary::Enumerations;
ISO20022::TypeLibrary::XMLSchema.
NOTE The ISO20022::Profile Package contains no Package that corresponds to the
ISO20022::Metamodel::ScopeToConceptual Package, because it is not necessary for the Profile to define any
Stereotypes in order to implement that Metamodel Package.
4.3 Basic organization of the Profile specification
Clause 5 systematically outlines the Metamodel, Package by Package, defining how each Metamodel element
maps to UML (it does not include the Packages of the Metamodel that the Profile does not cover, which are
listed in the Scope). Within each Metamodel Package, the Metaclasses are treated in alphabetical order, and
2 © ISO 2013 – All rights reserved

---------------------- Page: 10 ----------------------
ISO 20022-2:2013(E)
2)
then any DataTypes contained in the Package are treated in alphabetical order . For each Metaclass and
DataType, the Corresponding UML Element is specified.
After outlining the ISO20022::Metamodel Package and its sub-Packages, Clause 5 covers the
ISO20022::TypeLibrary Package and its sub-Packages, defining how each element maps to UML.
In many cases, the definition of how an element maps to UML refers to Stereotypes and
Tag Definitions that are normatively defined in Annex A.
4.4 Properties of the Metamodel and UML — Tag Definitions
In outlining the Metamodel, Metaclass by Metaclass, this part of ISO 20022 lists each of the Properties of the
Metaclass along with the defined approach for modelling that Property in UML. In some cases, the definition
states that the Property in question maps to a Tag Definition defined in Annex A.
4.5 Properties of the Metamodel that correspond to existing UML Properties
In many cases, a Property of a Metaclass from the Metamodel corresponds to a UML Property already
defined in the OMG’s UML specification. This part of ISO 20022 explicitly defines these correspondences. In
such a case, there is no need to define a Tag Definition to realize the Property in UML.
In a number of these cases, the Profile defines that the corresponding UML Property is the non-navigable
memberEnd of an Association in the UML specification, meaning that the Property cannot be captured in an
ISO 20022-compliant UML model. In essence, this means that the Metamodel supports the back-pointer
while UML does not, and there is no compelling reason to define a Tag Definition to fill the gap. The burden of
tracking and setting the back-pointer via a Tagged Value would fall entirely on the modeller, unless additional
code with specific knowledge of this back-pointer had been added to the UML tool.
4.6 AssociationEnds
UML 1.x has a Metaclass named AssociationEnd. UML 2.x does not have a Metaclass of that name; the
Metaclass has been replaced by the “memberEnd” Property of Association. Consequently, this part of ISO
20022 refers frequently to a “memberEnd” of an Association, whereas UML 1.x discourse would refer to an
“AssociationEnd.” For readability, the quotation marks have been omitted when referring to this Property,
even though all other Property names are in quotation marks when they appear in narrative text.
4.7 Constraints
Profile Constraints are expressed in OCL. The Constraints are motivated by the fact that the Profile is an
implementation of the ISO 20022 Metamodel, and they restrict the freedom of the UML modeller. UML models
that do not adhere to the Constraints are not ISO 20022-compliant.
4.8 Figures
The definitions in Annex A of the Profile Stereotypes and Tagged Definitions include figures that use UML
Profile notation to graphically depict the Stereotypes and Tag Definitions. The figures also depict the UML
Metaclasses that the Stereotypes extend, and the Stereotypes’ superclasses where applicable. As is typical
in specifications of MOF Metamodels and UML Profiles, the diagrams duplicate some of the information
contained in the narrative text. The narrative text is normative and the diagrams are non-normative.
4.9 How modellers choose which UML Diagrams to create
A complete overview of when to use which UML diagram can be found in ISO 20022-3.

2) The DataTypes that lie within the Metamodel Package and its contained Packages are DataTypes used to specify the
Metamodel. On the other hand, the DataTypes that lie within the ISO20022::TypeLibrary Package and its contained
Packages are DataTypes used by modellers to specify ISO 20022–compliant financial models.
© ISO 2013 – All rights reserved 3

---------------------- Page: 11 ----------------------
ISO 20022-2:2013(E)
5 Mapping the Metamodel’s elements to UML
5.1 General
This clause defines how each element of the Metamodel is realized in UML.
5.2 UML realization of ISO20022::Metamodel
5.2.1 General
This subclause defines how the elements of the ISO20022::Metamodel Package map to UML.
5.2.2 Metaclass: BusinessProcessCatalogue
 Corresponding UML Element: A <>-stereotyped Package.
 Mappings of the Metaclass’s Properties:
3)
repository: not implemented in the Profile ;
topLevelCatalogueEntry: corresponds to UML Package’s “packagedElement” Property, which poin
...