ISO/FDIS 20022-9

ISO/DISFDIS 20022-9:
ISO/TC 68/SC 9
Secretariat: AFNOR
Date: 2025(en)-12-12
2025-09-26
Financial services — Universal financial industry message scheme —

Part 9:
Syntax generation requirements and rules
Services financiers — Schéma universel de messages pour l'industrie financière —
Partie 9:
FDIS stage
ISO /FDIS 20022-9:2025(Een)
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication
may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying,
or posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO
at the address below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: + 41 22 749 01 11
E-mail: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO 2025 – All rights reserved
ii
ISO/DISFDIS 20022-9:2025(en)
Contents
Foreword . vi
Introduction . vii
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Background . 2
5 How to read this document . 2
5.1 General. 2
5.2 Difference between terms (verbs) of “use” and “utilize” in Syntax generation rules . 2
5.3 Outline of steps to create Syntax generation rules . 2
6 General requirements of Syntax generation . 3
6.1 Transformation of logical level metamodel concepts . 3
6.2 Transformation of data types . 4
6.3 Common content structure of a syntax generation specification document . 5
7 ISO 20022 transformation rules for MessageSet . 6
7.1 General. 6
7.2 Preconditions . 6
7.3 Transformation constraints . 6
7.4 Other rules for the specific syntax . 7
8 MessageInstances . 9
8.1 General. 9
8.2 Completeness . 9
8.3 Other rules for the specific syntax . 9
9 Method . 9
10 Syntax generation rules of Logical classes . 10
10.1 General. 10
10.2 MessageSet . 10
10.3 MessageDefinition . 10
10.4 MessageDefinitionIdentifier . 11
10.5 MessageBuildingBlock . 11
10.6 MessageComponentType . 12
10.7 MessageElement . 14
10.8 Other considerations . 16
11 Syntax generation rules of user-defined data types . 16
11.1 General. 16
11.2 Link data types . 17
11.3 Boolean data types . 17
11.4 Sequence data types . 18
11.5 Numeric data types . 20
11.6 Temporal data types . 23
Annex A (normative) A template for syntax generation rules . 26
Annex B (informative) Conformance to this document . 30
Annex C (informative) Maintenance process of metamodel . 32
Bibliography . 34
© ISO 2025 – All rights reserved
iii
ISO /FDIS 20022-9:2025(Een)
Foreword . v
Introduction . vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Background . 2
5 How to read this document . 2
5.1 General. 2
5.2 Difference between terms (verbs) of “use” and “utilize” in Syntax generation rules . 2
5.3 Outline of steps to create Syntax generation rules . 2
6 General requirements of Syntax generation . 3
6.1 Transformation of logical level metamodel concepts . 3
6.2 Transformation of data types . 4
6.3 Common content structure of a syntax generation specification document . 5
7 ISO 20022 transformation rules for MessageSet . 5
7.1 General. 5
7.2 Preconditions . 6
7.3 Transformation constraints . 6
7.4 Other rules for the specific syntax . 7
8 MessageInstances . 8
8.1 General. 8
8.2 Completeness . 8
8.3 Other rules for the specific syntax . 8
9 Method . 8
10 Syntax generation rules of Logical classes . 9
10.1 General. 9
10.2 MessageSet . 9
10.3 MessageDefinition . 9
10.4 MessageDefinitionIdentifier . 10
10.5 MessageBuildingBlock . 10
10.6 MessageComponentType . 11
10.6.1 General. 11
10.6.2 ExternalSchema . 11
10.6.3 MessageComponent . 12
10.6.4 ChoiceComponent . 12
10.7 MessageElement . 13
10.7.1 General. 13
10.7.2 MessageAttribute . 13
10.7.3 MessageAssociationEnd where aggregation is composite . 13
10.7.4 MessageAssociationEnd where aggregation is none or shared . 14
10.8 Other considerations . 15
11 Syntax generation rules of user-defined data types . 15
11.1 General. 15
11.2 Link data types . 16
11.2.1 Pointer . 16
11.3 Boolean data types . 16
11.3.1 Boolean . 16
iv © ISO 2025 – All rights reserved
iv
ISO/DISFDIS 20022-9:2025(en)
11.3.2 Indicator . 16
11.4 Sequence data types . 17
11.4.1 Binary . 17
11.4.2 String . 17
11.4.3 Text . 17
11.4.3.1 Text with language use 17
11.4.3.2 Text without language use 18
11.4.4 CodeSet . 18
11.4.4.1 CodeSet with Codes 18
11.4.4.2 CodeSet without Codes 18
11.4.5 IdentifierSet . 19
11.5 Numeric data types . 19
11.5.1 Decimal . 19
11.5.2 Quantity . 19
11.5.3 Rate . 20
11.5.4 Amount . 20
11.5.4.1 Amount with currencyIdentifierSet 20
11.5.4.2 Amount without currencyIdentifierSet 20
11.6 Temporal data types . 22
11.6.1 DateTime . 22
11.6.2 Date . 22
11.6.3 Time . 22
11.6.4 Year . 22
11.6.5 Month . 23
11.6.6 Day . 23
11.6.7 YearMonth . 23
11.6.8 MonthDay . 23
11.6.9 Duration . 24
Annex A (normative) A Template of Syntax Generation Rules . 25
A.1 General . 25
A.2 Template . 25
Annex B (Informative) Conformance to this document . 29
Annex C (Informative) Maintenance process of metamodel . 30
Bibliography . 31

