CollateralProposalResponseV03

colr.008.001.03

Scope This CollateralProposalResponse message is sent by the collateral taker or its collateral manager to the collateral giver or its collateral manager to either accept or reject the collateral which has been proposed for the margin call. This message applies to both initial and counter proposals. If the collateral proposal is rejected then a new collateral proposal must be made.

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

Usage The CollateralProposalResponse message can be sent in response to a previously received CollateralProposal message in order to accept or reject the collateral that has been proposed to cover the margin call.

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
%% CollateralProposalResponseV03 recursion level 0 with max 0
class CollateralProposalResponseV03{
    TransactionIdentification IsoMax35Text
}
CollateralProposalResponseV03 *-- "1..1" Obligation3 : Obligation
CollateralProposalResponseV03 *-- "1..1" ICollateralProposalResponse2Choice : ProposalResponse
CollateralProposalResponseV03 *-- "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
%% Obligation3 recursion level 0 with max 1
class Obligation3{
    ExposureType ExposureType5Code
}
Obligation3 *-- "1..1" IPartyIdentification33Choice : PartyA
Obligation3 *-- "0..1" IPartyIdentification33Choice : ServicingPartyA
Obligation3 *-- "1..1" IPartyIdentification33Choice : PartyB
Obligation3 *-- "0..1" IPartyIdentification33Choice : ServicingPartyB
Obligation3 *-- "0..1" CollateralAccount1 : CollateralAccountIdentification
Obligation3 *-- "1..1" IDateAndDateTimeChoice : ValuationDate
%% IPartyIdentification33Choice recursion level 1 with max 1
%% IPartyIdentification33Choice recursion level 1 with max 1
%% IPartyIdentification33Choice recursion level 1 with max 1
%% IPartyIdentification33Choice recursion level 1 with max 1
%% CollateralAccount1 recursion level 1 with max 1
class CollateralAccount1{
    Identification IsoMax35Text
    Name IsoMax70Text
}
CollateralAccount1 *-- "0..1" ICollateralAccountIdentificationType1Choice : Type
%% IDateAndDateTimeChoice recursion level 1 with max 1
  

Obligation3 members

ProposalResponse building block

Details the response to the collateral which has been proposed for the margin call. The proposed collateral can be accepted or rejected.

Provides the collateral proposal response for the variation margin and the segregated independent amount, or the segregated independent amount only. For comparison, see the ISO20022 official specification

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

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

classDiagram
    class IOuterRecord
    CollateralProposalResponseV03 --|> IOuterRecord : Implements
    CollateralProposalResponseV03Document --|> IOuterDocument~CollateralProposalResponseV03~ : Implements
    class IOuterDocument~CollateralProposalResponseV03~ {
        CollateralProposalResponseV03 Message
     }
  

Document wrapper for serialization

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

classDiagram
    CollateralProposalResponseV03Document *-- CollateralProposalResponseV03 : 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.008.001.03">
    <CollPrpslRspn>
        <TxId>
            <!-- TransactionIdentification inner content -->
        </TxId>
        <Oblgtn>
            <!-- Obligation inner content -->
        </Oblgtn>
        <PrpslRspn>
            <!-- ProposalResponse inner content -->
        </PrpslRspn>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </CollPrpslRspn>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_f5lIsVnMEeSPgY23yCMQSQ"
  nextVersions="_fkI0oYFrEeWtPe6Crjmeug"
  name="CollateralProposalResponseV03"
  definition="Scope&#xD;&#xA;This CollateralProposalResponse message is sent by the collateral taker or its collateral manager to the collateral giver or its collateral manager to either accept or reject the collateral which has been proposed for the margin call. This message applies to both initial and counter proposals. If the collateral proposal is rejected then a new collateral proposal must be made.&#xD;&#xA;&#xD;&#xA;The message definition is intended for use with the ISO20022 Business Application Header.&#xD;&#xA;&#xD;&#xA;Usage&#xD;&#xA;The CollateralProposalResponse message can be sent in response to a previously received CollateralProposal message in order to accept or reject the collateral that has been proposed to cover the margin call."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="CollPrpslRspn"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_f5lIs1nMEeSPgY23yCMQSQ"
    nextVersions="_fkI0o4FrEeWtPe6Crjmeug"
    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="_f5lItVnMEeSPgY23yCMQSQ"
    nextVersions="_fkI0pYFrEeWtPe6Crjmeug"
    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="_cSBe4WNeEeSLD8nyfZcLzQ" />
  <messageBuildingBlock
    xmi:id="_f5lIt1nMEeSPgY23yCMQSQ"
    nextVersions="_fkI0p4FrEeWtPe6Crjmeug"
    name="ProposalResponse"
    definition="Details the response to the collateral which has been proposed for the margin call. The proposed collateral can be accepted or rejected.&#xD;&#xA;"
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="PrpslRspn"
    complexType="_vOOvQWTUEeSSTJlMfOKFsA" />
  <messageBuildingBlock
    xmi:id="_f5lIuVnMEeSPgY23yCMQSQ"
    nextVersions="_fkI0qYFrEeWtPe6Crjmeug"
    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="008"
    flavour="001"
    version="03" />
</messageDefinition>

ISO Building Blocks

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