MeetingInstructionV09

seev.004.001.09

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, to require attendance to a meeting, to request registration of securities and assign a proxy. One instruction or 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 (BAH).

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
%% MeetingInstructionV09 recursion level 0 with max 0
class MeetingInstructionV09{
    MeetingInstructionIdentification IsoMax35Text
}
MeetingInstructionV09 *-- "0..1" Pagination1 : Pagination
MeetingInstructionV09 *-- "1..1" MeetingReference10 : MeetingReference
MeetingInstructionV09 *-- "1..1" SecurityIdentification19 : FinancialInstrumentIdentification
MeetingInstructionV09 *-- "0..1" MeetingInstructionCancellation1 : InstructionCancellationRequestIdentification
MeetingInstructionV09 *-- "0..1" MeetingInstructionIdentification1 : CancelledInstructionIdentification
MeetingInstructionV09 *-- "0..1" DocumentIdentification32 : OtherDocumentIdentification
MeetingInstructionV09 *-- "1..1" Instruction7 : Instruction
MeetingInstructionV09 *-- "0..1" SupplementaryData1 : SupplementaryData
  

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

Pagination building block

Page number of the message and continuation indicator to indicate that the multi-part instruction is to continue or that the message is the last page of the multi-part instruction. Number used to sequence pages when it is not possible for data to be conveyed in a single message and the data has to be split across several pages (messages). For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Pagination1 recursion level 0 with max 1
class Pagination1{
    PageNumber IsoMax5NumericText
    LastPageIndicator IsoYesNoIndicator
}
  

Pagination1 members

Member name Description Data Type / Multiplicity
PageNumber Page number. IsoMax5NumericText - Required 1..1
LastPageIndicator Indicates the last page. IsoYesNoIndicator - Required 1..1

MeetingInstructionIdentification building block

Unique identification of the group of meeting instruction messages when the instruction is split in multiple (paginated) messages. Specifies a character string with a maximum length of 35 characters. For comparison, see the ISO20022 official specification This message is declared as Max35Text in the ISO specification. In our implementation, it is represented in source code as IsoMax35Text. Due to global using directives, it is treated as a System.String by the compiler and runtime.

MeetingReference building block

Set of elements to allow the unambiguous identification of a meeting. Identification of a meeting. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% MeetingReference10 recursion level 0 with max 1
class MeetingReference10{
    MeetingIdentification IsoMax35Text
    IssuerMeetingIdentification IsoMax35Text
    MeetingDateAndTime IsoISODateTime
    Type MeetingType4Code
}
MeetingReference10 *-- "0..1" IMeetingTypeClassification2Choice : Classification
MeetingReference10 *-- "0..5" PostalAddress1 : Location
MeetingReference10 *-- "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
  

MeetingReference10 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 - Required 1..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 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

InstructionCancellationRequestIdentification building block

Identification of the cancellation request message requesting cancellation of individual instruction(s). Identification of the cancellation request message requesting cancellation of individual instruction(s). For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% MeetingInstructionCancellation1 recursion level 0 with max 1
class MeetingInstructionCancellation1{
    MeetingInstructionCancellationRequestIdentification IsoMax35Text
    SingleInstructionIdentification IsoMax35Text
}
  

MeetingInstructionCancellation1 members

Member name Description Data Type / Multiplicity
MeetingInstructionCancellationRequestIdentification Identification of the meeting instruction cancellation request message containing the individual instruction(s) for which the cancellation was requested. IsoMax35Text - Required 1..1
SingleInstructionIdentification Identification of the individual instruction for which the cancellation was requested. IsoMax35Text - Required 1..1

CancelledInstructionIdentification building block

Identification of the message and individual instruction(s) for which the cancellation was requested. Identification of the message and individual instruction(s) for which the cancellation was requested. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% MeetingInstructionIdentification1 recursion level 0 with max 1
class MeetingInstructionIdentification1{
    MeetingInstructionIdentification IsoMax35Text
    SingleInstructionIdentification IsoMax35Text
}
  

MeetingInstructionIdentification1 members

Member name Description Data Type / Multiplicity
MeetingInstructionIdentification Identification of the previous meeting instruction message containing the individual instruction(s) for which the cancellation was requested. IsoMax35Text - Required 1..1
SingleInstructionIdentification Identification of the individual instruction for which the cancellation was requested. IsoMax35Text - Required 1..1

OtherDocumentIdentification building block