© ISO 2025 – All rights reserved
v
ISO /FDIS 20022-9:2025(Een)
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.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types of
ISO document should be noted. This document was drafted in accordance with the editorial rules of the
ISO/IEC Directives, Part 2 (see www.iso.org/directives).
ISO draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). ISO takes no position concerning the evidence, validity or applicability of any claimed patent rights
in respect thereof. As of the date of publication of this document, ISO had not received notice of (a) patent(s)
which may be required to implement this document. However, implementers are cautioned that this may not
represent the latest information, which may be obtained from the patent database available at
www.iso.org/patents. ISO shall not be held responsible for identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 68, Financial services, Subcommittee SC 9,
Information exchange for financial services.
A list of all parts in the ISO 20022 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.
vi © ISO 2025 – All rights reserved
vi
ISO/DISFDIS 20022-9:2025(en)
Introduction
The ISO 20022 series defines a scalable, methodical process to ensure consistent descriptions of messages
throughout the financial services industry.
The purpose of the ISO 20022 series 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 the ISO 20022 series was the rapid growth in the scale and sophistication of
messaging within financial services during the 1990s using the ISO 15022 series. The financial services
industry (hereafter referred to as "the industry") created the first version of the ISO 20022 series as the
successor to the ISO 15022 series in response to that trigger. Since the ISO 15022 series, the industry has
broadened the scope from securities to the entire industry for the ISO 20022 series.
The ISO 20022 series is based on open technology standards, which historically have evolved more rapidly
than the industry itself. Consequently, the ISO 20022 series 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 the ISO 20022 series has emerged followed the widespread adoption of
the internet. for business. The eXtensible Mark-up Language (XML) emerged as the de facto standard for
document representation on the internet and it became the first syntax for the ISO 20022 series.
The modelling process is further refined into three levels which, in addition to the messaging technology
standard, is why the ISO 20022 series is based on four levels: the Scopescope level, the Conceptualconceptual
level, the Logicallogical level and the Physicalphysical level. This four-level approach is based on the first four
[2][ ]
levels of the Zachman Framework. 0 . 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 Unified Modelling Language (UML) because
it is widely supported and supports multiple levels of abstraction. The models created in accordance with ISO
20022-1 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. ISO 20022-1 defines a process by which
these models can be created and maintained by the modellers.
The model artefacts are stored in an ISO 20022 Repository (hereafter referred to as "the Repository)."). The
Repository and physical level artefacts are exposed in a publicly accessible location, such as a website, serviced
by a Registration Authority. The name and contact information of the Registration Authority for the ISO 20022
series can be found at www.iso.org/maintenance_agencieswww.iso.org/maintenance_agencies.
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.
The ISO 20022 series is organized into the following parts.
— — ISO 20022-1 describes in Meta-Object Facility (MOF) the metamodel of all the models and the
Repository. according to ISO/IEC 19502:2005 (MOF).
— — ISO 20022-2 covers the UML profile, a grounding of general UML into a specific subset defined for the
ISO 20022 series (to be used when UML is selected to define the models).
— — ISO 20022-3 describes a modelling method to produce models for the ISO 20022 series.
© ISO 2025 – All rights reserved
vii
ISO /FDIS 20022-9:2025(Een)
— — 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 business concept model interoperability, and logical model alignment and reverse
engineering.
— — 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 Logicallogical level model into a
Physicalphysical level description in ASN.1.
— — This document describes generic guidelines, which are used to define schema generation rules for any
specific syntax.
This document is a set of “meta rules” (in other wordsi.e. guidelines) which specifies how to develop and
document a set of syntax generation rules for specific syntax scheme (e.g. XML, ASN.1 and JSON) from the meta
model to facilitate interoperability. Figure 10 depicts the relationship of this document with ISO 20022-1 and
specific syntax schemes. A set of generation rules is necessary to transform the logical level of the metamodel
defined in ISO 20022-1 to the physical representations.
viii © ISO 2025 – All rights reserved
viii
ISO/DISFDIS 20022-9:2025(en)
Figure 1 — Relationship of this document with ISO 20022-1 and specific syntaxes
NOTE This document provides a guideline framework to document syntax scheme generation rules which is
modelled after ISO 20022-4 and ISO 20022-8. Although ISO 20022-4 and ISO 20022-8 are standalone documents in the
ISO 20022 series, they are regarded as conforming to this document. This document is not a specification that supersedes
ISO 20022-4 and ISO 20022-8.
© ISO 2025 – All rights reserved
ix
ISO/DIS 20022-9:2025(en)
DRAFT International Standard
Financial services — Universal financial industry message scheme —
—
Part 9:
Syntax generation requirements and rules
1 Scope
This document complements the ISO 20022 Metamodel, as specified in ISO 20022-1, with generic
requirements and guidelines to define specific syntax generation rules for other encodings in order to produce
schemas based on each specific syntax generation rules in compliance with this document. Such specific
syntaxes include XML, ASN.1 and JSON. (XML and ASN.1 do not imply ISO 20022-4 XML schema generation
and ISO 20022-8 ASN.1 generation only. W3C XML Schema, ASN.1 and JSON can be used to express or define
a variety type of schemas.)
Under this metamodel-driven and syntax-agnostic approach of ISO 20022 series, interoperability is ensured
at the conceptual level of the metamodel specified in ISO 20022-1, rather than at the physical level of syntaxes
specified in ISO 20022-4 and ISO 20022-8.
In this document, "schema" refers to the "SyntaxMessageScheme" defined in ISO 20022-1. However, for ease
of reading, this document will hereafter refer to it as "schema" which is a general term for design documents
that define data structures.
1 1)
The metaclass “MessageDefinition” that is described in ISO 20022- 1:— , , Figure 13 is the target of the
transformation specified in this document, but the metaclass “MessageChoreography” is not. In other words,
this document is only the rules for the syntax of the data representation language. For example, Application
Programming Interfaceapplication programming interface (API) specific aspects are outside the scope of this
document.
Regarding the concept of conformance to this document, see Annex B.0.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content constitutes
requirements of this document. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
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.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:

