SD-12.12 — Proxy Voting & Stewardship Operations

Business Domain: BD-12 Investment Operations & Servicing (Back office) · Applies: PUB

Purpose

Operates the proxy-voting process and supports the firm’s active stewardship — processing meeting ballots, applying the voting policy, executing votes, and maintaining the record of voting and engagement. Holding listed equity carries a voting right, and stewardship codes increasingly expect that right to be exercised deliberately and the exercise disclosed. SD-12.12 is the operational capability behind that. It exists because proxy voting is a real, deadline-driven operational flow with a material governance dimension — and because it has a hard interaction with securities lending that has to be managed. It is not the capture of the meeting event — SD-12.6 captures a shareholder meeting as a seev-family event; SD-12.12 votes it — and it is not the recall of a lent security — SD-12.13 executes recall; SD-12.12 is the voting decision that triggers a recall. SD-12.12 owns the vote and the engagement record; SD-12.6 owns the meeting event; SD-12.13 owns the loan book.

Service Operations

Ballot processing — receive and process meeting ballots and agendas against the firm’s holdings as at the meeting record date.
Voting-policy application — apply the firm’s voting policy (and, where used, a proxy adviser’s recommendation) to each resolution, generating the recommended vote.
Vote execution — submit the vote instruction through the voting agent or platform, against the voting deadline, and confirm it was lodged.
Share-recall coordination — identify holdings out on loan that the firm intends to vote, and instruct SD-12.13 Securities Lending Operations to recall them before the record date.
Engagement tracking — maintain the record of stewardship engagement with investee issuers — meetings, letters, escalation — alongside the voting record.
Vote and engagement disclosure — produce the voting record and stewardship-activity disclosure the firm publishes under the applicable stewardship code.
Conflict and split-vote handling — manage conflicts of interest in voting, and split votes where holdings are held across portfolios with differing instructions.

Inputs and outputs

Inputs: meeting events from SD-12.6 (PB-07, meeting events); holdings as at the record date from SD-12.1; the loan book from SD-12.13 (which holdings are lent); the firm’s voting policy and any proxy-adviser recommendations.
Outputs: lodged votes, recall instructions, the voting record and the stewardship-engagement record — consumed by SD-12.13 Securities Lending Operations (recall instructions), SD-16.2 Owner & Investor Reporting (the voting and stewardship disclosure), SD-16.5 Sustainability & Stewardship Governance, and SD-13.9 ESG & Sustainability Data (engagement feeds the ESG record).

Entities

Consumes: PB-07 Corporate Action (meeting events), E-04 Holding / Position (book = ibor — the live voting position as at the record date), E-01 Legal Entity (the investee issuer), E-03 Portfolio / Mandate; the SD-12.1 holdings as at the record date; the SD-12.13 loan book; the SD-12.6 meeting events.
Owns: PB-11 Proxy Vote — one vote record per (meeting, resolution, portfolio), carrying the recommendation, the cast vote, the rationale and the conflict flag, for stewardship-code disclosure. The meeting event remains PB-07 (owned by SD-12.6); the holding is owned by the book-of-record domains. A stewardship engagement — a free-form, multi-interaction case record — is not an entity; it is carried as Document Metadata (E-15) and classification.

Standards

Stewardship codes — the UK Stewardship Code and equivalent codes in other markets — set the expectation that voting rights are exercised and the exercise disclosed; they are the reason this is a named Service Domain rather than a custodian black box.
ISO 20022 securities-events (seev) family — the meeting-notification and vote-instruction messages (the meeting and proxy-voting sub-set of seev).
The hard record-date discipline — a security must be held (and, if lent, recalled) by the record date to be voted — is the operational constraint that links SD-12.12 to SD-12.13.

Open extensions

The Service-Operation-level input/output contracts.
The split-vote sub-model on PB-11 — the rules by which a firm’s vote is split across portfolios and mandates.
The recall-decision sub-model — the cost / benefit test of recalling a lent holding to vote it, the SD-12.12 / SD-12.13 interface.