WorkflowTrading & Execution

Trade Error Management

Trade error management worked as one conversation with seven agents: every error costed, decided and signed the same day

Every trade error costed, decided and signed the same day, with each client made whole.

See one case, screen by screen ↓
demo15eventsof one order's life rebuilt from four systems, each cited to its log line, with the missed chance marked
demo$38,412meteredas the correction filled: $37,512 to one fund, $900 to the other, $0 netted across clients, matched to the cent by a second agent
target100%of errors closed with cause, clause, two signatures and cited evidence
targetSamedayfrom report to signed decision, against about six business days today
In short

What is Trade Error Management?

Trade error management is how an investment adviser logs each trade error, finds its cause, restores the client and decides who pays under its trade error policy. Trade Error Management does that work as a conversation with seven agents that open each case, rebuild the order from the logs, cost the correction per client and apply the policy clause by clause. A compliance officer decides, a second person or the CCO approves, operations books the payment and fund accounting confirms the client is whole.

AI in asset management: a buyer's guide to agentic AI for investment managers →

Updated

The problem

Why trade error management still runs on a spreadsheet

Trade error management starts with a plain duty: when a trade goes wrong (the wrong fund, the wrong side, ten times the quantity, an order never sent) the adviser owes its client the position it would have had, at the firm's cost unless a broker caused it. Anyone looking for SEC trade error guidance finds that the Advisers Act says nothing specific about trade errors, so examiners test each one against the firm's own trade error policy and its fiduciary duty. Today trade error handling runs on a spreadsheet: a trader emails compliance, operations rebuilds the order's life from four systems by hand, someone works out the cost in a workbook, and compliance picks a clause from a policy PDF.

T+1 made it harder. Since May 28, 2024 a US trade settles one business day after trade date, so a wrong allocation is usually settled before anyone sees it, and the fix is a market trade with a real dollar cost. Advisers must keep time-stamped records of each allocation and affirmation under Rule 204-2. The errors in the work are familiar: gains netted against losses across clients, commissions forgotten, one signature where policy wants two, broker claims never chased, the same allocation template causing the same error three times. And an exam request for every trade error and how it was resolved takes about a week to assemble.

typical1dayto settle a US trade since May 28, 2024: a wrong allocation is usually settled before anyone sees it
typical80%of custodian or manager self-affirmed trades affirmed by 9 p.m. on trade date, against 97% through central matching
demo$54,482in 60 daysfrom three allocation errors on one shared order template at the sample firm, each closed on its own
Where a trade error's business days goestimated
By hand6 days
With the solution1 days
  • Noticing, reporting and logging the error1 → 0.1 d
  • Rebuilding the order from the OMS, FIX logs, matching and custodian1 → 0.1 d
  • Working out the correction cost per client0.5 → 0.1 d
  • Choosing the clause and getting a second signature1.5 → 0.3 d
  • Booking the payment and confirming the fund received it2 → 0.4 d

Estimated split for a typical trade error at a manager of the sample firm's size, by hand and with the solution.

How it works

How an error becomes a client made whole

Seven agents open, rebuild, cost and check every error; compliance decides, a second person approves.

What comes in
Signals inbreaks, alerts, notices, reports · any system, any language
Agents at work
Intake agentopen, merge, route
Then
Reconstruction agentevery event cited
Cause agentcause, or a question
Then
Cost agentper client, never netted
Review agentrecompute every dollar
Then
Policy agentclause, payer, route
Pattern agentrepeat causes, fixes
A person decides
Compliance, CCO, operationsdecide, approve, book, confirm
What comes out
Signed decision
Client made whole
Examiner-ready error log
One case, step by step

One trade error, worked as a conversation: from a cash break to a client made whole

