Direct Answer
Trades do not always stay as executed. Exchanges can bust clearly erroneous trades. Brokers can correct allocation errors. Counterparties can DK (Don't Know) trades they have no record of. Each of these events requires the OMS to retroactively adjust its records, not by editing the original fill, but by appending a correcting entry to the fill ledger that reverses the original's effect and, where applicable, replaces it with the corrected values.
The retroactive nature of corrections is what makes them operationally dangerous. By the time a bust arrives, the affected position may have been traded against, marked to market for P&L, used in a risk report, or included in a client statement. Every downstream computation that used the busted fill must be identified and restated. OMS systems that cannot apply retroactive corrections without manual intervention are a chronic source of position discrepancies and P&L restatements.
Key Takeaways
- Fill ledgers are append-only: Original fills are never deleted or edited. Busts and amendments create correcting entries that reverse or modify the original's effect.
- Busts must reverse fills atomically: Reversing a busted fill requires updating the fill ledger, the order record, the position, and the cash ledger in a single transaction.
- Retroactive busts create cascade restatements: If the busted position was traded against, both the bust and subsequent trades' P&L must be recomputed from the fill history.
- DK resolution requires bilateral coordination: The buy-side and broker must compare their records to identify the discrepancy, there is no automated resolution path for a DK without human investigation.
- Amendments change specific attributes, not the entire trade: A price correction changes only the price, quantity and account remain. An account designation amendment changes only the account, price and quantity remain.
- Exchange bust windows are short: For U.S. equities, the requesting party typically has 30 minutes to initiate a bust; the exchange has 30 minutes to decide. OMS systems must be able to receive and process bust notifications on any timeline.
- Post-bust positions may be legally short: If the busted buy was subsequently used as the basis for a sell, reversing the buy may leave the account with a short position it did not intend to have. The OMS must flag this immediately for remediation.
- Corrections affect regulatory reporting: If a corrected trade was included in a regulatory report (large trader report, form PF, etc.), the report may need to be amended. The audit trail must clearly show when the original was filed and when the correction was made.
Core Concepts
Trade bust mechanics in the OMS
A trade bust arrives at the OMS as a FIX Execution Report with ExecType='H' (Trade Cancel) or, in some implementations, as a proprietary message from the prime broker containing the original trade's reference identifiers. The OMS must match the bust notification to the original fill using the exchange's trade identifier (the FIX ExecID or TradeID field). This matching is critical, a bust processed against the wrong fill corrupts a different position without fixing the intended one.
Once matched, the OMS processes the bust by: (1) creating a new fill record in the ledger with the same quantity but negative sign and the same price as the original fill, referencing the original ExecID; (2) debiting or crediting the order's filled quantity and average price to reverse the original fill's contribution; (3) updating the position by subtracting the busted quantity from the appropriate long or short position; (4) updating the cash ledger by reversing the cash committed or received from the original fill; (5) logging all changes with the bust notification timestamp and reason.
The hardest case is a bust that arrives after the position has been traded against. Consider: account buys 5,000 shares (fill F-001), then sells 2,000 shares (fill F-002). If F-001 is busted, the remaining net position is: long 5,000 - short 2,000 - reversal of long 5,000 = short 2,000. The account is now short 2,000 shares it did not intend to be short in. This condition must be detected immediately and flagged for remediation, typically. The account buys 2,000 shares to cover the inadvertent short.
Evidence to retain: the original fill, the bust notification, the correcting fill entry, and a cross-reference between them must all be retained in the fill ledger. Regulators examining the account's trading activity must be able to reconstruct what happened: the original trade, the bust, and the subsequent remediation trade are all part of the audit record.
DK (Don't Know) resolution process
A DK occurs when a counterparty receives a trade confirmation and has no matching record in their own system. In the institutional workflow: the broker sends a trade confirmation to the buy-side OMS (typically via DTC's Institutional Delivery system or directly via FIX). If the buy-side's operations team does not recognize the trade, they issue a DK.
DK resolution involves comparing records to identify the mismatch. Common causes: the broker allocated a fill from a block order to the wrong buy-side account (the buy-side has the trade booked to a different account, so the specific confirmation looks like a new trade); the buy-side received the fill via their direct FIX connection with the EMS and booked it there, but the broker's institutional confirmation arrived separately with a different reference; or the trade genuinely does not exist in the buy-side's records because a fill was dropped.
Once the cause is identified, resolution takes one of three paths: (1) the buy-side accepts the confirmation with a corrected account, the trade was real but booked to the wrong account; (2) the buy-side accepts and the broker adds the missing booking on their side; (3) the trade is cancelled bilaterally because it was entered in error. DK resolution typically has a T+1 deadline, unresolved DKs by the settlement date create settlement fails.
Testing DK handling means verifying that the OMS can: receive a DK notification, suspend settlement processing for the affected trade, present the discrepancy to operations for investigation, and accept a resolution instruction (match-with-correction or cancel) that updates the system atomically. Systems that route DKs only via email and leave the OMS record unchanged until someone manually edits it are operationally fragile.
Trade amendments and price corrections
A trade amendment changes a specific field of an already-executed trade. The most common amendments are price corrections, when a fill was reported at an incorrect price (due to a data entry error or a system glitch at the venue). The OMS must support price correction by: creating a negative fill at the original price, creating a positive fill at the corrected price, and recomputing average price and P&L effects.
Price correction after marked-to-market creates a retroactive P&L change. If a fill was reported at $100 but should have been $99, the corrected fill shows a gain of $1 per share that previously did not appear. If this fill is from a prior trading day and P&L has already been reported to clients, the correction must be disclosed and the prior day's P&L restated. The OMS must support backdated corrections, applying the correction as of the original trade date, and must log that a backdated correction was made.
Account designation amendments are among the most sensitive corrections because they move a trade from one account to another, affecting both accounts' positions and P&L. Regulators scrutinize these amendments closely, particularly when the reassignment happens to improve P&L for one account at the expense of another (favoring a proprietary account over client accounts, or vice versa). The OMS must require an explicit reason code for every account designation amendment, and the amendment must be reviewed and approved by compliance if it occurs after execution.
Cascade effects and P&L restatement
The most operationally complex bust scenario involves multiple subsequent fills that depended on the busted fill. The OMS must be able to reconstruct the counterfactual fill history, what would the position and P&L have been at each point in time if the busted fill had never occurred. This requires replaying the fill ledger in order, omitting the busted fill and all fills that depended on it.
Most OMS implementations handle this with a "correction mode" that takes the account's fill history, marks the busted fill as voided, and computes positions and P&L from scratch using the remaining fills. This operation can be expensive for accounts with long trading histories but is necessary to produce accurate restated P&L. Firms that cannot do this automatically must do it manually in a spreadsheet, a slow, error-prone process that is inappropriate for large or complex accounts.
Worked Scenario
At 10:15 AM, Account 09 buys 10,000 shares of XYZ at $50.00 (fill F-100). At 10:40, sells 3,000 shares at $51.00 (fill F-101, realized gain $3,000). At 11:00, the exchange notifies a bust of F-100, the price was clearly erroneous (actual market was $45.00 at the time).
- Bust received: OMS receives ExecType=H, referencing F-100. Locates fill F-100: 10,000 shares at $50.00.
- Correcting fill created: F-100B: -10,000 shares at $50.00. This reverses the entire original buy. Fill ledger now shows: F-100 (+10,000 @ $50), F-101 (-3,000 @ $51), F-100B (-10,000 @ $50).
- Position recomputed: From fill ledger: long 10,000 - sell 3,000 - bust reversal 10,000 = net -3,000 (SHORT 3,000 shares). OMS flags the account as inadvertently short. Alert fires.
- Cash recomputed: Original buy committed $500,000. Sell F-101 received $153,000 net (3,000 × $51). Bust reversal releases $500,000 (cash goes back). Net cash effect of bust: +$500,000 restored. But account now has a short position incurring borrowing costs and risk.
- P&L restated: F-101 (sell 3,000) was originally recorded as a gain of $3,000 against a $50 cost basis. With F-100 busted, the cost basis of the sold shares is undefined. The sell is now a short sale. Realized P&L from F-101 is now reclassified as short sale proceeds ($153,000).
- Remediation trade: Operations instructs the desk to buy 3,000 XYZ to cover the inadvertent short. The remediation trade executes at $45.20. Gain on the short cover: $153,000 proceeds minus $135,600 cover = $17,400 (unintentional profit on an inadvertent short, flagged for regulatory disclosure).
- Audit trail complete: F-100, F-101, F-100B, and the remediation trade are all logged with timestamps, reasons, and cross-references.
Measurement Framework
| Measurement | Question it answers |
|---|---|
| Bust processing latency | How long from bust notification receipt to position correction in the OMS? Should be under 5 minutes for automated processing; under 30 minutes with manual intervention. |
| Inadvertent short rate from busts | How often do trade busts create inadvertent short positions? High rate indicates the firm frequently trades against positions that may be busted, a risk management concern. |
| DK resolution time | How long from DK notification to confirmed resolution? Target: same-day for DKs received before 2 PM; next-morning for late DKs. Unresolved DKs create settlement fails. |
| Account amendment frequency and reason distribution | How many account designation amendments per month, and what are the stated reasons? High frequency or unusual reason distributions warrant compliance review. |
| P&L restatement frequency from corrections | How many prior-day P&L figures are restated each month due to amendments or busts? Should trend toward zero as trade data quality improves. |
| Correcting fill audit trail completeness | For every correcting fill, does the fill record include: original ExecID, correction type, correction reason, approver, and timestamp? Any missing field is an audit gap. |
Common Failure Modes
Bust processed against wrong fill
If the OMS matches a bust notification to the wrong fill, because the ExecID lookup returns multiple matches or the matching logic is too loose, the wrong position is reversed. The intended position remains incorrect, and a different position is now doubly incorrect. This is operationally catastrophic and hard to detect because both systems will report positions that look superficially reasonable.
Prevention requires that ExecIDs be globally unique and that bust matching use the full ExecID, including venue prefix, not just a partial match. The matching result must be confirmed by the operations team before the correcting fill is written to the ledger.
Bust processed but order not reopened for re-routing
When a fill is busted, the order that generated the fill should have its filled quantity reversed and the order potentially re-opened for the busted quantity to be re-executed. If the OMS reverses the position and cash but does not update the order's state, the order appears to be fully filled while the position no longer reflects the full expected quantity. The trader may not realize that the order needs to be re-submitted, leaving the portfolio under its target position.
Amendment without compliance review creating cherry-picking appearance
An account designation amendment that moves a profitable trade from one account to another, regardless of the actual reason, creates the appearance of cherry-picking (directing good trades to favored accounts after seeing the result). Even if the amendment was made for a legitimate, documented reason, the pattern is a regulatory red flag. Systems that allow amendments without mandatory compliance workflow approval for amendments after execution create regulatory risk even when the underlying amendments are innocent.
Prior-day bust creating uncorrected client report
When a bust arrives after end-of-day client reports have been sent, the OMS must not only correct the internal position but must also generate a corrected client report. Systems that apply the bust correction internally but do not trigger a client report amendment leave the client with incorrect information. If the client makes investment decisions based on the incorrect report, the firm may have a client service liability in addition to an operational one.
Cascade restatement not covering all fill-dependent calculations
When a bust triggers a cascade restatement, the OMS may correctly recompute positions and fill-level P&L but fail to update derived calculations that reference those positions: risk exposure reports, value-at-risk, regulatory capital calculations, and performance attribution. If these derived calculations are not refreshed after the restatement, they continue to reflect incorrect values until their next scheduled update, potentially hours or days later.
Frequently Asked Questions
What is a trade bust?
A trade bust (also called a trade cancellation or break trade) is the retroactive cancellation of an already-executed trade by the exchange or regulator. Busts typically occur when a trade was clearly erroneous, executed at a price far outside the prevailing market due to a fat-finger error, a system malfunction, or a clearly mistaken order. The exchange nullifies the trade, and both parties are required to return to their pre-trade positions as if the trade never occurred.
How does the OMS process an exchange-initiated bust?
The OMS receives a FIX Execution Report with ExecType='H' (Trade Cancel) or ExecType='G' (Trade Correct) referencing the original fill's ExecID. The OMS must: (1) locate the original fill in the fill ledger; (2) create a correcting fill record with negative quantity and the original price; (3) atomically update the order and position to reverse the original fill's effect; (4) record the bust in the audit trail with the exchange's stated reason. The original fill record must not be deleted, the correction is additive, not destructive.
What is a DK'd trade?
A DK (Don't Know) trade is one that a counterparty refuses to acknowledge. In institutional trading, a broker sends a trade confirmation to the buy-side, and the buy-side 'DKs' it by reporting that they have no record of the trade. DKs can arise from genuine errors (the broker allocated a trade to the wrong account), from miscommunication (the buy-side received the fill via a different channel and already booked it with a different reference), or from outright disputes. Both parties must resolve the DK before settlement.
What is the difference between a bust and an amendment?
A bust nullifies a trade entirely. It is as if the trade never occurred. An amendment (also called a correction or trade modify) changes a specific attribute of the trade: the price, the quantity, or the account designation. Amendments are less disruptive than busts because they preserve the trade relationship but correct a specific data error. The OMS must support amendments by: creating a correcting fill for the original value, creating a new fill for the corrected value, and updating order, position, and cash records accordingly.
What is a clearly erroneous trade under exchange rules?
Exchange rules define clearly erroneous trades as transactions where the price, size, or other terms deviate by more than a specified threshold from the reference price at the time of the trade. For example, NYSE Rule 7.10 (Clearly Erroneous Executions) sets numerical guidelines that vary by security price level and market conditions. Trades that meet these criteria can be busted by the exchange even if both parties agreed to the terms at execution time.
What happens to P&L when a bust arrives after the position was marked to market?
When a bust arrives after EOD P&L has already been computed, the P&L must be restated retroactively. The busted fill is reversed as of the original execution time, not the bust receipt time, to accurately reflect when the trade did and did not exist. If the account traded further against the busted position (e.g., bought 1,000 shares, then sold 500, then the 1,000-share buy is busted), the position and all subsequent P&L calculations must be reconstructed from the fill ledger after removing the busted fill.
How long does an exchange have to bust a trade?
Exchange rules impose time limits on busting trades. For U.S. equities, the requesting party typically has 30 minutes after the erroneous execution to submit a bust request. The exchange then has 30 minutes to decide. After those windows close, the trade is generally deemed final and must settle, even if it was clearly erroneous. Post-window corrections require bilateral agreement between the parties rather than unilateral exchange action.
What is a trade amendment for account designation?
An account designation amendment corrects which account a trade was booked to. This can occur when: an allocation is entered incorrectly (the trade was meant for Fund A but booked to Fund B), when a block order's allocation schedule had an error, or when a trader entered the wrong account code. The amendment requires reversing the original booking from the incorrect account and re-booking to the correct account, updating both accounts' positions and cash, and generating correcting trade confirmations.
What downstream records need revisiting when a bust or amendment lands after reporting?
A single corrected execution can invalidate a chain: the position record, the average cost basis, realized and unrealized profit, any allocation derived from the block, margin and buying power at the time, execution quality measures, and any report already distributed. Recording which artefacts consumed a given execution turns the question of what to recompute into a lookup rather than a search. Where a report was already sent, the correction usually needs communicating rather than silently restating.
References
- NYSE Rule 7.10: Clearly Erroneous Executions: Defines the thresholds and procedures for busting clearly erroneous trades on the NYSE.
- FINRA Rule 11892: Clearly Erroneous Transactions in Exchange-Listed Securities: FINRA's parallel rule for bust procedures across all exchange-listed securities.
- DTCC National Institutional Settlement (NIS): The settlement infrastructure through which DK procedures and trade confirmations are managed.
- FIX 5.0 SP2 Specification: ExecType Values: Defines ExecType='H' (Trade Cancel) and ExecType='G' (Trade Correct) and associated processing requirements.
Educational Disclaimer
This guide is for educational purposes only and does not constitute financial, legal, or compliance advice. Trade bust and amendment procedures vary by exchange, instrument type, and jurisdiction. Consult qualified professionals before implementing correction workflows.