MeetingInstructionV07

seev.004.001.07

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
%% MeetingInstructionV07 recursion level 0 with max 0
MeetingInstructionV07 *-- "1..1" MeetingReference10 : MeetingReference
MeetingInstructionV07 *-- "1..1" SecurityIdentification19 : FinancialInstrumentIdentification
MeetingInstructionV07 *-- "0..1" DocumentIdentification32 : OtherDocumentIdentification
MeetingInstructionV07 *-- "1..1" Instruction5 : Instruction
MeetingInstructionV07 *-- "0..1" SupplementaryData1 : SupplementaryData
  

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

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

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
%% Instruction5 recursion level 0 with max 1
class Instruction5{
    SingleInstructionIdentification IsoMax35Text
    RequestedExecutionDate IsoISODateTime
    VoteExecutionConfirmation IsoYesNoIndicator
}
Instruction5 *-- "1..1" SafekeepingAccount12 : AccountDetails
Instruction5 *-- "0..1" Proxy10 : Proxy
Instruction5 *-- "0..1" VoteDetails5 : VoteDetails
Instruction5 *-- "0..0" IndividualPerson41 : MeetingAttendee
Instruction5 *-- "0..1" SpecificInstructionRequest3 : SpecificInstructionRequest
%% SafekeepingAccount12 recursion level 1 with max 1
class SafekeepingAccount12{
    AccountIdentification IsoMax35Text
    SubAccountIdentification IsoMax35Text
}
SafekeepingAccount12 *-- "0..1" IPartyIdentification231Choice : AccountOwner
SafekeepingAccount12 *-- "1..15" HoldingBalance10 : InstructedBalance
SafekeepingAccount12 *-- "0..250" IPartyIdentification233Choice : RightsHolder
SafekeepingAccount12 *-- "0..1" PledgeInformation1 : PledgeDetails
%% Proxy10 recursion level 1 with max 1
class Proxy10{
    ProxyType ProxyType2Code
}
Proxy10 *-- "0..1" IndividualPerson42 : PersonDetails
%% VoteDetails5 recursion level 1 with max 1
VoteDetails5 *-- "1..1" IVote15Choice : VoteInstructionForAgendaResolution
VoteDetails5 *-- "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
%% SpecificInstructionRequest3 recursion level 1 with max 1
class SpecificInstructionRequest3{
    SecuritiesRegistration IsoYesNoIndicator
}
SpecificInstructionRequest3 *-- "0..1" IParticipationMethod1Choice : ParticipationMethod
  

Instruction5 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. SafekeepingAccount12 - Required 1..1
Proxy Identification of the person appointed by the security holder as the proxy. Proxy10 - Optional 0..1
VoteDetails Detailed voting instructions. VoteDetails5 - 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. SpecificInstructionRequest3 - 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 MeetingInstructionV07 implementation follows a specific implementaiton pattern. First of all, MeetingInstructionV07 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, MeetingInstructionV07Document implements IOuterDocument. Because MeetingInstructionV07 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type MeetingInstructionV07.

classDiagram
    class IOuterRecord
    MeetingInstructionV07 --|> IOuterRecord : Implements
    MeetingInstructionV07Document --|> IOuterDocument~MeetingInstructionV07~ : Implements
    class IOuterDocument~MeetingInstructionV07~ {
        MeetingInstructionV07 Message
     }
  

Document wrapper for serialization

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

classDiagram
    MeetingInstructionV07Document *-- MeetingInstructionV07 : 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.07">
    <MtgInstr>
        <MtgRef>
            <!-- MeetingReference inner content -->
        </MtgRef>
        <FinInstrmId>
            <!-- FinancialInstrumentIdentification inner content -->
        </FinInstrmId>
        <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="_sVyKT_EkEeqRfth943bvEA"
  nextVersions="_lKgSgRrdEeyhRdHRjakS2w"
  previousVersion="_yXBbiayREemMosWmlQ33EA"
  name="MeetingInstructionV07"
  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="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="MtgInstr"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_sVyKVfEkEeqRfth943bvEA"
    nextVersions="_lKgShxrdEeyhRdHRjakS2w"
    previousVersion="_yXBbi6yREemMosWmlQ33EA"
    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="_sVyKV_EkEeqRfth943bvEA"
    nextVersions="_lKgSiRrdEeyhRdHRjakS2w"
    previousVersion="_yXBbjayREemMosWmlQ33EA"
    name="FinancialInstrumentIdentification"
    definition="Security for which the meeting is organised."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="FinInstrmId"
    complexType="_ho6XQYlXEeWPSZi0kAOXhg" />
  <messageBuildingBlock
    xmi:id="_ucYQwPKxEeqRfth943bvEA"
    nextVersions="_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="_sVyKWfEkEeqRfth943bvEA"
    nextVersions="_lKgSjRrdEeyhRdHRjakS2w"
    previousVersion="_yXBbj6yREemMosWmlQ33EA"
    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="_7NKXMfNXEeqRfth943bvEA" />
  <messageBuildingBlock
    xmi:id="_sVyKW_EkEeqRfth943bvEA"
    nextVersions="_lKgSjxrdEeyhRdHRjakS2w"
    previousVersion="_yXBbkayREemMosWmlQ33EA"
    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="07" />
</messageDefinition>

ISO Building Blocks

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