Under preparation. Stage at the time of publication: ISO/DIS 20022-1:2025.
1)
Under preparation. Stage at the time of publication: ISO/DIS 20022-1:2025.
ISO /FDIS 20022-9:2025(Een)
— ISO Online browsing platform: available at https://www.iso.org/obp
— IEC Electropedia: available at https://www.electropedia.org/
3.1
artefact
constituent of the specific syntax that is generated by the Syntax Generation Rules
EXAMPLE When the specific syntax is XML, “artefacts” include XML elements “xs:schema”, “xs:complexType”,
[1][ ]
“xs:simpleType”, “xs:element”, “xs:attribute” and so on of W3C’s XML Schema Definition Language 0 and their XML
attributes “name”, “type”, “base” and so on.
4 Background
Extensible Markup Language (XML), a standard defined by W3C (the World Wide Web Consortium (W3C),
was adopted for the representation (i.e. the syntax) of standardized ISO 20022 MessageDefinitions originally
when the first edition of the ISO 20022 series was published in 2004. ISO 20022-4 defined a set of XML design
rules.
This document contains the guidelines for documenting the generation and transformation rules for any
representation other than XML and ASN.1 as described in ISO 20022-4 and ISO 20022-8 respectively. This
document is the framework to meet the community need for supporting ISO 20022 logical message design in
other representations such as JavaScript Object Notation (JSON) and binary encoding; this addresses
timeliness of community requirements.
Annex CAnnex C describes the maintenance process for features, introduced by future syntaxes adopted based
on this document, which can affect the metamodel defined in ISO 20022-1.
5 How to read this document
5.1 General
In this document, the subclauses titled "Syntax generation rules" explain each step to specify syntax
generation. It is the essential part of transformation guidelines.
“EXAMPLE”, where provided, refers to an example syntax generation rules to help readers and implementors
understand what Syntaxsyntax generation rules means easily because Syntaxsyntax generation rules are
described in a very generic and abstract manner.
5.2 Difference between terms (verbs) of “use” and “utilize” in Syntax generation rules
When processing literal information of metamodel such as names, this document uses the terms (verbs) “use”
and “utilize” to express separate meanings.
— — The term (verb) “use” is for expressing that the literal information is used as is without editing or
modifying.
— — The term (verb) “utilize” is for expressing that the literal information may be edited/modified by
abbreviating, adding either prefix or suffix or both, etc., or may be used without change.
5.3 Outline of steps to create Syntax generation rules
Figure 20 is an outline of the steps to create a document of syntax generation rules using this document.
2 © ISO 2025 – All rights reserved
ISO/DISFDIS 20022-9:2025(en)
Figure 2 — Outline of steps to create Syntax generation rules
6 General requirements of Syntax generation
6.1 Transformation of logical level metamodel concepts
The logical level metamodel concepts (or metaclass) defined in ISO 20022-1 are the sources of transformation.
When developing syntax generation rules, these metamodel concepts shall describe how they are to be
transformed to specific artefacts of the target syntax. Where concepts are not applicable and not transformed,
this should be noted accordingly.
When semantic markup is used to define additional logical metadata, transformation rules shall document if
they or how they should be transformed.
The logical level metamodel concepts to be transformed are as follows.
— — MessageSet
— — MessageDefinition
— — MessageDefinitionIdentifier
© ISO 2025 – All rights reserved
ISO /FDIS 20022-9:2025(Een)
— — MessageBuildingBlock
— — MessageComponentType
— — ExternalSchema
— — MessageComponent
— — ChoiceComponent
— — MessageElement
— — MessageAttribute
— — MessageAssociationEnd
See ISO 20022-1 for definitions of each concept.
Any other constraints and considerations may be specified for the syntax if necessary.
6.2 Transformation of data types
The following DataType representations defined in ISO 20022-1 are also the sources of transformation. When
developing syntax generation rules, those DataType representations shall be described how they are
transformed to specific data type representations of the syntax. It is not required to transform all DataTypes
It depends on the specific syntax whether. Whether some DataTypes can be transformed or not depends on
the specific syntax. Where DataTypes are not applicable and not transformed, this should be noted
accordingly.
The user-defined DataTypes to be transformed are as follows.:
— — Pointer
— — Boolean
— — Indicator
— — Binary
— — String
— — Text
— — CodeSet
— — IdentifierSet
— — Decimal
— — Quantity
— — Rate
— — Amount
— — DateTime
4 © ISO 2025 – All rights reserved
ISO/DISFDIS 20022-9:2025(en)
— — Date
— — Time
— — Year
— — Month
— — Day
— — YearMonth
— — MonthDay
— — Duration
See ISO 20022-1 for definitions of each DataType.

6.3 Common content structure of a syntax generation specification document
The content structure of a syntax generation specification document outlined in this document shall be
followed.
The template structure outlined in Annex A,0, which consists of the metamodel concepts specified in ISO
20022-1, shall be followed. This template makes it easier to establish semantic correspondences at the level
of metamodel concepts between different syntaxes or even different applications of the same syntax.
NOTE The clause number "N” depends on the number of previous clauses in each specific syntax generation
specification document.
[Clause N]: ISO 20022 transformation rules for MessageSet
— — Comprehensive description of transformation for a specific syntax regarding MessageSet.
[Clause N+1]: MessageInstances
— — Description of either constraints or requirements or both of physical instances for a specific syntax.
[Clause N+2]: Method
— — Explanation of general method of transformation and define components of the transformation rules
as specified in the following clauses, i.e. logical classes transformation and user-defined data types
transformation.
[Clause N+3]: Logical classes
— — Transformation rules of logical class meta-models to artefacts of the specific syntax.
[Clause N+4]: User-defined data types
— — Transformation rules of user-defined data types which use DataType representations defined in ISO
20022-1 to artefacts of the specific syntax.
© ISO 2025 – All rights reserved
ISO /FDIS 20022-9:2025(Een)
7 ISO 20022 transformation rules for MessageSet
7.1 General
7.1.1 Overview
This clause describes general requirements for transformation itself as a whole.
7.1.2 Syntax generation rules
“Preconditions” shall at least be described as they are common for all syntaxes. Other rules for the specific
syntax may be described in addition to these.
7.2 Preconditions
7.2.1 Overview
First of all, it is necessary to know what the input of the transformation is when developing transformation
rules.
7.2.2 Syntax generation rules
The input of transformation is themetaclass “MessageSet” which is common for all syntaxes. Therefore, the
description shall be stated as follows:
“The MessageSet used as input for the transformation is a valid instance of the MessageSet metaclass.”
7.3 Transformation constraints
7.3.1 Overview
In addition to information relevant for the validation of message instances with a generated schema,
annotations may include unabbreviated names (original full names), definitions and meaning of concepts,
along with constraints and metadata such as the units, referenced type and identification scheme. This is
beneficial for users, including software developers and operational staff.
Therefore, if the syntax has a feature of adding such explanation (hereafter “annotation”), the specific syntax
generation rules may specify rules for adding annotations in a schema document.
7.3.2 Syntax generation rules
Describe how a specific artefact(s) of the syntax corresponding to the annotation for each concept is
generated.
The metamodel information used for annotation includes:
— — Definition:
— — Forfor RepositoryConcept: its "name" property and "definition" property.
— — Application Information:
— — Forfor all RepositoryConcepts: its "name" property;
— — Forfor Indicator Data Type: its "meaningWhenFalse" property and
"meaningWhenTrue" property;
6 © ISO 2025 – All rights reserved
ISO/DISFDIS 20022-9:2025(en)
— — Forfor Quantity Data Type: its "unitCode" property;
— — Forfor Rate Data Type: its "baseUnitCode" property and "baseValue" property;
— — Forfor IdentifierSet Data Type: its "identificationScheme" property;
— — Forfor CodeSet Data Type: its "identificationScheme" property and "reference"
property.
— — Minor Version Information:
— — Forfor MessageDefinition, MessageDefinition and CodeSet Data Type: its
"revision" property, "variation" property and "draft" property.
— — Constraint Information:
— — Forfor RepositoryConcept: "expression" property and "expressionLanguage"
property of Constraint referenced by its "constraint" property.
— — Quantity Information:
— — Forfor Amount Data Type with non-empty "currencyIdentifierSet" property: its
"name" property to generate a quantity identifier.
— — Reference Information:
— — Forfor MessageComponentType that is referenced by non-composite
MessageAssociationEnd: its "name" property to generate a reference identifier.
— — General Information:
— — Forfor MessageDefinition: "area" property, "function" property, "flavour"
property and "version" property of MessageDefinitionIdentifier referenced by its
"messageDefinitionIdentifier" property.
Non-metamodel information used for annotation includes:
— — Metadata Information:
— — Datedate of the repository, date time the schema was generated;
— — Thethe identifier of the generator software;
— — Itsits registration status in the repository, its revision and variant.
7.4 Other rules for the specific syntax
Syntax-specific requirements, such as use of some functions of the specific syntax, namespace of syntax
elements and granularity of schemas, shall be described as required by each syntax.
2)
EXAMPLE See ISO 20022-4:2025,:— , 5.3 and 5.4 for examples of other rules for MessageSet.

