A missed corporate action election, a late incident ticket and a control rated effective
Arden Asset Management, with £12bn AUM, administers income elections on its funds. In March a dividend election for a £300m holding was missed because the custodian's instruction deadline was misread; the fund received the default cash option rather than the higher-value stock option. The shortfall and client compensation came to £720,000. The error was found nine weeks later during a custodian reconciliation. The operations team logged the incident six weeks after discovery, and the loss database recorded only the £720,000 cash loss, not the near miss in January when a similar deadline was caught by a temporary contractor. The control is described as 'four-eyes review of the corporate actions checklist'; evidence is a scanned checklist with initials. A sample of 60 checklists found 14 where the preparer and reviewer initials were the same. Internal audit had rated the control 'effective' because no exceptions were recorded.
1. Classify the event under the Basel event types and explain why the classification matters for loss data and capital.
Read the worked answer
Classification The event is an execution, delivery and process management loss. The failure was in the process of capturing the custodian deadline, completing the election and checking it before submission. It is not a market loss: the fund's economic loss arose because the instruction was not executed, not because the market moved against a deliberate position. It is not client, products and business practices in the mis-selling sense, because there was no unsuitable advice or product design failure; the compensation is a consequence of the process failure.
Why classification matters
- It determines where the loss sits in the event taxonomy, which drives reporting, root-cause analysis and ownership.
- It allows the firm to aggregate similar events, including the January near miss, and see whether this is a one-off or a pattern.
- It supports scenario analysis and capital assessment: repeated corporate action failures are a different risk from a single fraud or a systems outage.
- It affects regulatory reporting if the firm is subject to operational risk loss reporting requirements.
Judgement The £720,000 is an operational loss and should be recorded gross, with any recoveries shown separately. The near miss should be captured even though it produced no loss, because it is evidence that the control was not working before the March event. Classifying the event only as a 'client compensation' item would obscure the process root cause and make the loss data less useful.
2. Identify the root causes and control weaknesses beyond the identical initials.
Read the worked answer
Root causes
- The deadline source was not controlled. Staff relied on reading a custodian notice, with no central calendar or system field showing the election deadline.
- The checklist was a documentary artefact, not a control. Initials do not evidence that an independent review took place, and 14 of 60 samples suggest the review was either not independent or not performed.
- The process depended on temporary staff without adequate training or supervision; the January near miss was caught by a contractor, which suggests the permanent process was weaker.
- Reconciliation was too slow. Nine weeks to detect a missed election is far too long for an event with a hard deadline; detection should be at the point of instruction and shortly after the deadline.
- Incident reporting was delayed by six weeks, which suggests fear, unclear ownership or a process that only records losses after compensation is agreed.
- Internal audit relied on the absence of recorded exceptions. A control that leaves no independent evidence cannot be tested by asking whether exceptions were logged.
Control weaknesses There is no segregation between preparation and review, no system-enforced deadline, no independent post-deadline confirmation with the custodian, and no near-miss capture. The loss database captures only cash losses, so it understates the frequency of control failures. The audit rating of 'effective' is not supported by the evidence: the sample of identical initials is itself an exception.
3. Design a control test that would have detected the failure and explain how the near miss should be treated.
Read the worked answer
Control test design
- Objective: confirm that every income election is independently reviewed before the custodian deadline and that the instruction matches the entitlement and the chosen option.
- Population: all income elections in the period, not a sample of checklists only. The population should be reconciled to the custodian's corporate action calendar so that missed elections are included.
- Sample: risk-based sample covering high-value holdings, complex elections, temporary staff and deadlines that fall on holidays.
- Attributes: deadline recorded from an independent source; calculation of entitlement checked; election instruction agreed to the authorised decision; reviewer is different from preparer; review evidenced by a system timestamp or named approval, not initials; instruction sent before the deadline; post-deadline confirmation received.
- Exception criteria: any missing independent evidence, any preparer/reviewer match, any instruction after the deadline, any election not in the population.
- Re-performance: for a sample, re-read the custodian notice and recalculate the deadline and entitlement. This would have caught the March error.
Near-miss treatment The January event should be recorded as a near miss with potential impact, root cause and the control that caught it. It should be reviewed alongside actual losses, reported to the risk committee and used to change the process. Near misses should not be blamed on the individual who caught the error. The fact that a temporary contractor caught it is a warning, not a comfort. The firm should set a target for near-miss reporting and track whether the same root cause recurs.