What is custodian bank corporate action election testing?

Custodian bank corporate action election testing verifies that a custody system correctly presents eligible securities events to clients, records and validates their choices, submits instructions by the required deadlines, and processes the resulting allocations. It checks the full path from event terms and client holdings through to updated cash and securities positions, including applicable market rules and event-specific defaults.

What custodian bank corporate action election testing covers

A corporate action is an event affecting a security or its holders, such as a rights issue, tender offer or voluntary dividend choice. For an event with elections, the custodian receives event details from a market source or agent, determines which client accounts are eligible, communicates the options, collects instructions and passes accepted elections to the relevant market intermediary.

Testing checks that event terms are interpreted correctly: eligible security and market, option descriptions, election deadlines, response requirements and any default option. It also verifies that entitlements use the right positions and that the system applies account mandates, instruction channels and cut-off times correctly. Requirements can vary by market, event and client agreement, so expected results should come from approved business rules and event specifications.

The downstream result matters as much as instruction capture. The system may receive confirmation that an election was accepted, rejected, changed or scaled. Tests should verify the resulting allocation, including securities, cash and any residual quantities, then reconcile it against the event terms and account records. Where an event is subject to proration, for example, the final allocation may differ from the quantity a client elected.

How to test the election lifecycle

Use linked test cases across the custody platform, client channel, event data feed and downstream processing. Cover valid and invalid instructions, different client accounts, event states and time boundaries. Include cases where an event is amended or cancelled, an instruction is changed, an account becomes ineligible, or a market response arrives after submission.

Check both business outcomes and system controls. A valid instruction should be recorded against the correct event, account and option, with an audit trail showing its source and status. An instruction after the applicable cut-off should follow the documented rule, such as rejection or referral for review. Replayed or duplicate messages should not create duplicate elections or allocations. Where manual review is required, verify the queue, permissions and status changes as well as the eventual outcome.

Testing depends on accurate event terms, representative positions and working interfaces. Environment drift in calendars, market cut-offs or event configuration can make a result misleading. Use controlled test data with known holdings and expected entitlements, and capture the incoming event, client instruction, outbound message, acknowledgement and final position or cash entries as evidence. This is a focused form of corporate action processing testing, with particular attention to client choice and the resulting election.

Practical example

Assume a voluntary event offers eligible holders a cash option or a stock option, and the test account holds 100 eligible shares. Configure the event with its approved deadline, option codes, default treatment and stock allocation terms. Submit an instruction for the stock option for the full eligible quantity before the client cut-off.

Verify that the account is eligible, the choice is accepted once, and the outbound instruction contains the correct account, event, option and quantity. Process an acknowledgement and the resulting allocation. Compare the booked securities and any cash adjustment with the configured event terms, then check the account position and event status. Repeat with an instruction submitted after the deadline and confirm the configured late-instruction outcome. The expected result must reflect the event's actual rules, including any rounding or proration, rather than an assumed universal treatment.

This example can be extended into end-to-end testing in banking when the same event passes through a client portal, custody platform, market interface and accounting records. Validate each boundary as well as the final account state so that a correct screen display cannot conceal a rejected message or incorrect posting.