Iso20022

MeetingInstructionStatusV05

seev.006.001.05

Scope The Receiver of the MeetingInstruction or MeetingInstructionCancellationRequest sends the MeetingInstructionStatus message to the Sender of these messages. The message gives the status of a complete message or of one or more specific instructions within the message. Usage The MeetingInstructionStatus message is used for four purposes. First, it provides the status on the processing of a MeetingInstructionCancellationRequest message, for example, whether the request message is rejected or accepted. Second, it is used to provide a global processing or rejection status of a MeetingInstruction message. Third, it is used to provide a detailed processing or rejection status of a MeetingInstruction message, for example, for each instruction in the MeetingInstruction message the processing or rejection status is individually reported by using the InstructionIdentification element. This identification allows the receiver of the status message to link the status confirmation to its original instruction. The blocking of securities should be confirmed via an MT 508 (Intra-Position Advice). Fourth, it is used as a reminder to request voting instructions. This is done by indicating NONREF in the Identification element of the InstructionIdentification component and by using the status code NotReceived in the ProcessingStatus. 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
%% MeetingInstructionStatusV05 recursion level 0 with max 0
MeetingInstructionStatusV05 *-- "1..1" IInstructionType1Choice : InstructionType
MeetingInstructionStatusV05 *-- "1..1" MeetingReference7 : MeetingReference
MeetingInstructionStatusV05 *-- "1..1" SecurityIdentification14 : FinancialInstrumentIdentification
MeetingInstructionStatusV05 *-- "1..1" IInstructionTypeStatus2Choice : InstructionTypeStatus
MeetingInstructionStatusV05 *-- "0..1" SupplementaryData1 : SupplementaryData

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

InstructionType building block

Type of instruction. Type of instruction. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% IInstructionType1Choice recursion level 0 with max 1

InstructionType1Choice members

Member name Description Data Type / Multiplicity

MeetingReference building block

Series of elements which allow to identify a meeting. Identification of a meeting. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% MeetingReference7 recursion level 0 with max 1
class MeetingReference7{
    MeetingIdentification IsoMax35Text
    IssuerMeetingIdentification IsoMax35Text
    MeetingDateAndTime IsoISODateTime
    Type MeetingType3Code
}
MeetingReference7 *-- "0..1" IMeetingTypeClassification1Choice : Classification
MeetingReference7 *-- "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
}

MeetingReference7 members

Member name Description Data Type / Multiplicity
MeetingIdentification Identification assigned to the 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 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 Specifies the type of meeting for which instructions are sent. MeetingType3Code - 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

FinancialInstrumentIdentification building block

Identifies the securities for which the meeting is organised. Identification of a security. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% SecurityIdentification14 recursion level 0 with max 1
class SecurityIdentification14{
    ISIN IsoISINIdentifier
    Description IsoMax140Text
}
SecurityIdentification14 *-- "0..0" OtherIdentification1 : OtherIdentification
%% OtherIdentification1 recursion level 1 with max 1
class OtherIdentification1{
    Identification IsoMax35Text
    Suffix IsoMax16Text
}
OtherIdentification1 *-- "1..1" IIdentificationSource3Choice : Type

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

InstructionTypeStatus building block

Type of instruction status. Choice of instruction type status. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% IInstructionTypeStatus2Choice recursion level 0 with max 1

InstructionTypeStatus2Choice members

Member name Description Data Type / Multiplicity

SupplementaryData building block

Additional information that can not 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 MeetingInstructionStatusV05 implementation follows a specific implementaiton pattern. First of all, MeetingInstructionStatusV05 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, MeetingInstructionStatusV05Document implements IOuterDocument. Because MeetingInstructionStatusV05 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type MeetingInstructionStatusV05.

classDiagram
    class IOuterRecord
    MeetingInstructionStatusV05 --|> IOuterRecord : Implements
    MeetingInstructionStatusV05Document --|> IOuterDocument~MeetingInstructionStatusV05~ : Implements
    class IOuterDocument~MeetingInstructionStatusV05~ {
        MeetingInstructionStatusV05 Message
     }

