Lesson 22.5: Election Processing

Where This Lesson Fits

Lesson 22.2 established the theoretical distinction between mandatory and voluntary processing models and introduced election processing as the defining operational obligation of voluntary events. Lessons 22.3 and 22.4 examined mandatory income events and capital structure events in detail. This lesson returns to the voluntary processing model and examines election processing as an operational discipline in its own right — not as a workflow step within a broader mandatory event, but as a complete end-to-end process with its own data requirements, validation logic, deadline constraints, reconciliation obligations, and failure modes.

Election processing is where the voluntary model is most operationally exposed. The risk in mandatory events is processing accuracy — calculating and posting the correct entitlement. The risk in voluntary events is election integrity — ensuring that every account that intended to elect did so correctly, that every valid election was transmitted before the deadline, and that every account without an election received the correct default treatment. These risks require different controls, different monitoring workflows, and different exception management approaches than mandatory event processing.

This lesson provides the operational detail that makes election processing manageable at scale: the complete receipt-to-transmission workflow for individual elections, the monitoring and escalation discipline for managing a population of elections in flight simultaneously, and the post-election reconciliation procedures that confirm the correct outcome for every account regardless of whether it elected or received default treatment.

Lesson Objective

By the end of this lesson, students should be able to describe the complete operational workflow for capturing, validating, tracking, and transmitting client elections for a voluntary corporate action; explain the validation criteria applied to each election at receipt and the disposition of invalid elections; describe how elections are aggregated and transmitted to the custodian or DTC before the deadline; explain how the operations team monitors election receipt status during the election window and manages the pre-deadline follow-up process; define and apply the concept of default treatment and describe how it is applied to non-electing accounts after the election deadline; describe the post-election reconciliation workflow and what it must confirm for both electing and non-electing accounts; and identify the primary election processing failure modes and the controls that prevent each.

Lesson Overview

Election processing is the set of operational activities that transforms a voluntary corporate action announcement — which establishes that holders have a choice to make — into a correctly processed outcome for every account that holds the affected security, whether or not that account submitted an election. The process begins when the announcement is received and the election window opens, and it does not end until the final reconciliation confirms that every account has received the correct outcome: elected consideration for accounts that submitted valid elections, and default consideration for accounts that did not.

At the level of a single election, the process is straightforward: an advisor or client submits an instruction, the operations team validates the instruction against a defined set of criteria, the valid instruction is recorded in the processing system and assigned to the account, and the instruction is included in the aggregated transmission to the custodian before the deadline. The complexity emerges at scale: when 200 accounts hold a security affected by a tender offer, the operations team must simultaneously manage up to 200 individual election workflows, each with its own submission timing, validation status, and deadline constraint — all against a single external deadline that applies to the entire population.

Election processing events in practice range from straightforward tender offers (two choices: tender all shares at the offer price, or retain all shares) to complex merger elections with multiple consideration alternatives, partial election options (tender some shares but not others), and proration mechanics that alter the final allocation for each electing account based on aggregate election results. The operational procedures for simple and complex elections share the same structural backbone — receipt, validation, tracking, transmission, reconciliation — but the data requirements, validation logic, and post-election calculations are substantially more involved for complex events.

Why This Matters in Wealth & Asset Operations

Election processing failures have direct financial consequences for clients that are more visible and more immediate than most other corporate action processing errors. A dividend posted at the wrong rate affects the cash balance; the client may notice but the error can be corrected with an adjustment posting. A missed tender offer election at a 30% premium means the client's shares were not tendered: the client retains shares at the post-offer market price rather than receiving the premium cash consideration. If the offer succeeds and the acquirer takes the company private, the client may have no further opportunity to exit at a comparable price. The financial harm is not correctable by an adjustment posting — it is a permanent economic consequence of the missed election.

This direct connection between election processing quality and client financial outcomes makes election management one of the highest-stakes operational responsibilities in a corporate action department. Operations professionals who understand election processing at the level of this lesson — not just the theoretical model from Lesson 22.2, but the actual receipt-to-transmission mechanics, the validation criteria, the monitoring discipline, and the post-election reconciliation — are equipped to protect clients from election losses that would be both financially significant and operationally preventable.

Core Concept

Election — An instruction submitted by or on behalf of a beneficial owner of a security directing the custodian to process a voluntary corporate action event in a specific manner for that account. A valid election must identify the account, the security, the elected action (tender, subscribe, exchange, etc.), the quantity subject to the election, and the elected form of consideration if multiple alternatives are available. An election is valid only if it is received before the internal deadline, references a position the account actually holds, and does not exceed the electable quantity in the account.

