MeetingInstructionV03

seev.004.001.03

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
%% MeetingInstructionV03 recursion level 0 with max 0
MeetingInstructionV03 *-- "1..1" MessageIdentification1 : Identification
MeetingInstructionV03 *-- "1..1" MeetingReference4 : MeetingReference
MeetingInstructionV03 *-- "1..1" IPartyIdentification9Choice : InstructingParty
MeetingInstructionV03 *-- "1..1" SecurityIdentification11 : SecurityIdentification
MeetingInstructionV03 *-- "1..1" Instruction2 : Instruction

Now, we will zero-in one-by-one on each of these building blocks.

Identification 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
%% 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

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. 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

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
%% Instruction2 recursion level 0 with max 1
class Instruction2{
    InstructionIdentification IsoMax35Text
    RequestedExecutionDate IsoISODateTime
    VoteExecutionConfirmation IsoYesNoIndicator
}
Instruction2 *-- "1..1" SafekeepingAccount4 : AccountDetails
Instruction2 *-- "0..1" Proxy4 : Proxy
Instruction2 *-- "0..1" VoteDetails2 : VoteDetails
Instruction2 *-- "0..0" IndividualPerson17 : MeetingAttendee
Instruction2 *-- "0..1" SpecificInstructionRequest1 : SpecificInstructionRequest
%% SafekeepingAccount4 recursion level 1 with max 1
class SafekeepingAccount4{
    AccountIdentification IsoMax35Text
}
SafekeepingAccount4 *-- "0..1" IPartyIdentification9Choice : AccountOwner
SafekeepingAccount4 *-- "0..1" SubAccount2 : SubAccountDetails
SafekeepingAccount4 *-- "1..10" HoldingBalance5 : InstructedBalance
SafekeepingAccount4 *-- "0..10" IPartyIdentification9Choice : RightsHolder
%% Proxy4 recursion level 1 with max 1
class Proxy4{
    ProxyType ProxyType2Code
}
Proxy4 *-- "0..1" IndividualPerson17 : PersonDetails
Proxy4 *-- "0..1" IVote2Choice : VoteInstructionForAgendaResolution
%% VoteDetails2 recursion level 1 with max 1
VoteDetails2 *-- "1..1" IVote2Choice : VoteInstructionForAgendaResolution
VoteDetails2 *-- "0..1" IVoteInstructionForMeetingResolution1Choice : VoteInstructionForMeetingResolution
%% IndividualPerson17 recursion level 1 with max 1
class IndividualPerson17{
    BirthName IsoMax35Text
    GivenName IsoMax35Text
}
IndividualPerson17 *-- "0..1" PersonIdentification6 : Identification
IndividualPerson17 *-- "0..1" ILongPostalAddress2Choice : Address
IndividualPerson17 *-- "0..1" IPartyIdentification9Choice : EmployingParty
IndividualPerson17 *-- "1..1" AttendanceCard2 : AttendanceCardDetails
%% SpecificInstructionRequest1 recursion level 1 with max 1
class SpecificInstructionRequest1{
    ParticipationRegistration IsoYesNoIndicator
    BlockingSecurities IsoYesNoIndicator
    SecuritiesRegistration IsoYesNoIndicator
}

Instruction2 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.	SafekeepingAccount4 - Required 1..1
Proxy	Identification of the person appointed by the security holder as proxy.	Proxy4 - Optional 0..1
VoteDetails	Specifies detailed voting instructions.	VoteDetails2 - 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.	IndividualPerson17 - 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 MeetingInstructionV03 implementation follows a specific implementaiton pattern. First of all, MeetingInstructionV03 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, MeetingInstructionV03Document implements IOuterDocument. Because MeetingInstructionV03 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type MeetingInstructionV03.

classDiagram
    class IOuterRecord
    MeetingInstructionV03 --|> IOuterRecord : Implements
    MeetingInstructionV03Document --|> IOuterDocument~MeetingInstructionV03~ : Implements
    class IOuterDocument~MeetingInstructionV03~ {
        MeetingInstructionV03 Message
     }

Document wrapper for serialization

The only real purpose MeetingInstructionV03Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:seev.004.001.03’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using MeetingInstructionV03.ToDocument() method. The returned MeetingInstructionV03Document value will serialize correctly according to ISO 20022 standards.

classDiagram
    MeetingInstructionV03Document *-- MeetingInstructionV03 : 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.03">
    <MtgInstr>
        <Id>
            <!-- Identification inner content -->
        </Id>
        <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="_Tqz_QtEwEd-BzquC8wXy7w_-2059690567"
  nextVersions="_Tq9JOdEwEd-BzquC8wXy7w_-1580879636"
  previousVersion="_TqgdUtEwEd-BzquC8wXy7w_-118091241"
  name="MeetingInstructionV03"
  definition="Scope&#xD;&#xA;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.&#xD;&#xA;Usage&#xD;&#xA;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.&#xD;&#xA;The MeetingInstruction message may only be sent for one security, though several safekeeping places may be specified.&#xD;&#xA;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="_Tqz_Q9EwEd-BzquC8wXy7w_-823119403"
    name="Identification"
    definition="Identifies the meeting instruction message."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Id"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_Tqz_RNEwEd-BzquC8wXy7w_-834204444"
    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="_Tqz_RdEwEd-BzquC8wXy7w_-839745662"
    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="_Tqz_RtEwEd-BzquC8wXy7w_-862832216"
    name="SecurityIdentification"
    definition="Identifies the security for which the meeting is organised."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="SctyId"
    complexType="_TBKB89p-Ed-ak6NoX_4Aeg_-524266634" />
  <messageBuildingBlock
    xmi:id="_Tqz_R9EwEd-BzquC8wXy7w_-879456271"
    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="_RC8Bsdp-Ed-ak6NoX_4Aeg_927602263" />
  <messageDefinitionIdentifier
    businessArea="seev"
    messageFunctionality="004"
    flavour="001"
    version="03" />
</messageDefinition>

ISO Building Blocks

The following items are used as building blocks to construct this message.