At Quillfield Capital, 120,000 Corvane Industrial shares bought for the Equity Income Fund were booked to the Global Value Fund. Nobody typed up a case: the agents opened it themselves, and the compliance officer works it with them in plain words. Here is the trade error resolution that follows, screen by screen, in the working solution.

  1. 01Monday, 11:40 a.m.

    The agents have worked since 7:12; Nadia starts with what needs her

    Nadia Rahman · Compliance officer, Trading Compliance

    Nadia's Today screen shows 23 open cases across 8 desks, 14 waiting for her (5 decisions, 1 question, 7 to close, 1 claim), $212,198 to correct in October and 4 repeat causes. Beside her queue sit the agents' conversation and what they did this morning: at 7:12 the Intake agent opened TE-2026-0318 from a cash break in Equity Income, and at 7:58 it merged Marcus Bell's report of the same error into it (96% match).

    “Seven agents work these cases. Ask what they found, or tell them what to do.”

  2. 02One question

    She asks the agents where to start

    Nadia Rahman · Compliance officer

    Nadia asks “What should I decide first?” The answer ranks her day: TE-2026-0318 first, then the four others due today, and TE-2026-0312, which waits for her answer on §3.1. One click on “Open TE-2026-0318” takes her to the case.

    “Start with TE-2026-0318: $38,412.00, due today at 5:00 p.m., and the CCO still has to approve after you.”

  3. 038:05 a.m.

    The order's life, rebuilt and cited line by line

    Reconstruction agent

    From the order management system audit trail, the FIX log, central trade matching and the custodian, with a chat excerpt from the communications archive, the agent rebuilt 15 events. The error happened on October 15 at 9:44:31 a.m., when saved template US-VALUE-BLOCK v3 filled the account with Global Value and nobody changed it. The time-stamped allocation record (Rule 204-2) opens beside the timeline, and the missed chance is marked: a post-trade check on October 16 closed by operations as “model drift”.

    The Reconstruction agent never edits a source system; it marks gaps instead of filling them.

  4. 0410:52 a.m.

    A cost meter that ticks with the fills and refuses to net

    Cost agent and Review agent

    Derek Lindqvist approved the trade error correction at 8:20: Global Value sold 120,000 at $40.9016 and Equity Income bought 120,000 at $41.1905. The meter built the cost fill by fill: $33,768.00 loss on the unwind, $3,600.00 in commissions on the wrong buy and the corrective sale, $144.00 in SEC Section 31 and FINRA fees, and $900.00 for the higher price Equity Income paid. A minute later the Review agent recomputed it from the raw fills on its own: $38,412.00, a match to the cent, all 19 citations open.

    “No gain arose, and nothing is netted across clients (§2.5).” — Cost agent

  5. 05Before she signs

    “Why doesn't the broker pay?” — asked and answered from the record

    Cause agent and Policy agent

    The Cause agent put the cause at 91%: the template filled the wrong fund and the trader did not change it. The Policy agent applied §2.3, the firm pays, routed the approval to the CCO under §4.2 and listed both funds' boards for the quarterly report. Nadia asks why not the broker, and the answer comes with the allocation record, the clause and the fills behind it.

    “Because Kestrel did what we told it. Our allocation instruction at 4:12:33 p.m. named GVF-0412, Global Value, and Kestrel booked it exactly.”

  6. 06Signed

    She decides with a reason code, and the case goes to the CCO

    Nadia Rahman · Compliance officer

    The approval shows the case, the decision (the firm pays $38,412.00), Trade Error Policy v5.1 §2.3, 37 cited sources with the Review agent's $0.00 difference, and the next step: Catherine Moreau, CCO (§4.2). Nadia picks “Policy applied as proposed”, ticks the signature box and sends it.

    “I have reviewed the evidence and sign this decision.”

  7. 07Approved

    The CCO approves on the same evidence

    Catherine Moreau · Chief Compliance Officer

    At $25,000 or more the policy wants the CCO. Catherine sees who decided it and why, the clause and the evidence on one page, and approves as decided. Nadia could not have approved it herself: the maker of a decision can never check or approve it.

    “Decided by Nadia Rahman · Policy applied as proposed.” Next: Derek Lindqvist to book the payment.

  8. 08Client whole

    Booked from the error account, confirmed in both funds

    Derek Lindqvist and Joanna Pike

    Derek books the drafted ledger entry: $38,412.00 from firm error account 9-ERR-001, $37,512.00 to Global Value and $900.00 to Equity Income, never from client commissions (§2.6). Nothing moves until he books it. Joanna Pike in fund accounting confirms both funds received the cash, and the case closes with every step signed and logged.

    “Closed. The client is whole, two people signed, the payment is booked and confirmed.” — Policy agent

  9. 0911:02 a.m.

    The third error on one template becomes a change request

    Pattern agent

    The Pattern agent linked the case to TE-2026-0251 (Hollis Rail) and TE-2026-0287 (Brightline Pharmaceuticals): three allocation errors on US-VALUE-BLOCK v3 in 60 days, $54,482 in all. Asked “Which fix would save the most?”, it names the size warning being built first (7 errors, $61,940 this year, CHG-55074), then this template, whose change request waits for Sam Deluca, Global Head of Trading. Fixes already in place show their errors before and since.

    The Pattern agent never changes a system; a change request needs the Global Head of Trading.

  10. 10On every queue

    The same conversation on the checks queue

    Leah Brandt · Compliance manager

    Every queue, report and setting has the agents beside it. Leah, who checks decisions under $25,000, asks “Which checks can I approve with one signature?” The Review agent names three, TE-2026-0316, TE-2026-0311 and TE-2026-0304: each under $25,000, decided by someone else, its total recomputed to the cent. Nothing is signed until she clicks “Review and sign them”.

    Every action the agents propose waits for a person's click, and is logged.

