SystemInvestment Operations & Middle Office

Failed Trade Management

Failed trade management where agents find the cause, price the miss and check the fix, and two people decide before each market's cut-off

Target 20–30% fewer fails, each fix cited and checked before the market’s cut-off.

See one case, screen by screen ↓
demo49minfrom the unmatched status to matched on the sample trade, 59 minutes before Euroclear Bank's cut-off
demo99.98%of status messages, allegements and counterparty emails in 11 languages linked to their trades by the agents
demoEUR 1,184a dayof CSDR penalty avoided on one sale fixed before cut-off, and a EUR 9.6M fund overdraft with it
target20–30%fewer settlement fails, each fix cited and checked before the market's cut-off
In short

What is Failed Trade Management?

Failed trade management — also called settlement fails management, or trade fails management — is the work of finding, fixing and accounting for trades that are unaffirmed, unmatched or failing to settle: reading the status, finding the cause, chasing the counterparty, re-instructing before the market's cut-off, and reconciling the penalties afterwards. Failed Trade Management gives settlement and trade support teams seven agents that link every message to its trade, name the cause with evidence, price a miss, and draft and check the fix, while an analyst approves and a second person releases.

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

Updated

The problem

Why failed trade management still runs on portals, inboxes and spreadsheets

Failed trade management is a race against cut-offs. Since the US moved to T+1 under SEC Rule 15c6-1 on May 28, 2024, a settlement team has one evening to affirm a trade and one morning to fix it, and Europe, the UK and Switzerland move to T+1 on October 11, 2027. Every market and custodian has its own amendment deadline in its own time zone; once it passes, the trade fails for the day. Yet the work is still done by reading MT548 reason codes in custodian portals, opening the allegement, searching a shared mailbox for the counterparty's new instruction — often written in German, French or Japanese — checking the SSI record, re-keying the instruction and tracking who is chasing what in a spreadsheet.

The cost lands on the funds. Under CSDR settlement discipline every late business day draws a cash penalty — 1 basis point of the trade a day for liquid shares — charged through the custodian, and a sale that fails can leave a fund short of the cash for its next purchase. Wrong standing settlement instructions cause about one fail in five, the most preventable cause there is. And at month end someone still has to reconcile the penalty reports, dispute the errors and chase the credits brokers did not pass on.

typical3.01%of DTC transactions failed in April 2026, up from 2.83% before T+1
typical1bp a dayCSDR cash penalty on a failing trade in liquid shares, for every business day it is late
typical~20%of trade fails caused by incorrect standing settlement instructions
Where a six-analyst desk's day on settlement fails goes, in analyst-daysestimated
By hand5 days
With the solution1.3 days
  • Reading status codes in custodian portals1 → 0.1 d
  • Finding the counterparty's instruction in emails and letters1.3 → 0.2 d
  • Checking the SSI and pricing what a miss costs0.8 → 0.1 d
  • Drafting chasers and re-keying instructions1 → 0.3 d
  • Second checks, releases and escalations0.5 → 0.4 d
  • Penalty reports and tracking who is chasing what0.5 → 0.1 d

Estimated split of one day's exception work for a desk of six settlement analysts, by hand and with the solution.

How it works

How a failing trade gets fixed before cut-off

Seven agents link, explain, price, draft and check every fail; an analyst approves and a second person releases.

What comes in
Messages in40,212 trades today · status, allegements, affirmations, emails in any language
Agents at work
Intake agentlink every message
Forecast agentscore tomorrow
Then
Cause agentthe real reason, cited
Then
Penalty agentprice a miss
Chaser agentdraft the fix
Then
Checker agentre-check every fix
Cut-off agentplan to each deadline
A person decides
Analyst, supervisorapprove, then release
What comes out
Matched before cut-off
Penalties reconciled
Evidence pack
One case, step by step

One failed trade, worked with the agents from unmatched to matched

