seev.006.001.04
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, for example, 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, for example, 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
%% MeetingInstructionStatusV04 recursion level 0 with max 0
MeetingInstructionStatusV04 *-- "1..1" MessageIdentification1 : Identification
MeetingInstructionStatusV04 *-- "1..1" IInstructionType1Choice : InstructionType
MeetingInstructionStatusV04 *-- "1..1" MeetingReference4 : MeetingReference
MeetingInstructionStatusV04 *-- "1..1" IPartyIdentification9Choice : ReportingParty
MeetingInstructionStatusV04 *-- "1..1" SecurityIdentification11 : SecurityIdentification
MeetingInstructionStatusV04 *-- "1..1" IInstructionTypeStatus1Choice : InstructionTypeStatus
MeetingInstructionStatusV04 *-- "0..1" Extension2 : Extension
Now, we will zero-in one-by-one on each of these building blocks.
Identification 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 |
InstructionType building block
Type of instruction. Type of instruction. For comparison, see the ISO20022 official specification
classDiagram direction tb %% IInstructionType1Choice recursion level 0 with max 1
InstructionType1Choice members
| Member name | Description | Data Type / Multiplicity |
|---|
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
%% MeetingReference4 recursion level 0 with max 1
class MeetingReference4{
MeetingIdentification IsoMax35Text
IssuerMeetingIdentification IsoMax35Text
MeetingDateAndTime IsoISODateTime
Type MeetingType2Code
}
MeetingReference4 *-- "0..1" IMeetingTypeClassification1Choice : Classification
MeetingReference4 *-- "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
}
MeetingReference4 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. | IMeetingTypeClassification1Choice - 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. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% SecurityIdentification11 recursion level 0 with max 1
class SecurityIdentification11{
Description IsoMax140Text
}
SecurityIdentification11 *-- "1..1" ISecurityIdentification11Choice : Identification
%% ISecurityIdentification11Choice recursion level 1 with max 1
SecurityIdentification11 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Identification | Identification of a security. | ISecurityIdentification11Choice - Required 1..1 |
| Description | Textual description of a security instrument. | IsoMax140Text - Optional 0..1 |
InstructionTypeStatus building block
Type of instruction status. Choice of instruction type status. For comparison, see the ISO20022 official specification
classDiagram direction tb %% IInstructionTypeStatus1Choice recursion level 0 with max 1
InstructionTypeStatus1Choice members
| Member name | Description | Data Type / Multiplicity |
|---|
Extension 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
%% Extension2 recursion level 0 with max 1
class Extension2{
PlaceAndName IsoMax350Text
}
Extension2 *-- "1..1" ExtensionEnvelope1 : ExtensionEnvelope
%% ExtensionEnvelope1 recursion level 1 with max 1
ExtensionEnvelope1 *-- "1..1" ExtensionContents1 : ExtensionContents
Extension2 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| PlaceAndName | Name qualifying the information provided in the Text field, and place where this information should be inserted. | IsoMax350Text - Optional 0..1 |
| ExtensionEnvelope | Technical element wrapping the extension. | ExtensionEnvelope1 - Required 1..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the MeetingInstructionStatusV04 implementation follows a specific implementaiton pattern. First of all, MeetingInstructionStatusV04 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, MeetingInstructionStatusV04Document implements IOuterDocument. Because MeetingInstructionStatusV04 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type MeetingInstructionStatusV04.
classDiagram
class IOuterRecord
MeetingInstructionStatusV04 --|> IOuterRecord : Implements
MeetingInstructionStatusV04Document --|> IOuterDocument~MeetingInstructionStatusV04~ : Implements
class IOuterDocument~MeetingInstructionStatusV04~ {
MeetingInstructionStatusV04 Message
}
Document wrapper for serialization
The only real purpose MeetingInstructionStatusV04Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:seev.006.001.04’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using MeetingInstructionStatusV04.ToDocument() method. The returned MeetingInstructionStatusV04Document value will serialize correctly according to ISO 20022 standards.
classDiagram
MeetingInstructionStatusV04Document *-- MeetingInstructionStatusV04 : 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.04">
<MtgInstrSts>
<Id>
<!-- Identification inner content -->
</Id>
<InstrTp>
<!-- InstructionType inner content -->
</InstrTp>
<MtgRef>
<!-- MeetingReference inner content -->
</MtgRef>
<RptgPty>
<!-- ReportingParty inner content -->
</RptgPty>
<SctyId>
<!-- SecurityIdentification inner content -->
</SctyId>
<InstrTpSts>
<!-- InstructionTypeStatus inner content -->
</InstrTpSts>
<Xtnsn>
<!-- Extension inner content -->
</Xtnsn>
</MtgInstrSts>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_TqXTUNEwEd-BzquC8wXy7w_99042676"
nextVersions="_xDAOO1tcEeSwKe7KuKvXhg"
previousVersion="_TqDxVdEwEd-BzquC8wXy7w_1419808465"
name="MeetingInstructionStatusV04"
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, for example, 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, for example, 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="_TqgdQNEwEd-BzquC8wXy7w_73824110"
nextVersions="_xDAOPVtcEeSwKe7KuKvXhg"
name="Status1Rule"
definition="If InstructionType/InstructionIdentification is present, then InstructionTypeStatus/InstructionStatus must be present."
registrationStatus="Provisionally Registered"
expression="<RuleDefinition xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><ComplexRule xsi:type="ComplexRule"><mustBe><connector>AND</connector><BooleanRule xsi:type="Presence"><leftOperand>/InstructionTypeStatus/InstructionStatus</leftOperand></BooleanRule></mustBe><onCondition><connector>AND</connector><BooleanRule xsi:type="Presence"><leftOperand>/InstructionType/InstructionIdentification</leftOperand></BooleanRule></onCondition></ComplexRule></RuleDefinition>
" />
<constraint
xmi:id="_TqgdQ9EwEd-BzquC8wXy7w_542631525"
nextVersions="_xDAOP1tcEeSwKe7KuKvXhg"
name="Status2Rule"
definition="If InstructionType/InstructionCancellationIdentification is present, then InstructionTypeStatus/CancellationStatus must be present."
registrationStatus="Provisionally Registered"
expression="<RuleDefinition xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><ComplexRule xsi:type="ComplexRule"><mustBe><connector>AND</connector><BooleanRule xsi:type="Presence"><leftOperand>/InstructionTypeStatus/CancellationStatus</leftOperand></BooleanRule></mustBe><onCondition><connector>AND</connector><BooleanRule xsi:type="Presence"><leftOperand>/InstructionType/InstructionCancellationIdentification</leftOperand></BooleanRule></onCondition></ComplexRule></RuleDefinition>
" />
<constraint
xmi:id="_TqgdRtEwEd-BzquC8wXy7w_-454440828"
nextVersions="_xDAOQVtcEeSwKe7KuKvXhg"
name="Reminder1Rule"
definition="If InstructionType/InstructionIdentification/Identification is "NONREF", then InstructionTypeStatus/InstructionStatus/GlobalInstructionStatus/ProcessingStatus/Status must be NOIN."
registrationStatus="Provisionally Registered"
expression="<RuleDefinition xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><ComplexRule xsi:type="ComplexRule"><mustBe><connector>AND</connector><BooleanRule xsi:type="EqualToValue"><leftOperand>/InstructionTypeStatus/InstructionStatus/GlobalInstructionStatus/ProcessingStatus/Status</leftOperand><rightOperand>NotReceived</rightOperand></BooleanRule></mustBe><onCondition><connector>AND</connector><BooleanRule xsi:type="EqualToValue"><leftOperand>/InstructionType/InstructionIdentification/Identification</leftOperand><rightOperand>NONREF</rightOperand></BooleanRule></onCondition></ComplexRule></RuleDefinition>
" />
<messageBuildingBlock
xmi:id="_TqXTUdEwEd-BzquC8wXy7w_-693693241"
name="Identification"
definition="Identifies the meeting instruction status message."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Id"
complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
<messageBuildingBlock
xmi:id="_TqXTUtEwEd-BzquC8wXy7w_-28327531"
nextVersions="_xDAORVtcEeSwKe7KuKvXhg"
name="InstructionType"
definition="Type of instruction."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="InstrTp"
complexType="_RCWL1Np-Ed-ak6NoX_4Aeg_869239445" />
<messageBuildingBlock
xmi:id="_TqXTU9EwEd-BzquC8wXy7w_-1403252543"
nextVersions="_xDAOR1tcEeSwKe7KuKvXhg"
name="MeetingReference"
definition="Series of elements which allow to identify a meeting."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="MtgRef"
complexType="_Tj3tZtp-Ed-ak6NoX_4Aeg_-658253867" />
<messageBuildingBlock
xmi:id="_TqXTVNEwEd-BzquC8wXy7w_-2038284389"
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="_TqXTVdEwEd-BzquC8wXy7w_-363218248"
nextVersions="_xDAOS1tcEeSwKe7KuKvXhg"
name="SecurityIdentification"
definition="Identifies the securities for which the meeting is organised."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="SctyId"
complexType="_TBKB89p-Ed-ak6NoX_4Aeg_-524266634" />
<messageBuildingBlock
xmi:id="_TqXTVtEwEd-BzquC8wXy7w_1595413206"
nextVersions="_xDAOTVtcEeSwKe7KuKvXhg"
name="InstructionTypeStatus"
definition="Type of instruction status."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="InstrTpSts"
complexType="_RCWL19p-Ed-ak6NoX_4Aeg_1310681941" />
<messageBuildingBlock
xmi:id="_TqXTV9EwEd-BzquC8wXy7w_510788685"
name="Extension"
definition="Additional information that can not be captured in the structured fields and/or any other specific block."
registrationStatus="Provisionally Registered"
minOccurs="0"
xmlTag="Xtnsn"
complexType="_QzJSNdp-Ed-ak6NoX_4Aeg_251191216" />
<messageDefinitionIdentifier
businessArea="seev"
messageFunctionality="006"
flavour="001"
version="04" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.