CollateralSubstitutionResponseV05

colr.011.001.05

Scope The CollateralSubstitutionResponse message is sent by either the collateral taker or its collateral manager to the collateral giver or its collateral manager. This is a response to the CollateralSubstitutionRequest message and the collateral proposed in the substitution request can be accepted or rejected. If the collateral proposed is rejected then a new CollateralSubstitutionRequest should be sent. Note: There are cases where the collateral giver will send this message when the collateral taker has initiated the CollateralSubstitutionRequest message, for example in case of breach in the concentration limit.

The message definition is intended for use with the ISO20022 Business Application Header.

Usage This is a response to the CollateralSubstitutionRequest message and the collateral proposed in the substitution request can be accepted or rejected.

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
%% CollateralSubstitutionResponseV05 recursion level 0 with max 0
class CollateralSubstitutionResponseV05{
    TransactionIdentification IsoMax35Text
}
CollateralSubstitutionResponseV05 *-- "1..1" Obligation9 : Obligation
CollateralSubstitutionResponseV05 *-- "0..1" Agreement4 : Agreement
CollateralSubstitutionResponseV05 *-- "1..1" SubstitutionResponse2 : SubstitutionResponse
CollateralSubstitutionResponseV05 *-- "0..1" SupplementaryData1 : SupplementaryData
  

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

TransactionIdentification building block

Unambiguous identification of the transaction as know by the instructing party. Specifies a character string with a maximum length of 35 characters. For comparison, see the ISO20022 official specification This message is declared as Max35Text in the ISO specification. In our implementation, it is represented in source code as IsoMax35Text. Due to global using directives, it is treated as a System.String by the compiler and runtime.

Obligation building block

Provides information like the identification of the party or parties associated with the collateral agreement, the exposure type and the valuation date. Provides information like the identification of the party or parties associated with the collateral agreement, the exposure type and the valuation date. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Obligation9 recursion level 0 with max 1
class Obligation9{
    ExposureType ExposureType11Code
}
Obligation9 *-- "1..1" IPartyIdentification178Choice : PartyA
Obligation9 *-- "0..1" IPartyIdentification178Choice : ServicingPartyA
Obligation9 *-- "1..1" IPartyIdentification178Choice : PartyB
Obligation9 *-- "0..1" IPartyIdentification178Choice : ServicingPartyB
Obligation9 *-- "0..1" CollateralAccount3 : CollateralAccountIdentification
Obligation9 *-- "0..1" BlockChainAddressWallet5 : BlockChainAddressOrWallet
Obligation9 *-- "1..1" IDateAndDateTime2Choice : ValuationDate
%% IPartyIdentification178Choice recursion level 1 with max 1
%% IPartyIdentification178Choice recursion level 1 with max 1
%% IPartyIdentification178Choice recursion level 1 with max 1
%% IPartyIdentification178Choice recursion level 1 with max 1
%% CollateralAccount3 recursion level 1 with max 1
class CollateralAccount3{
    Identification IsoMax35Text
    Name IsoMax70Text
}
CollateralAccount3 *-- "0..1" ICollateralAccountIdentificationType3Choice : Type
%% BlockChainAddressWallet5 recursion level 1 with max 1
class BlockChainAddressWallet5{
    Identification IsoMax140Text
    Name IsoMax70Text
}
BlockChainAddressWallet5 *-- "0..1" ICollateralAccountIdentificationType3Choice : Type
%% IDateAndDateTime2Choice recursion level 1 with max 1
  

Obligation9 members

Agreement building block

Agreement details for the over the counter market. Agreement details for the over the counter market. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Agreement4 recursion level 0 with max 1
class Agreement4{
    AgreementDetails IsoMax140Text
    AgreementIdentification IsoMax140Text
    AgreementDate IsoISODate
    BaseCurrency ActiveCurrencyCode
}
Agreement4 *-- "0..1" IAgreementFramework1Choice : AgreementFramework
%% IAgreementFramework1Choice recursion level 1 with max 1
  

Agreement4 members

SubstitutionResponse building block