Friday, October 16, 2026, at Quillfield Capital, a global asset manager with settlement desks in New York, London and Singapore: 40,212 trades settle today in 31 markets, 183 exceptions are open and 37 need a person. Here is one of them — a EUR 11.8 million sale failing at Euroclear Bank — screen by screen, as the analyst works it with the agents.

  1. 0113:04 London

    Her afternoon, and what the agents already did

    Anika Shah · Settlement operations analyst, EMEA

    Anika works the Euroclear, CREST and Clearstream lanes from London. Today shows 8 items waiting for her of the 14 exceptions assigned to her, 1 h 25 min to Euroclear Bank's 15:30 Brussels cut-off, 96 fails so far against 118 at this time yesterday, and EUR 186,420 of penalties avoided in October. Since 7 a.m. the agents have read 18,406 status messages, 2,214 allegements and 412 counterparty emails in 11 languages, and linked 99.98% of them to their trades.

    Checker agent: “Re-checked 386 proposed fixes before they reached a person; stopped 9, including a quantity question on QF-88177.”

  2. 02The lanes

    Every exception racing its own market's cut-off

    Anika Shah · Settlement operations analyst, EMEA

    One lane per market — DTC, Euroclear Bank, CREST and Hong Kong — on one hours-from-now axis, each with a red line at its local cut-off and a clock in its own time zone. Every open exception sits where the agents expect to fix it, colored by cause and sized by the money at stake a day. 19 trades are projected to miss, EUR 1,418 a day at stake if nothing changes. Hong Kong has closed, and its lane is marked stale because the sub-custodian's file is 24 minutes late.

    “Closed for today. 13 trades rolled to Monday, October 19. Chasers sent in Chinese and English.”

  3. 0314:04 Brussels

    QF-88213 is unmatched, and the agents already know why

    Intake agent and Cause agent

    The sale of 410,000 Hallberg Industrie AG to Brennmoor Securities AG for the Quillfield European Equity Fund — EUR 11,840,800, about $13.7 million — is unmatched at Euroclear Bank, reason REAG. The Intake agent linked the MT548 status and Brennmoor's MT578 allegement. The Cause agent, at 0.97 confidence, names the reason: our instruction still carries Brennmoor's old account 23715, because the trade was enriched on October 14 at 10:12 and the SSI team verified the new account 41908 on October 15 at 16:20.

    Cause agent: “Same cause on 3 more Brennmoor trades settling Monday.”

  4. 04The evidence

    The counterparty's German email, beside the English

    Anika Shah · Settlement operations analyst, EMEA

    Every statement cites its source. Jana Kessler of Brennmoor wrote on October 14 at 08:31 Frankfurt: “Neues Konto: 41908 (bisher 23715)”. The Intake agent's English sits beside the original, with the same lines highlighted in both. The other tabs hold the status message, the allegement, the SSI record, our instruction, the penalty and the history.

    The Intake agent translates every message and keeps the original beside the English.

  5. 05Before she decides

    What does a miss cost? She asks.

    Anika Shah and the Penalty agent

    The Penalty agent has priced the miss: EUR 1,184.08 a day — 1.0 basis point of EUR 11,840,800, liquid shares — or EUR 2,368 by Monday's close, charged to the fund through the custodian. The sale also funds Monday's Vantaa Grid purchase, so a miss would overdraw the fund by EUR 9,630,100. Anika types “What if Brennmoor doesn't match by 15:00?” and the agents answer with their sources: call Brennmoor's settlement desk on the number on file and escalate to Rafael Mendes at 15:00, half an hour before the cut-off.

    Penalty agent on buy-ins: “Not applicable: mandatory buy-ins are not in force under CSDR.”

  6. 0614:05:12

    Drafted by one agent, re-checked by another, approved by her

    Anika Shah · maker

    The Chaser agent drafted the cancel-and-replace of our MT543 — receiving-agent account 23715 to 41908, the only field that changes — and a short note to Brennmoor in German. The Checker agent passed it 6 of 6: the verified SSI, a match with Brennmoor's own instruction, a valid format, no sanctions hit, and quantity, amount and date unchanged. Above $5M the release is the supervisor's. Anika approves with the reason “Verified SSI — re-instruct”.

    “You are the maker. You cannot also release this instruction.”

  7. 0714:07:03

    Above $5 million, the supervisor releases

    Rafael Mendes · Settlement operations supervisor

    Partials, shapes, buy-in responses and anything above $5M wait in Rafael's queue, each with the rule that sent it there and the Checker agent's result. He releases QF-88213 with the reason “Checked against the evidence”; the SWIFT gateway sends the cancel and the new MT543 at 14:07:40, and the custodian acknowledges at 14:07:52. Nobody releases what they approved: Anika's own partial on QF-87952 reads “You approved this: someone else releases it”.

    Rafael Mendes: “Nothing above five million leaves without my eyes on it.”

  8. 0814:31:06

    Matched, 59 minutes before the cut-off

    Intake agent and Penalty agent

    The custodian's status comes back matched at Euroclear Bank. The Penalty agent records EUR 1,184 a day avoided and no overdraft on Monday, and October's penalties avoided rise to EUR 187,604. The maker, the checker, the gateway and every agent step are on the trade's record, with the time and the reason.

    Cause agent: “Three more Brennmoor trades settling Monday still carry account 23715. Shall I prepare the re-instructions?”

  9. 09Monday, scored today

    The same cause, fixed before it fails

    Forecast agent

    The Forecast agent scored Monday's 31,980 settlements on trade date: 214 score 0.60 or more. The top three are the Brennmoor trades still on account 23715 — QF-88240 at 0.96, QF-88231 and QF-88214 at 0.95. One approval prepares all three re-instructions: two go to a second analyst, Diego Ramos, and QF-88240, at EUR 5,917,200, to Rafael. Over the last 20 days, 38% of the trades it flagged failed, against 0.86% of all trades.

    Forecast agent: “I propose pre-chases; I never send one on my own.”

  10. 10When the agents disagree

    A quantity question goes to a person

    Checker agent

    Kaito Shoken's letter, in Japanese, offers 300,000 Kinsei Robotics shares on Monday and the remainder on Tuesday, and the Chaser agent drafted an acceptance of the partial. The Checker agent disagrees: our trade is 320,000 and Kaito's instruction is for 300,000, so the gap is a quantity mismatch (DQUA), not only short securities. Both arguments are on the screen, and the analyst chooses: accept the partial of 300,000, or query the quantity with Kaito.

    Checker agent: “Accepting the partial would leave 20,000 unexplained … A person decides.”

