seev.005.001.05
Scope The MeetingInstructionCancellationRequest message is sent by the same party that sent the MeetingInstruction message. It is sent to request the cancellation of all instructions included in the original the MeetingInstruction message. Usage This message must be answered by a MeetingInstructionStatus message. Some instructions in the previously sent MeetingInstruction message may have already been executed and cannot be cancelled. This information should appear clearly in the status message. This message definition is intended for use with the Business Application Header.
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
%% MeetingInstructionCancellationRequestV05 recursion level 0 with max 0
MeetingInstructionCancellationRequestV05 *-- "1..1" MessageIdentification : PreviousReference
MeetingInstructionCancellationRequestV05 *-- "0..1" MeetingReference7 : MeetingReference
MeetingInstructionCancellationRequestV05 *-- "0..1" SecurityIdentification14 : FinancialInstrumentIdentification
MeetingInstructionCancellationRequestV05 *-- "0..1" SafekeepingAccount6 : InstructedPosition
MeetingInstructionCancellationRequestV05 *-- "0..1" SupplementaryData1 : SupplementaryData
Now, we will zero-in one-by-one on each of these building blocks.
PreviousReference building block
Identifies the instruction to be cancelled. Unique and unambiguous identifier for a message, as assigned by the Sender. This unique identifier can be used for cross-referencing purposes in subsequent messages. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% MessageIdentification recursion level 0 with max 1
class MessageIdentification{
Identification IsoMax35Text
}
MessageIdentification members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Identification | String of characters that uniquely identifies a message. | IsoMax35Text - Required 1..1 |
MeetingReference building block
Series of elements which allow to identify a meeting. Identification of a meeting. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% MeetingReference7 recursion level 0 with max 1
class MeetingReference7{
MeetingIdentification IsoMax35Text
IssuerMeetingIdentification IsoMax35Text
MeetingDateAndTime IsoISODateTime
Type MeetingType3Code
}
MeetingReference7 *-- "0..1" IMeetingTypeClassification1Choice : Classification
MeetingReference7 *-- "0..5" PostalAddress1 : Location
%% IMeetingTypeClassification1Choice recursion level 1 with max 1
%% PostalAddress1 recursion level 1 with max 1
class PostalAddress1{
AddressType AddressType2Code
AddressLine IsoMax70Text
StreetName IsoMax70Text
BuildingNumber IsoMax16Text
PostCode IsoMax16Text
TownName IsoMax35Text
CountrySubDivision IsoMax35Text
Country CountryCode
}
MeetingReference7 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| MeetingIdentification | Identification assigned to the general meeting by the party notifying the meeting. It must be unique for the party notifying the meeting. | IsoMax35Text - Optional 0..1 |
| IssuerMeetingIdentification | Identification assigned to the meeting by the issuer. It must be unique for the issuer. | IsoMax35Text - Optional 0..1 |
| MeetingDateAndTime | Date and time at which the meeting will take place. | IsoISODateTime - Required 1..1 |
| Type | Specifies the type of meeting for which instructions are sent. | MeetingType3Code - Required 1..1 |
| Classification | Classifies the type of meeting. | IMeetingTypeClassification1Choice - Optional 0..1 |
| Location | Place of the company meeting for the scheduled meeting date. | PostalAddress1 - Collection 0..5 |
FinancialInstrumentIdentification building block
Identifies the security for which the meeting is organised. Identification of a security. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% SecurityIdentification14 recursion level 0 with max 1
class SecurityIdentification14{
ISIN IsoISINIdentifier
Description IsoMax140Text
}
SecurityIdentification14 *-- "0..0" OtherIdentification1 : OtherIdentification
%% OtherIdentification1 recursion level 1 with max 1
class OtherIdentification1{
Identification IsoMax35Text
Suffix IsoMax16Text
}
OtherIdentification1 *-- "1..1" IIdentificationSource3Choice : Type
SecurityIdentification14 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| ISIN | International Securities Identification Number (ISIN). A numbering system designed by the United Nation’s International Organisation for Standardisation (ISO). The ISIN is composed of a 2-character prefix representing the country of issue, followed by the national security number (if one exists), and a check digit. Each country has a national numbering agency that assigns ISIN numbers for securities in that country. | IsoISINIdentifier - Optional 0..1 |
| OtherIdentification | Identification of a security by proprietary or domestic identification scheme. | OtherIdentification1 - Unknown 0..0 |
| Description | Textual description of a security instrument. | IsoMax140Text - Optional 0..1 |
InstructedPosition building block
Identifies the account and instructed positions for which the instruction cancellation request applies. A safekeeping account is an account on which a securities entry is made. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% SafekeepingAccount6 recursion level 0 with max 1
class SafekeepingAccount6{
AccountIdentification IsoMax35Text
}
SafekeepingAccount6 *-- "0..1" IPartyIdentification40Choice : AccountOwner
SafekeepingAccount6 *-- "0..1" SubAccount2 : SubAccountDetails
SafekeepingAccount6 *-- "1..10" HoldingBalance8 : InstructedBalance
SafekeepingAccount6 *-- "0..10" IPartyIdentification40Choice : RightsHolder
%% IPartyIdentification40Choice recursion level 1 with max 1
%% SubAccount2 recursion level 1 with max 1
class SubAccount2{
Identification IsoMax35Text
}
%% HoldingBalance8 recursion level 1 with max 1
class HoldingBalance8{
BalanceType SecuritiesEntryType2Code
}
HoldingBalance8 *-- "1..1" IUnitOrFaceAmountOrCode1Choice : Balance
HoldingBalance8 *-- "0..1" ISafekeepingPlaceFormat2Choice : SafekeepingPlace
%% IPartyIdentification40Choice recursion level 1 with max 1
SafekeepingAccount6 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| AccountIdentification | Unique and unambiguous identification for the account between the account owner and the account servicer. | IsoMax35Text - Required 1..1 |
| AccountOwner | Party that legally owns the account. | IPartyIdentification40Choice - Optional 0..1 |
| SubAccountDetails | Identification of a subaccount within the safekeeping account. | SubAccount2 - Optional 0..1 |
| InstructedBalance | Quantity of securities in the sub-balance. | HoldingBalance8 - Collection 1..10 |
| RightsHolder | Owner of the voting rights. | IPartyIdentification40Choice - Collection 0..10 |
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 MeetingInstructionCancellationRequestV05 implementation follows a specific implementaiton pattern. First of all, MeetingInstructionCancellationRequestV05 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, MeetingInstructionCancellationRequestV05Document implements IOuterDocument. Because MeetingInstructionCancellationRequestV05 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type MeetingInstructionCancellationRequestV05.
classDiagram
class IOuterRecord
MeetingInstructionCancellationRequestV05 --|> IOuterRecord : Implements
MeetingInstructionCancellationRequestV05Document --|> IOuterDocument~MeetingInstructionCancellationRequestV05~ : Implements
class IOuterDocument~MeetingInstructionCancellationRequestV05~ {
MeetingInstructionCancellationRequestV05 Message
}
Document wrapper for serialization
The only real purpose MeetingInstructionCancellationRequestV05Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:seev.005.001.05’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using MeetingInstructionCancellationRequestV05.ToDocument() method. The returned MeetingInstructionCancellationRequestV05Document value will serialize correctly according to ISO 20022 standards.
classDiagram
MeetingInstructionCancellationRequestV05Document *-- MeetingInstructionCancellationRequestV05 : 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:seev.005.001.05">
<MtgInstrCxlReq>
<PrvsRef>
<!-- PreviousReference inner content -->
</PrvsRef>
<MtgRef>
<!-- MeetingReference inner content -->
</MtgRef>
<FinInstrmId>
<!-- FinancialInstrumentIdentification inner content -->
</FinInstrmId>
<InstdPos>
<!-- InstructedPosition inner content -->
</InstdPos>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</MtgInstrCxlReq>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_xDAOKVtcEeSwKe7KuKvXhg"
nextVersions="_yXBbaayREemMosWmlQ33EA"
previousVersion="_TniBy9EwEd-BzquC8wXy7w_-914512760"
name="MeetingInstructionCancellationRequestV05"
definition="Scope
The MeetingInstructionCancellationRequest message is sent by the same party that sent the MeetingInstruction message. It is sent to request the cancellation of all instructions included in the original the MeetingInstruction message.
Usage
This message must be answered by a MeetingInstructionStatus message. Some instructions in the previously sent MeetingInstruction message may have already been executed and cannot be cancelled. This information should appear clearly in the status message.
This message definition is intended for use with the Business Application Header."
registrationStatus="Registered"
messageSet="_wRe70U2rEeG_I4xRYCA_7g"
xmlTag="MtgInstrCxlReq"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<constraint
xmi:id="_xDAOK1tcEeSwKe7KuKvXhg"
nextVersions="_yXBba6yREemMosWmlQ33EA"
previousVersion="_TnrLtNEwEd-BzquC8wXy7w_1355573798"
name="Cancellation3Guideline"
definition="It is recommended to cancel an instruction message by using PreviousReference only. It is recommended to avoid the repetition of optional building blocks, unless otherwise specified by market practise rules and or legislation. If any information is present in the optional building blocks, it must be identical to the information being present into the instruction message being cancelled."
registrationStatus="Provisionally Registered" />
<messageBuildingBlock
xmi:id="_xDAOL1tcEeSwKe7KuKvXhg"
nextVersions="_yXBbbayREemMosWmlQ33EA"
previousVersion="_TniBzdEwEd-BzquC8wXy7w_-1998274389"
name="PreviousReference"
definition="Identifies the instruction to be cancelled."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="PrvsRef"
complexType="_Q6l-Cdp-Ed-ak6NoX_4Aeg_1451391033" />
<messageBuildingBlock
xmi:id="_xDAOMVtcEeSwKe7KuKvXhg"
nextVersions="_yXBbb6yREemMosWmlQ33EA"
previousVersion="_TniBztEwEd-BzquC8wXy7w_452823918"
name="MeetingReference"
definition="Series of elements which allow to identify a meeting."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="MtgRef"
complexType="_uG79UVuPEeSmO6RkXg92Lg" />
<messageBuildingBlock
xmi:id="_xDAONVtcEeSwKe7KuKvXhg"
nextVersions="_yXBbcayREemMosWmlQ33EA"
previousVersion="_TnrLsdEwEd-BzquC8wXy7w_-1092424616"
name="FinancialInstrumentIdentification"
definition="Identifies the security for which the meeting is organised."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="FinInstrmId"
complexType="_TBAQ7dp-Ed-ak6NoX_4Aeg_896067631" />
<messageBuildingBlock
xmi:id="_xDAON1tcEeSwKe7KuKvXhg"
previousVersion="_TnrLstEwEd-BzquC8wXy7w_738498553"
name="InstructedPosition"
definition="Identifies the account and instructed positions for which the instruction cancellation request applies."
registrationStatus="Provisionally Registered"
minOccurs="0"
xmlTag="InstdPos"
complexType="_HjiCdVtiEeSwKe7KuKvXhg" />
<messageBuildingBlock
xmi:id="_prYCsVtoEeSwKe7KuKvXhg"
nextVersions="_yXBbdayREemMosWmlQ33EA"
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="seev"
messageFunctionality="005"
flavour="001"
version="05" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.