FinancialInstrumentReportingCurrencyCodeReportV01

auth.048.001.01

The MiFIRCurrencyCodeReport message provides the details the ISO 4217 currency codes and is created by ESMA for distribution to National Competent Authorities.

Message Construction

Every ISO20022 message has at the highest level what we call ‘building blocks’. Because the message is constructed as immutable records, the association is by composition. Below you can see the relationship between the message and its constituent building blocks: For comparison, see the ISO20022 official specification

classDiagram
     direction LR
%% FinancialInstrumentReportingCurrencyCodeReportV01 recursion level 0 with max 0
FinancialInstrumentReportingCurrencyCodeReportV01 *-- "1..1" SecuritiesCurrencyIdentification2 : CurrencyData
FinancialInstrumentReportingCurrencyCodeReportV01 *-- "0..1" SupplementaryData1 : SupplementaryData
  

Now, we will zero-in one-by-one on each of these building blocks.

CurrencyData building block

Report all currencies and countries which use that currency. Details an individual currency including details on which country trades the currency. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% SecuritiesCurrencyIdentification2 recursion level 0 with max 1
class SecuritiesCurrencyIdentification2{
    FractionalDigit IsoMax1Number
    PreEuro IsoTrueFalseIndicator
    Modification Modification1Code
    LastUpdated IsoISODate
}
SecuritiesCurrencyIdentification2 *-- "1..1" CurrencyCodeAndName1 : Currency
SecuritiesCurrencyIdentification2 *-- "1..1" CountryCodeAndName3 : CountryDetails
SecuritiesCurrencyIdentification2 *-- "1..1" IPeriod4Choice : ValidityPeriod
%% CurrencyCodeAndName1 recursion level 1 with max 1
class CurrencyCodeAndName1{
    Code ActiveOrHistoricCurrencyCode
    Name IsoMax70Text
}
%% CountryCodeAndName3 recursion level 1 with max 1
class CountryCodeAndName3{
    Code CountryCode
    Name IsoMax70Text
}
%% IPeriod4Choice recursion level 1 with max 1
  

SecuritiesCurrencyIdentification2 members

SupplementaryData building block

Additional information that can not be captured in the structured fields and/or any other specific block. Additional information that can not be captured in the structured fields and/or any other specific block. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% SupplementaryData1 recursion level 0 with max 1
class SupplementaryData1{
    PlaceAndName IsoMax350Text
}
SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope
%% IsoSupplementaryDataEnvelope1 recursion level 1 with max 1
  

SupplementaryData1 members

Extensibility and generalization considerations

To facilitate generalized design patterns in the system, the FinancialInstrumentReportingCurrencyCodeReportV01 implementation follows a specific implementaiton pattern. First of all, FinancialInstrumentReportingCurrencyCodeReportV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, FinancialInstrumentReportingCurrencyCodeReportV01Document implements IOuterDocument. Because FinancialInstrumentReportingCurrencyCodeReportV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type FinancialInstrumentReportingCurrencyCodeReportV01.

classDiagram
    class IOuterRecord
    FinancialInstrumentReportingCurrencyCodeReportV01 --|> IOuterRecord : Implements
    FinancialInstrumentReportingCurrencyCodeReportV01Document --|> IOuterDocument~FinancialInstrumentReportingCurrencyCodeReportV01~ : Implements
    class IOuterDocument~FinancialInstrumentReportingCurrencyCodeReportV01~ {
        FinancialInstrumentReportingCurrencyCodeReportV01 Message
     }
  

Document wrapper for serialization

The only real purpose FinancialInstrumentReportingCurrencyCodeReportV01Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:auth.048.001.01’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using FinancialInstrumentReportingCurrencyCodeReportV01.ToDocument() method. The returned FinancialInstrumentReportingCurrencyCodeReportV01Document value will serialize correctly according to ISO 20022 standards.

classDiagram
    FinancialInstrumentReportingCurrencyCodeReportV01Document *-- FinancialInstrumentReportingCurrencyCodeReportV01 : Document
  

Sample of message format

This is an abbreviated version of what the message should look like.

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:auth.048.001.01">
    <FinInstrmRptgCcyCdRpt>
        <CcyData>
            <!-- CurrencyData inner content -->
        </CcyData>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </FinInstrmRptgCcyCdRpt>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_4LK8N0RNEee7JdgA9zPESA"
  name="FinancialInstrumentReportingCurrencyCodeReportV01"
  definition="The MiFIRCurrencyCodeReport message provides the details the ISO 4217 currency codes and is created by ESMA for distribution to National Competent Authorities."
  registrationStatus="Registered"
  messageSet="_m18yAApTEeeand7dul6qJQ"
  xmlTag="FinInstrmRptgCcyCdRpt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_4LK8OURNEee7JdgA9zPESA"
    name="CurrencyData"
    definition="Report all currencies and countries which use that currency."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="CcyData"
    complexType="_c7l_wX58EeaUaa1DpZmwUw" />
  <messageBuildingBlock
    xmi:id="_4LK8O0RNEee7JdgA9zPESA"
    name="SupplementaryData"
    definition="Additional information that can not be captured in the structured fields and/or any other specific block."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="SplmtryData"
    complexType="_Qn0zC9p-Ed-ak6NoX_4Aeg_468227563" />
  <messageDefinitionIdentifier
    businessArea="auth"
    messageFunctionality="048"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

The following items are used as building blocks to construct this message.