- From
- Accounts Receivable <[email protected]>
- To
- [email protected]
- Subject
- Invoice 58213, your PO 24-1187
Please see the attached invoice. Thank you for your business.
Carverton Steel
PDFInvoice_58213.pdf · 94 KBThree-way invoice check
It's the three-way match your AP person does by hand today: the invoice against the PO against what was actually received. A small tool that watches your vendor invoice inbox, reads every invoice, finds the PO and the receiver in your ERP, and checks each line before anyone keys it. Nobody sorts receivers or staples paperwork together. Every weekday morning, one email tells your AP person what's ready to enter, what needs a closer look, and why.
9:40 AM. A vendor invoice lands in your invoice inbox.
Please see the attached invoice. Thank you for your business.
Carverton Steel
PDFInvoice_58213.pdf · 94 KBUntil now, somebody printed it, circled the PO number, dug out the receiver and stapled the two together before checking a single price.
What happens next
Each step is marked with what does the work. The AI reads the invoice. Plain software finds, checks and reports.
It reads the PDF the way a person would, scanned paper invoices included: the vendor, the invoice number and date, the PO number, and every line with its quantity, unit price and amount, plus freight, tax and the total. When one invoice covers two POs, each PO gets checked on its own.
If it can't read an invoice cleanly, or there's no PO number on it, it says exactly that and hands it to a person. Nothing gets dropped quietly.
| Ln | Description | Qty | Unit | Amount |
|---|---|---|---|---|
| 1 | 1018 cold-rolled flat, 1/2 x 4 x 144 | 12 | $38.50 | $462.00 |
| 2 | A36 hot-rolled plate, 3/8 x 48 x 96 | 4 | $412.75 | $1,651.00 |
| 3 | 6061-T6 round bar, 2.0 x 144 | 6 | $186.20 | $1,117.20 |
It looks the PO up in your ERP, with its lines and its receivers. The rule your AP person already follows is built in: no invoice gets entered before the material has arrived. If nothing's been received yet, the invoice is held, and it's rechecked every half hour until the receiver posts.
If the PO isn't in your ERP at all, say because it was bought through your accounting system, the invoice is set aside and labeled, so nobody wonders where it went.
Then plain software checks what the AI read against the PO. Every price, to the cent. How many were billed against how many actually came in, not counting anything rejected and sent back. Whether the vendor's own math adds up, line by line and to the total. Whether the invoice bills more than the whole PO is worth. Whether another invoice is already open against the same PO.
It also pulls the GL account off the PO and proposes an entry date in the month the material was received. A small price difference gets a second look. A big one gets flagged to check with purchasing before anyone enters it. The AI never gets the last word. The checks do.
One email goes to whoever you name. Ready to enter: every invoice that passed every check, with its receiver number, GL account and total alongside. Needs intervention: anything that didn't, with the specific reason. Held: invoices still waiting on material. Nothing goes out on weekends.
It doesn't type invoices into your ERP. Your AP person still keys each one, from a list where the finding and checking are already done. If the tool itself ever stops checking the inbox, the subject line says so in plain words, so a quiet morning never passes for all clear.
A ready invoice passed every check listed at the top of this email
Every item in the morning email has a link. It opens a page with three buttons: mark it entered, set it aside, or park it while the vendor sends a corrected invoice. No login, nothing to install. Entered and set-aside items drop off the list. A parked one moves to its own section until the corrected invoice shows up.
When it does, the new one gets checked from scratch. If it looks like a repeat of an invoice already received, it says so: check the new one, set the old one aside, and don't key it twice.
Choose what to do with it. This records your decision and removes it from the digest.
Mark entered Set aside (not an invoice, or handled) Awaiting vendor (corrected invoice expected)When your AP person keys an invoice into your ERP and it flows through to your accounting system as a bill, the next half-hour run finds it there. Same vendor, same invoice number, same amount: the invoice closes on its own. Nobody has to mark anything.
If the bill's amount doesn't match the invoice it checked, or the same invoice number shows up twice, nothing gets closed. The invoice goes back in front of a person with a plain note: one of the two is wrong, compare them before paying.
Where the AI is, and where it isn't
AI is very good at reading a document it has never seen before. It isn't exact, so here it only reads. Every number it pulls off an invoice gets checked against your PO and your receiver before anyone is told the invoice is ready.
It had to earn it
One morning it flagged two of the three invoices it checked. Both invoices were right. A steel supplier doesn't print your part numbers. It bills the material in its own words, like "cold-rolled flat, 1/2 x 5," while your PO carries your own part number. The tool was pairing lines on part number and nothing else, so on one steel invoice it flagged all 13 lines, and every one of them matched the PO to the cent.
Plenty of vendors work that way. Steel suppliers bill the material, and platers and heat treaters bill the operation. So now, for vendors you've marked that way, lines get paired on exact quantity and exact unit price instead. A second review of that fix caught the hole it opened: when you pair lines on price, the price always agrees. So I added one check that no line-by-line logic can get past. An invoice can never bill more than the whole PO is worth.
That's what making one of these hold looks like. You find the invoices that break it, and you close each gap without opening a new one.
Built once, adapted to yours
Everything above is how the tool was built and tested. The parts that do the hard work stay the same. The parts that touch your systems, your vendors and your AP rules get fitted to how you already work.
Platers and heat treaters billing per lot, matched to the lot you sent out.
Hundreds of small invoices a week, with the ones that need a look at the top.
Vendor invoices matched against receipts across more than one warehouse.
How it gets set up
It only reads from them. Nothing gets replaced, and nothing gets written into your ERP.
Which ones print your part numbers and which bill in their own words, how close a price has to be to pass, and who gets the morning email.
Your AP person keeps working the way they do now and checks the morning list against their own, until you trust what it calls ready.
Vendors email it there, and paper ones get scanned into the same place. From then on your AP person works the list instead of the pile, starting with the ones that need a look.
Quoted up front, no hourly billing. I host it and keep it running, and a care plan covers fixes and changes as your vendors change. The code is yours, and I'll transfer it to you at any time.
Linked Operations · AI implementation for manufacturers
Tell me how vendor invoices reach you today and what happens to them after that. I'll tell you straight whether a tool like this fits, whether something lighter would do, or whether it isn't worth it for you.
Email Jason →Jason Markham
Nearly 25 years in manufacturing, including a decade running a machine shop. I build these tools myself.
I help manufacturers and distributors implement AI, automate workflows, and reduce errors with small, focused software builds that take over the back office work: the data, the paperwork, the busywork between the systems they already run.