DTC Deadline — The date and time established by the Depository Trust Company by which all elections for a voluntary corporate action must be submitted to DTC by the custodian on behalf of its client accounts. The DTC deadline is the hard external constraint that cannot be extended regardless of what occurs on the firm's side. The firm's internal election deadline is set several business days before the DTC deadline to provide processing buffer between the last accepted client election and the DTC submission.

Election Withdrawal — The cancellation or modification of a previously submitted election before the election deadline. Most voluntary events permit election withdrawal and resubmission until the deadline, allowing clients who change their mind during the election window to revise their instruction. An election withdrawal must be processed in the same timeline as the original election: the withdrawal must be received before the internal deadline and transmitted to the custodian before the DTC deadline. After the deadline, elections are irrevocable.

Together, these three concepts define the operational boundaries of election processing: what constitutes a valid instruction, when it must be received, and what happens if the account holder changes their mind before the window closes. Everything else in election processing — the validation workflow, the tracking discipline, the transmission procedures — serves to ensure that valid elections are honored within these boundaries and that the consequences of invalid or missing elections are correctly applied.

Election Receipt Channels and Sources

Elections reach the operations team through multiple channels, each with different data quality characteristics, timing patterns, and validation requirements. Managing election receipt across all channels simultaneously requires a centralized election tracking system that aggregates incoming instructions regardless of source.

• Advisor-Submitted Elections — The most common source of elections in a wealth management context. The client communicates their election preference to their advisor, who submits the instruction on the client's behalf through the firm's advisor portal, by email to the corporate action operations team, or by phone (with a written confirmation follow-up). Advisor-submitted elections require validation of the advisor's authority to act on behalf of the account (confirmed through the account's advisory agreement), the account's qualifying position, and the instruction completeness. Advisor submissions are the most variable in format and the most likely to arrive in an incomplete state requiring clarification before acceptance.
• Client Portal Elections — Self-service elections submitted directly by the client through the firm's online portal. Portal elections typically have a more structured format (the portal prompts the client to select from defined options and enter a quantity) that reduces the risk of incomplete instructions. However, portal elections still require validation: the portal may not have a real-time position feed, so the elected quantity may exceed the account's actual holding if the position has changed since the client last viewed their account. Portal submissions with quantity errors must be corrected through outreach before the internal deadline.
• Written Instructions — Formal written election letters submitted by clients directly or through legal counsel, typically required for complex accounts (trust accounts, estate accounts) where the election represents a fiduciary decision. Written instructions must be reviewed for authorization (signed by the appropriate authorized parties), completeness, and compliance with election terms before acceptance. Written instructions are the slowest-arriving channel and require the longest lead time for processing; operations teams must identify accounts likely to submit written instructions at event setup and build the longer processing timeline into their internal deadline calculations for those accounts.
• Custodian Default Election — Not a submission channel, but a default election applied by the custodian on behalf of accounts that do not submit any other election before the DTC deadline. The custodian applies the default treatment specified by the issuer in the event terms to all non-electing accounts simultaneously at deadline. The operations team must know the default treatment for each event at setup — it is not determined by the custodian, it is determined by the issuer, and it is stated in the official event documentation.
• Discretionary Manager Elections — In accounts managed under a discretionary advisory mandate, the investment manager may have authority to submit elections on behalf of the client without seeking individual client approval for each event, provided the election falls within the scope of the manager's discretionary authority as defined in the investment management agreement. The operations team must confirm discretionary authority before accepting a manager-submitted election and must maintain documentation of the authority basis for each discretionary election submitted.

Election Validation: Criteria and Disposition

Every election received must be validated before it is recorded as accepted in the processing system. Validation is not a single check — it is a structured review against multiple criteria, each of which can produce a different disposition: accepted, returned for correction, or rejected.

• Account Identification Validity — The election must reference a valid, active account number. Elections that reference a non-existent account number, a closed account, or an account that does not hold the affected security are returned to the submitter for correction immediately. An election for the correct client but the wrong account number (e.g., the client has multiple accounts and referenced the wrong one) is a correctable error if identified before the internal deadline.
• Position Verification — The account must hold the affected security as of the current date, and the elected quantity must not exceed the account's current holding. Elections for quantities greater than the held position are returned for quantity correction. If the account has pending trades in the security that have not yet settled, the team must confirm whether the position will be higher or lower at the record date and advise the submitter accordingly. Elections for zero-position accounts are rejected outright.
• Election Completeness — The election must contain all required fields: account identifier, security identifier (CUSIP or ticker), election action (tender, subscribe, exchange, etc.), elected quantity, and — for events with multiple consideration choices — the elected form of consideration. Incomplete elections are returned to the submitter for completion. For complex events with multiple sub-elections (e.g., tender different quantities for different consideration types), each sub-election is validated independently.
• Timing Validity — The election must be received before the internal election deadline. Elections received after the internal deadline may be accepted at the firm's discretion if time permits validation and transmission before the DTC deadline; elections received after the DTC deadline are rejected without exception. Timing validity is recorded as the date and time of receipt in the processing system, not the date and time of the submitter's action, to create an accurate audit trail of when the instruction was actually received by the firm.
• Authorization Validity — The submitter must have authority to act on behalf of the account. Advisor elections must be consistent with the advisory agreement; client elections must come from an authorized signatory; discretionary manager elections must fall within documented discretionary authority. Elections from unauthorized submitters are rejected and must be resubmitted by an authorized party before the internal deadline.
• Election Term Conformity — The election must conform to the terms of the specific event. For a tender offer with a minimum tender requirement, elections that tender fewer shares than the minimum are invalid. For events with partial election restrictions (e.g., elections must be in lots of 100 shares), elections for non-conforming quantities are returned for adjustment. The operations team must be familiar with the specific election constraints of each event to apply this validation correctly.

