CollateralManagementCancellationRequestV03

colr.005.001.03

Scope This CollateralManagementCancellationRequest message is sent by:

• the collateral taker or its collateral manager to the collateral giver or its collateral manager,
• the collateral giver or its collateral manager to the collateral taker or its collateral manager This message is used to request the cancellation of a previously sent MarginCallRequest message, MarginCallResponse message, CollateralProposal message, CollateralProposalResponse message, MarginCallDisputeNotification message or a CollateralSubstitutionRequest message.

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

Usage The CollateralManagementCancellationRequest message is used to request the cancellation of a collateral message. When requesting the cancellation of a message there must be a cancellation reason specified. When the CollateralManagementCancellationRequest message is used to cancel a collateral message the reference of the original message must be specified. The rejection or acceptance of a CollateralManagementCancellationRequest message is made using a CollateralManagementCancellationStatus message.

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
%% CollateralManagementCancellationRequestV03 recursion level 0 with max 0
class CollateralManagementCancellationRequestV03{
    TransactionIdentification IsoMax35Text
}
CollateralManagementCancellationRequestV03 *-- "1..1" IReference2Choice : Reference
CollateralManagementCancellationRequestV03 *-- "1..1" Obligation3 : Obligation
CollateralManagementCancellationRequestV03 *-- "1..1" CollateralCancellationReason1 : CancellationReason
CollateralManagementCancellationRequestV03 *-- "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.

Reference building block

Reference to the message advised to be cancelled. Choice between the identification of the MarginCallRequest message, the MarginCallResponse message, the CollateralProposal message, the CollateralProposalResponse message, the CollateralSubstitutionRequest message, the CollateralSubstitutionResponse message, the CollateralSubstitutionConfirmation message, the InterestPaymentRequest message, the InterestPaymentResponse message, the InterestPaymentStatement message or the MarginCallDisputeNotification message. For comparison, see the ISO20022 official specification

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

Reference2Choice members

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

CancellationReason building block

It is used to detail the reason for the cancellation of a previously sent request. Reason for which the collateral message has been cancelled. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% CollateralCancellationReason1 recursion level 0 with max 1
class CollateralCancellationReason1{
    AdditionalInformation IsoMax35Text
}
CollateralCancellationReason1 *-- "1..1" ICollateralCancellationType1Choice : CancellationReasonCode
%% ICollateralCancellationType1Choice recursion level 1 with max 1
  

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

classDiagram
    class IOuterRecord
    CollateralManagementCancellationRequestV03 --|> IOuterRecord : Implements
    CollateralManagementCancellationRequestV03Document --|> IOuterDocument~CollateralManagementCancellationRequestV03~ : Implements
    class IOuterDocument~CollateralManagementCancellationRequestV03~ {
        CollateralManagementCancellationRequestV03 Message
     }
  

Document wrapper for serialization

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

classDiagram
    CollateralManagementCancellationRequestV03Document *-- CollateralManagementCancellationRequestV03 : 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.005.001.03">
    <CollMgmtCxlReq>
        <TxId>
            <!-- TransactionIdentification inner content -->
        </TxId>
        <Ref>
            <!-- Reference inner content -->
        </Ref>
        <Oblgtn>
            <!-- Obligation inner content -->
        </Oblgtn>
        <CxlRsn>
            <!-- CancellationReason inner content -->
        </CxlRsn>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </CollMgmtCxlReq>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_AP6ogV9MEeSMgPeFpRHeJw"
  nextVersions="_Z6K7cYFrEeWtPe6Crjmeug"
  name="CollateralManagementCancellationRequestV03"
  definition="Scope&#xD;&#xA;This CollateralManagementCancellationRequest message is sent by:&#xD;&#xA;- the collateral taker or its collateral manager to the collateral giver or its collateral manager,&#xD;&#xA;- the collateral giver or its collateral manager to the collateral taker or its collateral manager&#xD;&#xA;This message is used to request the cancellation of a previously sent MarginCallRequest message, MarginCallResponse message, CollateralProposal message, CollateralProposalResponse message, MarginCallDisputeNotification message or a CollateralSubstitutionRequest message.&#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 CollateralManagementCancellationRequest message is used to request the cancellation of a collateral message. When requesting the cancellation of a message there must be a cancellation reason specified.&#xD;&#xA;When the CollateralManagementCancellationRequest message is used to cancel a collateral message the reference of the original message must be specified. The rejection or acceptance of a CollateralManagementCancellationRequest message is made using a CollateralManagementCancellationStatus message."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="CollMgmtCxlReq"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_AP6og19MEeSMgPeFpRHeJw"
    nextVersions="_Z6K7c4FrEeWtPe6Crjmeug"
    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="_AP6ohV9MEeSMgPeFpRHeJw"
    nextVersions="_Z6K7dYFrEeWtPe6Crjmeug"
    name="Reference"
    definition="Reference to the message advised to be cancelled."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Ref"
    complexType="_TYNGkKerEeCq2KR6DaC1kQ_992102367" />
  <messageBuildingBlock
    xmi:id="_AP6oh19MEeSMgPeFpRHeJw"
    nextVersions="_Z6K7d4FrEeWtPe6Crjmeug"
    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="_AP6oiV9MEeSMgPeFpRHeJw"
    nextVersions="_Z6K7eYFrEeWtPe6Crjmeug"
    name="CancellationReason"
    definition="It is used to detail the reason for the cancellation of a previously sent request."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="CxlRsn"
    complexType="_UnhiwNp-Ed-ak6NoX_4Aeg_-540863751" />
  <messageBuildingBlock
    xmi:id="_AP6oi19MEeSMgPeFpRHeJw"
    nextVersions="_Z6K7e4FrEeWtPe6Crjmeug"
    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="005"
    flavour="001"
    version="03" />
</messageDefinition>

ISO Building Blocks

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