Who it’s for

Built for everyone who touches a failing trade.

The same afternoon, seen by five of the people who carry it — what their day looked like, and what it looks like now.

AS
Anika ShahSettlement operations analyst · EMEA desk, London
Settlement operations analyst
Before
Reads reason codes in custodian portals, hunts for the counterparty's new account in a shared mailbox, often in German or French, and re-keys the instruction under the clock.
Now
Opens each trade with the cause cited, the miss priced and a checked fix drafted; reads the evidence, asks the agents what she needs and approves with a reason.
RM
Rafael MendesSettlement operations supervisor · EMEA, London
Settlement operations supervisor
Before
Releases partials, shapes, buy-in responses and anything above $5M, and has to reassemble each case before he puts his name to it.
Now
Works one queue by rule — 3 partials, 2 shapes, 1 buy-in response, 3 above $5M — each with the Checker agent's result, and is escalated 60 minutes before a market's cut-off.
GH
Grace HollowayHead of Trade Support (global) · New York
Head of Trade Support
Before
Answers to the COO and the fund boards for fail rates and penalties: “I need to know which counterparties cost us money, and why.”
Now
Signs off the month-end CSDR penalty reconciliation once Rafael prepares it — September: 1,191 of 1,206 penalties agree, 15 appeals drafted worth EUR 6,240.
KA
Kenji AraiCounterparty relationship manager · Singapore
Counterparty relationship manager
Before
Takes repeat-failing counterparties to service reviews: “Give me the evidence before I call their head of settlements.”
Now
Opens Brennmoor's scorecard — a 2.30% fail rate, the highest of 14, with 3 of its last 6 fails traced to one SSI change — and claims the credits two brokers have not passed on.
OF
Owen FairleySSI team · checker
SSI team checker
Before
Guards the SSI master against changes that arrive by email, including ones that only look like they came from a counterparty.
Now
Calls back on the number on file before he approves a change, and sees the look-alike domain flagged as possible fraud before anyone acts on it.
Built on the engine

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

Seven agents link, explain, price, draft and check every fail; an analyst approves and a second person releases.

Intake agent

Reads settlement status (MT548 / sese.024), allegements (MT578 / sese.028), pending statements and penalty reports (MT537), affirmation reports, custodian fails files and counterparty emails and letters in any language, and links each one to its trade, keeping the original beside the English.

  • Never discards a message it cannot link: below 0.95 it waits for a person with the best candidates
  • Never acts on an SSI change: routes it to the SSI team and flags look-alike senders
Forecast agent

