Iso20022

MeetingInstructionStatusV03

seev.006.001.03

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.

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
%% MeetingInstructionStatusV03 recursion level 0 with max 0
MeetingInstructionStatusV03 *-- "1..1" MessageIdentification1 : Identification
MeetingInstructionStatusV03 *-- "1..1" IInstructionType1Choice : InstructionType
MeetingInstructionStatusV03 *-- "1..1" MeetingReference4 : MeetingReference
MeetingInstructionStatusV03 *-- "1..1" IPartyIdentification9Choice : ReportingParty
MeetingInstructionStatusV03 *-- "1..1" SecurityIdentification11 : SecurityIdentification
MeetingInstructionStatusV03 *-- "1..1" IInstructionTypeStatus1Choice : InstructionTypeStatus

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

Identification building block

Identifies the meeting instruction status 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

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

ReportingParty building block

Party reporting the status. 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 securities 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

InstructionTypeStatus building block

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

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

InstructionTypeStatus1Choice members

Member name Description Data Type / Multiplicity

Extensibility and generalization considerations

To facilitate generalized design patterns in the system, the MeetingInstructionStatusV03 implementation follows a specific implementaiton pattern. First of all, MeetingInstructionStatusV03 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, MeetingInstructionStatusV03Document implements IOuterDocument. Because MeetingInstructionStatusV03 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type MeetingInstructionStatusV03.

classDiagram
    class IOuterRecord
    MeetingInstructionStatusV03 --|> IOuterRecord : Implements
    MeetingInstructionStatusV03Document --|> IOuterDocument~MeetingInstructionStatusV03~ : Implements
    class IOuterDocument~MeetingInstructionStatusV03~ {
        MeetingInstructionStatusV03 Message
     }

Document wrapper for serialization

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

classDiagram
    MeetingInstructionStatusV03Document *-- MeetingInstructionStatusV03 : 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.03">
    <MtgInstrSts>
        <Id>
            <!-- Identification inner content -->
        </Id>
        <InstrTp>
            <!-- InstructionType inner content -->
        </InstrTp>
        <MtgRef>
            <!-- MeetingReference inner content -->
        </MtgRef>
        <RptgPty>
            <!-- ReportingParty inner content -->
        </RptgPty>
        <SctyId>
            <!-- SecurityIdentification inner content -->
        </SctyId>
        <InstrTpSts>
            <!-- InstructionTypeStatus inner content -->
        </InstrTpSts>
    </MtgInstrSts>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_TqDxVdEwEd-BzquC8wXy7w_1419808465"
  nextVersions="_TqXTUNEwEd-BzquC8wXy7w_99042676"
  previousVersion="_Tpw2YNEwEd-BzquC8wXy7w_322491691"
  name="MeetingInstructionStatusV03"
  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."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="MtgInstrSts"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <constraint
    xmi:id="_TqNiUdEwEd-BzquC8wXy7w_1051073169"
    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="_TqNiVNEwEd-BzquC8wXy7w_1583021114"
    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="_TqNiV9EwEd-BzquC8wXy7w_-1094860805"
    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="_TqDxVtEwEd-BzquC8wXy7w_800896967"
    name="Identification"
    definition="Identifies the meeting instruction status message."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Id"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_TqDxV9EwEd-BzquC8wXy7w_163995952"
    name="InstructionType"
    definition="Type of instruction."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="InstrTp"
    complexType="_RCWL1Np-Ed-ak6NoX_4Aeg_869239445" />
  <messageBuildingBlock
    xmi:id="_TqDxWNEwEd-BzquC8wXy7w_-1804950275"
    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="_TqDxWdEwEd-BzquC8wXy7w_-2052453533"
    name="ReportingParty"
    definition="Party reporting the status."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="RptgPty"
    complexType="_QRUXhtp-Ed-ak6NoX_4Aeg_967984948" />
  <messageBuildingBlock
    xmi:id="_TqDxWtEwEd-BzquC8wXy7w_-1766163547"
    name="SecurityIdentification"
    definition="Identifies the securities for which the meeting is organised."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="SctyId"
    complexType="_TBKB89p-Ed-ak6NoX_4Aeg_-524266634" />
  <messageBuildingBlock
    xmi:id="_TqNiUNEwEd-BzquC8wXy7w_1193457913"
    name="InstructionTypeStatus"
    definition="Type of instruction status."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="InstrTpSts"
    complexType="_RCWL19p-Ed-ak6NoX_4Aeg_1310681941" />
  <messageDefinitionIdentifier
    businessArea="seev"
    messageFunctionality="006"
    flavour="001"
    version="03" />
</messageDefinition>

ISO Building Blocks

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