SecuritiesFinancingReportingPairingRequestV01

auth.078.001.01

The SecuritiesFinancingReportingPairingRequest is sent by the trade repository (TR) to the other trade repositories (TRs) in order to identify the trade repository (TR) holding information on a second leg of a given transaction.

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
%% SecuritiesFinancingReportingPairingRequestV01 recursion level 0 with max 0
SecuritiesFinancingReportingPairingRequestV01 *-- "1..1" TradeTransactionIdentification4 : TransactionIdentification
SecuritiesFinancingReportingPairingRequestV01 *-- "0..1" SupplementaryData1 : SupplementaryData
  

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

TransactionIdentification building block

Information related to transactions that are to be paired. Provides details on transaction and conducting counterparty. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% TradeTransactionIdentification4 recursion level 0 with max 1
class TradeTransactionIdentification4{
    UniqueTradeIdentifier IsoMax52Text
}
TradeTransactionIdentification4 *-- "1..1" IOrganisationIdentification9Choice : ReportingCounterparty
TradeTransactionIdentification4 *-- "1..1" IOrganisationIdentification9Choice : OtherCounterparty
TradeTransactionIdentification4 *-- "0..1" MasterAgreement6 : MasterAgreement
TradeTransactionIdentification4 *-- "0..1" IOrganisationIdentification9Choice : AgentLender
TradeTransactionIdentification4 *-- "0..1" IOrganisationIdentification9Choice : TripartyAgent
%% IOrganisationIdentification9Choice recursion level 1 with max 1
%% IOrganisationIdentification9Choice recursion level 1 with max 1
%% MasterAgreement6 recursion level 1 with max 1
class MasterAgreement6{
    Version IsoMax50Text
    OtherMasterAgreementDetails IsoMax350Text
}
MasterAgreement6 *-- "1..1" IAgreementType1Choice : Type
%% IOrganisationIdentification9Choice recursion level 1 with max 1
%% IOrganisationIdentification9Choice recursion level 1 with max 1
  

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

classDiagram
    class IOuterRecord
    SecuritiesFinancingReportingPairingRequestV01 --|> IOuterRecord : Implements
    SecuritiesFinancingReportingPairingRequestV01Document --|> IOuterDocument~SecuritiesFinancingReportingPairingRequestV01~ : Implements
    class IOuterDocument~SecuritiesFinancingReportingPairingRequestV01~ {
        SecuritiesFinancingReportingPairingRequestV01 Message
     }
  

Document wrapper for serialization

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

classDiagram
    SecuritiesFinancingReportingPairingRequestV01Document *-- SecuritiesFinancingReportingPairingRequestV01 : 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.078.001.01">
    <SctiesFincgRptgPairgReq>
        <TxId>
            <!-- TransactionIdentification inner content -->
        </TxId>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </SctiesFincgRptgPairgReq>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_2zvL_QuAEeqVvtu9Ny8FDA"
  nextVersions="_mxP0EcIVEeunlsN4rAgJZA"
  name="SecuritiesFinancingReportingPairingRequestV01"
  definition="The SecuritiesFinancingReportingPairingRequest is sent by the trade repository (TR) to the other trade repositories (TRs) in order to identify the trade repository (TR) holding information on a second leg of a given transaction."
  registrationStatus="Registered"
  messageSet="_80T9UAw7Eeqb0PC56-ljDA"
  xmlTag="SctiesFincgRptgPairgReq"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_2zvL_wuAEeqVvtu9Ny8FDA"
    nextVersions="_mxP0E8IVEeunlsN4rAgJZA"
    name="TransactionIdentification"
    definition="Information related to transactions that are to be paired."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="TxId"
    complexType="_CUwEIaxiEem81-uIvTF5rQ" />
  <messageBuildingBlock
    xmi:id="_2zvMAQuAEeqVvtu9Ny8FDA"
    nextVersions="_mxP0FcIVEeunlsN4rAgJZA"
    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="078"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

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