SecuritiesFinancingReportingTransactionReportV01

auth.052.001.01

The SecuritiesFinancingReportingTransactionReport message is sent by the report submitting entity to the trade repository (TR) to report on the securities financing transactions or sent by the trade repository (TR) to the authority or made available by the trade repository (TR) to the report submitting entity and the reporting counterparty as well as the entity responsible for reporting, if applicable.

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
%% SecuritiesFinancingReportingTransactionReportV01 recursion level 0 with max 0
SecuritiesFinancingReportingTransactionReportV01 *-- "1..1" ITradeData15Choice : TradeData
SecuritiesFinancingReportingTransactionReportV01 *-- "0..1" SupplementaryData1 : SupplementaryData
  

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

TradeData building block

Data concerning the reporting trade. Data concerning the reporting trade. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% ITradeData15Choice recursion level 0 with max 1
  

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

classDiagram
    class IOuterRecord
    SecuritiesFinancingReportingTransactionReportV01 --|> IOuterRecord : Implements
    SecuritiesFinancingReportingTransactionReportV01Document --|> IOuterDocument~SecuritiesFinancingReportingTransactionReportV01~ : Implements
    class IOuterDocument~SecuritiesFinancingReportingTransactionReportV01~ {
        SecuritiesFinancingReportingTransactionReportV01 Message
     }
  

Document wrapper for serialization

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

classDiagram
    SecuritiesFinancingReportingTransactionReportV01Document *-- SecuritiesFinancingReportingTransactionReportV01 : 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.052.001.01">
    <SctiesFincgRptgTxRpt>
        <TradData>
            <!-- TradeData inner content -->
        </TradData>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </SctiesFincgRptgTxRpt>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_2zvMHQuAEeqVvtu9Ny8FDA"
  nextVersions="_0kYl0cKvEeuzU9S_IANlog"
  name="SecuritiesFinancingReportingTransactionReportV01"
  definition="The SecuritiesFinancingReportingTransactionReport message is sent by the report submitting entity to the trade repository (TR) to report on the securities financing transactions or sent by the trade repository (TR) to the authority or made available by the trade repository (TR) to the  report submitting entity and the reporting counterparty as well as the entity responsible for reporting, if applicable."
  registrationStatus="Registered"
  messageSet="_80T9UAw7Eeqb0PC56-ljDA"
  xmlTag="SctiesFincgRptgTxRpt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_2zvMHwuAEeqVvtu9Ny8FDA"
    name="TradeData"
    definition="Data concerning the reporting trade."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="TradData"
    complexType="_30uHkf_qEemm3skPVSMJQg" />
  <messageBuildingBlock
    xmi:id="_2zvMIQuAEeqVvtu9Ny8FDA"
    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="052"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

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