Document wrapper for serialization

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

classDiagram
    MeetingInstructionStatusV05Document *-- MeetingInstructionStatusV05 : 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.006.001.05">
    <MtgInstrSts>
        <InstrTp>
            <!-- InstructionType inner content -->
        </InstrTp>
        <MtgRef>
            <!-- MeetingReference inner content -->
        </MtgRef>
        <FinInstrmId>
            <!-- FinancialInstrumentIdentification inner content -->
        </FinInstrmId>
        <InstrTpSts>
            <!-- InstructionTypeStatus inner content -->
        </InstrTpSts>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </MtgInstrSts>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_xDAOO1tcEeSwKe7KuKvXhg"
  nextVersions="_yXBbd6yREemMosWmlQ33EA"
  previousVersion="_TqXTUNEwEd-BzquC8wXy7w_99042676"
  name="MeetingInstructionStatusV05"
  definition="Scope&#xD;&#xA;The Receiver of the MeetingInstruction or MeetingInstructionCancellationRequest sends the MeetingInstructionStatus message to the Sender of these messages.&#xD;&#xA;The message gives the status of a complete message or of one or more specific instructions within the message.&#xD;&#xA;Usage&#xD;&#xA;The MeetingInstructionStatus message is used for four purposes.&#xD;&#xA;First, it provides the status on the processing of a MeetingInstructionCancellationRequest message, for example, whether the request message is rejected or accepted.&#xD;&#xA;Second, it is used to provide a global processing or rejection status of a MeetingInstruction message.&#xD;&#xA;Third, it is used to provide a detailed processing or rejection status of a MeetingInstruction message, for example, for each instruction in the MeetingInstruction message the processing or rejection status is individually reported by using the InstructionIdentification element. This identification allows the receiver of the status message to link the status confirmation to its original instruction.&#xD;&#xA;The blocking of securities should be confirmed via an MT 508 (Intra-Position Advice).&#xD;&#xA;Fourth, it is used as a reminder to request voting instructions. This is done by indicating NONREF in the Identification element of the InstructionIdentification component and by using the status code NotReceived in the ProcessingStatus.&#xD;&#xA;This message definition is intended for use with the Business Application Header."
  registrationStatus="Registered"
  messageSet="_wRe70U2rEeG_I4xRYCA_7g"
  xmlTag="MtgInstrSts"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <constraint
    xmi:id="_xDAOPVtcEeSwKe7KuKvXhg"
    nextVersions="_yXBbeayREemMosWmlQ33EA"
    previousVersion="_TqgdQNEwEd-BzquC8wXy7w_73824110"
    name="Status1Rule"
    definition="If InstructionType/InstructionIdentification is present, then InstructionTypeStatus/InstructionStatus must be present."
    registrationStatus="Provisionally Registered"
    expression="&lt;RuleDefinition xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;&gt;&lt;ComplexRule xsi:type=&quot;ComplexRule&quot;&gt;&lt;mustBe&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/InstructionTypeStatus/InstructionStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/mustBe&gt;&lt;onCondition&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/InstructionType/InstructionIdentification&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/onCondition&gt;&lt;/ComplexRule&gt;&lt;/RuleDefinition&gt;&#xA;" />
  <constraint
    xmi:id="_xDAOP1tcEeSwKe7KuKvXhg"
    nextVersions="_yXBbe6yREemMosWmlQ33EA"
    previousVersion="_TqgdQ9EwEd-BzquC8wXy7w_542631525"
    name="Status2Rule"
    definition="If InstructionType/InstructionCancellationIdentification is present, then InstructionTypeStatus/CancellationStatus must be present."
    registrationStatus="Provisionally Registered"
    expression="&lt;RuleDefinition xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;&gt;&lt;ComplexRule xsi:type=&quot;ComplexRule&quot;&gt;&lt;mustBe&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/InstructionTypeStatus/CancellationStatus&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/mustBe&gt;&lt;onCondition&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;Presence&quot;&gt;&lt;leftOperand&gt;/InstructionType/InstructionCancellationIdentification&lt;/leftOperand&gt;&lt;/BooleanRule&gt;&lt;/onCondition&gt;&lt;/ComplexRule&gt;&lt;/RuleDefinition&gt;&#xA;" />
  <constraint
    xmi:id="_xDAOQVtcEeSwKe7KuKvXhg"
    previousVersion="_TqgdRtEwEd-BzquC8wXy7w_-454440828"
    name="Reminder1Rule"
    definition="If InstructionType/InstructionIdentification/Identification is &quot;NONREF&quot;, then InstructionTypeStatus/InstructionStatus/GlobalInstructionStatus/ProcessingStatus/Status must be NOIN."
    registrationStatus="Provisionally Registered"
    expression="&lt;RuleDefinition xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;&gt;&lt;ComplexRule xsi:type=&quot;ComplexRule&quot;&gt;&lt;mustBe&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;EqualToValue&quot;&gt;&lt;leftOperand&gt;/InstructionTypeStatus/InstructionStatus/GlobalInstructionStatus/ProcessingStatus/Status&lt;/leftOperand&gt;&lt;rightOperand&gt;NotReceived&lt;/rightOperand&gt;&lt;/BooleanRule&gt;&lt;/mustBe&gt;&lt;onCondition&gt;&lt;connector&gt;AND&lt;/connector&gt;&lt;BooleanRule xsi:type=&quot;EqualToValue&quot;&gt;&lt;leftOperand&gt;/InstructionType/InstructionIdentification/Identification&lt;/leftOperand&gt;&lt;rightOperand&gt;NONREF&lt;/rightOperand&gt;&lt;/BooleanRule&gt;&lt;/onCondition&gt;&lt;/ComplexRule&gt;&lt;/RuleDefinition&gt;&#xA;" />
  <messageBuildingBlock
    xmi:id="_xDAORVtcEeSwKe7KuKvXhg"
    nextVersions="_yXBbf6yREemMosWmlQ33EA"
    previousVersion="_TqXTUtEwEd-BzquC8wXy7w_-28327531"
    name="InstructionType"
    definition="Type of instruction."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="InstrTp"
    complexType="_RCWL1Np-Ed-ak6NoX_4Aeg_869239445" />
  <messageBuildingBlock
    xmi:id="_xDAOR1tcEeSwKe7KuKvXhg"
    nextVersions="_yXBbgayREemMosWmlQ33EA"
    previousVersion="_TqXTU9EwEd-BzquC8wXy7w_-1403252543"
    name="MeetingReference"
    definition="Series of elements which allow to identify a meeting."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="MtgRef"
    complexType="_uG79UVuPEeSmO6RkXg92Lg" />
  <messageBuildingBlock
    xmi:id="_xDAOS1tcEeSwKe7KuKvXhg"
    nextVersions="_yXBbg6yREemMosWmlQ33EA"
    previousVersion="_TqXTVdEwEd-BzquC8wXy7w_-363218248"
    name="FinancialInstrumentIdentification"
    definition="Identifies the securities for which the meeting is organised."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="FinInstrmId"
    complexType="_TBAQ7dp-Ed-ak6NoX_4Aeg_896067631" />
  <messageBuildingBlock
    xmi:id="_xDAOTVtcEeSwKe7KuKvXhg"
    nextVersions="_yXBbhayREemMosWmlQ33EA"
    previousVersion="_TqXTVtEwEd-BzquC8wXy7w_1595413206"
    name="InstructionTypeStatus"
    definition="Type of instruction status."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="InstrTpSts"
    complexType="_q8cZMV6uEeSyc4g_pm5hbw" />
  <messageBuildingBlock
    xmi:id="_sMzdoVtoEeSwKe7KuKvXhg"
    nextVersions="_yXBbh6yREemMosWmlQ33EA"
    name="SupplementaryData"
    definition="Additional information that can not 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="006"
    flavour="001"
    version="05" />
</messageDefinition>

ISO Building Blocks

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