seev.004.001.02
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.
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
%% MeetingInstructionV02 recursion level 0 with max 0
MeetingInstructionV02 *-- "1..1" MessageIdentification1 : MeetingInstructionIdentification
MeetingInstructionV02 *-- "1..1" MeetingReference3 : MeetingReference
MeetingInstructionV02 *-- "1..1" IPartyIdentification9Choice : InstructingParty
MeetingInstructionV02 *-- "1..1" SecurityIdentification3 : SecurityIdentification
MeetingInstructionV02 *-- "1..1" Instruction1 : Instruction
Now, we will zero-in one-by-one on each of these building blocks.
MeetingInstructionIdentification building block
Identifies the meeting instruction 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 |
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 |
InstructingParty building block
Party notifying the instructions. 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 security 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 |
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
%% Instruction1 recursion level 0 with max 1
class Instruction1{
InstructionIdentification IsoMax35Text
RequestedExecutionDate IsoISODateTime
VoteExecutionConfirmation IsoYesNoIndicator
}
Instruction1 *-- "1..1" SafekeepingAccount3 : AccountDetails
Instruction1 *-- "0..1" Proxy2 : Proxy
Instruction1 *-- "0..1" VoteDetails1 : VoteDetails
Instruction1 *-- "0..0" IndividualPerson13 : MeetingAttendee
Instruction1 *-- "0..1" SpecificInstructionRequest1 : SpecificInstructionRequest
%% SafekeepingAccount3 recursion level 1 with max 1
class SafekeepingAccount3{
AccountIdentification IsoMax35Text
}
SafekeepingAccount3 *-- "0..1" IPartyIdentification9Choice : AccountOwner
SafekeepingAccount3 *-- "0..1" SubAccount2 : SubAccountDetails
SafekeepingAccount3 *-- "1..10" HoldingBalance4 : InstructedBalance
SafekeepingAccount3 *-- "0..10" IPartyIdentification9Choice : RightsHolder
%% Proxy2 recursion level 1 with max 1
class Proxy2{
ProxyType ProxyType2Code
}
Proxy2 *-- "0..1" IndividualPerson13 : PersonDetails
Proxy2 *-- "0..1" IVote1Choice : VoteInstructionForAgendaResolution
%% VoteDetails1 recursion level 1 with max 1
VoteDetails1 *-- "1..1" IVote1Choice : VoteInstructionForAgendaResolution
VoteDetails1 *-- "0..1" VoteInstructionForMeetingResolution1 : VoteInstructionForMeetingResolution
%% IndividualPerson13 recursion level 1 with max 1
class IndividualPerson13{
BirthName IsoMax35Text
GivenName IsoMax35Text
}
IndividualPerson13 *-- "0..1" PersonIdentification2 : Identification
IndividualPerson13 *-- "0..1" ILongPostalAddress2Choice : Address
IndividualPerson13 *-- "0..1" IPartyIdentification9Choice : EmployingParty
IndividualPerson13 *-- "1..1" AttendanceCard1 : AttendanceCardDetails
%% SpecificInstructionRequest1 recursion level 1 with max 1
class SpecificInstructionRequest1{
ParticipationRegistration IsoYesNoIndicator
BlockingSecurities IsoYesNoIndicator
SecuritiesRegistration IsoYesNoIndicator
}
Instruction1 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. | SafekeepingAccount3 - Required 1..1 |
| Proxy | Identification of the person appointed by the security holder as proxy. | Proxy2 - Optional 0..1 |
| VoteDetails | Specifies detailed voting instructions. | VoteDetails1 - Optional 0..1 |
| MeetingAttendee | Identification of the security holder who will attend and vote at the meeting in person and/or a person assigned by the security holder to attend the meeting without having any voting rights or taking any action. | IndividualPerson13 - Unknown 0..0 |
| SpecificInstructionRequest | Request to execute specific instructions, such as participation registration, securities registration or blocking of securities. | SpecificInstructionRequest1 - Optional 0..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the MeetingInstructionV02 implementation follows a specific implementaiton pattern. First of all, MeetingInstructionV02 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, MeetingInstructionV02Document implements IOuterDocument. Because MeetingInstructionV02 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type MeetingInstructionV02.
classDiagram
class IOuterRecord
MeetingInstructionV02 --|> IOuterRecord : Implements
MeetingInstructionV02Document --|> IOuterDocument~MeetingInstructionV02~ : Implements
class IOuterDocument~MeetingInstructionV02~ {
MeetingInstructionV02 Message
}
Document wrapper for serialization
The only real purpose MeetingInstructionV02Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:seev.004.001.02’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using MeetingInstructionV02.ToDocument() method. The returned MeetingInstructionV02Document value will serialize correctly according to ISO 20022 standards.
classDiagram
MeetingInstructionV02Document *-- MeetingInstructionV02 : 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.02">
<MtgInstr>
<MtgInstrId>
<!-- MeetingInstructionIdentification inner content -->
</MtgInstrId>
<MtgRef>
<!-- MeetingReference inner content -->
</MtgRef>
<InstgPty>
<!-- InstructingParty inner content -->
</InstgPty>
<SctyId>
<!-- SecurityIdentification inner content -->
</SctyId>
<Instr>
<!-- Instruction inner content -->
</Instr>
</MtgInstr>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_TqgdUtEwEd-BzquC8wXy7w_-118091241"
nextVersions="_Tqz_QtEwEd-BzquC8wXy7w_-2059690567"
name="MeetingInstructionV02"
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."
registrationStatus="Registered"
messageSet="_urpIICeJEeOCeO5e7islRQ"
xmlTag="MtgInstr"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_TqqOQNEwEd-BzquC8wXy7w_-118091210"
name="MeetingInstructionIdentification"
definition="Identifies the meeting instruction message."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="MtgInstrId"
complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
<messageBuildingBlock
xmi:id="_TqqOQdEwEd-BzquC8wXy7w_-118091239"
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="_TqqOQtEwEd-BzquC8wXy7w_-118091223"
name="InstructingParty"
definition="Party notifying the instructions."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="InstgPty"
complexType="_QRUXhtp-Ed-ak6NoX_4Aeg_967984948" />
<messageBuildingBlock
xmi:id="_TqqOQ9EwEd-BzquC8wXy7w_859115464"
name="SecurityIdentification"
definition="Identifies the security for which the meeting is organised."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="SctyId"
complexType="_QdiOk9p-Ed-ak6NoX_4Aeg_2006961788" />
<messageBuildingBlock
xmi:id="_TqqORNEwEd-BzquC8wXy7w_1179875106"
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="_RW6GmNp-Ed-ak6NoX_4Aeg_-1229563854" />
<messageDefinitionIdentifier
businessArea="seev"
messageFunctionality="004"
flavour="001"
version="02" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.