Scores tomorrow's settlements for fail risk on trade date, from positions and cash in portfolio accounting, each counterparty's settlement history, central matching status and the SSI change log, and says why in plain words.

  • Never sends a chaser on its own; proposes pre-chases
Cause agent

Names the real reason for each fail — not just the status code — with cited evidence from the message history, the allegement, the email thread and the SSI master, and finds other trades with the same cause.

  • Below 0.85 confidence, asks a person
  • Every statement cites its source
Penalty agent

Prices the CSDR penalty, funding and overdraft cost and buy-in risk before the cut-off, reconciles daily and monthly penalty reports against its own calculation, and drafts appeals and credit claims.

  • Never books or disputes a penalty without sign-off
  • Prices with the rate table version in force that day
Chaser agent

Drafts the chaser in the counterparty's own language, from templates in 11 languages, and the amended instruction: a cancel-and-replace, a partial or a shape request.

  • Never sends an instruction
  • Never edits an SSI
Checker agent

Re-validates every fix before a person sees it: the verified SSI, the counterparty's allegement, format, sanctions, unchanged economics and the release rule. It runs on a separate model family from the agent that drafted the fix.

  • Cannot approve; a failed check blocks release
  • A disagreement with the Chaser agent goes to a person with both arguments
Cut-off agent

Plans the day backward from each market's cut-off, in its own time zone and holiday calendar, re-plans when a clock or a status moves, and escalates what will not make it.

  • Never changes an owner without telling them
  • Escalations notify; they do not act
Analyst, supervisor, SSI team

Approve, release, verify SSIs. The agents propose; a named person decides.

Ask in plain words

Ask about any failed trade, in plain words

Every working screen has the agents beside it. Ask about a trade, a market, a counterparty or a penalty, or tell them what to do: each answer cites its source, and anything that moves a position is only prepared for a person to confirm.

Why is QF-88213 failing?

QF-88213 is unmatched at Euroclear Bank because our instruction carries Brennmoor's old account 23715. Brennmoor moved to 41908 in a German email on October 14, and its own instruction already uses 41908. Our SSI master has had the verified account since Oct 15 at 16:20; this trade was enriched the day before.

Which trades will miss today's cut-offs?

19 trades are projected to miss today's cut-offs, EUR 1,418 a day of exposure: 6 at Euroclear Bank (cut-off 15:30 Brussels), 5 at CREST (15:00 London) and 8 at DTC (14:00 New York). I have highlighted them on the lanes.

Re-instruct every Brennmoor trade still on the old account

Three more Brennmoor trades settling Monday still carry account 23715: QF-88214 (EUR 2,633,600), QF-88231 (EUR 3,658,200) and QF-88240 (EUR 5,917,200). I have prepared all three re-instructions for your approval: two will go to a second analyst to release, and QF-88240, above $5M, to Rafael Mendes.

What did CSDR penalties cost our funds in October?

In October to date, CSDR penalties charged to Quillfield funds are EUR 41,880; credits received are EUR 29,310 of EUR 33,940 expected, so EUR 4,630 has not been passed on by two brokers. The Quillfield European Equity Fund bore the most: EUR 9,860 charged, EUR 2,980 after credits.

Every screen

The working solution, as it ships.

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

TodayThe settlement analyst's home: items waiting, the next cut-off, fails so far against yesterday, CSDR penalties avoided, market clocks and what the agents did since 7 a.m.
Cut-off lanesEvery failing or unaffirmed trade on one lane per market, moving toward that market's own cut-off, colored by cause and sized by money at stake.
The trade, with the agents' workA failed trade's cause cited by the agents, the penalty priced, the cancel-and-replace drafted and checked 6 of 6, and the approval panel for the analyst.
Evidence in any languageThe counterparty's German email beside the English, the new SSI account highlighted in both, with the status message, allegement and SSI record a tab away.
Ask the agentsThe analyst asks what happens if the trade does not match by 15:00, beside the CSDR penalty math and the fund's cash ladder.
Approved, released, matchedMaker and checker on the record, the instruction sent through the SWIFT gateway, matched before the cut-off, and three more trades with the same cause.
ApprovalsMaker-checker release queue for settlement exceptions: partials, shapes, buy-in responses and amendments above $5M, with self-release blocked.
When the agents disagreeThe Checker agent questions a partial settlement drafted from a Japanese letter, and the analyst decides with both arguments shown.
Settlement fail predictionMonday's settlements scored for fail risk on trade date, with the reason for each and the pre-chase or re-instruction proposed.
CSDR penaltiesCSDR penalties charged, credits received and not passed on, penalties avoided, the month-end reconciliation and the cost by cause.
Counterparty scorecardOne counterparty's fails, causes, open trades, read-only SSI change log and contacts, with the agents' findings for the service review.
SSI requestsStanding settlement instruction changes routed to the SSI team, with a look-alike domain flagged as possible fraud and the original beside the English.
Audit trailEvery message, agent step, approval, release and status change with who, when, why and the evidence, chained, with an evidence pack to export.
Governance

