seev.008 — Meeting Vote Execution Confirmation
The effective post-meeting confirmation of vote execution. The voting agent attests that every vote of the registered holder was indeed presented during the AGM/EGM and counted in the official results published by the issuer.
Purpose and place in the flow
seev.008 closes the voting loop:
- seev.001 → meeting notice.
- seev.003 → eligibility notified.
- seev.004 → voting instruction submitted.
- seev.008 → executed vote confirmed post-meeting.
The message carries the confirmation that each resolution voted by the investor was indeed presented during the meeting and counted in the official tallies. It's the legal record of the vote, required in case of disputes (shareholder litigation, SEC request, forensic audit).
For votes executed at < 100% of eligibility (partial voting case or proxy weighting), seev.008 details the effectively voted portion vs eligible.
XML structure
- Id — unique confirmation identifier.
- MtgRef — meeting reference.
- AcctDtls / EligPosId — registered holder account details.
- VoteInstrId — voting instruction reference (original seev.004).
- VoteExctn — Vote Execution: date, status, and SnglInstrExctn (repeating) with label, executed vote, count.
Key fields
VoteInstrId— original seev.004 reference.VoteExctn/ExctnDtTm— exact execution date / time.VoteExctn/ExctnSts/Cd— EXEC (executed), PNDG (pending), RJCT (rejected — vote not counted).SnglInstrExctn/IssrLabl— resolution label.SnglInstrExctn/ExctnVote/Cd— vote effectively counted (may differ from seev.004 on reject or correction).SnglInstrExctn/VoteCnt— number of votes effectively counted.
XML example
Post-AGM Apple 12 April 2026 confirmation: the 5,000 John Smith Family Trust votes were executed as requested (FOR on RESOL-001, AGNS on 002, ABST on 003):
<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:seev.008.001.06">
<MtgVoteExctnConf>
<Id>VOTEEXCT-AAPL-2026-001</Id>
<MtgRef>
<MtgId>AAPL-AGM-2026</MtgId>
<IssrMtgId>APPLE-AGM-2026-MARCH</IssrMtgId>
<MtgDtAndTm>2026-04-12T10:00:00Z</MtgDtAndTm>
<Tp><Cd>AGM</Cd></Tp>
</MtgRef>
<FinInstrmId>
<ISIN>US0378331005</ISIN>
</FinInstrmId>
<AcctDtls>
<AcctOwnr>
<Id>
<AnyBIC><AnyBIC>BNPAFRPP</AnyBIC></AnyBIC>
</Id>
</AcctOwnr>
<SfkpgAcct><Id>BNPPSAFEKEEP-NYSE-001</Id></SfkpgAcct>
<EligPosId>EP-AAPL-AGM-2026-001</EligPosId>
</AcctDtls>
<VoteInstrId>MTGINSTR-AAPL-2026-001</VoteInstrId>
<VoteExctn>
<ExctnDtTm>2026-04-12T11:30:00Z</ExctnDtTm>
<ExctnSts>
<Cd>EXEC</Cd>
</ExctnSts>
<SnglInstrExctn>
<IssrLabl>RESOL-001</IssrLabl>
<ExctnVote><Cd>FOR</Cd></ExctnVote>
<VoteCnt>5000</VoteCnt>
</SnglInstrExctn>
<SnglInstrExctn>
<IssrLabl>RESOL-002</IssrLabl>
<ExctnVote><Cd>AGNS</Cd></ExctnVote>
<VoteCnt>5000</VoteCnt>
</SnglInstrExctn>
<SnglInstrExctn>
<IssrLabl>RESOL-003</IssrLabl>
<ExctnVote><Cd>ABST</Cd></ExctnVote>
<VoteCnt>5000</VoteCnt>
</SnglInstrExctn>
</VoteExctn>
</MtgVoteExctnConf>
</Document> VoteInstrId = MTGINSTR-AAPL-2026-001— original seev.004 reference.VoteExctn/ExctnDtTm— executed during the AGM (12 April at 11:30).VoteExctn/ExctnSts/Cd = EXEC— vote effectively counted.- Three
SnglInstrExctndetail each resolution with its effective count (5,000 = full match).
Common pitfalls
- Divergent VoteInstrId — without seev.004 matching, the investor cannot verify their vote was executed.
- ExctnVote ≠ VoteInstr/Cd — if execution differs from instruction (correction or partial reject case), the reason must be documented in narrative. Otherwise dispute.
- Unjustified partial VoteCnt — if VoteCnt < VoteEntmnt (see seev.003), explain the reason (shares sold between record date and execution, for example).
- No seev.008 for rejected vote — even a rejected vote needs an explicit seev.008 (with ExctnSts = RJCT and reason). Absence = incomplete audit.
- Timing too late — beyond 5 days, compliance escalation. Voting agents that voluntarily delay risk SRD II sanctions.