Election Tracking: Before vs. After Internal Deadline

The election window divides into two operationally distinct phases: the open collection phase (from announcement through the internal deadline) and the closed processing phase (from the internal deadline through the DTC submission). The operations team's role and priorities differ significantly between these two phases.

During the open collection phase, the primary objective is maximizing the proportion of qualifying accounts that submit valid elections, particularly for accounts with large positions or where the default treatment is significantly less favorable than the elected alternative. The team's activities are outbound as much as inbound: monitoring the election receipt log to identify accounts that have not submitted elections, escalating high-priority non-electing accounts to advisor relationship managers for follow-up, and facilitating the correction of invalid elections that were returned for correction. The team is also continuously processing incoming elections — validating, recording, and acknowledging each one — and must maintain accurate real-time tracking of election receipt status across the entire qualifying population. During this phase, election withdrawals and revisions are permitted and must be processed promptly.

Once the internal deadline passes, the team's focus shifts entirely to transmission preparation. No new elections are accepted (unless the DTC deadline has not yet passed and exceptional circumstances warrant discretionary acceptance). The accepted election inventory is finalized, aggregated by election type and consideration form, and formatted for transmission to the custodian. Non-electing accounts are confirmed for default treatment and the default processing instructions are prepared simultaneously with the election transmission package. After transmission, the team monitors for custodian receipt confirmation and rejection messages. Any rejection received from the custodian after transmission must be investigated and resolved before the DTC deadline — which is why the internal deadline buffer is operationally essential.

Operational Workflow

The following describes the complete election processing workflow for a voluntary tender offer affecting 150 client accounts, from event setup through post-election reconciliation.

1. Event Setup and Election System Configuration. Upon announcement, the tender offer is entered in the corporate action processing system with all key terms: security, offer price, election window open and close dates, DTC deadline, internal election deadline (set 3 business days before DTC deadline), election options (tender all, tender partial, retain all), minimum tender requirement if any, and default treatment (position retained for non-electing accounts). The system is configured to accept elections for this event from the moment of setup. A qualifying account population report is generated: 150 accounts holding the security, with total shares and position size by account.
2. Notification Dispatch. Notification of the tender offer is transmitted to all 150 qualifying account contacts through the firm's notification system (detailed in Lesson 22.6). The notification includes the offer terms, election options, default treatment, internal election deadline, and submission instructions. Advisor notification is also transmitted simultaneously so advisors can proactively contact clients about the election. The notification timestamp for each account is recorded as the start of the firm's notification obligation for this event.
3. Election Receipt and Validation. Elections begin arriving from advisors and clients through the firm's election channels. Each election received is validated against the six criteria described in the previous section. Valid elections are recorded in the processing system with a timestamped receipt confirmation sent to the submitter. Invalid elections are returned to the submitter immediately with a description of the deficiency and a request for correction before the internal deadline. Each election state — received, valid, returned, corrected — is tracked in real time in the election monitoring log.
4. Election Monitoring and Escalation. The election monitoring log is reviewed daily by the operations supervisor. A report is generated each day showing: total qualifying accounts (150), elections received to date, elections accepted as valid, elections returned for correction, elections corrected and accepted, and accounts with no election received. From day 5 of a 15-business-day window, accounts with large positions and no election are flagged for advisor escalation. The advisor relationship team is notified of these accounts and asked to contact the client to confirm their intended election. For accounts where the escalation produces an election submission, the operations team validates and records it through the normal workflow.
5. Internal Deadline Enforcement. At the internal deadline (12:00 noon on day 12, 3 business days before the DTC deadline), the election collection window closes. Elections received after this point are not accepted through the standard workflow. The election inventory is frozen: accepted elections are confirmed, returned elections that were not corrected before the deadline are marked as expired, and all accounts without an accepted election are confirmed for default treatment. The final election tally is reviewed for accuracy before transmission preparation begins.
6. Transmission Preparation and Submission. The accepted elections are aggregated by election type (tender/retain), formatted in the custodian's required instruction format, and reviewed for accuracy before submission. The aggregate instruction — specifying the total shares tendered across all electing accounts and the breakdown by account — is submitted to the custodian before the DTC deadline. The submission is logged with a timestamp. The custodian's receipt confirmation is monitored; any rejection messages received after submission are investigated immediately and corrected if time permits before the DTC deadline.
7. Default Treatment Application. Simultaneously with election transmission, default treatment instructions are prepared for all non-electing accounts. For this tender offer, the default is position retained: no tendering instruction is submitted for non-electing accounts, and their position remains in the account. The operations team confirms that non-electing accounts are not included in the tender instruction set and that their position records will not be modified at the offer close date.
8. Post-Election Reconciliation. After the offer closes and results are published, the operations team reconciles the outcome for every account: electing accounts are confirmed to have received the offer price per share tendered (cash credited, tendered shares removed), and non-electing accounts are confirmed to retain their original position. Any account where the actual outcome differs from the expected outcome — an account that elected to tender but did not receive the cash consideration, or an account that did not elect but had shares removed — is escalated as an exception for immediate investigation. Proration results (if applicable) are verified per account, and accounts whose elected allocation was adjusted for proration are confirmed to have received the prorated outcome rather than the full elected amount.

