◆ Autonomous Worker
Runs the bank's general-ledger reconciliations against every sub-ledger and source feed, matches the millions of lines that tie, and isolates the breaks with a proposed explanation. Runs nightly across the book, auto-clearing immaterial timing items and escalating breaks above materiality to a senior controller agent.
Memory
Working The account under reconciliation and its current break list.
Episodic Recurring reconciling items and how they were cleared before.
Semantic Chart of accounts, account-mapping rules, materiality thresholds.
Procedural Matching and break-resolution playbooks refined from senior-controller-agent overrides.
Store Vector store + reconciliation ledger
Orchestration
router-fanout MCPA2A
Harness · Managed Agents … high-throughput session; context editing clears matched-line output; sandboxed code-exec for the matching and difference math.
Tools
{ } General ledger API { } Sub-ledger + source feeds API ›_ Matching + reconciliation engine Code exec ⌕ Reconciliation workpaper store Retrieval ⇄ Senior controller agent A2A
Evals & guardrails
- Reconciliation-tolerance guardrail: breaks above materiality cannot auto-clear … forced escalation.
- Daily agent-as-judge sample of cleared reconciling items vs. accountant gold set.
- Immutable, exam-ready workpaper produced for every account reconciled.
- OpenTelemetry trace of every match decision retained.
Offline reflection
Nightly consolidation replays the day's senior-controller-agent overrides as Reflexion-style lessons, sharpening the matching and break-classification playbooks (procedural memory).
Frontier edge
- ▲Self-improving fleet: a matching pattern learned on one bank's chart of accounts is shared across the reconciliation population between nightly runs.
- ▲Continual learning (eval-gated): every senior-controller-agent override on a break becomes a lesson, lifting auto-match rates without a full retrain.
- ▲Formal action-gating: each auto-clear is a cryptographically signed, replayable action that provably cannot exceed the materiality threshold.
A sample run
Trigger Nightly batch lands; GL-to-payments-sub-ledger reconciliation kicks off.
- 1Match GL postings to sub-ledger lines on amount, date and reference.
- 2Isolate the unmatched residual; classify timing vs. true difference.
- 3Pull the source detail for each break; propose an explanation.
- 4Write the workpaper; auto-clear immaterial timing items.
Output A reconciled account with a documented break list … three timing items auto-cleared, one $2.1m true difference escalated to the senior controller agent with the source detail attached.
In numbers
~40,000
Accounts reconciled / night
99.4%
Lines auto-matched
11s
Avg. time per account