Accountancy practice
AI Finance Operations
My qualified team spends its week processing documents instead of advising clients.
A practice handling roughly 1,800 client documents a month across photographs, scans, portal exports and email attachments. Qualified staff transcribe rather than advise, month-end compresses against filing deadlines, and the advisory conversation that clients would actually pay for keeps getting postponed.
The product
AI Finance Operations
The queue, the approval screen, the exception list. Every number is readable and every handover is visible.
Built by Koderead to show the operating system. Figures are a worked example.
Watch one record
Where the handover actually happens.
A screenshot shows a state. This follows a single record through the system, including the point where it stops and waits for a person.
Invoice arrives06:02
Email attachment, one of two hundred this morning.
Fields extracted06:02
Tuned against this practice's own document corpus.
Matched to a purchase order06:02
Supplier recognised, PO located, terms retrieved.
Validation fails — stopped06:03
High confidence and still held. Accuracy is not the control.
Cleared from the exception queue09:15
Field highlighted, cause stated. Seconds, not reopening the PDF.
Posted, indexed, searchable09:15
Filed against supplier, period and purchase order automatically.
State
- From
- Whitrow Logistics
- Format
- PDF, scanned
- Reference
- INV-88216
- Touched by a person
- Not yet
No filing is submitted unattended — everything is prepared for review and signature
Deeper into the build
The screens where a person is still in the loop.
A queue is easy to show. What matters is what happens at the record, at the approval, and at the exception — because that is where the design either holds or does not.
- Supplier
- Whitrow Logistics
- Net extracted
- £4,087.60
- VAT extracted
- £817.52
- Total extracted
- £4,905.12
- Matched purchase order
- PO-11482
- PO total
- £4,837.12
- Difference
- £68.00
System recommendation
Do not post. Three-way match failed on total. The difference corresponds to a fuel surcharge line absent from the purchase order — likely legitimate, but it needs an authorisation before it reaches the ledger.
- Three-way match failed
- Supplier on file
- Within tolerance for approval
Payment release always requires human authorisation. Nothing posts on a best guess.
High extraction confidence and still held. Accuracy is not the control — validation is.
- Documents processed
- 1,842
- Straight through
- 1,536
- Errors caught pre-ledger
- 97
83.4%
- Straight-through rate — month 161%
- Straight-through rate — month 376%
- Straight-through rate — month 683.4%
- Supplier not on file118New vendor approval
- Tax inconsistent with lines74Field highlighted for correction
- Duplicate reference30Blocked before posting
- Illegible scan42Re-request from client
264 items awaiting a person, grouped by cause so one decision clears a class rather than a case.
Straight-through rate is worked upward month on month by tuning against the exceptions, not by relaxing the checks.
The change
Where the work moved.
Amber marks a step the system performs. Solid ink marks one a person still performs. The counts above each column say the same thing in numbers.
Today
5 human steps- Performed by Customer
Client sends records
Photos, scans, sheets
- Performed by A person
Opened and sorted
By hand
- Performed by A person
Fields transcribed
Line by line
- Performed by A person
Cross-checked if time allows
- Performed by A person
Filed to a shared drive
- Performed by A person
Discrepancy found at month end
After
1 human step- Performed by Customer
Client sends records
- Performed by Automated
Extracted and classified
- Performed by System
Validated against rules
Totals, tax, PO
- Performed by System
Posts straight through
When checks pass
- Performed by A person
Clears the exception queue
Failures only
- Performed by System
Indexed and searchable
- Automated
- A person
- System
- Customer
Scope of authority
What this system is not allowed to do.
On a real engagement this is a document your operations lead signs before anyone writes code.
- No filing is submitted unattended — everything is prepared for review and signature
- Payment release always requires human authorisation
- A document failing validation stops; it is never posted on a best guess
- Confidence thresholds are set by the practice's finance lead, not by Koderead
- Client data is excluded from model training in writing
Built from
The solutions behind this build.
Your version of this
This took a mapped workflow before it took any code.
If this looks like your accountancy practice, the place to start is the same place we started here.