Six-Step AI Workflow with Human Oversight
Each step shows the workspace, what the AI completed, and what still needs human review.
Steps 2, 4 and 5 need a person. Step 2 is waiting for approval right now. Click it to open the full walkthrough.
Estimates are directional and based on stated assumptions. All names, organizations, and identifying details have been anonymized in accordance with our confidentiality agreements.
How a Global Financial Services Firm Built a Ledger Reconciled Daily Against the Bank's Own Statement
Every transaction from the moment it lands off a bank feed to the moment a client sees it in their own view. The agents book what checks out, hold what does not, match the books to the bank's own statement, and carry the month to one screen a person signs. People decide three things: a held payment, a month's close, and a filing that goes out in the firm's name. Six stations, run as a loop: what breaks at reconciliation and what a filing check catches become the checks tomorrow's entries book against.
What Was Broken
What We Built
Six stations and 14 subagents. Each subagent carries its own tasks and its own refusal.
How It Runs
Transaction Booking
Nobody is asked anything hereAgents collect every entry off every feed, put each one in one format, book the ones whose amount, date and account check out, and hold the rest for a re-send. Nothing waits on a person here. A held entry is never booked and never dropped.
Fraud Review
A person answers hereAgents score every payment against that account's own months of history, hold the ones the history cannot explain, and build the case file a person decides on. A fraud analyst decides every held payment. Releasing or blocking a client's money is a decision that carries a name.
Daily Reconciliation
Nobody is asked anything hereAgents match every booked entry to a line on the bank's statement, clear the timing gaps that close themselves, and carry each true break to the close with a correcting entry already drafted. Nothing waits on a person here. A drafted correcting entry is never posted; it waits for a person at the close.
Monthly Close
A person answers hereAgents check every account against its own reconciliation, draft the accrual and correction journals with the evidence attached, and put the month, the forecast and the open items on one screen for a signature. The controller posts the drafted journals and signs the close. A month closes under a person's name, not an agent's.
Regulatory Filing
A person answers hereAgents build each filing from the closed books on the regulator's own template, tie every figure back to the entries that sum to it, and hold the filing until a person signs. The compliance officer signs every filing. A report goes to a regulator in the firm's name, and that name is a person's to give.
Client Reporting
Nobody is asked anything hereAgents refresh every client's view from the same ledger the close signed, answer a client's question out of that record with the entries quoted, and say not in the record where it is not. Nothing waits on a person here. An answer the record cannot carry is refused, not rounded.
Where a Person Decides
Operating Model
This changes how work flows through the team.
What Transfers, What Must Be True
Failure Modes
What breaks this pattern:
An entry with a bad amount, date or account goes straight into the ledger. Every report built on that ledger now carries the error.
A break the desk cannot explain gets a drafted entry that clears it. The books now agree with a guess instead of the bank.
Anyone who wants the audit trail different gets it edited. The record shows what someone wanted, not what happened.
A figure built on held or unexplained entries goes into the client report with no hold shown. The client acts on a number nobody inside the firm stands behind.
Directional Outcomes
What the agent counts, and the station that counts it.
These counts are the tallies from one monitored run of the agents. They are not monthly or annual totals.
What Runs Where
Every step names the subagent that does the work, the record it writes, the thing that raises a question for a person, and what it is allowed to touch. This is drawn from the source, not from a diagram somebody kept in sync by hand.
feed-intakeledger/booked/<txn-id>.jsonhold-unbookable-entryledger/booked/**, ledger/held/**, the feeds read-onlyfraud-screenfraud/cases/<case-id>.jsonrelease-or-block-held-paymentfraud/cases/**, ledger/** read-onlystatement-matchrecon/<date>/matched.json, recon/<date>/breaks/<break-id>.jsoncarry-break-to-closerecon/**, ledger/** and the statements read-onlyclose-the-monthclose/<period>/checklist.json, close/<period>/journals/<journal-id>.jsonsign-the-closeclose/**, everything else read-onlyregulatory-filingfilings/<report-id>/draft.md, audit/<report-id>/trail.jsonsubmit-in-firm-namefilings/**, audit/**, close/** read-onlyclient-viewportal/<client-id>/view.json, portal/answers/<question-id>.jsonanswer-not-in-the-recordportal/**, everything else read-onlyStack
Every system this agent reads or writes.