Corporate Actions Processing Software: Keep the Vendor Platform, or Build the Layer It Leaves You?

When is off the shelf genuinely the right call here?

Buy, and commission nothing, if you are a smaller institution holding mostly domestic securities with predominantly mandatory events. Dividends, stock splits and simple mergers are handled well by any credible platform, and by many custodians as part of the service. If you can push the servicing burden to a custodian who does it properly, that is usually the cheapest correct answer in this category. Building a corporate actions platform to process dividends is spending six figures to automate arithmetic.

Buy the vendor platform regardless of size, because you almost certainly should not replace it. Broadridge, SmartStream, FIS XSP, Gresham and SS&C carry deep event type coverage and message handling that has been shaped by decades of real events across the industry. Recreating that breadth is expensive, slow, and it is the part where packaged systems are strongest. Every one of these is used widely for good reasons and we would tell a client to keep theirs.

The third reason to buy has nothing to do with volume. If nobody in operations will own the reconciliation rules, buy. A build in this category needs a named person who decides which source is authoritative for which market and event type, and who reviews that decision when it turns out to be wrong. Without that, you get a system that flags conflicts nobody resolves, which is the same team doing the same work with more screens.

The honest test is whether you can reconstruct a specific event. Pick one voluntary event from last quarter and try to show who was notified, when, what came back, and what the default action was for holders who never replied. If that takes an hour, you are fine.

When does a custom build actually pay off?

If that reconstruction takes a day, the evidence layer is already costing you more than it would cost to build. That is the single most useful test in this category, and it is the one most firms fail.

Build, alongside a vendor rather than instead of one, when several of these hold. You process more than a couple of hundred voluntary events a year. Your scrub team spends more time reconciling announcement sources than servicing events. You have paid a client compensation for a missed election or an incorrect entitlement in the last two years. You service clients across multiple markets with genuinely different deadline chains.

The underlying reason is structural rather than a criticism of any product. Announcement sources disagree, and not usually through error. Two data vendors, a depository notification and the issuer agent's own document will differ on the record date, the ratio, whether fractions are cashed out, or the election deadline, because terms get amended and because each source normalises differently. Every user of every vendor platform still runs a scrub team. That is the shape of the problem, not a gap somebody forgot to fill.

The second structural reason is that corporate actions is one of the few operations areas where an error converts directly into a payment with no argument available. A tender offer closes, a client with 400,000 shares was not taken out, and the notification went to an email address a relationship manager updated in the customer system three months ago and nowhere else. The compensation is not disputed, because the record shows nothing went out.

How do they compare on the things that matter in this industry?

Compare on the residual work rather than on feature lists, because the feature lists are largely accurate and largely about event types you already handle.

• Announcement versioning. Most implementations flatten sources into one record on arrival. What you want is every source stored separately and versioned, compared field by field, with automatic agreement where all sources match and a queue showing only the disputed fields with sources side by side. Ask any vendor whether an analyst's decision is recorded against the field or against the event.
• Deadline chains. The market deadline is not your deadline. Your client cutoff sits before your custodian's, which sits before the depository's, which sits before the issuer agent's, each with its own buffer and its own market holiday calendar. Off the shelf configuration usually handles a deadline. It rarely handles a chain of them.
• Position states in entitlement. The ratio on a settled long position is arithmetic. The errors live in positions in transit across record date, fails, partial settlements, securities out on loan where the entitlement follows the borrower, multiple share classes, and beneficial owners holding across several accounts where an election minimum applies at one level and not another.
• Market claims. These should be a first class output of the entitlement calculation rather than a follow up task, particularly since the shorter settlement cycle in the United States compressed the window in which trades around record date resolve.
• Intake channels. You build a portal and half your clients use it. The rest email, call, or send a file in their own format. What matters is whether an instruction is one object with several intake paths and identical validation on all of them, or a portal with manual exceptions beside it.
• Amendment handling. Terms change after clients have elected. The system must re-notify affected holders, re-validate instructions and record the sequence, which is impossible if the announcement was overwritten.
• Evidence portability. Disputes surface years later. Ask what the event version history and notification trail look like as an export.

What does total cost of ownership look like at your scale?

