colr.007.001.05
Scope The CollateralProposal message is sent by the collateral giver or its collateral manager to the collateral taker or its collateral manager, to propose the collateral to be delivered. This message is sent once the Margin Call is agreed or partially agreed and can be used for new collateral at the initiation of an exposure or for additional collateral for variation of an existing exposure. This message is used for both initial collateral proposal and subsequent counter proposals.
The message definition is intended for use with the ISO20022 Business Application Header.
Usage This message is sent once the Margin Call is agreed or partially agreed and can be used for new collateral at the initiation of an exposure or for additional collateral for variation of an existing exposure. The collateral proposal can include securities, cash and other types of collateral.
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 %% CollateralProposalV05 recursion level 0 with max 0 class CollateralProposalV05{ TransactionIdentification IsoMax35Text } CollateralProposalV05 *-- "1..1" Obligation5 : Obligation CollateralProposalV05 *-- "0..1" Agreement4 : Agreement CollateralProposalV05 *-- "1..1" Proposal5 : TypeAndDetails CollateralProposalV05 *-- "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 %% Obligation5 recursion level 0 with max 1 class Obligation5{ ExposureType ExposureType5Code } Obligation5 *-- "1..1" IPartyIdentification100Choice : PartyA Obligation5 *-- "0..1" IPartyIdentification100Choice : ServicingPartyA Obligation5 *-- "1..1" IPartyIdentification100Choice : PartyB Obligation5 *-- "0..1" IPartyIdentification100Choice : ServicingPartyB Obligation5 *-- "0..1" CollateralAccount3 : CollateralAccountIdentification Obligation5 *-- "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 %% CollateralAccount3 recursion level 1 with max 1 class CollateralAccount3{ Identification IsoMax35Text Name IsoMax70Text } CollateralAccount3 *-- "0..1" ICollateralAccountIdentificationType3Choice : Type %% IDateAndDateTimeChoice recursion level 1 with max 1
Obligation5 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. | CollateralAccount3 - 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 |
TypeAndDetails building block
Indicates whether this is an initial or counter proposal. Indicates the type of proposal and if the proposal is 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 %% Proposal5 recursion level 0 with max 1 class Proposal5{ CollateralProposalType ProposalType1Code } Proposal5 *-- "1..1" ICollateralProposal5Choice : CollateralProposal %% ICollateralProposal5Choice recursion level 1 with max 1
Proposal5 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
CollateralProposalType | Indicates whether this is an initial or counter proposal. | ProposalType1Code - Required 1..1 |
CollateralProposal | Provides details about the proposal for the variation margin and the segregated independent amount, or the segregated independent amount only. | ICollateralProposal5Choice - Required 1..1 |
SupplementaryData building block
Additional information that cannot be captured in the structured elements 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 CollateralProposalV05 implementation follows a specific implementaiton pattern. First of all, CollateralProposalV05 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, CollateralProposalV05Document implements IOuterDocument. Because CollateralProposalV05 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type CollateralProposalV05.
classDiagram class IOuterRecord CollateralProposalV05 --|> IOuterRecord : Implements CollateralProposalV05Document --|> IOuterDocument~CollateralProposalV05~ : Implements class IOuterDocument~CollateralProposalV05~ { CollateralProposalV05 Message }
Document wrapper for serialization
The only real purpose CollateralProposalV05Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:colr.007.001.05’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using CollateralProposalV05.ToDocument() method. The returned CollateralProposalV05Document value will serialize correctly according to ISO 20022 standards.
classDiagram CollateralProposalV05Document *-- CollateralProposalV05 : 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.007.001.05">
<CollPrpsl>
<TxId>
<!-- TransactionIdentification inner content -->
</TxId>
<Oblgtn>
<!-- Obligation inner content -->
</Oblgtn>
<Agrmt>
<!-- Agreement inner content -->
</Agrmt>
<TpAndDtls>
<!-- TypeAndDetails inner content -->
</TpAndDtls>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</CollPrpsl>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_3UoYMYoxEeaNTaanBSMWmg"
nextVersions="_J4YkVygrEeyB747fKu7_rw"
previousVersion="_ih0twYFrEeWtPe6Crjmeug"
name="CollateralProposalV05"
definition="Scope
The CollateralProposal message is sent by the collateral giver or its collateral manager to the collateral taker or its collateral manager, to propose the collateral to be delivered. This message is sent once the Margin Call is agreed or partially agreed and can be used for new collateral at the initiation of an exposure or for additional collateral for variation of an existing exposure. This message is used for both initial collateral proposal and subsequent counter proposals.

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

Usage
This message is sent once the Margin Call is agreed or partially agreed and can be used for new collateral at the initiation of an exposure or for additional collateral for variation of an existing exposure. The collateral proposal can include securities, cash and other types of collateral."
registrationStatus="Registered"
messageSet="_J0aB9KV_EeW0_oPI5GRpwg"
xmlTag="CollPrpsl"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_3UoYM4oxEeaNTaanBSMWmg"
nextVersions="_J4YkXSgrEeyB747fKu7_rw"
previousVersion="_ih0tw4FrEeWtPe6Crjmeug"
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="_3UoYNYoxEeaNTaanBSMWmg"
nextVersions="_J4YkXygrEeyB747fKu7_rw"
previousVersion="_ih0txYFrEeWtPe6Crjmeug"
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="_oZfTEa_XEeaiqo1qOdNaWg" />
<messageBuildingBlock
xmi:id="_3UoYN4oxEeaNTaanBSMWmg"
nextVersions="_J4YkYSgrEeyB747fKu7_rw"
previousVersion="_ih0tx4FrEeWtPe6Crjmeug"
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="_3UoYOYoxEeaNTaanBSMWmg"
nextVersions="_J4YkYygrEeyB747fKu7_rw"
previousVersion="_ih0tyYFrEeWtPe6Crjmeug"
name="TypeAndDetails"
definition="Indicates whether this is an initial or counter proposal."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="TpAndDtls"
complexType="_rL_T8YpIEeaNTaanBSMWmg" />
<messageBuildingBlock
xmi:id="_3UoYO4oxEeaNTaanBSMWmg"
nextVersions="_J4YkZSgrEeyB747fKu7_rw"
previousVersion="_ih0ty4FrEeWtPe6Crjmeug"
name="SupplementaryData"
definition="Additional information that cannot be captured in the structured elements and/or any other specific block."
registrationStatus="Provisionally Registered"
minOccurs="0"
xmlTag="SplmtryData"
complexType="_Qn0zC9p-Ed-ak6NoX_4Aeg_468227563" />
<messageDefinitionIdentifier
businessArea="colr"
messageFunctionality="007"
flavour="001"
version="05" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.