Rigby builds an AI agent that compares every invoice line against its purchase order and goods receipt, flags discrepancies and duplicates, and routes exceptions to a human. It verifies and flags. It never moves your money. Live in days, flat fee.
It is the single most important control in AP. Done well, it stops overbilling, duplicate payments, and silent price creep. Done by hand, it is slow, error-prone, and the first thing that gets skipped when volume spikes. Rigby runs the comparison at line level, every time, against the documents your ERP and operations systems already hold.
What you agreed to buy, from whom, at what unit price, in what quantity.
What was actually delivered: quantities received, condition, date logged.
What the vendor is billing you for, line by line, with their pricing and totals.
Five steps, all running on top of the ERP, TMS, and document tools you already use.
The agent ingests the invoice from email, EDI, or a shared folder, extracts header and line-level data, and identifies the referenced PO number.
It pulls the matching purchase order and, for 3-way matching, the goods receipt from your ERP or TMS via API.
Line by line, it compares quantities, unit prices, units of measure, and totals against your configured tolerances.
Discrepancies, duplicates, price variances, and missing receipts are categorized and surfaced with the supporting evidence.
Clean invoices land in your approval queue; exceptions go to the right human in Slack, Teams, or email with one-click context.
We are precise about what the agent owns, what we scope carefully, and what we will not touch.
Once you have this done you won't have to worry about missing document errors and the downstream consequences ever again.
For a freight operator running on McLeod, Rigby pulls delivery records and supporting document files directly from the TMS API, checks each document for legibility, and detects mismatches between the load, the BOL, and the rate confirmation before billing goes out. The same engine powers line-level invoice matching: same retrieval, same comparison, same exception routing, applied to AP.
Read the case studyFlat fee, live in days. Rigby verifies and flags. Your team keeps approvals and payments.