Identification of other messages/documents as well as the messages/documents number. Identification of a document as well as the document number and type of link. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% DocumentIdentification32 recursion level 0 with max 1
DocumentIdentification32 *-- "1..1" IDocumentIdentification3Choice : Identification
DocumentIdentification32 *-- "0..1" IDocumentNumber5Choice : DocumentNumber
DocumentIdentification32 *-- "0..1" IProcessingPosition7Choice : LinkageType
%% IDocumentIdentification3Choice recursion level 1 with max 1
%% IDocumentNumber5Choice recursion level 1 with max 1
%% IProcessingPosition7Choice recursion level 1 with max 1
  

DocumentIdentification32 members

Member name Description Data Type / Multiplicity
Identification Unique identifier of the document (message) assigned either by the account servicer or the account owner. IDocumentIdentification3Choice - Required 1..1
DocumentNumber Identification of the type of document. IDocumentNumber5Choice - Optional 0..1
LinkageType Specifies when this document is to be processed relative to another referred document. IProcessingPosition7Choice - Optional 0..1

Instruction building block

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
%% Instruction7 recursion level 0 with max 1
class Instruction7{
    SingleInstructionIdentification IsoMax35Text
    RequestedExecutionDate IsoISODateTime
    VoteExecutionConfirmation IsoYesNoIndicator
}
Instruction7 *-- "1..1" SafekeepingAccount15 : AccountDetails
Instruction7 *-- "0..1" Proxy12 : Proxy
Instruction7 *-- "0..1" VoteDetails6 : VoteDetails
Instruction7 *-- "0..0" IndividualPerson41 : MeetingAttendee
Instruction7 *-- "0..1" SpecificInstructionRequest4 : SpecificInstructionRequest
%% SafekeepingAccount15 recursion level 1 with max 1
class SafekeepingAccount15{
    AccountIdentification IsoMax35Text
    BlockChainAddressOrWallet IsoMax140Text
    SubAccountIdentification IsoMax35Text
}
SafekeepingAccount15 *-- "0..1" IPartyIdentification231Choice : AccountOwner
SafekeepingAccount15 *-- "1..15" HoldingBalance12 : InstructedBalance
SafekeepingAccount15 *-- "0..250" IPartyIdentification246Choice : RightsHolder
SafekeepingAccount15 *-- "0..1" PledgeInformation1 : PledgeDetails
%% Proxy12 recursion level 1 with max 1
class Proxy12{
    ProxyType ProxyType3Code
}
Proxy12 *-- "0..1" IndividualPerson42 : PersonDetails
%% VoteDetails6 recursion level 1 with max 1
VoteDetails6 *-- "1..1" IVote15Choice : VoteInstructionForAgendaResolution
VoteDetails6 *-- "0..1" IVoteInstructionForMeetingResolution3Choice : VoteInstructionForMeetingResolution
%% IndividualPerson41 recursion level 1 with max 1
class IndividualPerson41{
    ParticipationMethod VotingParticipationMethod2Code
}
IndividualPerson41 *-- "0..1" IPartyIdentification232Choice : Identification
IndividualPerson41 *-- "0..1" IPartyIdentification129Choice : EmployingParty
IndividualPerson41 *-- "1..1" AttendanceCard3 : AttendanceCardDetails
%% SpecificInstructionRequest4 recursion level 1 with max 1
class SpecificInstructionRequest4{
    SecuritiesRegistration IsoYesNoIndicator
}
SpecificInstructionRequest4 *-- "0..1" IParticipationMethod3Choice : ParticipationMethod
  

Instruction7 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. SafekeepingAccount15 - Required 1..1
Proxy Identification of the person appointed by the security holder as the proxy. Proxy12 - Optional 0..1
VoteDetails Detailed voting instructions. VoteDetails6 - 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. IndividualPerson41 - Unknown 0..0
SpecificInstructionRequest Request to execute specific instructions, such as participation registration, securities registration or blocking of securities. SpecificInstructionRequest4 - 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 MeetingInstructionV09 implementation follows a specific implementaiton pattern. First of all, MeetingInstructionV09 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, MeetingInstructionV09Document implements IOuterDocument. Because MeetingInstructionV09 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type MeetingInstructionV09.

classDiagram
    class IOuterRecord
    MeetingInstructionV09 --|> IOuterRecord : Implements
    MeetingInstructionV09Document --|> IOuterDocument~MeetingInstructionV09~ : Implements
    class IOuterDocument~MeetingInstructionV09~ {
        MeetingInstructionV09 Message
     }
  

Document wrapper for serialization

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

