seev.006.001.02
Scope The Receiver of the MeetingInstruction or MeetingInstructionCancellationRequest sends the MeetingInstructionStatus message to the Sender of these messages. The message gives the status of a complete message or of one or more specific instructions within the message. Usage The MeetingInstructionStatus message is used for four purposes. First, it provides the status on the processing of a MeetingInstructionCancellationRequest message, ie, whether the request message is rejected or accepted. Second, it is used to provide a global processing or rejection status of a MeetingInstruction message. Third, it is used to provide a detailed processing or rejection status of a MeetingInstruction message, ie, for each instruction in the MeetingInstruction message the processing or rejection status is individually reported by using the InstructionIdentification element. This identification allows the receiver of the status message to link the status confirmation to its original instruction. The blocking of securities should be confirmed via an MT 508 (Intra-Position Advice). Fourth, it is used as a reminder to request voting instructions. This is done by indicating NONREF in the Identification element of the InstructionIdentification component and by using the status code NotReceived in the ProcessingStatus.
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 %% MeetingInstructionStatusV02 recursion level 0 with max 0 MeetingInstructionStatusV02 *-- "1..1" MessageIdentification1 : MeetingInstructionStatusIdentification MeetingInstructionStatusV02 *-- "1..1" MessageIdentification : InstructionIdentification MeetingInstructionStatusV02 *-- "1..1" MessageIdentification : InstructionCancellationIdentification MeetingInstructionStatusV02 *-- "1..1" MeetingReference3 : MeetingReference MeetingInstructionStatusV02 *-- "1..1" IPartyIdentification9Choice : ReportingParty MeetingInstructionStatusV02 *-- "1..1" SecurityIdentification3 : SecurityIdentification MeetingInstructionStatusV02 *-- "1..1" IInstructionStatus1Choice : InstructionStatus MeetingInstructionStatusV02 *-- "1..1" ICancellationStatus1Choice : CancellationStatus
Now, we will zero-in one-by-one on each of these building blocks.
MeetingInstructionStatusIdentification building block
Identifies the meeting instruction status message. Identifies a message by a unique identifier and the date and time when the message was created by the sender. For comparison, see the ISO20022 official specification
classDiagram direction tb %% MessageIdentification1 recursion level 0 with max 1 class MessageIdentification1{ Identification IsoMax35Text CreationDateTime IsoISODateTime }
MessageIdentification1 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
Identification | Identification of the message. | IsoMax35Text - Required 1..1 |
CreationDateTime | Date of creation of the message. | IsoISODateTime - Required 1..1 |
InstructionIdentification building block
Identifies the meeting instruction message for which the status is provided. 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 |
InstructionCancellationIdentification building block
Identifies the meeting instruction cancellation request message for which the status is provided. 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. Elements which allow to identify a meeting. For comparison, see the ISO20022 official specification
classDiagram direction tb %% MeetingReference3 recursion level 0 with max 1 class MeetingReference3{ MeetingIdentification IsoMax35Text IssuerMeetingIdentification IsoMax35Text MeetingDateAndTime IsoISODateTime Type MeetingType2Code Classification MeetingTypeClassification1Code ExtendedClassification IsoExtended350Code } MeetingReference3 *-- "0..5" PostalAddress1 : Location %% 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 }
MeetingReference3 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
MeetingIdentification | Identification assigned to a 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 a 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. | MeetingType2Code - Required 1..1 |
Classification | Classifies the type of meeting. | MeetingTypeClassification1Code - Optional 0..1 |
ExtendedClassification | This code can be used in case another meeting classifications is required. | IsoExtended350Code - Optional 0..1 |
Location | Place of the company meeting for the scheduled meeting date. | PostalAddress1 - Collection 0..5 |
ReportingParty building block
Party reporting the status. Identification of a party. For comparison, see the ISO20022 official specification
classDiagram direction tb %% IPartyIdentification9Choice recursion level 0 with max 1
PartyIdentification9Choice members
Member name | Description | Data Type / Multiplicity |
---|
SecurityIdentification building block
Identifies the securities for which the meeting is organised. Identification of a security by its symbol. For comparison, see the ISO20022 official specification
classDiagram direction tb %% SecurityIdentification3 recursion level 0 with max 1 class SecurityIdentification3{ ISIN IsoISINIdentifier TickerSymbol IsoTickerIdentifier CUSIP IsoCUSIPIdentifier SEDOL IsoSEDOLIdentifier QUICK IsoQUICKIdentifier } SecurityIdentification3 *-- "0..1" AlternateFinancialInstrumentIdentification1 : OtherIdentification %% AlternateFinancialInstrumentIdentification1 recursion level 1 with max 1 class AlternateFinancialInstrumentIdentification1{ DomesticIdentificationSource CountryCode ProprietaryIdentificationSource IsoMax16Text Identification IsoMax35Text }
SecurityIdentification3 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 - Required 1..1 |
TickerSymbol | Letters that identify a stock traded on a stock exchange. The Ticker Symbol is a short and convenient way of identifying a stock, eg, RTR.L for Reuters quoted in London. | IsoTickerIdentifier - Optional 0..1 |
CUSIP | Committee on Uniform Securities and Identification Procedures (CUSIP). The standards body that created and maintains the securities classification system in the US. The CUSIP is composed of a 9-character number that uniquely identifies a particular security. Non-US securities have a similar number called the CINS number. | IsoCUSIPIdentifier - Optional 0..1 |
SEDOL | Stock Exchange Daily Official List (SEDOL) number. A code used by the London Stock Exchange to identify foreign stocks, especially those that aren’t actively traded in the US and don’t have a CUSIP number. | IsoSEDOLIdentifier - Optional 0..1 |
QUICK | Identifier of a security assigned by the Japanese QUICK identification scheme for financial instruments. | IsoQUICKIdentifier - Optional 0..1 |
OtherIdentification | Proprietary identification of a security assigned by an institution or organisation. | AlternateFinancialInstrumentIdentification1 - Optional 0..1 |
InstructionStatus building block
Status applying to the instruction request received. The instruction is identified by the InstructionIdentification. Status applying to the instruction request received. For comparison, see the ISO20022 official specification
classDiagram direction tb %% IInstructionStatus1Choice recursion level 0 with max 1
InstructionStatus1Choice members
Member name | Description | Data Type / Multiplicity |
---|
CancellationStatus building block
Status applying to the instruction cancellation request received. The instruction cancellation is identified by the InstructionCancellationIdentification. Status applying to the instruction cancellation request received. For comparison, see the ISO20022 official specification
classDiagram direction tb %% ICancellationStatus1Choice recursion level 0 with max 1
CancellationStatus1Choice members
Member name | Description | Data Type / Multiplicity |
---|
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the MeetingInstructionStatusV02 implementation follows a specific implementaiton pattern. First of all, MeetingInstructionStatusV02 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, MeetingInstructionStatusV02Document implements IOuterDocument. Because MeetingInstructionStatusV02 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type MeetingInstructionStatusV02.
classDiagram class IOuterRecord MeetingInstructionStatusV02 --|> IOuterRecord : Implements MeetingInstructionStatusV02Document --|> IOuterDocument~MeetingInstructionStatusV02~ : Implements class IOuterDocument~MeetingInstructionStatusV02~ { MeetingInstructionStatusV02 Message }
Document wrapper for serialization
The only real purpose MeetingInstructionStatusV02Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:seev.006.001.02’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using MeetingInstructionStatusV02.ToDocument() method. The returned MeetingInstructionStatusV02Document value will serialize correctly according to ISO 20022 standards.
classDiagram MeetingInstructionStatusV02Document *-- MeetingInstructionStatusV02 : 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.006.001.02">
<MtgInstrSts>
<MtgInstrStsId>
<!-- MeetingInstructionStatusIdentification inner content -->
</MtgInstrStsId>
<InstrId>
<!-- InstructionIdentification inner content -->
</InstrId>
<InstrCxlId>
<!-- InstructionCancellationIdentification inner content -->
</InstrCxlId>
<MtgRef>
<!-- MeetingReference inner content -->
</MtgRef>
<RptgPty>
<!-- ReportingParty inner content -->
</RptgPty>
<SctyId>
<!-- SecurityIdentification inner content -->
</SctyId>
<InstrSts>
<!-- InstructionStatus inner content -->
</InstrSts>
<CxlSts>
<!-- CancellationStatus inner content -->
</CxlSts>
</MtgInstrSts>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_Tpw2YNEwEd-BzquC8wXy7w_322491691"
nextVersions="_TqDxVdEwEd-BzquC8wXy7w_1419808465"
name="MeetingInstructionStatusV02"
definition="Scope
The Receiver of the MeetingInstruction or MeetingInstructionCancellationRequest sends the MeetingInstructionStatus message to the Sender of these messages.
The message gives the status of a complete message or of one or more specific instructions within the message.
Usage
The MeetingInstructionStatus message is used for four purposes.
First, it provides the status on the processing of a MeetingInstructionCancellationRequest message, ie, whether the request message is rejected or accepted.
Second, it is used to provide a global processing or rejection status of a MeetingInstruction message.
Third, it is used to provide a detailed processing or rejection status of a MeetingInstruction message, ie, for each instruction in the MeetingInstruction message the processing or rejection status is individually reported by using the InstructionIdentification element. This identification allows the receiver of the status message to link the status confirmation to its original instruction.
The blocking of securities should be confirmed via an MT 508 (Intra-Position Advice).
Fourth, it is used as a reminder to request voting instructions. This is done by indicating NONREF in the Identification element of the InstructionIdentification component and by using the status code NotReceived in the ProcessingStatus."
registrationStatus="Registered"
messageSet="_urpIICeJEeOCeO5e7islRQ"
xmlTag="MtgInstrSts"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<constraint
xmi:id="_Tp6nYtEwEd-BzquC8wXy7w_657172379"
name="Status1Rule"
definition="If InstructionIdentification is present, then InstructionStatus must be present."
registrationStatus="Provisionally Registered" />
<constraint
xmi:id="_Tp6nZdEwEd-BzquC8wXy7w_996104107"
name="Status2Rule"
definition="If InstructionCancellationIdentification is present, then CancellationStatus must be present."
registrationStatus="Provisionally Registered" />
<constraint
xmi:id="_Tp6nbtEwEd-BzquC8wXy7w_1509541562"
name="Reminder1Rule"
definition="If InstructionIdentification/Identification is "NONREF", then InstructionStatus/GlobalInstructionStatus/ProcessingStatus/Status must be NOIN."
registrationStatus="Provisionally Registered" />
<xors
xmi:id="_Tp6naNEwEd-BzquC8wXy7w_1593622368"
name="InstructionOrInstructionCancellationIdentificationRule"
definition="Either the InstructionIdentification or the InstructionCancellationIdentification must be present, but not both."
registrationStatus="Provisionally Registered"
impactedMessageBuildingBlocks="_Tpw2YtEwEd-BzquC8wXy7w_2026535768 _Tpw2Y9EwEd-BzquC8wXy7w_-1459248718" />
<xors
xmi:id="_Tp6na9EwEd-BzquC8wXy7w_1911198421"
name="InstructionOrCancellationStatusRule"
definition="Either the InstructionStatus or the CancellationStatus must be present, but not both."
registrationStatus="Provisionally Registered"
impactedMessageBuildingBlocks="_Tp6nYNEwEd-BzquC8wXy7w_-1918238262 _Tp6nYdEwEd-BzquC8wXy7w_-1891306191" />
<messageBuildingBlock
xmi:id="_Tpw2YdEwEd-BzquC8wXy7w_322491753"
name="MeetingInstructionStatusIdentification"
definition="Identifies the meeting instruction status message."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="MtgInstrStsId"
complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
<messageBuildingBlock
xmi:id="_Tpw2YtEwEd-BzquC8wXy7w_2026535768"
name="InstructionIdentification"
definition="Identifies the meeting instruction message for which the status is provided."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="InstrId"
complexType="_Q6l-Cdp-Ed-ak6NoX_4Aeg_1451391033" />
<messageBuildingBlock
xmi:id="_Tpw2Y9EwEd-BzquC8wXy7w_-1459248718"
name="InstructionCancellationIdentification"
definition="Identifies the meeting instruction cancellation request message for which the status is provided."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="InstrCxlId"
complexType="_Q6l-Cdp-Ed-ak6NoX_4Aeg_1451391033" />
<messageBuildingBlock
xmi:id="_Tpw2ZNEwEd-BzquC8wXy7w_322491723"
name="MeetingReference"
definition="Series of elements which allow to identify a meeting."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="MtgRef"
complexType="_TlgsINp-Ed-ak6NoX_4Aeg_-1687570906" />
<messageBuildingBlock
xmi:id="_Tpw2ZdEwEd-BzquC8wXy7w_322491769"
name="ReportingParty"
definition="Party reporting the status."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="RptgPty"
complexType="_QRUXhtp-Ed-ak6NoX_4Aeg_967984948" />
<messageBuildingBlock
xmi:id="_Tpw2ZtEwEd-BzquC8wXy7w_322491740"
name="SecurityIdentification"
definition="Identifies the securities for which the meeting is organised."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="SctyId"
complexType="_QdiOk9p-Ed-ak6NoX_4Aeg_2006961788" />
<messageBuildingBlock
xmi:id="_Tp6nYNEwEd-BzquC8wXy7w_-1918238262"
name="InstructionStatus"
definition="Status applying to the instruction request received. The instruction is identified by the InstructionIdentification."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="InstrSts"
complexType="_RWnLp9p-Ed-ak6NoX_4Aeg_1278003297" />
<messageBuildingBlock
xmi:id="_Tp6nYdEwEd-BzquC8wXy7w_-1891306191"
name="CancellationStatus"
definition="Status applying to the instruction cancellation request received. The instruction cancellation is identified by the InstructionCancellationIdentification."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="CxlSts"
complexType="_RVa41dp-Ed-ak6NoX_4Aeg_-538392841" />
<messageDefinitionIdentifier
businessArea="seev"
messageFunctionality="006"
flavour="001"
version="02" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.