Real-World Example

A specialty materials company held in 92 client accounts receives a cash tender offer at $58.00 per share — a 34% premium to the prior day's closing price of $43.28. The offer is for all outstanding shares, the election window is 20 business days, and the default treatment is position retained. The DTC deadline is the last business day of the election window at 2:00 PM. The firm's internal deadline is set for the close of business on day 17 (3 business days before the DTC deadline).

The operations team identifies the 92 qualifying accounts, with positions ranging from 25 shares to 8,400 shares. Total firm-wide exposure: 142,650 shares. At the declared offer price, total potential consideration is approximately $8.27 million. Because the premium is large and the default treatment results in clients retaining shares at market price rather than receiving the premium, the team classifies this as a high-priority election event and assigns a senior processor as the dedicated election coordinator for the duration of the window.

Advisor notification is transmitted on day 1. By day 5, 31 of 92 accounts have submitted elections, all of which are valid. The monitoring report on day 5 identifies 61 accounts without elections, including 12 accounts with positions above 1,000 shares. The election coordinator transmits a prioritized escalation list to the advisor relationship team for the 12 large-position non-electing accounts. By day 10, 8 of the 12 large-position accounts have submitted elections. Three of the remaining four are contacted directly by the operations team, and two submit elections. One account remains without an election: the account holder is traveling internationally and unreachable.

On day 14, the operations team receives an election from an advisor for account #7712 — but the elected quantity (2,400 shares) exceeds the account's confirmed position (2,100 shares). The election is returned to the advisor with a correction request on the same day. The advisor resubmits a corrected election for 2,100 shares on day 15. The correction is validated and accepted.

At the internal deadline on day 17, the election inventory is: 89 accounts with accepted elections (tender all), 3 accounts with no election (default: position retained). The aggregate transmission is prepared for 89 accounts, covering 138,825 tendered shares, and submitted to the custodian at 3:45 PM on day 17. The custodian confirms receipt the following morning, with no rejections. The 3 non-electing accounts are confirmed for position retention.

At offer close, 89 accounts receive cash consideration at $58.00 per share (total: $8,051,850), and the tendered share positions are removed. Three accounts retain their positions at the post-offer market price of $57.75 (the offer was successful, and the shares continue to trade at a slight discount to the offer price). Post-election reconciliation confirms the correct outcome for all 92 accounts.

Common Mistakes

Mistake 1: Recording Elections as Accepted Without Completing Full Validation

Under deadline pressure, operations teams sometimes acknowledge elections as accepted before completing all validation steps — particularly position verification and authorization review. An election acknowledged but not fully validated may be discovered to be invalid (excess quantity, unauthorized submitter) only at the transmission preparation stage, when there is far less time to return it for correction. Every election must be fully validated at receipt, regardless of how close to the internal deadline it arrives. A partially validated election is not a valid election and should not be marked as accepted until all criteria are confirmed.

Mistake 2: Failing to Monitor for Custodian Rejection Messages After Transmission

The operations team's work does not end at transmission submission. Custodians sometimes reject election submissions after they have been received — because the submission format contains errors, because the account's position at the custodian differs from the firm's internal record, or because the submission arrived close to the DTC deadline and was processed after the window closed. Teams that submit elections and move on without monitoring for rejection confirmations may believe all elections were accepted when one or more were rejected. Monitoring for rejection messages must remain active from the point of submission until the DTC deadline has passed and all accounts are confirmed as either elected or defaulted by the custodian.