2)
Under preparation. Stage at the time of publication: ISO/DIS 20022-4:2025.
© ISO 2025 – All rights reserved
ISO /FDIS 20022-9:2025(Een)
8 © ISO 2025 – All rights reserved
ISO/DISFDIS 20022-9:2025(en)
8 MessageInstances
8.1 General
8.1.1 Overview
This clause describes either constraints or requirements, or both of physical instances for a specific syntax
such as encoding of message instances and namespaces to be used to qualify element names used in message
instances of the specific syntax.
8.1.2 Syntax generation rules
“Completeness” shall at least be described as they are common for all syntaxes. Other rules for the specific
syntax may be described.
8.2 Completeness
8.2.1 Overview
This is a common requirement for the translation.
8.2.2 Syntax generation rules
The following description shall be stated except that the part in square brackets shall be replaced by the name
of the schema which is specific to the syntax.
“The list of transformation rules described in the following clauses is complete. Therefore, no other
transformation rules are applicable and no other information may be added to the [insert the name of
schema which is specific to the syntax here (e.g. “XML Schema” for XML syntax)] outside of what is allowed
by the transformation rules given below.
The [insert the name of schema which is specific to the syntax here (e.g. “XML Schema” for XML syntax)]
is a representation of the MessageDefinition.”

8.3 Other rules for the specific syntax
Syntax-specific requirements, such as encoding and abbreviated names, shall be described as required by each
syntax.
EXAMPLE See ISO 20022-4:2025,:—, 6.1, 6.2, 6.3, 6.4 and 6.5 for examples of other rules for MessageInstances.
9 Method
This clause explains the general approach of transformation such as components of the transformation rules,
whereas the subsequent clauses (i.e. logical classes transformation, user-def
...