Corporate Actions Automation for Global Custody Operations
Turning Announcements Into Entitlements Without Losing Money in the Middle
Corporate actions processing is the part of post-trade that resisted automation longest, and the reason is not technical conservatism. An announcement arrives as prose, sometimes in a language other than the one your operations team reads, from several sources that do not agree on the ratio or the dates. Rules differ by market. Many events require a client decision before a deadline set by an intermediary who set it earlier than the market's own. And a mistake at any point is a direct financial loss to a client rather than a processing delay.
That combination is why corporate actions automation pays disproportionately. The manual effort is high, the error cost is direct, and a meaningful share of the losses are quietly absorbed as operational cost rather than reported as anything.
What makes this genuinely hard?
Unstructured announcements, disagreeing sources, market-specific rules, client decisions against deadlines, and long intermediary chains.
| Difficulty | Consequence |
|---|---|
| Announcements arrive as text with varying formats | Manual interpretation and re-keying |
| Multiple data sources disagree on terms | Wrong terms propagate into entitlements |
| Market practice differs by jurisdiction | One rule set cannot serve a global book |
| Events require client elections with deadlines | Time pressure and default risk |
| Long chains of intermediaries | Each hop adds an earlier deadline and a re-keying risk |
| Amendments and cancellations arrive late | Recalculation after notification has gone out |
| Tax treatment varies by holder and market | Documentation-driven, not computable alone |
| Fractional entitlements | Rounding decisions with client impact |
Where do the losses actually occur?
Missed deadlines, incorrect entitlements, unclaimed compensation, and unreclaimed tax.
Those four categories account for most of the financial damage, and only the first is usually visible as an incident. Incorrect entitlements get discovered on reconciliation, market claims go unpursued because nobody owns them, and withholding tax reclaim is left because the documentation effort exceeds the perceived benefit per event. Quantify all four before designing a programme, because the business case is frequently much stronger than the manual effort saving alone suggests.
Do you know the annual value of unreclaimed tax and unpursued market claims across your book?
What does the processing chain look like?
Ten stages, with automation potential varying sharply between them.
| Stage | Purpose | Automation potential |
|---|---|---|
| Announcement capture | Ingest from depositaries, vendors, issuers, agents | High, with extraction |
| Scrubbing and golden record | Reconcile sources into one authoritative event | High, with exception workflow |
| Eligibility determination | Which holdings are affected | High |
| Entitlement calculation | What each holder receives | High, if positions are right |
| Client notification | Inform holders with terms and deadlines | High |
| Election capture | Collect client instructions | High, with assisted exceptions |
| Instruction to market | Submit elections upstream | High, with messaging |
| Settlement and posting | Receive and allocate proceeds | High |
| Reconciliation | Confirm expected against actual | High |
| Market claims and compensation | Pursue and settle differences | Moderate, needs ownership |
The bottleneck is almost never the calculation. It is scrubbing, election chasing, and claims, which is where the people are and where the automation should be aimed first.
How do you build the golden record?
By comparing multiple sources, applying documented precedence, and routing discrepancies to a human.
Take feeds from the depositary, one or more commercial data vendors, and where available the issuer or agent, then compare field by field: event type, key dates, ratios, prices, options available, and conditions. Where they agree, proceed automatically. Where they disagree, apply documented precedence rules and route material differences for review, since a difference in a ratio is a client loss waiting to happen. Version every event so an amendment produces a new version rather than an overwrite, and keep the full history, because you will need to explain what you believed on the day you notified clients. The document extraction that makes capture tractable is covered in this guide to financial document intelligence pipelines.
Why is a single source insufficient?
Because sources disagree often enough to matter, and the error becomes yours once you act on it.
Depositary announcements can be incomplete or late, vendor data can contain transcription errors, and issuer communications can be superseded. A single-source process inherits every error without any chance of detection, and the loss lands on your client. Multi-source comparison is the control, and the exception rate it produces is a useful data quality measure on your providers rather than an inconvenience.
How should amendments be handled?
As a new event version with mandatory reassessment of everything already sent.
Amendments arrive after notifications have gone out and sometimes after elections have been received, so the workflow must recalculate entitlements, identify affected clients, decide whether elections remain valid, re-notify with the change made explicit, and reopen the election window where the market permits. Automate the detection and the impact assessment, and keep a human decision on client communication, since the message matters. Record the whole sequence, because an amended event handled badly generates complaints and sometimes claims.
How do you calculate entitlements correctly?
From positions as at the correct record date, including lending, borrowing, and unsettled trades.
Why are securities on loan the classic error?
Because economic entitlement and registered holding diverge, and the calculation must follow the contract.
A holding lent out is not in the account on record date, and the borrower may receive the distribution, with the lender's entitlement handled through a manufactured payment under the lending agreement. Ignore that and you either double-count or under-pay. The same applies to pending settlements around record date, repo positions, and collateral pledged away. The entitlement engine therefore needs a complete economic position view rather than a custody position, and that view has to come from the lending and financing systems, which is the integration described in securities lending and repo platform design. Reconciling pledged and lent positions against records is the same discipline as in this guide to pledged asset reconciliation.
Why must rounding policy be explicit?
Because fractional entitlements arise constantly and different treatments produce different client outcomes.
A one-for-seven bonus issue on an odd holding produces a fraction, and the treatment, rounding down with cash for the remainder, rounding to nearest, or aggregating across clients, changes what each client receives. Document the policy per event type and market, apply it consistently, and disclose it, because an undocumented default becomes an unexplainable difference during a client query. Aggregation across clients in particular needs a clear position, since any benefit arising from aggregation belongs to someone and that question is better answered in advance.
How should elections and deadlines be managed?
With an internal deadline earlier than the market's, a documented default, escalation, and recorded evidence.
Set your client-facing deadline early enough to instruct upstream comfortably, and be explicit that it is your deadline rather than the market's. Define the default action for non-response per event type, communicate it clearly at notification, escalate as the deadline approaches through channels the client actually monitors, and record every notification, reminder, and response with timestamps. When a client misses a deadline and disputes it, that record is the entire basis of your position, and it needs to show what was sent, when, to whom, and what the stated default was. Standing instructions help for repetitive event types and need periodic re-confirmation rather than indefinite persistence.
If a client disputed a missed election, could you produce every notification with timestamps?
How does message standardisation help?
By removing manual interpretation and re-keying between intermediaries.
Structured messaging is what allows an event to pass along a chain without being retyped, and inconsistent implementation is what undermines it. The CPMI's harmonised ISO 20022 data requirements exist because participants implement the same standard differently, and the same lesson applies here: a technically valid message populated inconsistently still requires human interpretation. Adopt the standard properly, populate the fields the same way every time, and treat any re-keying between systems in your own chain as a defect to remove. The data exchange problem across counterparties is well described in this guide to slow data exchange between parties, and asset-level allocation exchange in Modco asset allocation automation.
How do you handle market claims and tax?
As owned workflows with thresholds, not as residual activity.
Market claims arise when entitlement and settlement diverge around record date, and they need a process that detects the difference, values it, raises the claim within market timeframes, and pursues it. Without ownership they simply do not get raised, which is a pure loss. Withholding tax is harder, because entitlement to a treaty rate depends on beneficial ownership, documentation, and market-specific procedures, making reclaim a documentation workflow rather than a calculation. Automate the detection and the case creation, track documentation validity and expiry per client and market, and set a threshold below which pursuit is uneconomic so the decision is deliberate rather than accidental.
How should automation be sequenced?
Capture and scrubbing first, then entitlements, then elections, then claims and tax.
| Phase | Duration | Deliverable |
|---|---|---|
| Multi-source capture and extraction | 3 to 5 months | Automated ingestion with structured extraction |
| Golden record and scrubbing | 3 to 4 months | Comparison, precedence, versioning, exception workflow |
| Economic position integration | 2 to 4 months | Lending, repo, pending settlement included |
| Entitlement engine | 3 to 4 months | Calculation with explicit rounding policy per market |
| Notification and election capture | 3 to 4 months | Structured notification, digital election, evidence trail |
| Upstream instruction messaging | 2 to 3 months | Standard messages, no re-keying |
| Reconciliation and claims | 2 to 3 months | Automated detection, owned pursuit, thresholds |
| Tax reclaim workflow | 3 to 5 months | Documentation tracking, case management, thresholds |
Scrubbing before entitlements is deliberate: a perfectly engineered entitlement calculation on wrong event terms produces confident wrong numbers, which is worse than a manual process that hesitates. The reconciliation mechanics resemble those in nostro and vostro reconciliation automation, and the settlement infrastructure context sits within the CPMI-IOSCO Principles for financial market infrastructures, published in April 2012, which cover central securities depositories and securities settlement systems among other systemically important infrastructures.
Which metrics matter?
Straight-through rate by event type, scrubbing exception rate by source, missed deadlines, entitlement corrections, claims pursued, and tax reclaimed.
Report straight-through processing rate by event type rather than in aggregate, since mandatory cash distributions and complex voluntary events are different problems. Track scrubbing exceptions by source, which doubles as a data quality scorecard on your providers. Count missed election deadlines with cause, treating each as an incident. Report entitlement corrections after notification, because those are client-visible errors. Measure market claims raised versus identified, and tax reclaimed versus reclaimable, since both gaps are recoverable money. And track manual touches per event, which is the operating cost the programme exists to reduce.
Corporate actions is the clearest remaining example in post-trade of a process where manual effort and financial loss travel together. The automation that works starts by trusting no single announcement source, insists on an economic position view that includes lent and pledged securities, and treats election evidence and unclaimed money as first-class rather than residual.
Frequently Asked Questions
Why is corporate actions the least automated part of post-trade?
Because announcements arrive unstructured from multiple sources that disagree, market rules differ, and many events require a client decision against a deadline.
Where do the losses actually occur?
Missed election deadlines, incorrect entitlement calculations, unclaimed market claims, and unreclaimed withholding tax. Most are operational rather than market losses.
Why is trusting a single announcement source insufficient?
Because sources disagree on terms, dates, and ratios, and an error propagated into entitlements becomes a client loss. Comparison across sources is the control.
What is the most common entitlement calculation error?
Ignoring securities on loan or pending settlement. Positions must be evaluated as at the correct record date including lending, borrowing, and unsettled trades.
Why must rounding policy be explicit?
Because fractional entitlements arise constantly and different treatments produce different client outcomes. An undocumented default becomes an unexplainable discrepancy.
How should election deadlines be managed?
With an internal deadline earlier than the market deadline, a documented default action, escalation before expiry, and recorded evidence of what the client was told and when.
How does message standardisation help?
Structured, harmonised messaging reduces manual interpretation and re-keying between intermediaries, which is where most errors and delays are introduced.
What makes tax the hardest part?
Entitlement to treaty rates depends on documentation, beneficial ownership, and market-specific procedures, so reclaim is a documentation workflow rather than a calculation.