classDiagram
    MeetingInstructionV09Document *-- MeetingInstructionV09 : 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.09">
    <MtgInstr>
        <Pgntn>
            <!-- Pagination inner content -->
        </Pgntn>
        <MtgInstrId>
            <!-- MeetingInstructionIdentification inner content -->
        </MtgInstrId>
        <MtgRef>
            <!-- MeetingReference inner content -->
        </MtgRef>
        <FinInstrmId>
            <!-- FinancialInstrumentIdentification inner content -->
        </FinInstrmId>
        <InstrCxlReqId>
            <!-- InstructionCancellationRequestIdentification inner content -->
        </InstrCxlReqId>
        <CancInstrId>
            <!-- CancelledInstructionIdentification inner content -->
        </CancInstrId>
        <OthrDocId>
            <!-- OtherDocumentIdentification inner content -->
        </OthrDocId>
        <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="_nIzHsTQ7Ee22Z83HpR5E8w"
  previousVersion="_lKgSgRrdEeyhRdHRjakS2w"
  name="MeetingInstructionV09"
  definition="Scope&#xD;&#xA;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.&#xD;&#xA;Usage&#xD;&#xA;The MeetingInstruction message is used to vote, to require attendance to a meeting, to request registration of securities and assign a proxy. One instruction or multiple instructions can be carried within the same message.&#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&#xD;&#xA;MeetingInstructionStatus message, a new MeetingInstruction message can be sent.&#xD;&#xA;This message definition is intended for use with the Business Application Header (BAH)."
  registrationStatus="Registered"
  messageSet="_aYSVkfZkEemdMY5FVzFKKA"
  xmlTag="MtgInstr"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_xiGS4TT-Ee2tRf29bleifQ"
    name="Pagination"
    definition="Page number of the message and continuation indicator to indicate that the multi-part instruction is to continue or that the message is the last page of the multi-part instruction."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="Pgntn"
    complexType="_xhMHQa6XEees_ufOy2ci-g" />
  <messageBuildingBlock
    xmi:id="_7o9OIDT-Ee2tRf29bleifQ"
    name="MeetingInstructionIdentification"
    definition="Unique identification of the group of meeting instruction messages when the instruction is split in multiple (paginated) messages."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="MtgInstrId"
    simpleType="_YW1tKdp-Ed-ak6NoX_4Aeg_1913463446" />
  <messageBuildingBlock
    xmi:id="_nIzHtzQ7Ee22Z83HpR5E8w"
    previousVersion="_lKgShxrdEeyhRdHRjakS2w"
    name="MeetingReference"
    definition="Set of elements to allow the unambiguous identification of a meeting."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="MtgRef"
    complexType="_UP25gfKxEeqRfth943bvEA" />
  <messageBuildingBlock
    xmi:id="_nIzHuTQ7Ee22Z83HpR5E8w"
    previousVersion="_lKgSiRrdEeyhRdHRjakS2w"
    name="FinancialInstrumentIdentification"
    definition="Security for which the meeting is organised."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="FinInstrmId"
    complexType="_ho6XQYlXEeWPSZi0kAOXhg" />
  <messageBuildingBlock
    xmi:id="_J-5jgDUAEe2tRf29bleifQ"
    name="InstructionCancellationRequestIdentification"
    definition="Identification of the cancellation request message requesting cancellation of individual instruction(s)."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="InstrCxlReqId"
    complexType="_mbPBQDUAEe2tRf29bleifQ" />
  <messageBuildingBlock
    xmi:id="_bAVEMDUAEe2tRf29bleifQ"
    name="CancelledInstructionIdentification"
    definition="Identification of the message and individual instruction(s) for which the cancellation was requested."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="CancInstrId"
    complexType="_KPVWwDUBEe2tRf29bleifQ" />
  <messageBuildingBlock
    xmi:id="_nIzHuzQ7Ee22Z83HpR5E8w"
    previousVersion="_lKgSixrdEeyhRdHRjakS2w"
    name="OtherDocumentIdentification"
    definition="Identification of other messages/documents as well as the messages/documents number."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="OthrDocId"
    complexType="_ni5s8TnYEeWLJsP1cO-amg" />
  <messageBuildingBlock
    xmi:id="_nIzHvTQ7Ee22Z83HpR5E8w"
    previousVersion="_lKgSjRrdEeyhRdHRjakS2w"
    name="Instruction"
    definition="The position of the instructing party and the action that it wants to take."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="Instr"
    complexType="_wxo4kTT5Ee2j2eQlcOSMKg" />
  <messageBuildingBlock
    xmi:id="_nIzHvzQ7Ee22Z83HpR5E8w"
    previousVersion="_lKgSjxrdEeyhRdHRjakS2w"
    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="09" />
</messageDefinition>

ISO Building Blocks

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