The job
AP receives vendor invoices and pays them. Somewhere between the PO, the goods receipt, and the invoice, things drift: a price that isn’t the one that was agreed, a quantity billed that was never delivered, a credit note that was issued and never applied, the same invoice submitted twice under two numbers. Checking every invoice against its PO and receipt is exactly the work nobody has time for, which is why it’s usually sampled — and why the errors that get through are systematic rather than random.This is the continuous sibling of run an audit. That recipe runs these checks backward over 12–24 months of history to find money already lost; this one runs them on invoices as they arrive, before payment. Most teams do the lookback first — see from audit to prevention.
What you’ll build
- Each invoice becomes a case.
- The agent matches it to its PO, checks the received quantities, compares line prices against agreed prices, looks for duplicates and unapplied credits, and produces an audit verdict.
- Clean invoices come back
pass. Everything else comes back with the specific discrepancy, the amount at stake, and the evidence.
Ingredients
The starter SOP
Walkthrough
1
Load the reference data
Create
po_master, goods_receipts, credit_notes, and vendor_master as Storage tables. Keep them current with a scheduled workflow against your ERP — stale PO data produces false variances, which is the fastest way to lose your reviewers’ trust.2
Create the reconcile table
Invoice Audit, with Operating Procedures: Audit incoming vendor invoices according to the SOP.Output Fields: invoice_number, vendor, po_number, po_match_status, duplicate, quantity_variance, price_variance, unapplied_credit, total_exposure, verdict, flags. Grant Data Access to all four storage tables.3
Backfill a month you already know
Run last month’s invoices — a set where you know what was clean and what wasn’t. It calibrates the tolerances and shows you what the agent flags that your process currently misses.
4
Review
Work the
fail cases first, then needs_confirmation. Comment with the rule, not the outcome: “this vendor’s framework agreement supersedes the PO price — check the agreement before flagging” is something the SOP can absorb.What good looks like
A clean pass:Matched invoice INV-77301 to PO 4500219 on the quoted PO number; vendor Halvard Supply matches. No duplicate — no other Halvard invoice at 3,412.00 in the last 90 days. All 4 lines received in full. Prices match the PO exactly. No open credits for this vendor. Verdict: pass. Exposure: 0.00.A case the agent correctly refuses to resolve:
Invoice INV-77354 from Halvard Supply, 3,412.00, dated 4 days after INV-77301 for the same amount. Different invoice number and different article on line 2 (ART-5590 vs ART-5591), so this is not an exact duplicate — but the amount and window match the near-duplicate rule.The agent did the whole comparison and then stopped exactly where the evidence stopped. That’s a ten-second decision for AP instead of a twenty-minute investigation.duplicate: suspected, verdictneeds_confirmation. Both invoices listed. Not deciding: the article difference could be a genuine second delivery or a re-issue with a typo, and the vendor’s remittance history doesn’t distinguish them.
Iterating
Vendor-specific reality is what the starter SOP can’t know. It arrives through review comments:Reviewers keep overriding price variances for Halvard Supply — they have a framework agreement with quarterly price steps that the PO doesn’t reflect. Add a rule: for vendors with a framework agreement, check the agreement price before flagging a variance, and flag the PO as stale instead.Then run the improvement loop monthly against the accumulated review feedback.
Hardening
Intake from a mailbox
Route
invoices@ into the project so cases are created as invoices arrive.Agentic approval on the pass bucket
Enable Auto Review so clean invoices under your threshold clear automatically and AP works the exceptions.
Push the verdict back
A workflow writes the audit result onto the invoice in your AP system. It stays the system of record; nothing pays without approval.
Extraction upstream
At volume, structure invoice headers and line items first, then audit the rows.
Run the lookback too
The same checks over 12–24 months of history — read-only, and usually where teams start.
From audit to prevention
Why the lookback comes first, and what changes when these checks go continuous.
All vendor names, invoice numbers, article numbers, and amounts in this cookbook are invented. Replace them with your own data.
