seev.006.001.07
Scope The MeetingInstructionStatus message is sent by an intermediary to the sender of an instruction to confirm the status of such an instruction. The message gives the status of a complete message or of one or more specific instructions within the message. The message may also be sent by the issuer or the intermediary to confirm that a vote has been cast. Usage The MeetingInstructionStatus message is used for four purposes. First, it is used to provide a global processing or rejection status of a MeetingInstruction message. Second, it provides the status on the processing of a MeetingInstructionCancellationRequest message, for example, whether the request message is rejected or accepted. Third, it is used to provide a detailed processing or rejection status of one or more instructions within the MeetingInstruction message, for example, for each instruction in the MeetingInstruction message the processing or rejection status is individually reported by using the SingleInstructionIdentification element. This identification allows the receiver of the status message to link the status confirmation to its original instruction. Fourth, it is used to confirm that the related vote instruction has been confirmed as cast by the issuer or its agent. 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
%% MeetingInstructionStatusV07 recursion level 0 with max 0
MeetingInstructionStatusV07 *-- "1..1" IInstructionType2Choice : InstructionType
MeetingInstructionStatusV07 *-- "1..1" MeetingReference10 : MeetingReference
MeetingInstructionStatusV07 *-- "1..1" SecurityIdentification19 : FinancialInstrumentIdentification
MeetingInstructionStatusV07 *-- "1..1" IInstructionTypeStatus4Choice : InstructionTypeStatus
MeetingInstructionStatusV07 *-- "1..1" IPartyIdentification226Choice : ConfirmingParty
MeetingInstructionStatusV07 *-- "1..1" IPartyIdentification226Choice : VoteCastingParty
MeetingInstructionStatusV07 *-- "0..250" IPartyIdentification233Choice : RightsHolder
MeetingInstructionStatusV07 *-- "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 %% IInstructionType2Choice recursion level 0 with max 1
InstructionType2Choice members
| Member name | Description | Data Type / Multiplicity |
|---|
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 |
InstructionTypeStatus building block
Type of instruction status. Choice of instruction type status. For comparison, see the ISO20022 official specification
classDiagram direction tb %% IInstructionTypeStatus4Choice recursion level 0 with max 1
InstructionTypeStatus4Choice members
| Member name | Description | Data Type / Multiplicity |
|---|
ConfirmingParty building block
Party that confirms the receipt of the vote cast. Identification of a party. For comparison, see the ISO20022 official specification
classDiagram direction tb %% IPartyIdentification226Choice recursion level 0 with max 1
PartyIdentification226Choice members
| Member name | Description | Data Type / Multiplicity |
|---|
VoteCastingParty building block
Party that cast the voting ballot. Identification of a party. For comparison, see the ISO20022 official specification
classDiagram direction tb %% IPartyIdentification226Choice recursion level 0 with max 1
PartyIdentification226Choice members
| Member name | Description | Data Type / Multiplicity |
|---|
RightsHolder building block
Owner of the voting rights. Identification of a party. For comparison, see the ISO20022 official specification
classDiagram direction tb %% IPartyIdentification233Choice recursion level 0 with max 1
PartyIdentification233Choice members
| Member name | Description | Data Type / Multiplicity |
|---|
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 MeetingInstructionStatusV07 implementation follows a specific implementaiton pattern. First of all, MeetingInstructionStatusV07 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, MeetingInstructionStatusV07Document implements IOuterDocument. Because MeetingInstructionStatusV07 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type MeetingInstructionStatusV07.
classDiagram
class IOuterRecord
MeetingInstructionStatusV07 --|> IOuterRecord : Implements
MeetingInstructionStatusV07Document --|> IOuterDocument~MeetingInstructionStatusV07~ : Implements
class IOuterDocument~MeetingInstructionStatusV07~ {
MeetingInstructionStatusV07 Message
}
Document wrapper for serialization
The only real purpose MeetingInstructionStatusV07Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:seev.006.001.07’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using MeetingInstructionStatusV07.ToDocument() method. The returned MeetingInstructionStatusV07Document value will serialize correctly according to ISO 20022 standards.
classDiagram
MeetingInstructionStatusV07Document *-- MeetingInstructionStatusV07 : 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.07">
<MtgInstrSts>
<InstrTp>
<!-- InstructionType inner content -->
</InstrTp>
<MtgRef>
<!-- MeetingReference inner content -->
</MtgRef>
<FinInstrmId>
<!-- FinancialInstrumentIdentification inner content -->
</FinInstrmId>
<InstrTpSts>
<!-- InstructionTypeStatus inner content -->
</InstrTpSts>
<CnfrmgPty>
<!-- ConfirmingParty inner content -->
</CnfrmgPty>
<VoteCstgPty>
<!-- VoteCastingParty inner content -->
</VoteCstgPty>
<RghtsHldr>
<!-- RightsHolder inner content -->
</RghtsHldr>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</MtgInstrSts>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_sV77IfEkEeqRfth943bvEA"
nextVersions="_lKgSZxrdEeyhRdHRjakS2w"
previousVersion="_yXBbd6yREemMosWmlQ33EA"
name="MeetingInstructionStatusV07"
definition="Scope
The MeetingInstructionStatus message is sent by an intermediary to the sender of an instruction to confirm the status of such an instruction. The message gives the status of a complete message or of one or more specific instructions within the message.
The message may also be sent by the issuer or the intermediary to confirm that a vote has been cast.
Usage
The MeetingInstructionStatus message is used for four purposes.
First, it is used to provide a global processing or rejection status of a MeetingInstruction message.
Second, it provides the status on the processing of a MeetingInstructionCancellationRequest message, for example, whether the request message is rejected or accepted.
Third, it is used to provide a detailed processing or rejection status of one or more instructions within the MeetingInstruction message, for example, for each instruction in the MeetingInstruction message the processing or rejection status is individually reported by using the SingleInstructionIdentification element. This identification allows the receiver of the status message to link the status confirmation to its original instruction.
Fourth, it is used to confirm that the related vote instruction has been confirmed as cast by the issuer or its agent.
This message definition is intended for use with the Business Application Header (BAH)."
registrationStatus="Registered"
messageSet="_urpIICeJEeOCeO5e7islRQ"
xmlTag="MtgInstrSts"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<constraint
xmi:id="_sV77I_EkEeqRfth943bvEA"
nextVersions="_lKgSaRrdEeyhRdHRjakS2w"
previousVersion="_yXBbeayREemMosWmlQ33EA"
name="Status1Rule"
definition="If InstructionType/InstructionIdentification is present, then InstructionTypeStatus/InstructionStatus must be present."
registrationStatus="Provisionally Registered"
expression="<RuleDefinition><ComplexRule xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ComplexRule"><mustBe><connector>AND</connector><BooleanRule xsi:type="Presence"><leftOperand>/InstructionTypeStatus/InstructionStatus[*]</leftOperand></BooleanRule></mustBe><onCondition><connector>AND</connector><BooleanRule xsi:type="Presence"><leftOperand>/InstructionType/InstructionIdentification</leftOperand></BooleanRule></onCondition></ComplexRule></RuleDefinition>" />
<constraint
xmi:id="_sV77JfEkEeqRfth943bvEA"
nextVersions="_lKgSaxrdEeyhRdHRjakS2w"
previousVersion="_yXBbe6yREemMosWmlQ33EA"
name="Status2Rule"
definition="If InstructionType/InstructionCancellationIdentification is present, then InstructionTypeStatus/CancellationStatus must be present."
registrationStatus="Provisionally Registered"
expression="<RuleDefinition><ComplexRule xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ComplexRule"><mustBe><connector>AND</connector><BooleanRule xsi:type="Presence"><leftOperand>/InstructionTypeStatus/CancellationStatus</leftOperand></BooleanRule></mustBe><onCondition><connector>AND</connector><BooleanRule xsi:type="Presence"><leftOperand>/InstructionType/InstructionCancellationIdentification</leftOperand></BooleanRule></onCondition></ComplexRule></RuleDefinition>" />
<messageBuildingBlock
xmi:id="_sV77K_EkEeqRfth943bvEA"
nextVersions="_lKgScRrdEeyhRdHRjakS2w"
previousVersion="_yXBbf6yREemMosWmlQ33EA"
name="InstructionType"
definition="Type of instruction."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="InstrTp"
complexType="_5chpEbmwEemdEs93hOkPKA" />
<messageBuildingBlock
xmi:id="_sV77LfEkEeqRfth943bvEA"
nextVersions="_lKgScxrdEeyhRdHRjakS2w"
previousVersion="_yXBbgayREemMosWmlQ33EA"
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="_sV77L_EkEeqRfth943bvEA"
nextVersions="_lKgSdRrdEeyhRdHRjakS2w"
previousVersion="_yXBbg6yREemMosWmlQ33EA"
name="FinancialInstrumentIdentification"
definition="Security for which the meeting is organised."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="FinInstrmId"
complexType="_ho6XQYlXEeWPSZi0kAOXhg" />
<messageBuildingBlock
xmi:id="_sV77MfEkEeqRfth943bvEA"
nextVersions="_lKgSdxrdEeyhRdHRjakS2w"
previousVersion="_yXBbhayREemMosWmlQ33EA"
name="InstructionTypeStatus"
definition="Type of instruction status."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="InstrTpSts"
complexType="_ay2uYfNfEeqRfth943bvEA" />
<messageBuildingBlock
xmi:id="_sV77M_EkEeqRfth943bvEA"
nextVersions="_lKgSeRrdEeyhRdHRjakS2w"
previousVersion="_meGP0K-iEemJ1NnLPsTFaw"
name="ConfirmingParty"
definition="Party that confirms the receipt of the vote cast."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="CnfrmgPty"
complexType="_nbVCM6-kEemJ1NnLPsTFaw" />
<messageBuildingBlock
xmi:id="_sV77NfEkEeqRfth943bvEA"
nextVersions="_lKgSexrdEeyhRdHRjakS2w"
previousVersion="_UojDMK-lEemJ1NnLPsTFaw"
name="VoteCastingParty"
definition="Party that cast the voting ballot."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="VoteCstgPty"
complexType="_nbVCM6-kEemJ1NnLPsTFaw" />
<messageBuildingBlock
xmi:id="_sV77N_EkEeqRfth943bvEA"
nextVersions="_lKgSfRrdEeyhRdHRjakS2w"
previousVersion="_fWGLAK-lEemJ1NnLPsTFaw"
name="RightsHolder"
definition="Owner of the voting rights."
registrationStatus="Provisionally Registered"
maxOccurs="250"
minOccurs="0"
xmlTag="RghtsHldr"
complexType="_6264AfQ0EeqAradXpAelDQ" />
<messageBuildingBlock
xmi:id="_sV77OfEkEeqRfth943bvEA"
nextVersions="_lKgSfxrdEeyhRdHRjakS2w"
previousVersion="_yXBbh6yREemMosWmlQ33EA"
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="006"
flavour="001"
version="07" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.