Corporate Actions Automation: From ISO 15022 to Entitlements

Corporate actions are among the most operationally demanding events a securities operations team handles. Every dividend, split, rights issue, or merger triggers a chain of decisions, calculations, and entries that must be completed accurately and on time. When this work is done manually, across spreadsheets and email, it becomes a significant source of operational risk: missed deadlines, miscalculated entitlements, and incorrect postings can all lead to financial loss, client disputes, and regulatory scrutiny. Automating the corporate actions lifecycle is therefore not a convenience but a control imperative.

Why Manual Processing Is Risky and Costly

Corporate actions carry a unique combination of complexity and consequence. The terms of each event are announced by issuers and depositories in their own formats and on their own timelines, and the window to elect, calculate, and settle is often short. A single error in interpreting an event or in calculating who is entitled to what can cascade across thousands of client positions.

• Time Pressure: Record dates, election deadlines, and payment dates leave little room for manual rekeying or reconciliation, and a missed deadline cannot always be reversed.
• Calculation Risk: Entitlements depend on settled positions, ratios, fractional handling, and tax treatment. Manual computation across many holders multiplies the chance of error.
• Financial Exposure: Under- or over-paying clients, or posting to the wrong ledger account, creates direct losses and reconciliation breaks that are expensive to unwind.
• Audit and Control Gaps: Spreadsheet-driven processing rarely leaves a clean, reviewable trail of who calculated, reviewed, and approved each event.

The Corporate Actions Event Taxonomy

Corporate actions span a wide range of event types, each with its own terms and processing rules. A robust operation must be able to handle the full spectrum rather than just the common cases.

• Cash and Share Dividends: Distributions of cash or additional shares to holders, sometimes with an election between the two.
• Stock Splits and Consolidations: Adjustments to the number of shares outstanding that change quantity and price without changing total value.
• Rights Issues: Offers giving existing holders the right to subscribe to new shares, usually at a discount and within a fixed subscription period.
• Spin-offs and Mergers: Events that create new entities or combine existing ones, requiring careful mapping of old positions to new instruments.
• Bond and Sukuk Coupons: Periodic income payments on fixed-income and Islamic instruments, including profit distributions and scheduled coupon dates.
• Redemptions and Maturities: The repayment of principal at maturity or early call, which closes out a position and triggers a final cash movement.

Standardised Messaging and the ISO 15022 Flow

Event information rarely originates inside the firm. It flows in from depositories, custodians, and issuers, and the quality of that inbound data determines the accuracy of everything downstream. This is where standardised messaging matters. The ISO 15022 standard defines a common structured format for corporate action messages, so that an announcement from a depository can be parsed and processed automatically rather than transcribed by hand.

In a typical flow, the depository sends an announcement message notifying the firm that an event has been declared, carrying the event type, key dates, ratios, and options. Operations teams generally know this as the MT564 announcement. Once the event is paid or applied, the depository follows up with a confirmation message, commonly the MT566, evidencing the cash or securities movement that actually took place. Because these messages are structured and standardised, a system can ingest them, recognise the event type, and pre-populate the event record with consistent, machine-readable data. Standardisation removes ambiguity, reduces manual interpretation, and creates a reliable foundation for the entitlement calculation that follows.

Calculating Entitlements and Beneficiaries

Once an event is captured, the central task is determining who is entitled to the benefit and how much each holder should receive. This calculation rests on a few key inputs that must be applied consistently across every affected position.

• Record Date: The date that establishes which holders are entitled to participate. Only positions held as of the record date qualify.
• Settled Positions: Entitlements are normally based on settled holdings rather than pending trades, so the engine must distinguish settled from unsettled quantities.
• Event Terms: Ratios, rates, and prices from the announcement drive the per-holder amount, including how fractional results are rounded or paid.
• Withholding Tax: Many distributions are subject to withholding, which varies by instrument and holder profile and must be deducted to arrive at the net entitlement.

Performing this calculation accurately for a large book of beneficiaries is precisely the kind of repetitive, high-volume work where automation delivers both speed and reliability.

The Draft, Review, Approve, Post Lifecycle

Even with accurate inbound data and a reliable calculation, corporate actions demand strong process controls before any value moves. A disciplined lifecycle ensures that no single person can both create and release an event unchecked. The event moves through clear stages: it is first drafted from the inbound announcement and calculated entitlements; it is then reviewed for correctness against the event terms; it is approved by a separate authorised user; and only then is it posted to client accounts and the general ledger.

This separation of duties is the essence of maker-checker control. The person who prepares an event (the maker) is never the same person who approves it (the checker). The result is a built-in second pair of eyes on every event, a complete and reviewable audit trail of each action and approval, and far less opportunity for an undetected error to reach client books. For events that move real money against thousands of positions, this control is essential.

How ZagTrader Automates the Full Lifecycle

ZagTrader automates corporate actions from end to end. It ingests standardised ISO 15022 messages directly from the depository feed to capture events automatically, runs a beneficiary engine that calculates entitlements from settled positions, record dates, and withholding tax, enforces maker-checker approval at every stage, and posts the resulting movements to client accounts and the general ledger. The outcome is a faster, more accurate, and fully auditable corporate actions process that removes manual risk while keeping operations teams firmly in control.