Who it’s for

Built for everyone who signs off a trade error.

The same Corvane error, seen by five of the people in the trade error process who report, decide, check, approve and fix it: what their week looked like by hand, and what it looks like now.

NR
Nadia RahmanCompliance Officer, Trading Compliance, New York · decides cause, payer and amount
Compliance officer
Before
Pieces each case together from emails, a spreadsheet and the policy PDF, then picks the clause from memory.
Now
“Give me the clause and the evidence; I'll make the call.” Opens each case rebuilt, costed and checked, asks the agents what she needs, and signs with a reason code.
CM
Catherine MoreauChief Compliance Officer · approves every reimbursement of $25,000 or more
Chief Compliance Officer
Before
Signs large reimbursements between board prep and exam requests, with the sources spread across emails and a workbook.
Now
“If I sign it, I want to see every dollar’s source on one page.” Approves on one page with the maker’s signature, the clause and the cited cost, and approves policy, limit and agent threshold changes before they take effect.
MB
Marcus BellUS Equity Trader, New York · reports errors and executes corrections
US equity trader
Before
Reports an error by email or chat, often without the order facts, and is asked for them again later.
Now
“I'll own the mistake. Just don't make me rebuild the order by hand.” Gives the order ID and one sentence; the agents read the rest and come back only with questions.
DL
Derek LindqvistHead of Trading Operations · approves corrections, books payments
Head of Trading Operations
Before
Approves corrections by chat and closes the same kind of error again and again, one case at a time.
Now
“Fix it once, at the source, and show me it stayed fixed.” Books payments only after approval, and works the repeat causes with their cases and cost.
LB
Leah BrandtCompliance Manager · checks decisions under $25,000
Compliance manager
Before
Re-reads each decision under $25,000 against the workbook and the policy PDF, and cannot easily prove she never checked her own.
Now
Asks which checks are eligible, sees each total recomputed to the cent, and signs three with one signature; checking a decision she made is blocked.
Built on the engine

7 agents. Each with one job, and hard limits.

Seven agents open, rebuild, cost and check every error; compliance decides, a second person approves.

Intake agent

Opens cases from reconciliation breaks, post-trade compliance alerts, custodian notices, broker letters and trader reports; merges duplicate reports with a match score; routes signals that are not trade errors, such as a settlement fail, to the right team.

  • Never closes a case
  • Merges below 90% only with a person's yes
Reconstruction agent

