How Should Advisors Correct Trade Errors?

Marcus Chen

Bloomie Staffing contributor focused on financial advisor operations · July 24, 2026

Advisors should correct trade errors promptly, make affected clients whole when the firm caused a loss, preserve any client benefit unless policy and law support another treatment, and document discovery, calculation, approval, booking, communication, and root-cause remediation. The test is whether every error reached a fair, consistent, independently reviewed outcome.

Define an error before deciding how to fix it

A useful trade-error policy begins with a definition broad enough to capture operational reality. Wrong security, wrong side, wrong quantity, wrong account, missed trade, duplicate trade, late execution, breached restriction, incorrect price, failed settlement, and an order inconsistent with investment intent can all require review. A market move after a reasonable investment decision is not automatically an error; an instruction entered incorrectly is.

The distinction matters because staff should not be able to relabel a loss after seeing the outcome. Build an intake record with the intended order, actual order, discovery time, market conditions, affected accounts, person who found it, systems involved, and the rule or instruction that was missed. Preserve order tickets, chats, approvals, confirmations, custodian records, and price data before anyone edits the record.

Publicly filed adviser policies provide a practical benchmark. One SEC-filed compliance manual defines examples such as buying or selling the wrong security, overbuying or overselling, reversing buy and sell instructions, or violating client or legal restrictions. It also calls for correction as soon as reasonably practicable and review of control weaknesses.

Stop exposure and assign independent ownership

The first operational objective is to stop additional harm. Notify trading, operations, compliance, and the portfolio owner; freeze informal edits; confirm whether more accounts share the problem; and decide who can authorize a corrective trade. For a wrong-security purchase, the firm may need to sell the incorrect position and buy the intended one. For a missed sale, it may need to recreate the economic result using a defensible benchmark.

Speed matters, but hurried correction without segregation creates a second risk. The person who caused the error should not determine alone whether it was an error, choose the correction price, decide who receives a gain, and close the ticket. Require compliance or another independent reviewer to approve classification, calculation, account movement, client reimbursement, disclosure, and closure.

Broker-dealer rules address a narrower concept called a clearly erroneous transaction. FINRA Rule 11891 describes an obvious error in price, share count, other trading unit, or security identification. An adviser should not confuse that market-level review process with its broader fiduciary responsibility to correct an error in a client account.

Calculate the client outcome with a reproducible benchmark

A correction file should show the client’s actual position, the position the client should have held, the correction trades, commissions, fees, taxes or other costs considered, price source, timestamps, and the net economic difference. Use a benchmark defined in policy, such as the price available when the error was discovered or when correction reasonably could have occurred. Explain deviations caused by liquidity, market disruption, custodian timing, or client instructions.

Consider a simple example. An advisor intended to buy 500 shares of Fund A at $40 but entered Fund B. When operations discovered the mistake, Fund A was $41 and Fund B could be sold for $39.50. The file should not merely show two reversing tickets. It should calculate what the client would have owned absent the error, every correction cost, and the firm-funded amount needed to restore that position without shifting the firm’s mistake to the client.

Do not net unrelated gains and losses merely to reduce reimbursement. If one account was harmed and another benefited, test each client outcome under policy, contracts, disclosures, and applicable law. A public adviser error-correction policy filed with the SEC states that clients are made whole when the adviser causes a loss and, absent a contrary intermediary arrangement, clients keep gains.

Control error accounts, gains, and conflicts

Error accounts can be operationally necessary, but they must not become speculative trading accounts or places to hide outcomes. Reconcile every entry to a numbered error ticket, confirm that only correction activity appears, tie every profit or loss to the final disposition, and review aged positions daily. Monitor who can book to the account and prohibit delaying correction in hopes that the market improves.

Gains create a conflict because the firm may be tempted to keep favorable outcomes while assigning losses elsewhere. Write the gain-treatment rule in advance and apply it consistently across custodians, programs, account types, and employees. Review whether agreements with wrap sponsors or intermediaries change the mechanics, and escalate ambiguous cases to qualified legal and compliance personnel.

Test for patterns by trader, portfolio manager, security, custodian, strategy, time of day, error type, correction delay, and profit or loss. A recurring “wrong account” explanation that consistently moves profitable positions toward favored accounts may be an allocation problem, not a collection of innocent errors. Link the error log to allocation testing, personal-trading surveillance, complaints, best execution, and restriction monitoring.

Document communication, reimbursement, and closure

The closure package should include the original and corrected trades, calculation worksheet, approvals, accounting entries, reimbursement proof, error-account activity, client or intermediary communication, disclosure analysis, complaint analysis, root cause, corrective action, validation, and closure date. If no client communication occurred, record who made that decision and under which policy or agreement.

Track time from discovery to escalation, correction, reimbursement, and final closure. A reasonable internal target might require same-day escalation for open market exposure, next-business-day calculation review, and a dated owner for any external dependency. Those are operating targets, not universal legal deadlines; firms should set thresholds that fit their business and obligations.

Sample closed tickets against custodian cash and positions. A status of “resolved” is not evidence that reimbursement posted or the intended security landed in the account. Also search for error-like activity that never entered the log: canceled and rebooked trades, manual journals, unusual account transfers, price adjustments, fee credits, negative cash, restriction breaches, and client complaints.

Turn every error into a tested control improvement

Root-cause labels should be specific enough to drive action: stale model file, ambiguous instruction, missing pre-trade restriction, wrong account mapping, duplicate interface message, manual-keying mistake, incomplete approval, custodian rejection, weak segregation, or training gap. “Human error” is not a root cause when the process allowed one keystroke to reach a client account without detection.

Match the fix to the cause. Add a restricted-security rule, require dual approval above a threshold, remove unnecessary manual entry, validate account mappings, reconcile executions earlier, improve exception alerts, or change access rights. Then retest. A policy update without evidence that the new control works leaves the original risk open.

A Bloomie can gather order and custodian evidence, open numbered cases, calculate aging, reconcile reimbursements, flag repeated causes, prepare trend reports, and remind owners about validation. Human trading, operations, compliance, legal, and supervisory personnel must decide error status, correction method, client harm, disclosure, reimbursement, discipline, and regulatory reporting.