Failed trade management with every fix cited, checked and released by two people.

Every cause, price and fix citedEach statement links to the passage it came from — the status message, the allegement, the counterparty's email in the original and in English, the SSI record, the penalty rate table.
Two agents check, two people decideThe Checker agent re-validates every fix the Chaser agent drafts. The analyst approves; a second analyst releases below $5M, and the supervisor releases partials, shapes, buy-in responses and anything above $5M. Nobody releases what they approved.
SSIs change only through the SSI teamSettlement staff can request an SSI check but cannot record, approve or edit an SSI. The SSI team records the change, calls back on the number on file, and a second person approves it — the maker never checks their own change.
Look-alike requests are stoppedAn email from brennmoor-sec.co, a look-alike of Brennmoor's real domain brennmoor-sec.de, asking for payments to a new bank account is flagged as possible fraud and routed to the SSI team. Nothing changes in the SSI master.
What the agents may not doSend an instruction, edit an SSI, accept a partial, shape or buy-in, book or dispute a penalty, or change an owner without telling them. The SWIFT gateway sends only what a person released.
A chained audit trail and evidence packsEvery message, agent step, approval, release, send and status change is recorded with who, when, why and the evidence, each event chained to the one before it. Overrides of an agent carry a reason code and are reviewed monthly; records are kept 7 years, EU records in the EU region.
Configuration

Your release rules and cut-offs, not ours

Thresholds, cut-offs, escalations and penalty rates are settings. The platform administrator proposes a change with a reason, and it takes effect only after a second administrator approves it.

SettingDefaultChoose from
Second-analyst releaseAmendments below $5MSet by the firm in Thresholds and rules; held until a second administrator approves
Supervisor release$5M and above; every partial settlement, shape and buy-in responseThe amount is the firm's to set (the screen's example change: $5M to $4M)
Cause agent confidence floor0.85 — below it, the agent asks a personSet per agent, with its version and last evaluation
Intake linking threshold0.95 — below it, the message waits for a personSet per agent, with its version and last evaluation
Follow-up chaser20 minutes without a replyService levels and escalation
EscalationTo the supervisor 60 minutes before cut-off; to the Head of Trade Support 30 minutes before, above $5MService levels and escalation, with follow-the-sun ownership
Amendment cut-offsDTC 14:00 New York · Euroclear Bank 15:30 Brussels · CREST 15:00 London · Hong Kong 14:30Per market, in local time, with its holiday calendar and penalty regime — 31 markets
CSDR penalty ratesCommission Delegated Regulation (EU) 2017/389: 1.0 bp a day for liquid sharesA rate change is a reviewed setting with a new version; each day is priced with the version in force
Connections

Works with the systems a settlement desk already runs on

Order management systemtrades and allocations, about 40,000 settling a day
Global custodian and SWIFT gatewayMT548, MT578 and MT537 or ISO 20022 in; MT54x instructions out
Central matching and affirmationaffirmation status and confirms against the 9 p.m. ET cut-off
Portfolio accounting and fund administratorpositions, cash ladders, and penalty and overdraft bookings by fund
SSI master, CRM and sanctions screeningverified standing instructions (read-only), contacts, screening
Settlement mailboxes and documentscounterparty emails and letters in any language, originals kept
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
20–30%
fewer settlement fails, each fix cited and checked before the market's cut-off
Today3.01% of DTC trades fail
With agents20–30% fewer
typical
1bp a day
of CSDR penalty avoided on every liquid-share trade fixed before cut-off; every charged penalty reconciled
Missed cut-offEUR 1,184 ($1,380) a day on EUR 11.8M ($13.8M)
Fixed in timeEUR 0
target
100%
of unaffirmed US trades chased before 9 p.m. ET, ready for Europe's T+1 on October 11, 2027
chased before 9 p.m. ET
SEC Rule 15c6-2

