Distribution · 2025
Automating supplier document handling with document AI
Three people were keying 1,200 supplier invoices a week. We automated the routine majority and kept humans on the cases that need judgement.
- Client
- A regional building-supplies wholesaler
- Duration
- 9 weeks
- Services
- Data & AI, Software Engineering
- 92%
- Invoices processed straight through
- 1,200
- Documents handled per week
- 3 FTE
- Redeployed from data entry
The challenge
Around 1,200 supplier invoices arrived weekly across PDF, scanned paper, and email body text, in as many formats as there were suppliers. Three full-time staff keyed them into the ERP. Transcription errors surfaced weeks later as payment disputes, and the backlog grew each quarter. An off-the-shelf OCR product had been trialled and abandoned because it failed silently — wrong values entered the ERP with no indication anything was uncertain.
What we did
- 01
Started by measuring the actual distribution of document formats. Around seventy percent of volume came from twelve suppliers, so most of the value was reachable without solving the general case.
- 02
Built an extraction pipeline combining a document model with deterministic validation — totals must reconcile, dates must be plausible, supplier references must exist. The model proposes; the rules verify.
- 03
Made confidence explicit and routed on it. High-confidence, fully-reconciling documents post automatically; anything uncertain goes to a review queue with extracted fields shown against the source document.
- 04
Designed the review screen so correcting a field takes a keystroke, on the basis that the humans handling exceptions matter more to throughput than the model's raw accuracy.
- 05
Wrote back to the existing ERP through its supported interface, leaving the finance team's downstream processes and reports untouched.
The outcome
About 92% of invoices now post without human involvement. The remaining 8% reach a review queue taking a fraction of the original effort and — critically — the system no longer fails silently, because anything it is unsure about it declines to post. The three staff previously keying invoices moved to supplier management and exception handling.
Built with
- Python
- Document AI
- PostgreSQL
- AWS
- React
“The previous tool was confidently wrong, which was worse than useless. This one tells us when it does not know, and that is exactly why we trust the 92%.”
Next case study
Next step
Have something
similar?
Most of our work starts with a company that knows something is wrong but isn't sure what to build. That's a good place to begin.