Solution

Corporate Actions Monitor

For asset servicing, custody, and investment operations teams: every announcement normalized, cross-checked, and built into one validated golden copy.

ISO 15022/20022 messagesExchange noticesProspectusesVendor feedsCustodian emails
One validated golden copy per eventField-level lineage to each sourceEvery conflict human-approved

The problem

Why this exists

4+ sources

Announcements that disagree

SWIFT messages, vendor feeds, exchange PDFs, and custodian emails describe the same event differently — and someone has to establish the truth.

Hard deadlines

Voluntary events won't wait

Election deadlines tick down while analysts cross-reference sources by hand. A missed cutoff is a direct financial liability.

2× volume

Season breaks the desk

Dividend and proxy season doubles workload overnight, and the usual fix is temporary staff doing the riskiest work on the calendar.

The product, not a promise

A golden copy you can interrogate

Corporate Actions Monitor — workspace
Rights issue normalized — four sources ingestedcited
Ex-date agreed across all sourcesMatchedcited
Subscription ratio differs between vendor feed and prospectusverify
Narrative terms checked against prospectusVerifiedcited
Election deadline for voluntary eventTrackedcited
HUMAN-APPROVED BEFORE IT POSTS

How it works

File in. Answer out.

  1. 1

    Ingest

    Announcements arrive from SWIFT messages, vendor feeds, exchange PDFs, and custodian emails.

  2. 2

    Normalize

    Each announcement is parsed into a common event structure — dates, ratios, options, terms.

  3. 3

    Compare

    Sources are checked against each other field by field; discrepancies are isolated.

  4. 4

    Validate

    Dates, ratios, and narrative terms are verified, and a confidence-scored master record is built.

  5. 5

    Route

    Conflicting or low-confidence events go to a senior analyst; clean events flow straight through.

Who it's for

Built for the people who own the outcome

Corporate actions analyst

Judgment work only — the reconciliation does itself.

  • Sources compared field by field before you open the event
  • Conflicts arrive isolated, versions side by side
  • Standard mandatory events process touchless

Head of asset servicing

Seasonal spikes without seasonal staffing.

  • Dividend and proxy season absorbed by the platform
  • One golden copy feeding desks, risk, and client reporting
  • Every conflicted event approved by a named analyst

Risk & audit

Field-level lineage on every event.

  • Any date or ratio traceable to its source announcement
  • Validation and approval history kept per event
  • Audit trail produced by processing, available immediately
CustodiansAsset managersPrime brokersFund administratorsBroker-dealersWealth platforms
One recordvalidated golden copy per event
Field-levellineage back to each source
Touchlessprocessing for standard events
Human-approvedevery conflicting event

Corporate action announcements arrive as ISO 15022/20022 messages, vendor feeds, exchange PDFs, and custodian emails — and they routinely disagree with each other. Analysts burn hours cross-referencing sources to establish the truth while election deadlines on voluntary events tick down.

One validated record per event

This solution ingests every channel, normalizes each announcement into a common event structure, and compares sources field by field. Where sources agree, the validated master record — the golden copy — builds itself. Where they conflict, the discrepancy is isolated and routed to a senior analyst with every version presented side by side. Standard mandatory events process touchless; analyst time goes only to the events that genuinely need judgment, and every one of those calls is human-approved before it moves downstream.

Complex events are where manual processing hurts most. A misread ratio on a rights issue, a missed deadline on a Dutch auction or spin-off — each is a direct financial liability. The platform validates dates, checks ratios, and reads the narrative text of announcements against prospectus terms, flagging anything that deviates from the historical pattern for that event type.

Lineage down to the field

Every field in the master record carries lineage to the source document that supplied it, so an auditor — or a doubtful trader — can trace any date or ratio back to the original announcement in seconds. The same validated record feeds trading desks, risk teams, and client reporting at the same time, replacing the copy-paste chains that let versions drift. Seasonal spikes in dividend and proxy season are absorbed by the platform rather than by temporary staff, and the audit trail is a by-product of normal operation, ready the moment anyone asks.

Objections, answered

What teams ask us first

How do I trust the golden copy?

Every field carries lineage to the source announcement that supplied it, and any field where sources disagree is isolated and routed to a senior analyst rather than silently chosen. Consensus builds the record; conflict summons a person.

Does it fit our event taxonomy and controls?

Event structures, validation rules, and routing thresholds are configured to your operating model. The platform reads ISO 15022/20022 alongside unstructured sources like exchange PDFs and custodian emails.

What does audit get?

Field-level lineage, the version each source asserted, the validation results, and the named analyst who approved each conflicted event. The trail is a by-product of processing, available the moment an event closes.

How long does deployment take?

Connect the message flows and feeds you already receive; nothing upstream changes. First normalized events flow in days, with validation rules tuned against your live announcement traffic over the following weeks.

Bring your messiest rights issue.

Watch four disagreeing sources become one validated golden copy — with the conflict isolated for your analyst — live in the demo.

Request a demo