DerivativesTradeReconciliationStatisticalReportV02

auth.091.001.02

The DerivativesTradeReportReconciliationStatisticalReport message is sent by the trade repositories to the reporting counterparty, to report cumulative information within the reference period for the reconciliation status of the reported and outstanding derivatives.

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
%% DerivativesTradeReconciliationStatisticalReportV02 recursion level 0 with max 0
DerivativesTradeReconciliationStatisticalReportV02 *-- "1..1" IStatisticsPerCounterparty15Choice : ReconciliationStatistics
DerivativesTradeReconciliationStatisticalReportV02 *-- "0..1" SupplementaryData1 : SupplementaryData
  

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

ReconciliationStatistics building block

Detailed information on reconciliation process. Statistics per counterparty reporting under the local regulation. For comparison, see the ISO20022 official specification

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

StatisticsPerCounterparty15Choice members

Member name Description Data Type / Multiplicity

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

Member name Description Data Type / Multiplicity
PlaceAndName Unambiguous reference to the location where the supplementary data must be inserted in the message instance. In the case of XML, this is expressed by a valid XPath. IsoMax350Text - Optional 0..1
Envelope Technical element wrapping the supplementary data. IsoSupplementaryDataEnvelope1 - Required 1..1

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    DerivativesTradeReconciliationStatisticalReportV02 --|> IOuterRecord : Implements
    DerivativesTradeReconciliationStatisticalReportV02Document --|> IOuterDocument~DerivativesTradeReconciliationStatisticalReportV02~ : Implements
    class IOuterDocument~DerivativesTradeReconciliationStatisticalReportV02~ {
        DerivativesTradeReconciliationStatisticalReportV02 Message
     }
  

Document wrapper for serialization

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

classDiagram
    DerivativesTradeReconciliationStatisticalReportV02Document *-- DerivativesTradeReconciliationStatisticalReportV02 : 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.091.001.02">
    <DerivsTradRcncltnSttstclRpt>
        <RcncltnSttstcs>
            <!-- ReconciliationStatistics inner content -->
        </RcncltnSttstcs>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </DerivsTradRcncltnSttstclRpt>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_pVVviWmFEe2DRvVJM2Qy-g"
  name="DerivativesTradeReconciliationStatisticalReportV02"
  definition="The DerivativesTradeReportReconciliationStatisticalReport message is sent by the trade repositories to the reporting counterparty, to report cumulative information within the reference period for the reconciliation status of the reported and outstanding derivatives."
  registrationStatus="Registered"
  messageSet="_gVqhJBWsEeqvRcdYcNYAVw"
  xmlTag="DerivsTradRcncltnSttstclRpt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_pVVvi2mFEe2DRvVJM2Qy-g"
    name="ReconciliationStatistics"
    definition="Detailed information on reconciliation process."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="RcncltnSttstcs"
    complexType="_cDvmkVovEe23K4GXSpBSeg" />
  <messageBuildingBlock
    xmi:id="_pVVvjWmFEe2DRvVJM2Qy-g"
    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="091"
    flavour="001"
    version="02" />
</messageDefinition>

ISO Building Blocks

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