SecuritiesFinancingReportingReconciliationStatusAdviceV02

auth.080.001.02

The SecuritesFinancingReportingReconciliationStatusAdvice message is sent by the trade repositories (TRs) ) to other TR and to the authority or made available to the report submitting entity and the reporting counterparty as well as the entity responsible for reporting, if applicable, to provide a status advice for reconciliation.

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
%% SecuritiesFinancingReportingReconciliationStatusAdviceV02 recursion level 0 with max 0
SecuritiesFinancingReportingReconciliationStatusAdviceV02 *-- "1..1" ITradeData34Choice : ReconciliationData
SecuritiesFinancingReportingReconciliationStatusAdviceV02 *-- "0..1" SupplementaryData1 : SupplementaryData
  

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

ReconciliationData building block

Set of data concerning the reconciliation results. Set of data concerning the reporting trade. For comparison, see the ISO20022 official specification

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

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

classDiagram
    class IOuterRecord
    SecuritiesFinancingReportingReconciliationStatusAdviceV02 --|> IOuterRecord : Implements
    SecuritiesFinancingReportingReconciliationStatusAdviceV02Document --|> IOuterDocument~SecuritiesFinancingReportingReconciliationStatusAdviceV02~ : Implements
    class IOuterDocument~SecuritiesFinancingReportingReconciliationStatusAdviceV02~ {
        SecuritiesFinancingReportingReconciliationStatusAdviceV02 Message
     }
  

Document wrapper for serialization

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

classDiagram
    SecuritiesFinancingReportingReconciliationStatusAdviceV02Document *-- SecuritiesFinancingReportingReconciliationStatusAdviceV02 : 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.080.001.02">
    <SctiesFincgRptgRcncltnStsAdvc>
        <RcncltnData>
            <!-- ReconciliationData inner content -->
        </RcncltnData>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </SctiesFincgRptgRcncltnStsAdvc>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_gt-cEcKvEeuzU9S_IANlog"
  previousVersion="_2zvMAwuAEeqVvtu9Ny8FDA"
  name="SecuritiesFinancingReportingReconciliationStatusAdviceV02"
  definition="The SecuritesFinancingReportingReconciliationStatusAdvice message is sent by the trade repositories (TRs) ) to other TR and to the authority or made available to the report submitting entity and the reporting counterparty as well as the entity responsible for reporting, if applicable, to provide a status advice for reconciliation."
  registrationStatus="Registered"
  messageSet="_9iTc0K2XEeuIDus5QP8udw"
  xmlTag="SctiesFincgRptgRcncltnStsAdvc"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_gt-cE8KvEeuzU9S_IANlog"
    name="ReconciliationData"
    definition="Set of data concerning the reconciliation results."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="RcncltnData"
    complexType="_Ap4T0cK3EeuFNp8LZAnorg" />
  <messageBuildingBlock
    xmi:id="_gt-cFcKvEeuzU9S_IANlog"
    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="080"
    flavour="001"
    version="02" />
</messageDefinition>

ISO Building Blocks

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