FinancialInstrumentReportingInstrumentClassificationReportV01

auth.050.001.01

The FinancialInstrumentReportingInstrumentClassificationReport message is sent by ESMA to all national competent authorities and provides all valid combinations for classification of financial instruments (CFI) as per ISO 10962.

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
%% FinancialInstrumentReportingInstrumentClassificationReportV01 recursion level 0 with max 0
FinancialInstrumentReportingInstrumentClassificationReportV01 *-- "1..1" SecuritiesInstrumentClassification2 : InstrumentClassification
FinancialInstrumentReportingInstrumentClassificationReportV01 *-- "0..1" SupplementaryData1 : SupplementaryData
  

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

InstrumentClassification building block

Report detailing all classification for financial instruments (CFI) code. Details an individuation of the classification type of the financial instrument. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% SecuritiesInstrumentClassification2 recursion level 0 with max 1
class SecuritiesInstrumentClassification2{
    Identifier IsoCFIOct2015Identifier
    Modification Modification1Code
    LastUpdated IsoISODate
}
SecuritiesInstrumentClassification2 *-- "1..1" IPeriod4Choice : ValidityPeriod
%% IPeriod4Choice recursion level 1 with max 1
  

SecuritiesInstrumentClassification2 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 FinancialInstrumentReportingInstrumentClassificationReportV01 implementation follows a specific implementaiton pattern. First of all, FinancialInstrumentReportingInstrumentClassificationReportV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, FinancialInstrumentReportingInstrumentClassificationReportV01Document implements IOuterDocument. Because FinancialInstrumentReportingInstrumentClassificationReportV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type FinancialInstrumentReportingInstrumentClassificationReportV01.

classDiagram
    class IOuterRecord
    FinancialInstrumentReportingInstrumentClassificationReportV01 --|> IOuterRecord : Implements
    FinancialInstrumentReportingInstrumentClassificationReportV01Document --|> IOuterDocument~FinancialInstrumentReportingInstrumentClassificationReportV01~ : Implements
    class IOuterDocument~FinancialInstrumentReportingInstrumentClassificationReportV01~ {
        FinancialInstrumentReportingInstrumentClassificationReportV01 Message
     }
  

Document wrapper for serialization

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

classDiagram
    FinancialInstrumentReportingInstrumentClassificationReportV01Document *-- FinancialInstrumentReportingInstrumentClassificationReportV01 : 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.050.001.01">
    <FinInstrmRptgInstrmClssfctnRpt>
        <InstrmClssfctn>
            <!-- InstrumentClassification inner content -->
        </InstrmClssfctn>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </FinInstrmRptgInstrmClssfctnRpt>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_4LK8VURNEee7JdgA9zPESA"
  name="FinancialInstrumentReportingInstrumentClassificationReportV01"
  definition="The FinancialInstrumentReportingInstrumentClassificationReport message is sent by ESMA to all national competent authorities and provides all valid combinations for classification of financial instruments (CFI) as per ISO 10962."
  registrationStatus="Registered"
  messageSet="_m18yAApTEeeand7dul6qJQ"
  xmlTag="FinInstrmRptgInstrmClssfctnRpt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_4LK8V0RNEee7JdgA9zPESA"
    name="InstrumentClassification"
    definition="Report detailing all classification for financial instruments (CFI) code."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="InstrmClssfctn"
    complexType="_NHRMYX5xEeasY4u9QTizPQ" />
  <messageBuildingBlock
    xmi:id="_4LK8WURNEee7JdgA9zPESA"
    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="050"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

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