“demo” = seen in the working solution, on its sample data · “target” = the design goal, measured in a pilot · “estimated” = our estimate · “typical” = published figures and rates (DTCC equity trade volume insights — DTC fails 2.83% before T+1 and 3.01% in April 2026; Commission Delegated Regulation (EU) 2017/389 — CSDR cash penalty rates; TABB Group for DTCC — about 20% of fails from incorrect SSIs; SEC Release 34-96930 — T+1 under Rule 15c6-1, and Rule 15c6-2; ESMA final report on settlement discipline for T+1 — October 11, 2027). EUR figures are sample data. People, firms, funds, counterparties, issuers and identifiers named on this page are fictional — characters and sample data in the working solution.

Questions

What settlement and operations teams ask us.

What is failed trade management?

Failed trade management — also called settlement fails management, or trade fails management — is the work of finding, fixing and accounting for trades that are unaffirmed, unmatched or failing to settle: reading the status, finding the cause, chasing the counterparty, re-instructing before the market's cut-off, and reconciling the penalties afterwards. Failed Trade Management gives settlement and trade support teams seven agents that link every message to its trade, name the cause with evidence, price a miss, and draft and check the fix, while an analyst approves and a second person releases.

What causes failed trades, and how does it find the cause?

The usual causes are an SSI mismatch, an unaffirmed or unmatched trade, short securities, short cash and other data errors such as a wrong amount or settlement date; incorrect standing settlement instructions alone cause about one fail in five. The Cause agent reads the status code, the counterparty's allegement and its emails or letters in any language, names the real reason in one sentence with its sources, and finds other open trades with the same cause.

How are CSDR penalties calculated?

Under Commission Delegated Regulation (EU) 2017/389 the daily cash penalty is a rate on the trade's value — 1.0 basis point a day for liquid shares, 0.5 for illiquid shares, 0.20 for corporate bonds, 0.10 for sovereign debt, and the central bank rate for lack of cash. For CSDR penalty management, the Penalty agent prices each fail before the cut-off, reconciles every daily and monthly penalty report against its own calculation, drafts appeals and chases credits brokers did not pass on; the supervisor prepares the month end and the Head of Trade Support signs it off. Where there is no cash penalty regime, as in the UK and US, it prices funding and overdraft cost instead.

Does it handle T+1 settlement exceptions and trade affirmation by 9 p.m. ET?

Yes. SEC Rule 15c6-2 asks brokers to complete allocations, confirmations and affirmations by the end of trade date, and unaffirmed or unmatched trades have their own view. For each unaffirmed US trade the Chaser agent drafts a chaser asking the broker to affirm in central matching; the design goal is every one chased before the 9 p.m. ET affirmation cut-off on trade date. In the sample data, 96.6% of Thursday's US trades (6,002 of 6,214) were affirmed by 9 p.m. ET. The Forecast agent proposes pre-chases before 9 p.m. ET and 23:00 CET, ahead of Europe's move to T+1 on October 11, 2027.

Can it predict settlement fails before the settlement date?

Yes. The Forecast agent scores the next day's settlements on trade date from positions and cash, counterparty history, central matching status and SSI changes, and says why each one is at risk. In the working solution it scored 31,980 Monday settlements and flagged 214; over the last 20 days, 38% of flagged trades failed against 0.86% of all trades. It proposes pre-chases and never sends one on its own.

Can the agents or the settlement team change standing settlement instructions?

No. Settlement staff can only request an SSI check. Changes go to the SSI team, which records them, calls the counterparty back on the number on file and has a second person approve; the maker never checks their own change. Emails from look-alike domains are flagged as possible fraud before anyone acts on them.

Do people stay in control of every instruction?

Yes. The agents draft and check; they never send an instruction, accept a partial, shape or buy-in, or book a penalty. The analyst approves every fix with a reason code, a second analyst or the supervisor releases it, nobody can release what they approved, and every step is on a chained audit trail.

How long does it take to go live?

The Agentic Solution Engine builds and deploys it from your requirements and documents — your release rules, cut-off calendar, systems of record and a sample of past fails — and it goes live once every quality gate has passed. First-time setup ends with a test on yesterday's fails, so you see what the agents would have caught before you rely on them.

See it on
your fails.

We'll run Failed Trade Management on a sample of your own past settlement fails, status messages and counterparty emails.