/operational-risk

name: operational-risk
description: "Guide identification, measurement, and management of operational risk in trading and brokerage operations. Use when designing trade error detection and correction procedures, investigating trade breaks and reconciliation failures, classifying loss events under Basel taxonomy, developing key risk indicators (KRIs) and dashboards, responding to system outages or data feed failures or order routing errors, conducting root cause analysis after a trade error or operational incident, planning business continuity and disaster recovery for trading desks, preparing for FINRA or SEC operational risk examinations, or assessing technology risk in OMS and market data systems. Also covers fat-finger errors, error account P&L, and corrective action tracking."

Operational Risk

Core Concepts

Operational Risk Framework

Operational risk is the risk of loss resulting from inadequate or failed internal processes, people, and systems, or from external events. The Basel Committee's seven event-type categories map to trading operations as follows:

| Basel event type | Trading-operations examples | |---|---| | 1. Internal fraud | Unauthorized trading, intentional position mismarking, fictitious trade booking, front-running | | 2. External fraud | Account takeover, phishing for trade credentials, wire fraud in settlement instructions, counterparty manipulation | | 3. Employment practices and workplace safety | Inadequate operations training, key-person dependency, error-inducing workload | | 4. Clients, products, and business practices | Suitability failures, improper execution, best execution violations, failure to follow client instructions | | 5. Damage to physical assets | Data center or trading floor damage from natural disasters or civil disruption | | 6. Business disruption and system failures | OMS outages, market data feed failures, connectivity loss, exchange gateway and clearing system downtime | | 7. Execution, delivery, and process management | Trade errors, settlement fails, reconciliation breaks, failed corporate action processing, incorrect margin calculations (typically the largest loss category) |

**Risk identification** involves cataloging all operational risk exposures through process mapping, risk and control self-assessments (RCSAs), loss event analysis, scenario analysis, and audit findings. **Risk assessment** scores each risk on likelihood and impact dimensions, typically using a 5x5 heat map. **Risk monitoring** tracks KRIs, loss events, and control effectiveness. **Risk mitigation** applies controls (preventive and detective), process redesign, technology solutions, insurance, and business continuity planning.

Trade Errors

A trade error occurs when a transaction is executed incorrectly due to human mistake, system malfunction, or miscommunication. Common trade error types include:

• **Wrong security.** The wrong CUSIP, ISIN, or ticker is entered, resulting in a purchase or sale of an unintended security. Often caused by similar ticker symbols (e.g., entering "AAPL" instead of "APLE") or selecting the wrong line item from a dropdown.
• **Wrong quantity.** The number of shares, bonds, or contracts is incorrect. A frequent subcategory is the "fat finger" error where an extra digit is entered (e.g., 10,000 shares instead of 1,000).
• **Wrong side.** A buy is entered as a sell, or vice versa, resulting in a position that is the opposite of intended. The net exposure error is twice the intended trade size.
• **Wrong account.** The trade is executed in the wrong client account or in the firm's proprietary account instead of a client account. This creates suitability, allocation, and potential conflict-of-interest issues.
• **Duplicate orders.** The same order is submitted more than once due to system timeout and resubmission, double-clicking, or failure of deduplication logic. The firm ends up with twice the intended position.
• **Wrong price type or limit.** A market order is placed instead of a limit order, or the limit price is set incorrectly, resulting in execution at an unintended price.
• **Stale or cancelled order execution.** An order that should have been cancelled is executed because the cancellation was not processed in time or was lost in transit.

**Error detection methods.** Errors are detected through: real-time position monitoring (unexpected position changes trigger alerts), pre-trade validation rules (quantity limits, security restrictions, account eligibility checks), post-trade reconciliation (comparing expected vs. actual positions), client complaints, clearing firm or counterparty rejection notices, and P&L attribution (unexplained P&L often signals an error).

**Error correction procedures.** Once detected, errors must be corrected promptly:

• **Cancel and rebook.** The erroneous trade is cancelled and the correct trade is booked. If the error is caught before settlement, the cancel/rebook may occur on the same trade date. If caught after settlement, an as-of trade is used to adjust the position retroactively.
• **Error account.** Most broker-dealers maintain one or more error accounts (also called difference accounts) where erroneous trades are transferred pending resolution. The error account isolates the incorrect position from client accounts and tracks the resulting P&L. Error account activity is subject to supervisory review and must be documented.
• **Error P&L allocation.** Losses from trade errors are absorbed by the firm and may not be passed to clients. Gains from trade errors present a more nuanced situation — regulatory guidance and firm policy dictate whether the gain reverts to the client's account or remains in the error account. FINRA has stated that firms should not systematically benefit from trade errors at clients' expense.
• **Root cause analysis.** Every trade error should trigger a root cause analysis to determine whether the error was caused by a process deficiency, a technology i