SD-12.6 — Corporate Actions Processing

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

Purpose

Processes the events an issuer initiates on its own securities — dividends, splits, mergers, rights issues, tender offers — capturing each event, validating it against the firm’s holdings, running the election where the holder has a choice, and calculating the entitlement. A corporate action is the issuer acting; the investor is a passive recipient or, for voluntary events, a choosing one. SD-12.6 is the capability that processes that flow. It exists because a corporate action is not a trade — it is not executed, has no counterparty, and its terms and timing are set by the issuer — and it carries a hard date discipline and an election deadline that a missed step turns into a real loss. It is not income receipt — when a dividend’s cash actually arrives, booking it is SD-12.7 — and it is not proxy voting — a shareholder meeting is captured here as an event, but the vote is SD-12.12. SD-12.6 processes the corporate event through to its terms; SD-12.7 receives the cash; SD-12.12 votes the meeting. SD-12.6 also monitors and files securities class-action and litigation-recovery claims: a settlement is not an issuer event, but it is an entitlement event against a holding, monitored and filed on the same operational rails, so it sits here rather than warranting a thin Service Domain of its own.

Service Operations

Event capture and validation — capture each announced corporate action from data feeds and custodian announcements, and validate it (and, where sources disagree, reconcile them) against the affected holdings.
Key-date management — manage the four-date calendar — announcement, ex-date, record date, payment date — plus the election deadline, that governs every event’s entitlement and timing.
Entitlement calculation — calculate each portfolio’s entitlement — cash, securities, or both — against the holding as at the record date, not the processing date.
Election processing — for voluntary and mandatory-with-choice events, capture the holder’s election per portfolio against the election deadline, apply the default where no election is made, and submit the instruction to the custodian.
Mandatory-event processing — apply mandatory events — splits, mandatory mergers, mandatory redemptions — automatically to the affected positions.
Outcome posting — post the event outcome: a position change for a securities event, a cash entitlement for a cash event, an instrument change for a merger or name change, each as a Transaction and, where cash moves, a Cash Flow Event.
Complex-event handling — process multi-leg events — mergers with cash-and-stock consideration, spin-offs with cost-basis apportionment — and the cost-basis consequences they carry.
Securities class-action monitoring and claims filing — monitor securities class-action, antitrust and other litigation-settlement events against the funds’ and portfolios’ holdings, file the proof of claim within the bar date, and collect the recovery. A settlement is an entitlement event against a holding — monitored, validated against the affected positions, and filed on the same operational rails as a corporate action — and is commonly outsourced to a specialist claims administrator or the global custodian and overseen through SD-12.16; pursuing a recoverable claim is a recognised fiduciary duty.

Inputs and outputs

Inputs: corporate-action data feeds and custodian announcements via SD-13.4 Market & Reference Data Management; the firm’s holdings from SD-12.1; the instrument master from SD-13.1.
Outputs: processed corporate-action events, calculated entitlements and posted position / instrument changes — consumed by SD-12.7 Income & Distribution Processing (cash dividends and coupons through to receipt), SD-12.1 IBOR and SD-12.2 ABOR (the position and instrument effects), SD-12.12 Proxy Voting & Stewardship Operations (meeting events), SD-05.2 Portfolio Management & Monitoring, and SD-13.1 Instrument & Security Master (instrument-changing events).

Entities

Consumes: E-04 Holding / Position (book = ibor — entitlement is calculated against the live IBOR position as at the record date), E-02 Instrument / Asset, E-03 Portfolio / Mandate, PB-08 Income Schedule (the expected dividend / coupon a declared event confirms); the SD-12.1 firm’s holdings; the SD-13.1 instrument master; corporate-action data feeds and custodian announcements via SD-13.4 Market & Reference Data Management.
Owns: PB-07 Corporate Action — SD-12.6 is the authoritative source for the corporate-action event, its key-date calendar, and the election (currently held as an attribute set).
Open question: PB-07 flags the election for promotion to its own sub-entity — one election per (event, portfolio) — and an explicit entitlement-calculation sub-model. Both bear directly on this Service Domain.

Standards

ISO 20022 securities-events (seev) family — the corporate-action announcement, entitlement, instruction and confirmation messages; and the legacy ISO 15022 MT56x corporate-action messages.
The mandatory / voluntary / mandatory-with-choice classification and the four-date key-date calendar are the market-standard corporate-actions model, common across data vendors and custodians.
Corporate-actions processing is the area where messaging-standard adoption most directly reduces operational risk; the seev family is the current target standard.

Open extensions

The Service-Operation-level input/output contracts.
The election promoted to its own sub-entity, and the explicit entitlement-calculation sub-model — the open questions on PB-07.
The handling of cost-basis apportionment for spin-offs and cash-and-stock mergers.