seev.003.001.05
Scope An account servicer sends the MeetingEntitlementNotification to an issuer, its agent, an intermediary or an account owner to advise the entitlement in relation to a shareholders meeting. Usage This message is sent to advise the quantity of securities held by an account owner. The balance is specified for the securities for which the meeting is taking place. This entitlement message is sent by the account servicer or the registrar to an intermediary, the issuer’s agent or the issuer. It is also sent between the account servicer and the account owner or the party holding the right to vote. The message is also used to amend a previously sent MeetingEntitlementNotification. To notify an update, the RelatedReference must be included in the message. 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
%% MeetingEntitlementNotificationV05 recursion level 0 with max 0
MeetingEntitlementNotificationV05 *-- "0..1" MessageIdentification : RelatedReference
MeetingEntitlementNotificationV05 *-- "1..1" MeetingReference7 : MeetingReference
MeetingEntitlementNotificationV05 *-- "1..200" SecurityPosition9 : Security
MeetingEntitlementNotificationV05 *-- "1..1" EligibilityDates1 : Eligibility
MeetingEntitlementNotificationV05 *-- "0..1" SupplementaryData1 : SupplementaryData
Now, we will zero-in one-by-one on each of these building blocks.
RelatedReference building block
Identifies the meeting entitlement message to be modified. Unique and unambiguous identifier for a message, as assigned by the Sender. This unique identifier can be used for cross-referencing purposes in subsequent messages. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% MessageIdentification recursion level 0 with max 1
class MessageIdentification{
Identification IsoMax35Text
}
MessageIdentification members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Identification | String of characters that uniquely identifies a message. | IsoMax35Text - Required 1..1 |
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 |
Security building block
Identifies the security for which the meeting is organised, the account and the positions of the security holder. Identifies the securities for which the meeting is organised. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% SecurityPosition9 recursion level 0 with max 1
SecurityPosition9 *-- "1..1" SecurityIdentification14 : FinancialInstrumentIdentification
SecurityPosition9 *-- "0..1000" EligiblePosition6 : Position
%% SecurityIdentification14 recursion level 1 with max 1
class SecurityIdentification14{
ISIN IsoISINIdentifier
Description IsoMax140Text
}
SecurityIdentification14 *-- "0..0" OtherIdentification1 : OtherIdentification
%% EligiblePosition6 recursion level 1 with max 1
class EligiblePosition6{
AccountIdentification IsoMax35Text
}
EligiblePosition6 *-- "0..1" PartyIdentification71 : AccountOwner
EligiblePosition6 *-- "0..10" HoldingBalance7 : HoldingBalance
EligiblePosition6 *-- "0..10" PartyIdentification71 : RightsHolder
SecurityPosition9 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| FinancialInstrumentIdentification | Identification of the security, as assigned under a formal or proprietary identification scheme. | SecurityIdentification14 - Required 1..1 |
| Position | Amount of securities that are eligible for the vote. | EligiblePosition6 - Collection 0..1000 |
Eligibility building block
Defines the dates determining eligibility. Dates determining the entitlement. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% EligibilityDates1 recursion level 0 with max 1
class EligibilityDates1{
EntitlementFixingDate IsoISODate
}
EligibilityDates1 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| EntitlementFixingDate | Date at which the positions are struck to note which parties will receive the entitlement, e.g. record date, book close date. | IsoISODate - Required 1..1 |
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 MeetingEntitlementNotificationV05 implementation follows a specific implementaiton pattern. First of all, MeetingEntitlementNotificationV05 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, MeetingEntitlementNotificationV05Document implements IOuterDocument. Because MeetingEntitlementNotificationV05 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type MeetingEntitlementNotificationV05.
classDiagram
class IOuterRecord
MeetingEntitlementNotificationV05 --|> IOuterRecord : Implements
MeetingEntitlementNotificationV05Document --|> IOuterDocument~MeetingEntitlementNotificationV05~ : Implements
class IOuterDocument~MeetingEntitlementNotificationV05~ {
MeetingEntitlementNotificationV05 Message
}
Document wrapper for serialization
The only real purpose MeetingEntitlementNotificationV05Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:seev.003.001.05’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using MeetingEntitlementNotificationV05.ToDocument() method. The returned MeetingEntitlementNotificationV05Document value will serialize correctly according to ISO 20022 standards.
classDiagram
MeetingEntitlementNotificationV05Document *-- MeetingEntitlementNotificationV05 : 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.003.001.05">
<MtgEntitlmntNtfctn>
<RltdRef>
<!-- RelatedReference inner content -->
</RltdRef>
<MtgRef>
<!-- MeetingReference inner content -->
</MtgRef>
<Scty>
<!-- Security inner content -->
</Scty>
<Elgblty>
<!-- Eligibility inner content -->
</Elgblty>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</MtgEntitlmntNtfctn>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_xDAOGVtcEeSwKe7KuKvXhg"
nextVersions="_yXBbXayREemMosWmlQ33EA"
previousVersion="_Tme46dEwEd-BzquC8wXy7w_-1564035735"
name="MeetingEntitlementNotificationV05"
definition="Scope
An account servicer sends the MeetingEntitlementNotification to an issuer, its agent, an intermediary or an account owner to advise the entitlement in relation to a shareholders meeting.
Usage
This message is sent to advise the quantity of securities held by an account owner. The balance is specified for the securities for which the meeting is taking place.
This entitlement message is sent by the account servicer or the registrar to an intermediary, the issuer's agent or the issuer. It is also sent between the account servicer and the account owner or the party holding the right to vote.
The message is also used to amend a previously sent MeetingEntitlementNotification. To notify an update, the RelatedReference must be included in the message.
This message definition is intended for use with the Business Application Header."
registrationStatus="Registered"
messageSet="_wRe70U2rEeG_I4xRYCA_7g"
xmlTag="MtgEntitlmntNtfctn"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_xDAOHVtcEeSwKe7KuKvXhg"
nextVersions="_yXBbX6yREemMosWmlQ33EA"
previousVersion="_Tmop4NEwEd-BzquC8wXy7w_1924457442"
name="RelatedReference"
definition="Identifies the meeting entitlement message to be modified."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="RltdRef"
complexType="_Q6l-Cdp-Ed-ak6NoX_4Aeg_1451391033" />
<messageBuildingBlock
xmi:id="_xDAOH1tcEeSwKe7KuKvXhg"
nextVersions="_yXBbYayREemMosWmlQ33EA"
previousVersion="_Tmop4dEwEd-BzquC8wXy7w_-2017625191"
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="_xDAOI1tcEeSwKe7KuKvXhg"
nextVersions="_yXBbY6yREemMosWmlQ33EA"
previousVersion="_Tmop49EwEd-BzquC8wXy7w_-1091429962"
name="Security"
definition="Identifies the security for which the meeting is organised, the account and the positions of the security holder."
registrationStatus="Provisionally Registered"
maxOccurs="200"
minOccurs="1"
xmlTag="Scty"
complexType="_CuyrkVtjEeSwKe7KuKvXhg" />
<messageBuildingBlock
xmi:id="_xDAOJVtcEeSwKe7KuKvXhg"
nextVersions="_yXBbZayREemMosWmlQ33EA"
previousVersion="_Tmop5NEwEd-BzquC8wXy7w_1359668345"
name="Eligibility"
definition="Defines the dates determining eligibility."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Elgblty"
complexType="_TmHJHdp-Ed-ak6NoX_4Aeg_742278644" />
<messageBuildingBlock
xmi:id="_nfrAIVtoEeSwKe7KuKvXhg"
nextVersions="_yXBbZ6yREemMosWmlQ33EA"
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="003"
flavour="001"
version="05" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.