Mistake 3: Applying Default Treatment Inconsistently Across Accounts

Default treatment must be applied consistently to every account in the non-electing population — not selectively based on position size, account type, or advisor relationship. Operations teams that apply default treatment only to accounts they explicitly flag for default, rather than to all accounts not in the elected set, risk omitting accounts that should have received default treatment and producing an unreconciled gap between the total qualifying population and the sum of elected and defaulted accounts. The default population is defined as every qualifying account not included in the election transmission, and it must be explicitly confirmed and documented at the time of transmission, not assumed.

Mistake 4: Processing Election Withdrawals Without Verifying the Timing

When a client changes their mind during the election window and requests withdrawal of a previously submitted election, the withdrawal must be processed and the replacement instruction (if any) must be validated and transmitted before the DTC deadline. Operations teams that process election withdrawals at any time without checking the current position in the timeline risk accepting a withdrawal that cannot be replaced — because the replacement election would arrive after the internal deadline — leaving the account in an elected state when the client intended to change their election, or in an unelected state when the client intended to substitute a different election. Every election withdrawal request must be time-checked against the internal deadline before acceptance.

Mistake 5: Not Reconciling Post-Election Outcomes at the Account Level

Post-election reconciliation that confirms only aggregate totals — total shares tendered matches total custodian credit — without confirming outcomes at the account level will miss errors in the allocation of consideration between accounts. An aggregate reconciliation confirms the correct total was processed but does not confirm that the right accounts received the right amounts. Account-level reconciliation is required: each electing account must be confirmed to have received consideration for the quantity it tendered (adjusted for proration if applicable), and each non-electing account must be confirmed to have retained its full position with no consideration received. Without account-level reconciliation, individual account errors can persist undetected until a client inquiry surfaces them.

Practical Exercises

Exercise 1: Election Validation Triage

Your firm has received the following six elections for a voluntary tender offer. The offer is for all outstanding shares at $45.00 per share. The internal deadline is today at 5:00 PM. Evaluate each election against the validation criteria and determine: whether the election is (a) accepted as valid, (b) returned for correction with a specific deficiency identified, or (c) rejected outright. For elections returned for correction, state what correction is needed and whether the corrected election could still be accepted before the deadline. Election 1: Account #4412, 850 shares tendered, submitted by the account's advisor, account holds 850 settled shares, received at 2:15 PM. Election 2: Account #7821, 1,200 shares tendered, submitted by a client service associate (not the account's advisor of record), account holds 1,200 shares, received at 3:30 PM. Election 3: Account #3305, 500 shares tendered, submitted by the account's advisor, account holds 380 settled shares and 200 shares with a pending purchase settling tomorrow, received at 1:00 PM. Election 4: Account #9001, 600 shares tendered, submitted by the account's advisor, received at 5:20 PM. Election 5: Account #2244, election specifies "tender all shares" but does not state a quantity, submitted by the account holder directly, account holds 175 shares, received at 11:30 AM. Election 6: Account #5518, 900 shares tendered, submitted by the account's advisor, but the CUSIP referenced in the election is for a different security than the one subject to the tender offer, received at 9:00 AM.

Exercise 2: Election Monitoring and Escalation Design

A rights subscription event is open for 12 business days. The internal deadline is the close of day 10. Your firm has 75 qualifying accounts, with positions ranging from 50 to 3,000 shares. The rights allow each holder to purchase one additional share for every four held at an 18% discount to market; the default treatment is that unexercised rights are sold on the holder's behalf at the prevailing market price on the expiration date. Design a monitoring and escalation plan for the 12-day election window. Specify: (a) the election receipt data you will track daily in the monitoring log; (b) the threshold criteria for escalating a non-electing account to the advisor relationship team; (c) when you will begin escalation and how frequently you will issue escalation lists to the advisor team; (d) what you will do if an escalated account still has not submitted an election by day 10 at 3:00 PM; and (e) how you will confirm that the default treatment (rights sale) is correctly applied to all non-electing accounts after the internal deadline.

Exercise 3: Partial Election and Proration Scenario

A company announces a "modified Dutch auction" tender offer for up to 25% of its outstanding shares at a price between $30.00 and $35.00 per share, with proration if more than 25% of shares are tendered. Your firm holds the security across 40 accounts. After the internal deadline, the election inventory shows: 28 accounts tendered all shares (total: 84,000 shares), 6 accounts tendered partial positions (total: 8,200 shares), and 6 accounts submitted no election (position retained). The company announces that 100% of tendered shares are subject to proration: the actual acceptance rate is 62% of each account's tendered quantity. For each of the following three specific accounts, calculate the final outcome: Account A tendered 2,000 shares (full position); Account B tendered 500 shares (partial, holds 1,400 total); Account C submitted no election (holds 800 shares). Then describe what the post-election reconciliation for this event must confirm for each account type.

