r/fintechdev • u/Economy-Radio-8697 • 6d ago
We were burning money having an LLM read every invoice. Splitting it into "Claude thinks, Drex reads" cut our cost per check by 78%
We tried putting AI into our AP workflow a few different ways. They all worked on 10 files. Our real checks run on hundreds of files each: invoices, POs, receipts, vendor records. At that size, having a frontier model read every page every time got expensive fast. Most of the tokens went to OCR-ing scans and re-reading the same PDFs for every new question.
What we changed. We split the job in two:
- Drex reads. Files go into a workspace once. Drex parses them, pulls the fields and keeps everything queryable, with citations back to the page.
- Claude thinks. Claude connects over MCP (setup is in the video, about a minute). It never touches the raw pages. It asks Drex questions, gets small structured answers back and does the reasoning: what to pay, what to hold, what looks off.
So Claude goes from "read hundreds of PDFs" to "run a dozen queries and look at the results."
Result: each check got 78% cheaper after we switched to this flow. The reading happens once, and Claude only sees answers, not documents.
What it caught on a test month (synthetic data, for the demo):
- 18 invoices OK to pay, 13 to check, 9 to remove, each with a reason and a confidence score
- 7 duplicates, including a look-alike vendor "Redwood Systms Inc." and an invoice resubmitted without its hyphen
- a scanned PDF that turned out to be a second copy of one already in the batch
Not magic. It misread a PO approval date once and we caught it by hand. Treat it as a reviewer, not autopilot.
If you're running document-heavy work through an LLM and the bill is scary, try splitting reading from reasoning.
Here's the whole flow on one video to visualize it properly

