DerivativesTradeReportV02

auth.030.001.02

The DerivativesTradeReport is sent by the reporting entities to provide transaction data to the trade repositories (TRs) or by the trade repositories (TRs) to the 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
%% DerivativesTradeReportV02 recursion level 0 with max 0
DerivativesTradeReportV02 *-- "1..1" TradeQueryHeader4 : ReportHeader
DerivativesTradeReportV02 *-- "1..1" ITradeData19Choice : TradeData
DerivativesTradeReportV02 *-- "0..1" SupplementaryData1 : SupplementaryData
  

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

ReportHeader building block

Header information related to metadata of report message. Provides the details of the header for a trade transaction query message. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% TradeQueryHeader4 recursion level 0 with max 1
class TradeQueryHeader4{
    QueryExecutionDate IsoISODate
    NumberRecords IsoNumber
}
TradeQueryHeader4 *-- "1..1" Pagination1 : MessagePagination
%% Pagination1 recursion level 1 with max 1
class Pagination1{
    PageNumber IsoMax5NumericText
    LastPageIndicator IsoYesNoIndicator
}
  

TradeQueryHeader4 members

TradeData building block

Data concerning the reporting trade. Position/transaction reporting under EMIR regulation. For comparison, see the ISO20022 official specification

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

TradeData19Choice members

SupplementaryData building block

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

classDiagram
    class IOuterRecord
    DerivativesTradeReportV02 --|> IOuterRecord : Implements
    DerivativesTradeReportV02Document --|> IOuterDocument~DerivativesTradeReportV02~ : Implements
    class IOuterDocument~DerivativesTradeReportV02~ {
        DerivativesTradeReportV02 Message
     }
  

Document wrapper for serialization

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

classDiagram
    DerivativesTradeReportV02Document *-- DerivativesTradeReportV02 : 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.030.001.02">
    <DerivsTradRpt>
        <RptHdr>
            <!-- ReportHeader inner content -->
        </RptHdr>
        <TradData>
            <!-- TradeData inner content -->
        </TradData>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </DerivsTradRpt>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_6ULEkHg8Eeu3kecHd7QKUQ"
  previousVersion="_z7fHERLAEeqctpBfTmLJnw"
  name="DerivativesTradeReportV02"
  definition="The DerivativesTradeReport is sent by the reporting entities to provide transaction data to the trade repositories (TRs) or by the trade repositories (TRs) to the competent authorities."
  registrationStatus="Registered"
  messageSet="_GGPcdPcwEeqmJupSd3hH1w"
  xmlTag="DerivsTradRpt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_6ULEkng8Eeu3kecHd7QKUQ"
    name="ReportHeader"
    definition="Header information related to metadata of report message."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="RptHdr"
    complexType="_7oH-8cWBEeijrI2SDYOAOw" />
  <messageBuildingBlock
    xmi:id="_6ULElHg8Eeu3kecHd7QKUQ"
    name="TradeData"
    definition="Data concerning the reporting trade."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="TradData"
    complexType="_mijCQXg-Eeu3kecHd7QKUQ" />
  <messageBuildingBlock
    xmi:id="_6ULElng8Eeu3kecHd7QKUQ"
    name="SupplementaryData"
    definition="Additional information that cannot 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="030"
    flavour="001"
    version="02" />
</messageDefinition>

ISO Building Blocks

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