Rebuilds the order's life event by event from the OMS audit trail, FIX logs, central trade matching, custodian settlement and the communications archive, each event cited to its log line, with the error and any missed chance marked.

  • Never edits a source system
  • Marks gaps instead of filling them
Cause agent

Classifies the root cause (who, what, why) with a confidence and an alternative, reading the timeline, the cause categories and past cases.

  • Below 85% confidence it asks the trader or compliance instead of deciding
Cost agent

Meters the correction cost per client as fills arrive: price, commissions, fees, FX and opportunity cost, from the correction fills, commission schedules, fee tables and FX rates.

  • Never nets gains against losses across clients
  • Never books money
Review agent

Recomputes every cost independently from the raw fills, on a different model family from the Cost agent, and opens every citation before a person sees the case.

  • Blocks the case when its total differs by more than $1
Policy agent

Applies the trade error policy clause by clause: who pays, the approval route, and ERISA, UCITS and fund board notices. Drafts broker claims, reads replies in any language and keeps the 10-day clock.

  • Proposes only
  • Asks compliance when a clause does not settle the case
Pattern agent

Finds causes that keep coming back across cases, drafts the control fix for the OMS team with the cases as evidence, and later measures whether the fix worked.

  • Never changes a system
  • A change request needs the Global Head of Trading
Compliance officer, CCO, operations, fund accounting

Decide, approve, book, confirm. The agents propose; a named person decides.

Ask in plain words

Ask the agents about any trade error, in plain words

The agents' conversation sits on every case, queue, report and setting. Ask what they found, or tell them what to do; answers cite their sources, and every action they propose waits for your click.

What should I decide first?

Start with TE-2026-0318: $38,412.00, due today at 5:00 p.m., and the CCO still has to approve after you. Then the four due today: TE-2026-0314 ($14,770), TE-2026-0303 (214 accounts), TE-2026-0313 (gain stays) and TE-2026-0310 (no cost, fairness review). TE-2026-0312 waits for your answer on §3.1.

Why doesn't the broker pay?

Because Kestrel did what we told it. Our allocation instruction at 4:12:33 p.m. named GVF-0412, Global Value, and Kestrel booked it exactly. Section 2.4 applies only when a broker departs from our instruction. I checked all 214 fills: no departure.

Can anything be netted against this loss?

No. Global Value's loss and Equity Income's higher price belong to two different clients, and §2.5 forbids netting across clients. Neither account had a gain from this error to offset inside it.

What if the CCO limit fell to $20,000?

This year 5 more reimbursements would have gone to the CCO: 19 instead of 14. The change needs the CCO's approval and would become Trade Error Policy v5.2.

Every screen

The working solution, as it ships.

13 screens from the working solution, on its sample data. Pick one to see it large.

Trade error queue and the agentsThe compliance officer's trade error queue beside the agents' conversation: open cases, decisions waiting, October's correction cost, repeat causes and what the agents did this morning.
Ask the agents what to decide firstA plain question, “What should I decide first?”, answered with the cases ranked by deadline and amount, and one click to open the first.
The trade error case and cost meterThe error in plain words, the order facts, the trade error correction cost per fund with $0 netted across clients, and the decision panel with each clause cited.
The order rebuilt, every event citedThe timeline rebuilt from the logs with the error and the missed chance marked; the time-stamped allocation record kept under Rule 204-2 opens beside it.
Agents on the caseThe Policy agent and Pattern agent explain their work with sources, and answer “Why doesn't the broker pay?” from the allocation record and the fills.
Decide and sign under the trade error policyThe compliance officer's decision with the trade error policy clause, the cited evidence, a reason code and the signature, routed to the CCO at $25,000 or more.
CCO approvalThe Chief Compliance Officer approves on the same evidence, with the maker's name and reason; the maker can never approve her own decision.
Client made wholeDecided, approved, booked from the firm trade error account and confirmed in both funds: the closed case with every step signed and logged.
When the policy does not settle it, the agent asksA missed trade given by chat: the Policy agent quotes §3.1 and asks the compliance officer whether it was a firm order, with what each answer means for who pays.
Maker-checker approvalsThe checker asks which checks she can approve with one signature; the Review agent names three, each under $25,000, decided by someone else and recomputed to the cent.
Broker claimsClaims against brokers with their 10-day clock; a Tokyo broker's letter read in Japanese beside the English, the figures highlighted.
Repeat causes and their fixesTrade error causes that keep coming back, with their cases, cost and proposed fix, the agents' answer on which fix saves the most, and whether fixes in place worked.
Trade error reportingTrade error reporting in two minutes: the trader gives the order ID and one sentence, and the Intake agent reads the order and fill and proposes the error type to confirm.
Governance