Provides details about the collateral substitution response. Provides details about the collateral substitution response. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% SubstitutionResponse2 recursion level 0 with max 1
class SubstitutionResponse2{
    ResponseType Status4Code
}
SubstitutionResponse2 *-- "0..1" CollateralSubstitutionResponse1 : CollateralSubstitutionAcceptanceDetails
SubstitutionResponse2 *-- "0..1" CollateralSubstitutionResponse3 : CollateralSubstitutionRejectionDetails
%% CollateralSubstitutionResponse1 recursion level 1 with max 1
class CollateralSubstitutionResponse1{
    CollateralSubstitutionRequestIdentification IsoMax35Text
    AcceptedAmount IsoActiveCurrencyAndAmount
}
%% CollateralSubstitutionResponse3 recursion level 1 with max 1
class CollateralSubstitutionResponse3{
    CollateralSubstitutionRequestIdentification IsoMax35Text
    RejectedAmount IsoActiveCurrencyAndAmount
    RejectionReason RejectionReason68Code
    RejectionReasonInformation IsoMax140Text
}
  

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

classDiagram
    class IOuterRecord
    CollateralSubstitutionResponseV05 --|> IOuterRecord : Implements
    CollateralSubstitutionResponseV05Document --|> IOuterDocument~CollateralSubstitutionResponseV05~ : Implements
    class IOuterDocument~CollateralSubstitutionResponseV05~ {
        CollateralSubstitutionResponseV05 Message
     }
  

Document wrapper for serialization

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

classDiagram
    CollateralSubstitutionResponseV05Document *-- CollateralSubstitutionResponseV05 : 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:colr.011.001.05">
    <CollSbstitnRspn>
        <TxId>
            <!-- TransactionIdentification inner content -->
        </TxId>
        <Oblgtn>
            <!-- Obligation inner content -->
        </Oblgtn>
        <Agrmt>
            <!-- Agreement inner content -->
        </Agrmt>
        <SbstitnRspn>
            <!-- SubstitutionResponse inner content -->
        </SbstitnRspn>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </CollSbstitnRspn>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_J4YklSgrEeyB747fKu7_rw"
  previousVersion="_5bGyoYFrEeWtPe6Crjmeug"
  name="CollateralSubstitutionResponseV05"
  definition="Scope&#xD;&#xA;The CollateralSubstitutionResponse message is sent by either the collateral taker or its collateral manager to the collateral giver or its collateral manager. This is a response to the CollateralSubstitutionRequest message and the collateral proposed in the substitution request can be accepted or rejected. If the collateral proposed is rejected then a new CollateralSubstitutionRequest should be sent. Note: There are cases where the collateral giver will send this message when the collateral taker has initiated the CollateralSubstitutionRequest message, for example in case of breach in the concentration limit.&#xD;&#xA;&#xD;&#xA;The message definition is intended for use with the ISO20022 Business Application Header.&#xD;&#xA;&#xD;&#xA;Usage&#xD;&#xA;This is a response to the CollateralSubstitutionRequest message and the collateral proposed in the substitution request can be accepted or rejected."
  registrationStatus="Registered"
  messageSet="_L9Kq4XoIEeSUmamj3OpPWw"
  xmlTag="CollSbstitnRspn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_J4YkmygrEeyB747fKu7_rw"
    previousVersion="_5bGyo4FrEeWtPe6Crjmeug"
    name="TransactionIdentification"
    definition="Unambiguous identification of the transaction as know by the instructing party."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="TxId"
    simpleType="_YW1tKdp-Ed-ak6NoX_4Aeg_1913463446" />
  <messageBuildingBlock
    xmi:id="_J4YknSgrEeyB747fKu7_rw"
    previousVersion="_5bGypYFrEeWtPe6Crjmeug"
    name="Obligation"
    definition="Provides information like the identification of the party or parties associated with the collateral agreement, the exposure type and the valuation date."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Oblgtn"
    complexType="_wc_c4SgsEeyB747fKu7_rw" />
  <messageBuildingBlock
    xmi:id="_J4YknygrEeyB747fKu7_rw"
    previousVersion="_5bGyp4FrEeWtPe6Crjmeug"
    name="Agreement"
    definition="Agreement details for the over the counter market."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="Agrmt"
    complexType="_6T7_AYbEEeWguotXa4lFgg" />
  <messageBuildingBlock
    xmi:id="_J4YkoSgrEeyB747fKu7_rw"
    previousVersion="_5bGyqYFrEeWtPe6Crjmeug"
    name="SubstitutionResponse"
    definition="Provides details about the collateral substitution response."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="SbstitnRspn"
    complexType="_E7FbAStJEeyOa655cLd-DQ" />
  <messageBuildingBlock
    xmi:id="_J4YkoygrEeyB747fKu7_rw"
    previousVersion="_5bGyq4FrEeWtPe6Crjmeug"
    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="colr"
    messageFunctionality="011"
    flavour="001"
    version="05" />
</messageDefinition>

ISO Building Blocks

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