From Digital Heroes delivery experience, announcement reconciliation alone, meaning the versioned source store, field by field comparison and the conflict queue, runs $105,000 to $150,000. A first release adding event and deadline chain modelling across your markets, entitlement calculation over real position states and an election workflow with stepped escalation runs $150,000 to $230,000 across sixteen to twenty two weeks. A full platform with client election channels, depository instruction messaging, market claims, tax withholding and relief at source, and accounting and cash postings runs $290,000 to $780,000 phased over ten to eighteen months.

Market coverage is the dominant driver at $25,000 to $60,000 per market, because each brings its own deadline conventions, holiday calendars, fractional treatment, claim mechanics and tax rules. Supporting both ISO 15022 and ISO 20022 adds $30,000 to $70,000. Securities lending adds $25,000 to $55,000. Tax withholding and relief at source adds $35,000 to $90,000 and is a specialism in its own right. Each additional announcement source adds $10,000 to $25,000. A broker dealer servicing roughly 900 events a year across three markets, of which about 260 are voluntary, lands near $188,000 in twenty weeks.

Running costs are higher than most categories at 18 to 24 percent of build a year, because elections have hard deadlines and a defect on the afternoon of a market cutoff is an immediate financial event. Add $8,000 to $20,000 a year for message standard maintenance, $4,000 to $10,000 for holiday calendar and convention upkeep, which is small, boring and the direct cause of the errors that look most careless, and $5,000 to $12,000 for long term evidence retention. Each new market you take on later costs the same $25,000 to $60,000, triggered by client demand rather than by any plan of yours. And your announcement data subscriptions continue permanently, because the build reconciles vendor data rather than replacing it.

What does the hybrid look like, and when is it the honest answer?

Here the hybrid is not a compromise, it is the recommendation for essentially every firm large enough to be reading this. Keep the vendor platform for event type coverage, message handling and depository connectivity. Build the layer it leaves you: announcement source reconciliation, the deadline chain, election intake from every channel your clients actually use, and the evidence trail.

That split works because the boundaries are commercial as well as technical. Vendors have no reason to build deep reconciliation across their competitors' data feeds, and no reason to model your particular custody chain. The gap is permanent by design, which is exactly what makes it worth owning rather than waiting for. It is also the layer that survives if you change vendor later, which is worth real money on its own.

The smallest useful version is announcement reconciliation only, at $105,000 to $150,000, with elections still keyed where they are keyed today. It removes the work that consumes most of your scrub team's week and it proves whether the reconciliation rules will actually be owned. Add the deadline chain and escalation second, because that is where compensation payments come from.

Scope discipline matters more here than in most categories. Cover your top two or three markets by event volume properly and leave the long tail for a phase, because the tail holds the exotic events and it is not where your risk concentrates. Start with voluntary events only, since mandatory events are where your current process already works. Defer tax out of release one. Then run a full quarter through both processes before you rely on the new one.

Which should you choose, by operator size and stage?

Domestic only, mostly mandatory events, under about fifty voluntary events a year: buy, or push servicing to your custodian. A checklist plus your custodian's reporting is a proportionate control.

Domestic, fifty to two hundred voluntary events, one market: keep the vendor platform and fix process rather than software. Agree an explicit default action with every client for every voluntary event, so a non response produces a considered outcome rather than an accident. That is free and it removes a real share of your exposure.

Two hundred or more voluntary events, two to three markets: build the reconciliation and deadline layer. Roughly $150,000 to $230,000 over sixteen to twenty two weeks, alongside whatever you already run. This is the population where the scrub workbook has become the operational system and nobody has admitted it.

Global custodians and broker dealers with international client bases: build through the full platform, phased, and budget for market expansion as a recurring line rather than a project. Securities lending, both message standards and relief at source are each separate operational disciplines, and treating them as features on one list is how these programmes run long.

Any firm that has paid a compensation recently: build the evidence trail first. The cost of a dispute is usually not the entitlement itself, it is the weeks spent proving what was sent and when.

If you would rather scope this before committing budget, Digital Heroes has delivered more than 2,000 projects with a named team you can speak to before you sign, rather than a bench you meet in month two. The document is yours whichever way you go.