Iso20022

CollateralSubstitutionConfirmationV04

colr.012.001.04

Scope The CollateralSubstitutionConfirmation message is sent by:

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

Usage This message confirms the collateral delivery. The collateral taker will only release the return of collateral when the new piece of collateral is received. The collateral giver sends the collateral taker the notification that the collateral substitution (that is new piece(s) of collateral) have been released.

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
%% CollateralSubstitutionConfirmationV04 recursion level 0 with max 0
class CollateralSubstitutionConfirmationV04{
    TransactionIdentification IsoMax35Text
}
CollateralSubstitutionConfirmationV04 *-- "1..1" Obligation4 : Obligation
CollateralSubstitutionConfirmationV04 *-- "0..1" Agreement4 : Agreement
CollateralSubstitutionConfirmationV04 *-- "1..1" CollateralConfirmation1 : SubstitutionConfirmation
CollateralSubstitutionConfirmationV04 *-- "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
%% Obligation4 recursion level 0 with max 1
class Obligation4{
    ExposureType ExposureType5Code
}
Obligation4 *-- "1..1" IPartyIdentification100Choice : PartyA
Obligation4 *-- "0..1" IPartyIdentification100Choice : ServicingPartyA
Obligation4 *-- "1..1" IPartyIdentification100Choice : PartyB
Obligation4 *-- "0..1" IPartyIdentification100Choice : ServicingPartyB
Obligation4 *-- "0..1" CollateralAccount2 : CollateralAccountIdentification
Obligation4 *-- "1..1" IDateAndDateTimeChoice : ValuationDate
%% IPartyIdentification100Choice recursion level 1 with max 1
%% IPartyIdentification100Choice recursion level 1 with max 1
%% IPartyIdentification100Choice recursion level 1 with max 1
%% IPartyIdentification100Choice recursion level 1 with max 1
%% CollateralAccount2 recursion level 1 with max 1
class CollateralAccount2{
    Identification IsoMax35Text
    Name IsoMax70Text
}
CollateralAccount2 *-- "0..1" ICollateralAccountIdentificationType2Choice : Type
%% IDateAndDateTimeChoice recursion level 1 with max 1

Obligation4 members

Member name Description Data Type / Multiplicity
PartyA Defines one of the entities associated with the collateral agreement. IPartyIdentification100Choice - Required 1..1
ServicingPartyA Specifies the party that is acting on behalf of party A and that offers collateral management services. IPartyIdentification100Choice - Optional 0..1
PartyB Defines the other entity associated with the collateral agreement. IPartyIdentification100Choice - Required 1..1
ServicingPartyB Specifies the party that is acting on behalf of party B and that offers collateral management services. IPartyIdentification100Choice - Optional 0..1
CollateralAccountIdentification Provides additional information on the collateral account of the party delivering/receiving the collateral. CollateralAccount2 - Optional 0..1
ExposureType Specifies the underlying business area or type of trade causing the collateral movement. ExposureType5Code - Optional 0..1
ValuationDate Indicates the close of business date on which the initiating party is valuing the margin call. IDateAndDateTimeChoice - Required 1..1

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

Member name Description Data Type / Multiplicity
AgreementDetails Full details of the supporting legal agreement under which the margin call can be issued and/or governed. IsoMax140Text - Required 1..1
AgreementIdentification Common reference to the agreement between the two counterparties. IsoMax140Text - Optional 0..1
AgreementDate Date on which the collateral agreement was signed. IsoISODate - Required 1..1
BaseCurrency Denomination currency as specified in the collateral agreement. ActiveCurrencyCode - Required 1..1
AgreementFramework Specifies the underlying master agreement. IAgreementFramework1Choice - Optional 0..1

SubstitutionConfirmation building block

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

classDiagram
   direction tb
%% CollateralConfirmation1 recursion level 0 with max 1
class CollateralConfirmation1{
    CollateralSubstitutionRequestIdentification IsoMax35Text
    CollateralSubstitutionResponseIdentification IsoMax35Text
    ConfirmationType CollateralSubstitutionConfirmation1Code
    Comment IsoMax140Text
}

CollateralConfirmation1 members

