Agents
The first pass is done before anyone opens the case
Drop in a statement and a chain of agents goes to work: read every page, reconcile every balance, fix the dates, categorise, check the PDF for tampering and run the analysis. By the time an analyst opens the case, the evidence is laid out and the questions are flagged. People decide.
Case activity · on upload
Three statements, 214 pages
| Agent | Did | Result |
|---|---|---|
| Reader | 4,112 transactions from 214 pages | Done |
| Reconciler | 2 amounts moved to the right column | Fixed |
| Dates | US date order detected and resolved | Fixed |
| Forensics | One PDF re-saved in an editor | Warning |
| Analyst | 18 modules, 5 flags for review | Ready |
| Decision | Waiting for your policy run | You |
Illustrative case.
02 / The agents
Each one does one job, the same way every time
The checks that matter are deterministic. The same statement gives the same balances, the same flags and the same verdict on every run, which is what an audit trail needs.
01
Reader
Extracts date, description, amount in, amount out and balance for every transaction, from native PDFs and scans, on statements of one page or several hundred.
02
Reconciler
Walks the balance chain row by row. When an amount sits in the wrong column, the printed balance proves it and the reconciler moves it. Breaks it cannot explain are flagged.
03
Date resolver
Works out day-month or month-day order from the whole statement rather than one row, so 04/05 means the same thing on page one and page sixty.
04
Categoriser
Sorts every transaction into categories that feed affordability, the cash P&L and the analysis modules, under rules you can change.
05
Forensics
Reads the PDF's metadata and structure for signs of editing, re-saving or generation by tools no bank uses, and returns Normal, Warning or High Risk with the findings.
06
Analyst
Runs revenue, affordability, overdraft, unpaid, lender, HMRC, director and gambling analysis and marks what needs a person to look.
01 / How it runs
Read, check, analyse, then hand over
-
1
Read
Every page of every statement, any bank and layout, into transactions that keep the page they came from.
-
2
Check
Running balances reconciled against the printed ones, wrong-column amounts corrected, day and month order resolved across the whole statement.
-
3
Analyse
Categorisation, eighteen analysis modules and document forensics, run for the kind of applicant in the case.
-
4
Hand over
The case opens with figures, flags and the transactions behind each. Your policy runs on it when you ask, and a person makes the call.
03 / What they do not do
Agents prepare. People decide.
- No agent approves or declines anyone. The Decision Engine applies the policy you wrote, when you run it, and shows the rule behind every outcome.
- No agent contacts an applicant or sends anything outside your team.
- Every figure an agent produces can be traced to the transactions, and every transaction to its page.
Why not one big agent?
A single model asked to "analyse this statement" gives a different answer each run and cannot show its working. Small agents with narrow jobs and hard checks between them give the same answer twice. More on that choice.
Also on the platform