seev.004.001.05
Scope A party holding the right to vote sends the MeetingInstruction message to an intermediary, the issuer or its agent to request the receiving party to act upon one or several instructions. Usage The MeetingInstruction message is used to register for a shareholders meeting, request blocking or registration of securities. It is used to assign a proxy, to specify the names of meeting attendees and to relay vote instructions per resolution electronically. The MeetingInstruction message may only be sent for one security, though several safekeeping places may be specified. Once the message is sent, it cannot be modified. It must be cancelled by a MeetingInstructionCancellationRequest. Only after receipt of a confirmed cancelled status via the MeetingInstructionStatus message, a new MeetingInstruction message can be sent. 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
%% MeetingInstructionV05 recursion level 0 with max 0
MeetingInstructionV05 *-- "1..1" MeetingReference7 : MeetingReference
MeetingInstructionV05 *-- "1..1" SecurityIdentification14 : FinancialInstrumentIdentification
MeetingInstructionV05 *-- "1..1" Instruction3 : Instruction
MeetingInstructionV05 *-- "0..1" SupplementaryData1 : SupplementaryData
Now, we will zero-in one-by-one on each of these building blocks.
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 |
Instruction building block
Identifies the position of the instructing party and the action that they want to take. Provides information on the instruction. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% Instruction3 recursion level 0 with max 1
class Instruction3{
InstructionIdentification IsoMax35Text
RequestedExecutionDate IsoISODateTime
VoteExecutionConfirmation IsoYesNoIndicator
}
Instruction3 *-- "1..1" SafekeepingAccount6 : AccountDetails
Instruction3 *-- "0..1" Proxy6 : Proxy
Instruction3 *-- "0..1" VoteDetails3 : VoteDetails
Instruction3 *-- "0..0" IndividualPerson26 : MeetingAttendee
Instruction3 *-- "0..1" SpecificInstructionRequest1 : SpecificInstructionRequest
%% SafekeepingAccount6 recursion level 1 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
%% Proxy6 recursion level 1 with max 1
class Proxy6{
ProxyType ProxyType2Code
}
Proxy6 *-- "0..1" IndividualPerson26 : PersonDetails
Proxy6 *-- "0..1" IVote3Choice : VoteInstructionForAgendaResolution
%% VoteDetails3 recursion level 1 with max 1
VoteDetails3 *-- "1..1" IVote3Choice : VoteInstructionForAgendaResolution
VoteDetails3 *-- "0..1" IVoteInstructionForMeetingResolution2Choice : VoteInstructionForMeetingResolution
%% IndividualPerson26 recursion level 1 with max 1
class IndividualPerson26{
BirthName IsoMax35Text
GivenName IsoMax35Text
}
IndividualPerson26 *-- "0..1" PersonIdentification6 : Identification
IndividualPerson26 *-- "0..1" ILongPostalAddress2Choice : Address
IndividualPerson26 *-- "0..1" IPartyIdentification40Choice : EmployingParty
IndividualPerson26 *-- "1..1" AttendanceCard2 : AttendanceCardDetails
%% SpecificInstructionRequest1 recursion level 1 with max 1
class SpecificInstructionRequest1{
ParticipationRegistration IsoYesNoIndicator
BlockingSecurities IsoYesNoIndicator
SecuritiesRegistration IsoYesNoIndicator
}
Instruction3 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| InstructionIdentification | Identifies the detailed instruction. | IsoMax35Text - Required 1..1 |
| RequestedExecutionDate | Date at which the instruction must be executed. | IsoISODateTime - Optional 0..1 |
| VoteExecutionConfirmation | Indicates that a vote execution confirmation is requested. | IsoYesNoIndicator - Required 1..1 |
| AccountDetails | Identification of the securities account. | SafekeepingAccount6 - Required 1..1 |
| Proxy | Identification of the person appointed by the security holder as proxy. | Proxy6 - Optional 0..1 |
| VoteDetails | Specifies detailed voting instructions. | VoteDetails3 - Optional 0..1 |
| MeetingAttendee | Identification of the security holder who will attend and vote at the meeting in person and/or the person assigned by the security holder to attend the meeting without having any voting rights or taking any action. | IndividualPerson26 - Unknown 0..0 |
| SpecificInstructionRequest | Request to execute specific instructions, such as participation registration, securities registration or blocking of securities. | SpecificInstructionRequest1 - Optional 0..1 |
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 MeetingInstructionV05 implementation follows a specific implementaiton pattern. First of all, MeetingInstructionV05 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, MeetingInstructionV05Document implements IOuterDocument. Because MeetingInstructionV05 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type MeetingInstructionV05.
classDiagram
class IOuterRecord
MeetingInstructionV05 --|> IOuterRecord : Implements
MeetingInstructionV05Document --|> IOuterDocument~MeetingInstructionV05~ : Implements
class IOuterDocument~MeetingInstructionV05~ {
MeetingInstructionV05 Message
}
Document wrapper for serialization
The only real purpose MeetingInstructionV05Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:seev.004.001.05’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using MeetingInstructionV05.ToDocument() method. The returned MeetingInstructionV05Document value will serialize correctly according to ISO 20022 standards.
classDiagram
MeetingInstructionV05Document *-- MeetingInstructionV05 : 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.004.001.05">
<MtgInstr>
<MtgRef>
<!-- MeetingReference inner content -->
</MtgRef>
<FinInstrmId>
<!-- FinancialInstrumentIdentification inner content -->
</FinInstrmId>
<Instr>
<!-- Instruction inner content -->
</Instr>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</MtgInstr>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_xDAOUVtcEeSwKe7KuKvXhg"
nextVersions="_yXBbiayREemMosWmlQ33EA"
previousVersion="_Tq9JOdEwEd-BzquC8wXy7w_-1580879636"
name="MeetingInstructionV05"
definition="Scope
A party holding the right to vote sends the MeetingInstruction message to an intermediary, the issuer or its agent to request the receiving party to act upon one or several instructions.
Usage
The MeetingInstruction message is used to register for a shareholders meeting, request blocking or registration of securities. It is used to assign a proxy, to specify the names of meeting attendees and to relay vote instructions per resolution electronically.
The MeetingInstruction message may only be sent for one security, though several safekeeping places may be specified.
Once the message is sent, it cannot be modified. It must be cancelled by a MeetingInstructionCancellationRequest. Only after receipt of a confirmed cancelled status via the MeetingInstructionStatus message, a new MeetingInstruction message can be sent.
This message definition is intended for use with the Business Application Header."
registrationStatus="Registered"
messageSet="_wRe70U2rEeG_I4xRYCA_7g"
xmlTag="MtgInstr"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_xDAOVVtcEeSwKe7KuKvXhg"
nextVersions="_yXBbi6yREemMosWmlQ33EA"
previousVersion="_Tq9JO9EwEd-BzquC8wXy7w_668851111"
name="MeetingReference"
definition="Series of elements which allow to identify a meeting."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="MtgRef"
complexType="_uG79UVuPEeSmO6RkXg92Lg" />
<messageBuildingBlock
xmi:id="_xDAOWVtcEeSwKe7KuKvXhg"
nextVersions="_yXBbjayREemMosWmlQ33EA"
previousVersion="_TrG6MNEwEd-BzquC8wXy7w_2100528158"
name="FinancialInstrumentIdentification"
definition="Identifies the security for which the meeting is organised."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="FinInstrmId"
complexType="_TBAQ7dp-Ed-ak6NoX_4Aeg_896067631" />
<messageBuildingBlock
xmi:id="_xDAOW1tcEeSwKe7KuKvXhg"
nextVersions="_yXBbj6yREemMosWmlQ33EA"
previousVersion="_TrG6MdEwEd-BzquC8wXy7w_-1116418800"
name="Instruction"
definition="Identifies the position of the instructing party and the action that they want to take."
registrationStatus="Provisionally Registered"
minOccurs="1"
xmlTag="Instr"
complexType="_HGObUVtiEeSwKe7KuKvXhg" />
<messageBuildingBlock
xmi:id="_vE2o0VtoEeSwKe7KuKvXhg"
nextVersions="_yXBbkayREemMosWmlQ33EA"
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="004"
flavour="001"
version="05" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.