Currency

Overview

Currency identifies a specific currency that is the subject of, or denomination for, financial values in a research product. The element serves two distinct roles in RIXML: as a product classification under ProductClassifications for research that discusses currency-specific topics independently of any issuer or security, and as a denomination indicator within SecurityFinancials (and related financial containers such as IssuerFinancials) to declare the monetary unit of the financial values reported there. In every context, the specific currency is carried by the required currency attribute, which is constrained to ISO 4217 three-letter alpha codes via ISO4217CurrencyType (sources: data-dictionary-2.4 p.44, data-dictionary-2.5.1 p.47, level-one-2.3 p.17).

Usage

Use Currency in one of two ways: - As a product classification inside ProductClassifications: optional, with zero-to-many cardinality, to tag research that focuses on one or more specific currencies (e.g. FX commentary, monetary policy notes, currency-pair analysis) without reference to a particular issuer or security. For research that talks about currencies as an asset class in general terms, publishers should instead tag the asset class using Currency on AssetClass (sources: user-guide-2.3 p.32, data-dictionary-2.4 p.44, data-dictionary-2.5.1 p.47). - As a denomination indicator inside financial containers such as SecurityFinancials (and analogously IssuerFinancials): optional, appearing at most once, to declare the ISO 4217 currency in which the contained FinancialValue amounts are expressed (sources: level-one-2.3 p.17, level-one-2.3.1 p.17, level-one-2.4 p.17). In both roles the currency attribute is required and must contain a valid ISO 4217 three-letter uppercase alpha code (e.g. USD, EUR, JPY, GBP).

Rules

• MUSTThe currency attribute MUST contain a valid ISO 4217 three-letter uppercase alpha code, as constrained by ISO4217CurrencyType.[RIXML Release Notes v2.2 p.2] [RIXML Level One Addendum v2.3 p.17] [RIXML User Guide v2.3 p.32] [RIXML Implementation Guide v2.5.1 p.29]
• MUSTWhen Currency is used as a classification under ProductClassifications for research discussing financial values without mapping to a specific issuer or security, a specific currency MUST be indicated via currency — Currency is not a vehicle for generic currency commentary.[RIXML User Guide v2.3 p.32] [RIXML Research Data Dictionary v2.4 p.44]
• SHOULDFor research discussing currencies generically (the asset class as a whole), publishers SHOULD tag AssetClass with Currency rather than use the Currency classification element.[RIXML User Guide v2.3 p.32] [RIXML Release Notes v2.3 p.4] [RIXML Research Data Dictionary v2.4 p.44]
• SHOULDWhen financial estimates or values are reported in SecurityFinancials or IssuerFinancials, the denominating Currency SHOULD be specified so that consumers can correctly interpret the monetary values.[RIXML Level One Addendum v2.3 p.17] [RIXML Level One Addendum v2.4 p.17] [Industry Report (Advanced) Sample v2.4]↗

Relationships

• child-ofProductClassifications — Currency appears as an optional, zero-to-many child of ProductClassifications to classify research focused on specific currencies.
• child-ofSecurityFinancials — Currency appears as an optional single child of SecurityFinancials to declare the ISO 4217 denomination of the contained FinancialValue items.
• child-ofIssuerFinancials — IssuerFinancials uses Currency to constrain all contained financial values to a consistent monetary unit.
• constrained-byISO4217CurrencyType — The value of currency is constrained by ISO4217CurrencyType to exactly three uppercase alphabetic characters from the ISO 4217 code list.
• contrasts-withAssetClassEnum.Currency — Currency is for research about one or more specific currencies; for generic currency-asset-class discussions, use Currency on AssetClass instead.