Trade error management built for the examiner's question: cited, signed, on the record.

Every value cites its sourceEach event, cost line and agent statement opens its log line, fill, record or policy clause, and the Review agent opens every citation before a person sees the case.
Two people on every reimbursementA compliance officer decides cause, payer and amount; a second compliance officer checks under $25,000, the CCO approves $25,000 or more, and the COO joins at $250,000 with a fund board notice.
Segregation of duties, enforcedThe maker of a decision can never check or approve it, the trader who made the error can never approve its correction, administrators never sign, and fund accounting confirms receipt independently.
Agents propose; people decideThe agents never decide, book money or edit a source system. Every action they propose in the conversation waits for a person's click and is logged; below their confidence line they ask, and every human override carries a reason code.
Your trade error policy, clause by clauseNo reimbursement is netted across clients or paid from client commissions; ERISA accounts and Luxembourg UCITS funds follow their own clauses, including a CSSF Circular 24/856 assessment.
A chained audit trail, kept 7 yearsWho, what, when, why and on which evidence, for people and agents, in entries that cannot be edited. Policy versions and agent thresholds are approved by the CCO, each agent pins its prompt and model version, the Review agent runs on a second model family, and data stays in its region.
Configuration

Your trade error policy, not ours

Quillfield's own Trade Error Policy v5.1 was read into 14 rules at setup, each tied to its clause and accepted by compliance. Every approval limit is a setting: proposed by an administrator or compliance, approved by the CCO and saved as a new policy version.

SettingDefaultChoose from
Trade error policyTrade Error Policy v5.1, effective March 1, 2026: 14 rulesA new version is read by the Policy agent; compliance accepts each rule
CCO approves reimbursements of$25,000 or more (§4.2)Proposed by an administrator or compliance, approved by the CCO
CCO, COO and fund board at$250,000 or more (§4.2)Proposed by an administrator or compliance, approved by the CCO
Report an errorWithin 1 hour of discovery (§2.1)When missed: the compliance officer is told
Decide cause, payer and amountSame business day as the final cost, 5:00 p.m. ETClock held while an agent's question is open; when missed: the compliance manager, then the CCO
Client made wholeWithin 5 business days of the decisionWhen missed: the Head of Trading Operations and the CCO
Broker reply to a claim10 business days (§2.4)Then the firm pays the client and pursues the claim
Where data livesUS East · EU (Frankfurt) · Asia (Singapore), kept 7 yearsRegion per desk; legal holds; chat excerpts only
Connections

Works with the systems a trade error already touches

Order management systemorders, blocks, templates and the audit trail
Execution management and FIX logsorders sent, executions, cancels
Central trade matchingtime-stamped allocations, confirmations and affirmations
Portfolio accounting and custodianpositions, cash, reconciliation breaks, settlement and notices
General ledgerfirm error account bookings, written only after approval
Broker mailboxes and portalsclaims and replies, in any language
What it changes

The difference, in numbers.

Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
100%
of errors closed with cause, clause, two signatures and cited evidence
318 errors this year
each signed twice
target
30%
fewer repeat errors in a year, as repeat causes are fixed at their source
Todayeach case closed on its own
With agents3rd repeat flagged, fix drafted
target
1day
from report to signed decision, against about six business days today
By hand≈ 6 business days
With agentssame day