Exercise 4: Election Withdrawal and Resubmission

A tender offer election window closes in 4 business days. Your internal deadline is in 2 business days. The following three scenarios arise today. Scenario A: An advisor calls to withdraw a tender election submitted 5 days ago for account #3310 (800 shares tendered at $52.00) and resubmit a partial tender election for 400 shares only, because the client wants to retain half the position after reconsidering. Scenario B: A client calls to withdraw a tender election submitted by their advisor yesterday for account #8821 (1,500 shares tendered), claiming the advisor submitted the election without the client's authorization. No replacement election is requested. Scenario C: An advisor calls to withdraw an election submitted this morning for account #5503 (200 shares tendered at $52.00) and replace it with a "retain all" election, because the company announced a competing offer from a different acquirer at $58.00 per share this afternoon and the advisor wants to preserve the client's ability to tender to the higher offer. For each scenario, describe how the operations team should respond, what documentation is required, and what happens to the account's election status after the team's response.

Key Terms

Election — An instruction submitted by or on behalf of a beneficial owner directing the custodian to process a voluntary corporate action in a specified manner for that account. Must identify the account, security, action, quantity, and consideration form (if applicable) to be valid.

DTC Deadline — The date and time by which all election instructions for a voluntary corporate action must be submitted to the Depository Trust Company by the custodian. The hard external constraint on all election processing; cannot be extended.

Internal Election Deadline — The firm's self-imposed deadline, set several business days before the DTC deadline, after which no new client elections are accepted through the standard workflow. Provides processing buffer for validation, aggregation, and transmission.

Election Window — The period from event announcement through the election deadline during which holder instructions may be submitted and, where permitted, withdrawn or modified.

Election Withdrawal — The cancellation of a previously submitted election before the election deadline, permitting the account to revert to a non-elected state or submit a replacement instruction. Irrevocable after the deadline.

Default Treatment — The outcome applied by the custodian to accounts that do not submit a valid election before the DTC deadline. Defined by the issuer in the event terms; not determined by the operations team or the custodian.

Election Monitoring Log — A real-time tracking record of election receipt status for every qualifying account in a voluntary event, showing which accounts have submitted elections, which elections are pending validation, which have been returned for correction, and which accounts have no election on file.

Transmission Package — The aggregated, formatted set of election instructions submitted to the custodian before the DTC deadline, covering all accepted elections for all qualifying accounts in the firm's holdings.

Custodian Rejection — A message from the custodian indicating that a submitted election instruction was not accepted, due to format errors, quantity discrepancies, or timing issues. Must be investigated and resolved before the DTC deadline.

Proration — The proportional reduction of each electing account's tender or subscription quantity when aggregate elections exceed the available consideration pool. Applied by the paying agent; results must be verified per account in post-election reconciliation.

Discretionary Election — An election submitted by an investment manager on behalf of a client account without seeking individual client approval, under the authority granted by the account's discretionary investment management agreement.

Post-Election Reconciliation — The account-level verification that every qualifying account received the correct outcome: elected consideration (adjusted for proration) for accounts that tendered, and the correct default outcome for accounts that did not elect.

Knowledge Check

Question 1

An election is received from an advisor for account #4401 specifying a tender of 1,800 shares, but the account holds only 1,500 settled shares. The internal deadline is 3 days away. How should the operations team respond?

• A. Accept the election for 1,800 shares and tender as much as the custodian permits
• B. Return the election to the advisor with a note identifying the quantity discrepancy, and request a corrected instruction for no more than 1,500 shares before the internal deadline
• C. Accept the election for 1,500 shares automatically and apply default treatment to the overage
• D. Reject the election permanently, as it contained an invalid quantity

Correct Answer: B — An election with a quantity exceeding the held position is invalid and must be returned for correction. Because the internal deadline is 3 days away, correction and resubmission are feasible. The election should not be accepted at a different quantity than submitted (C) without the submitter's explicit instruction, and it should not be permanently rejected (D) if a corrected instruction can still be received in time.

Question 2

Why is the internal election deadline set several business days before the DTC deadline?

• A. To give clients more time to reconsider their elections before they become binding
• B. To reduce the number of elections the custodian must process
• C. To create a processing buffer allowing time to validate corrections, aggregate all elections, format the transmission package, and monitor for custodian rejection before the DTC deadline
• D. Because the DTC deadline applies only to large institutional accounts, not managed accounts

Correct Answer: C — The internal deadline buffer provides the processing time needed to correct late-arriving invalid elections, assemble and format the transmission package, submit to the custodian, and investigate any rejection messages — all before the external DTC deadline. Without the buffer, there is no time to recover from any error in the transmission process.