Member name Description Data Type / Multiplicity
CollateralSubstitutionRequestIdentification Reference to the collateral substitution request identification. IsoMax35Text - Required 1..1
CollateralSubstitutionResponseIdentification Reference to the collateral substitution response identification. IsoMax35Text - Optional 0..1
ConfirmationType Provides details about the status of the collateral substitution, either released or returned. CollateralSubstitutionConfirmation1Code - Required 1..1
Comment Allows to provides additional comments on the collateral substitution status. IsoMax140Text - Optional 0..1

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

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

classDiagram
    class IOuterRecord
    CollateralSubstitutionConfirmationV04 --|> IOuterRecord : Implements
    CollateralSubstitutionConfirmationV04Document --|> IOuterDocument~CollateralSubstitutionConfirmationV04~ : Implements
    class IOuterDocument~CollateralSubstitutionConfirmationV04~ {
        CollateralSubstitutionConfirmationV04 Message
     }

Document wrapper for serialization

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

classDiagram
    CollateralSubstitutionConfirmationV04Document *-- CollateralSubstitutionConfirmationV04 : 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.012.001.04">
    <CollSbstitnConf>
        <TxId>
            <!-- TransactionIdentification inner content -->
        </TxId>
        <Oblgtn>
            <!-- Obligation inner content -->
        </Oblgtn>
        <Agrmt>
            <!-- Agreement inner content -->
        </Agrmt>
        <SbstitnConf>
            <!-- SubstitutionConfirmation inner content -->
        </SbstitnConf>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </CollSbstitnConf>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_rREV0YFrEeWtPe6Crjmeug"
  nextVersions="_J4YkpSgrEeyB747fKu7_rw"
  previousVersion="_7A0N0WNmEeSIWbZ6by9dnA"
  name="CollateralSubstitutionConfirmationV04"
  definition="Scope&#xD;&#xA;The CollateralSubstitutionConfirmation message is sent by:&#xD;&#xA;- the collateral taker or its collateral manager to the collateral giver or its collateral manager, or&#xD;&#xA;- the collateral giver or its collateral manager to the collateral taker or its collateral manager.&#xD;&#xA;This message confirms the collateral delivery. The collateral taker will only release the return of collateral when the new piece of collateral is received. The collateral giver sends the collateral taker the notification that the collateral substitution (that is new piece(s) of collateral) have been released. In the event that multiple pieces of collateral are being delivered in place of the collateral due to be returned by the giver, this message should only be generated once all collateral pieces have been agreed between both parties. Then the taker confirms that the collateral substitution (that is all pieces have been received) and acknowledges return of collateral.&#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 message confirms the collateral delivery. The collateral taker will only release the return of collateral when the new piece of collateral is received. The collateral giver sends the collateral taker the notification that the collateral substitution (that is new piece(s) of collateral) have been released."
  registrationStatus="Registered"
  messageSet="_J0aB9KV_EeW0_oPI5GRpwg"
  xmlTag="CollSbstitnConf"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_rREV04FrEeWtPe6Crjmeug"
    nextVersions="_J4YkrSgrEeyB747fKu7_rw"
    previousVersion="_7A0N02NmEeSIWbZ6by9dnA"
    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="_rREV1YFrEeWtPe6Crjmeug"
    nextVersions="_J4YkrygrEeyB747fKu7_rw"
    previousVersion="_E3xr4GNnEeSIWbZ6by9dnA"
    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="_wtu2IYFvEeWtPe6Crjmeug" />
  <messageBuildingBlock
    xmi:id="_rREV14FrEeWtPe6Crjmeug"
    nextVersions="_J4YksSgrEeyB747fKu7_rw"
    previousVersion="_7A0N3WNmEeSIWbZ6by9dnA"
    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="_rREV2YFrEeWtPe6Crjmeug"
    nextVersions="_J4YksygrEeyB747fKu7_rw"
    previousVersion="_7A0N32NmEeSIWbZ6by9dnA"
    name="SubstitutionConfirmation"
    definition="Provides the status about the collateral substitution."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="SbstitnConf"
    complexType="_UnrTxNp-Ed-ak6NoX_4Aeg_-2119738374" />
  <messageBuildingBlock
    xmi:id="_rREV24FrEeWtPe6Crjmeug"
    nextVersions="_J4YktSgrEeyB747fKu7_rw"
    previousVersion="_7A0N4WNmEeSIWbZ6by9dnA"
    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="012"
    flavour="001"
    version="04" />
</messageDefinition>

ISO Building Blocks

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