“demo” = seen in the working solution, on its sample data · “target” = the design goal, measured in the live solution · “estimated” = our estimate · “typical” = published figures (SEC fact sheet for Release 34-96930: T+1 compliance date May 28, 2024, and time-stamped allocation and affirmation records under Rule 204-2; DTCC, Equities by the Numbers, April 2026: by 9 p.m. on trade date, 80% for custodian or manager self-affirmation against 97% through central matching). On exams: Dechert, Dealing with Investment Errors, and Strictly Business, Handling Trade Errors, on the Advisers Act's silence and examiners' requests; SEC Division of Examinations, Fiscal Year 2026 Examination Priorities. Quillfield Capital and the people, funds, brokers, issuers and orders named on this page are fictional: characters and sample data in the working solution.

Questions

What trading and compliance teams ask about trade error management.

What is trade error management?

Trade error management is how an investment adviser logs each trade error, finds its cause, restores the client and decides who pays under its trade error policy. Trade Error Management does that work as a conversation with seven agents that open each case, rebuild the order from the logs, cost the correction per client and apply the policy clause by clause. A compliance officer decides, a second person or the CCO approves, operations books the payment and fund accounting confirms the client is whole.

What is a trade error policy, and how does the solution apply it?

A trade error policy is the adviser's written rule for what counts as a trade error, how it is reported and corrected, who pays and who approves; trade error policy and procedures are a standard section of the compliance program that the annual review under Rule 206(4)-7 tests. At setup the Policy agent reads your own policy into rules, each tied to its clause, and compliance accepts each one; in the working solution Trade Error Policy v5.1 became 14 rules. On every case the agent quotes the clause it applied and the approval route.

Who pays for a trade error: the firm, the broker or the client?

Under the sample policy the firm pays for errors caused by its people, systems or vendors (§2.3), the broker pays when it departed from the firm's instruction (§2.4), and the client never bears an error the firm caused. A gain stays with the client account in which it arises (§2.5). The firm's share is booked from its trade error account, never from client commissions (§2.6). When a broker owes the loss, the Policy agent drafts the claim and keeps the 10-business-day clock, after which the firm pays the client and pursues the claim.

Can trade error gains and losses be netted across clients?

Not in this solution. The Cost agent keeps each client's amount separate and never nets gains against losses across clients, and the Review agent recomputes every dollar on its own. ERISA plan accounts follow their own clause (no gain netted against any loss, no corrective cross trades), and Luxembourg UCITS funds get a CSSF Circular 24/856 assessment.

How does it help with T+1 and time-stamped allocation records?

Under T+1 a wrong allocation usually settles before anyone sees it, so the case has to open from the first signal. The Intake agent watches reconciliation breaks, post-trade alerts, custodian notices and broker letters, and the Reconstruction agent reads the time-stamped allocation and affirmation records kept under Rule 204-2 into the timeline, each event cited.

Is there SEC trade error guidance, and what do examiners ask for?

The Advisers Act says nothing specific about trade errors, so examiners test each one against the firm's own trade error policy and its fiduciary duty, and typically ask for every trade error since the last exam and how each was resolved; the SEC's fiscal 2026 examination priorities put advisers' adherence to fiduciary standards first. The examiner pack builds that answer from the record: the trade error log, each case file with its evidence, policy versions, decisions and signatures, the audit trail and agent versions, hash-verified, with wealth client names and account numbers masked and every download logged.

Do people stay in control of trade error decisions?

Yes. The agents propose and never decide, book money or edit a source system. A compliance officer decides with a reason code, a second person approves (the CCO at $25,000 or more), the trader who made the error never approves its correction, and every override is logged with its reason.

How long does it take to go live?

The Agentic Solution Engine builds and deploys it from your requirements and documents (your trade error policy, approval limits, fund register and a sample of past cases), and it goes live once every quality gate has passed. First-time setup connects the systems of record, reads the policy into rules for compliance to accept, maps funds and approvers, and replays past cases so you can compare the agents with what your people decided.

See it on
your error log.

We'll run Trade Error Management on a sample of your own past trade errors, your trade error policy and the order records behind them.