Question 3

At offer close, post-election reconciliation for a tender offer reveals that account #7730 (which submitted a valid tender election) has its full share position still intact — no shares were tendered, and no cash consideration was received. What is the most likely cause, and what should the operations team do?

• A. The account elected to retain its shares — no action required
• B. The account's election was not included in the transmission package, or was rejected by the custodian after transmission. The team should investigate the election's transmission record and work with the custodian to determine the correct remediation.
• C. Proration reduced the account's tender to zero shares — this is the expected outcome
• D. The account holds shares in a different custodian sub-account — the position will be updated on the following business day

Correct Answer: B — An account with a valid election that shows no tendered shares and no consideration at offer close indicates that the election was either omitted from the transmission or rejected and not remediated. The operations team must trace the election through the transmission records, determine whether it was included and accepted by the custodian, and — if not — assess whether the client has a remedy against the firm for the missed election.

Question 4

A client calls on the last day of the election window (after the internal deadline but before the DTC deadline) to submit a tender election. The internal deadline passed 2 hours ago. How should the operations team handle this?

• A. Accept the election automatically because the DTC deadline has not yet passed
• B. Reject the election because the internal deadline has passed and elections are no longer accepted
• C. Exercise discretion: assess whether there is sufficient time remaining before the DTC deadline to validate the election, add it to the transmission package, and resubmit before the DTC deadline; if yes, accept; if no, inform the client that the election cannot be processed
• D. Accept the election and submit it separately to the custodian outside the standard transmission package

Correct Answer: C — Elections received after the internal deadline but before the DTC deadline may be accepted at the firm's discretion if there is sufficient time to process and transmit them before the external deadline. The firm is not required to accept late elections, but may choose to if capacity permits. The key constraint is the DTC deadline — if the election cannot be transmitted and confirmed before that deadline, it cannot be accepted regardless of the client's circumstances.

Question 5

Why must post-election reconciliation be performed at the account level rather than only at the aggregate level?

• A. Because account-level reconciliation is faster than aggregate reconciliation
• B. Because aggregate reconciliation cannot detect errors where the right total consideration was paid but to the wrong accounts, or where individual accounts received the wrong amount due to proration errors
• C. Because account-level reconciliation eliminates the need for custodian confirmation
• D. Because aggregate reconciliation is only required for events with proration

Correct Answer: B — Aggregate reconciliation confirms the correct total was processed but cannot detect account-level errors: an account that elected but received no consideration, an account that did not elect but had shares removed, or accounts whose proration allocation was calculated incorrectly. Only account-level reconciliation confirms the correct outcome for every individual account in the qualifying population.

Lesson Summary

Election processing is the end-to-end operational workflow that transforms a voluntary corporate action into a correctly processed outcome for every qualifying account — whether that account submitted an election or received default treatment. The workflow spans from receipt of the first election through post-election reconciliation confirming the final outcome for every account.

Elections are received through multiple channels — advisor submissions, client portals, written instructions, and discretionary manager elections — each with different data quality characteristics and timing patterns. Every election must be validated against six criteria: account identification, position verification, instruction completeness, timing validity, authorization validity, and election term conformity. Invalid elections are returned for correction immediately; the internal deadline determines whether correction and resubmission are still feasible.

The internal election deadline — set several business days before the DTC deadline — creates the processing buffer needed to finalize the election inventory, prepare the transmission package, submit to the custodian, and monitor for rejection messages before the external deadline. After the internal deadline, the election inventory is frozen and default treatment is confirmed for all non-electing accounts. After the DTC deadline, elections are irrevocable.

Post-election reconciliation must be performed at the account level — not just in aggregate — to confirm that every electing account received its elected consideration (adjusted for proration where applicable) and every non-electing account received the correct default outcome. Aggregate reconciliation that matches totals but does not verify individual account outcomes will miss errors that directly affect client accounts.

Looking Ahead

Election processing depends critically on one upstream function that has not yet been examined in detail: how clients and advisors learn that a voluntary event has been announced and that an election deadline is approaching. Without effective notification, even a perfectly designed election processing workflow produces poor outcomes — clients who are never informed of an event cannot submit elections they don't know are needed.

Lesson 22.6 examines event notification systems: how corporate action notifications are generated, what information they must contain, how they are distributed across different client and advisor channels, and how notification delivery is tracked and confirmed. Notification is not a passive communication function — it is an active operational obligation with timing requirements, content standards, and regulatory dimensions that must be managed as rigorously as the election processing workflows that depend on it.

Study Support

How to Approach This Lesson

