seev.004.001.06
Scope The MeetingInstruction message is sent by a party holding the right to vote 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 vote, require attendance to a meeting, request registration of securities and assign a proxy. One of multiple instructions can be carried within the same message. 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
%% MeetingInstructionV06 recursion level 0 with max 0
MeetingInstructionV06 *-- "1..1" MeetingReference8 : MeetingReference
MeetingInstructionV06 *-- "1..1" SecurityIdentification19 : FinancialInstrumentIdentification
MeetingInstructionV06 *-- "1..1" Instruction4 : Instruction
MeetingInstructionV06 *-- "0..1" SupplementaryData1 : SupplementaryData
Now, we will zero-in one-by-one on each of these building blocks.
MeetingReference building block
Set of elements that allow to identify unambiguously a meeting. Identification of a meeting. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% MeetingReference8 recursion level 0 with max 1
class MeetingReference8{
MeetingIdentification IsoMax35Text
IssuerMeetingIdentification IsoMax35Text
MeetingDateAndTime IsoISODateTime
Type MeetingType4Code
}
MeetingReference8 *-- "0..1" IMeetingTypeClassification2Choice : Classification
MeetingReference8 *-- "0..5" PostalAddress1 : Location
MeetingReference8 *-- "0..1" IPartyIdentification129Choice : Issuer
%% IMeetingTypeClassification2Choice 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
}
%% IPartyIdentification129Choice recursion level 1 with max 1
MeetingReference8 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| MeetingIdentification | Identification assigned to the general meeting by the party that provides the meeting notification. It must be unique to the party providing the notification. | 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 | Type of meeting for which instructions are sent. | MeetingType4Code - Required 1..1 |
| Classification | Classification type of the meeting. | IMeetingTypeClassification2Choice - Optional 0..1 |
| Location | Place of the company meeting for the scheduled meeting date. | PostalAddress1 - Collection 0..5 |
| Issuer | Specifies the institution that is the issuer of the security to which the meeting applies. | IPartyIdentification129Choice - Optional 0..1 |
FinancialInstrumentIdentification building block
Security for which the meeting is organised. Identification of a security. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% SecurityIdentification19 recursion level 0 with max 1
class SecurityIdentification19{
ISIN IsoISINOct2015Identifier
Description IsoMax140Text
}
SecurityIdentification19 *-- "0..0" OtherIdentification1 : OtherIdentification
%% OtherIdentification1 recursion level 1 with max 1
class OtherIdentification1{
Identification IsoMax35Text
Suffix IsoMax16Text
}
OtherIdentification1 *-- "1..1" IIdentificationSource3Choice : Type
SecurityIdentification19 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. | IsoISINOct2015Identifier - 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 it wants to take. Information about a meeting vote instruction. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% Instruction4 recursion level 0 with max 1
class Instruction4{
SingleInstructionIdentification IsoMax35Text
RequestedExecutionDate IsoISODateTime
VoteExecutionConfirmation IsoYesNoIndicator
}
Instruction4 *-- "1..1" SafekeepingAccount9 : AccountDetails
Instruction4 *-- "0..1" Proxy7 : Proxy
Instruction4 *-- "0..1" VoteDetails4 : VoteDetails
Instruction4 *-- "0..0" IndividualPerson39 : MeetingAttendee
Instruction4 *-- "0..1" SpecificInstructionRequest2 : SpecificInstructionRequest
%% SafekeepingAccount9 recursion level 1 with max 1
class SafekeepingAccount9{
AccountIdentification IsoMax35Text
SubAccountIdentification IsoMax35Text
}
SafekeepingAccount9 *-- "0..1" IPartyIdentification228Choice : AccountOwner
SafekeepingAccount9 *-- "1..15" HoldingBalance10 : InstructedBalance
SafekeepingAccount9 *-- "0..10" IPartyIdentification227Choice : RightsHolder
%% Proxy7 recursion level 1 with max 1
class Proxy7{
ProxyType ProxyType2Code
}
Proxy7 *-- "0..1" IndividualPerson39 : PersonDetails
Proxy7 *-- "0..1" IVote4Choice : VoteInstructionForAgendaResolution
%% VoteDetails4 recursion level 1 with max 1
VoteDetails4 *-- "1..1" IVote13Choice : VoteInstructionForAgendaResolution
VoteDetails4 *-- "0..1" IVoteInstructionForMeetingResolution3Choice : VoteInstructionForMeetingResolution
%% IndividualPerson39 recursion level 1 with max 1
IndividualPerson39 *-- "0..1" IPartyIdentification223Choice : PreassignedProxy
IndividualPerson39 *-- "0..1" IPartyIdentification129Choice : EmployingParty
IndividualPerson39 *-- "1..1" AttendanceCard2 : AttendanceCardDetails
%% SpecificInstructionRequest2 recursion level 1 with max 1
class SpecificInstructionRequest2{
SecuritiesRegistration IsoYesNoIndicator
}
SpecificInstructionRequest2 *-- "1..1" IParticipationMethod1Choice : ParticipationMethod
Instruction4 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| SingleInstructionIdentification | Identification of the individual 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. | SafekeepingAccount9 - Required 1..1 |
| Proxy | Identification of the person appointed by the security holder as the proxy. | Proxy7 - Optional 0..1 |
| VoteDetails | Detailed voting instructions. | VoteDetails4 - 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. | IndividualPerson39 - Unknown 0..0 |
| SpecificInstructionRequest | Request to execute specific instructions, such as participation registration, securities registration or blocking of securities. | SpecificInstructionRequest2 - Optional 0..1 |
SupplementaryData building block
Additional information that cannot 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 MeetingInstructionV06 implementation follows a specific implementaiton pattern. First of all, MeetingInstructionV06 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, MeetingInstructionV06Document implements IOuterDocument. Because MeetingInstructionV06 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type MeetingInstructionV06.
classDiagram
class IOuterRecord
MeetingInstructionV06 --|> IOuterRecord : Implements
MeetingInstructionV06Document --|> IOuterDocument~MeetingInstructionV06~ : Implements
class IOuterDocument~MeetingInstructionV06~ {
MeetingInstructionV06 Message
}
Document wrapper for serialization
The only real purpose MeetingInstructionV06Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:seev.004.001.06’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using MeetingInstructionV06.ToDocument() method. The returned MeetingInstructionV06Document value will serialize correctly according to ISO 20022 standards.
classDiagram
MeetingInstructionV06Document *-- MeetingInstructionV06 : 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.06">
<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="_yXBbiayREemMosWmlQ33EA"
nextVersions="_sVyKT_EkEeqRfth943bvEA"
previousVersion="_xDAOUVtcEeSwKe7KuKvXhg"
name="MeetingInstructionV06"
definition="Scope
The MeetingInstruction message is sent by a party holding the right to vote 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 vote, require attendance to a meeting, request registration of securities and assign a proxy. One of multiple instructions can be carried within the same message.
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="_urpIICeJEeOCeO5e7islRQ"
xmlTag="MtgInstr"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_yXBbi6yREemMosWmlQ33EA"
nextVersions="_sVyKVfEkEeqRfth943bvEA"
previousVersion="_xDAOVVtcEeSwKe7KuKvXhg"
name="MeetingReference"
definition="Set of elements that allow to identify unambiguously a meeting."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="MtgRef"
complexType="_eHSlsa7NEemG7MmivSuE5g" />
<messageBuildingBlock
xmi:id="_yXBbjayREemMosWmlQ33EA"
nextVersions="_sVyKV_EkEeqRfth943bvEA"
previousVersion="_xDAOWVtcEeSwKe7KuKvXhg"
name="FinancialInstrumentIdentification"
definition="Security for which the meeting is organised."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="FinInstrmId"
complexType="_ho6XQYlXEeWPSZi0kAOXhg" />
<messageBuildingBlock
xmi:id="_yXBbj6yREemMosWmlQ33EA"
nextVersions="_sVyKWfEkEeqRfth943bvEA"
previousVersion="_xDAOW1tcEeSwKe7KuKvXhg"
name="Instruction"
definition="Identifies the position of the instructing party and the action that it wants to take."
registrationStatus="Provisionally Registered"
minOccurs="1"
xmlTag="Instr"
complexType="_X58_Ia4cEemG7MmivSuE5g" />
<messageBuildingBlock
xmi:id="_yXBbkayREemMosWmlQ33EA"
nextVersions="_sVyKW_EkEeqRfth943bvEA"
previousVersion="_vE2o0VtoEeSwKe7KuKvXhg"
name="SupplementaryData"
definition="Additional information that cannot 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="06" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.