• Code Values: The set of valid values specifying the format of a Data Type having the representation type "Code".

Example: TradeTransactionConditionCode

Applies to: Data Types of Representation Type "Code"

• Code - The full name of a particular Code value within the set of valid values.

Example: "CumBonus" is the Code of the Code value "CBNS" in TradeTransactionConditionCode

Applies to: Data Types of Representation Type "Code"

When a Business / Message Component extends (refer to the " Extends" field description below) an other Business / Message Component, the former one inherits automatically the characteristics (i.e. the Business Elements and Rules) of the latter.

Therefore, for each Business / Message Element and for each Rule, the "Defined in" field indicates the original Business / Message Component from which this characteristic is inherited. For characteristics that are not inherited, the name of the current Business / Message Component is displayed.

Applies to: Business Elements; Message Elements; Rules

Provides a precise description of the meaning of the Dictionary item.

Applies to Dictionary items: Business Actors/Roles, Business Components, Message Components, Business Elements, Message Elements, Data Types, Codes and Business Associations

• Extends - The Business / Message Component is based on other Business / Message Component(s) and makes it more precise (by adding Business / Message Elements, Business Associations and /or Rules).

Applies to Dictionary items: Business Components, Message Components

• Is extended by - The Business / Message Component has been used as the basis for the listed Business / Message Components and can be considered as a common denominator.

Applies to Dictionary items: Business Components, Message Components

Message Components and Message Elements are usually based on a Business item (i.e. Business Component, Business Element or Business Association). This field indicates on which Business item, the Message Component or Element is based.

In a limited number of cases, a Message Element may have been introduced for purely technical reasons. Such a Message Elements is not based on a Business item because it has no business meaning. In this case the term "(Technical)" is indicated in the "Is based on" field.

For instance, a Message Element called "CurrentPageNumber" in a "Statement" Message Component would typically be listed as a "technical" element.

Applies to: Message Components; Message Elements.

Indicates the number of times a Business / Message Element may be repeated in an instance of the Business / Message Component it is defined in.

Multiplicity of Business Associations, if any, are shown in the pre-formatted sentences used for the description of Business Associations.

Applies to: Business Elements; Message Elements, Business Associations

The official name of the Dictionary item.

Applies to: All Dictionary items

Additional information provided for a Data Type, specifying values for technical information that is relevant for the Data Type Representation to which the Data Type belongs. This information does not appear in the XML schema.

Example: The "MeaningWhenTrue" property in the "PaymentDirectionIndicator" Data Type of the representation type "Indicator", provides the meaning of having the value "true" or "1" in an XML message instance.

Applies to: Data Types (of the Representation Type "Rate", "Identifier" or "Indicator").

The status of the item in the Repository registration life cycle. One of the following Registration Status values can be specified for each of the item:

• Provisionally Registered - The Repository item is pending final approval. This enables the Registration Authority to inform users that the Repository Item will potentially become "Registered" in the near future.
• Registered - The Repository item is ISO 20022 compliant and can be used for ISO 20022 compliant developments.
• Obsolete + Will be removed on: dd-month-yyyy - The Repository item is still compliant but cannot be used in new ISO 20022 compliant developments. The indicated in the "Will be removed on:" field is specified when the Repository item is no longer considered as compliant as of a specific date. This means the Repository item may no longer be used for registering updates to the Repository and will be removed from the Repository at the date specified as .

Applies to: All Repository items

A textual or formal description of the meaning of a Rule associated to a Business or Message Component.

Applies to: Rules.

There are two types of synonyms:

• Alternative names of a Dictionary item in a particular business context. The business context is specified between brackets.

Example:The synonym ":19A::REPA" is the representation of the Business Element "RepurchaseAmount" in the Business Component "RepurchaseAgreement" for the Enhanced-7775 syntax (ISO 15022).

• Possible representations of a Dictionary item in a particular syntax. The syntax is specified between brackets.

Example 2:"Strike price" is an alternative name for the "ExercisePrice" Business Element in the "Option" Business Component.

Applies to: Business Components, Message Components, Business Elements, Message Elements, Data Types, Enumerated Values, Business Associations, Business Actors and Roles.

Identifies the Business or Message Component or Data Type used to type a Business or Message Element.

Applies to: Business Elements, Message Elements.

Additional information provided for a Data Type, specifying values for technical information that is relevant for the Data Type Representation to which the Data Type belongs.
This information appears in the XML schema. The XML attribute is a name / value pair that is specified in the XML start-tag.
An XML attribute has a Data Type assigned, specifying the set of valid values of the XML attribute.

Example:The "Currency" XML Attribute in the "CurrencyAndAmount" Data Type specifies the Currency in which the amount must be considered.

Applies to: Data Types (of the Representation Type "Quantity" or "Amount").

Specific name assigned to a Message Element.
This name will appear as an XML tag in XML instances of Messages re-using this Message Element as well as in XML Schemas of Messages re-using this Message Element.

XML tags are attributed by the RA. They are derived from the UML name of the element which is abbreviated according to a set of rules specified in ISO 20022-4.
The mapping list of abbreviations used in XML tags is available here and is updated on a regular basis.

Applies to: Message Elements