Election processing is best understood as a race against a hard deadline — the DTC deadline — with a series of validation and processing steps that must all be completed before that deadline. Study the workflow as a timeline: what must happen in what order, and what is the latest point at which each step can be initiated and still completed before the deadline? This timeline perspective helps you understand why the internal deadline buffer exists, why invalid elections must be returned immediately (not at the end of the day), and why post-submission rejection monitoring cannot be deferred.

Key Patterns to Recognize

• Every election must be fully validated at receipt — not acknowledged and validated later.
• The internal deadline buffer is not slack time; it is a required processing window for validation, aggregation, transmission, and rejection monitoring.
• Default treatment is not inaction — it is a defined outcome that must be applied to every non-electing account explicitly and confirmed in post-election reconciliation.
• Post-election reconciliation must be account-level — aggregate totals do not detect individual account errors.
• Election withdrawals must be time-checked before acceptance — a withdrawal without a replacement may leave the account in an unintended state.

Questions to Test Your Understanding

• Can you list all six validation criteria for an election and describe what happens when each criterion fails?
• Do you understand why the internal deadline is set before the DTC deadline, and what happens in the time between them?
• Can you describe what post-election reconciliation must confirm for electing and non-electing accounts?
• Do you understand how proration affects the post-election reconciliation for accounts in oversubscribed events?
• Can you explain when an election received after the internal deadline may still be accepted?

Common Areas of Confusion

The most common confusion in this lesson involves the relationship between the internal deadline and the DTC deadline. The internal deadline is the firm's self-imposed cutoff — it is not a regulatory requirement, and elections received between the internal and DTC deadlines may be accepted at the firm's discretion. The DTC deadline is a hard external constraint — no election can be transmitted or accepted after it, regardless of circumstances. Students sometimes treat the internal deadline as if it were the DTC deadline and reject all late elections categorically; or treat the DTC deadline as if it were the internal deadline and accept all elections up to the DTC deadline without recognizing that transmission processing takes time. The second common confusion involves default treatment: some students treat non-electing accounts as simply unaffected, when in fact default treatment is an explicit defined outcome that must be confirmed and documented for every non-electing account.

How This Connects to the Larger System

Election processing connects directly to the notification systems in Lesson 22.6, which are what make client elections possible in the first place. It also connects to the voluntary event processing model established in Lesson 22.2, where the election processing workflow was introduced at a conceptual level. And it connects forward to the validation and reconciliation capstone in Lesson 22.7, where election processing accuracy is one of the key control dimensions assessed in the unit's system validation framework.

Practical Application

Application 1: Building an Election Processing Checklist

In practice, operations teams maintain a standardized election processing checklist for each category of voluntary event — tender offers, rights subscriptions, merger elections — that documents every required step from event setup through post-election reconciliation, the responsible team or individual for each step, the timing requirement relative to the internal and DTC deadlines, and the exception escalation trigger. Using a checklist ensures that no step is omitted under deadline pressure and that every election event is processed consistently regardless of which team member is managing it. Building and maintaining these checklists is a day-one practice in any corporate action department.

Application 2: Election Receipt Acknowledgment System

In practice, every valid election received triggers an automated acknowledgment to the submitter — timestamped with the receipt time and confirming the key election details: account number, security, elected action, quantity, and consideration form if applicable. This acknowledgment serves two purposes: it confirms to the advisor or client that the election was received and recorded (providing peace of mind and reducing duplicate submissions), and it creates a contemporaneous record that the election was received before the internal deadline, which is essential documentation if the election's timing is later disputed. The acknowledgment system is typically built into the corporate action processing platform and requires no manual action by the operations team for valid elections.

Application 3: Pre-Deadline Escalation Call Script

In practice, when the advisor relationship team is escalating non-electing accounts to advisors, they use a standardized call script that: identifies the event and the account at issue, states the election deadline and the elected versus default economic difference for the specific account's position, asks the advisor to confirm whether the client has been notified and to provide an expected election timing, and documents the outcome of the call in the election monitoring log. Having a pre-scripted escalation approach ensures consistency across the relationship team and reduces the risk that advisors are contacted with incomplete information about why the escalation is being made.

Application 4: Post-Election Reconciliation Exception Investigation

After any voluntary event closes, operations teams in practice produce a post-election reconciliation report that compares the expected outcome for each account (based on election or default status) against the actual outcome recorded in the custodian's and the internal system's records. Exceptions are categorized: accounts that elected but received no consideration (probable transmission or custodian rejection issue), accounts that did not elect but had their position altered (probable erroneous inclusion in transmission), and accounts with proration discrepancies (probable calculation error in applying proration results). Each exception category has a standard investigation path, and the resolution must be documented before the reconciliation is closed. Firms that perform this investigation rigorously after every voluntary event build institutional knowledge that reduces the frequency and severity of election errors in future events.

Lesson Navigation