Every morning, someone in accounts payable opens the supplier invoices. Some come in as email PDFs, some from a supplier portal, a few still by fax. For each one, they look up the purchase order in the ERP, check what the warehouse actually received, compare quantities and unit prices line by line, then key the invoice in. When a supplier bills a backordered item or last quarter's price, the invoice sits in a pile until someone reaches the buyer.

This is the three-way match: invoice, purchase order, receipt. It is where a distributor protects its margin, because a small price variance repeated over thousands of lines adds up. It is also a task many owners hesitate to hand to AI. What if the agent pays the wrong amount? Where do our supplier prices and terms end up? Who signs off? This article answers those questions plainly.

What the work looks like today

  • Invoices arrive in several formats and layouts, one per supplier, and each one is read and retyped.
  • Units of measure differ: the supplier bills by the box, the PO is in units, the receipt is in cases.
  • Partial shipments and backorders mean the invoice no longer matches what was received.
  • Price increases reach the invoice before they reach the purchase order.
  • Discrepancies are tracked in email threads, sticky notes or a spreadsheet only one person understands.
  • Nobody sees which invoices are blocked, or why, until the supplier calls about a late payment.

What the agent does, and what it never does alone

An agent reads each incoming invoice and extracts the supplier, invoice number, lines, quantities, unit prices and taxes. It finds the matching purchase order and receipts in the ERP and compares them line by line. When everything matches within the tolerances you set, it prepares the invoice for entry with the PO and receipt attached. When something does not match, it says exactly what: which line, how many units were received, what price is on the PO, what price was billed, and the likely cause, such as a partial delivery or a unit of measure.

The agent prepares. It does not decide. Its limits are written into how it is built, not left to good intentions.

  • It never pays a supplier or releases a payment run.
  • It never changes a price, a quantity or a purchase order in the ERP.
  • It never accepts a price increase, a substitution or a credit on its own.
  • It never writes to a supplier to dispute an invoice without a person reading and approving the message.
  • It never sets the tolerances: you decide what counts as a match and what goes to a person.

Where the data stays and who approves

The agent only gets access to what it needs: the accounts payable inbox, open purchase orders, receipts and the supplier file. A custom build can run inside your own environment and your existing Microsoft 365 or Google accounts, so your supplier prices and terms are not copied into yet another platform. Every step is logged: what the agent read, what it compared, what it proposed and who approved it. When an auditor or the controller asks why an invoice was paid, the answer is in one place.

Approval stays where it belongs. The AP clerk reviews and approves matched invoices in batches instead of keying each one. Exceptions go to the buyer who placed the order, with the variance already explained, because the buyer knows whether the price increase was agreed. Above an amount you set, a second approval is required. The controller still approves the payment run, exactly as before.

What known distributors and wholesalers have already done

FleetPride, a distributor of heavy-duty truck and trailer parts with over 250 locations in 45 states, had a backlog of more than 25,000 invoices in exception state, mainly due to price and quantity variances, according to Transcepta, the company it turned to for its invoice processing. With 2- and 3-way PO matching at the line level, Transcepta reports over 95% straight-through processing for PO-based invoices and real-time invoice status updates for suppliers.

Chadwell Supply, a family-owned wholesaler of appliances, electrical fixtures and more, with 19 US locations, needed a better way to match invoices to purchase orders and receipts. According to Medius, after automating three-way matching it increased touchless invoice capture from 20% to 75%, processes about 100,000 invoices a year, and opened new branches without adding AP staff.

Baldwin Supply Co., a Midwest wholesale distributor of mechanical power transmission and electrical control products, implemented Esker Accounts Payable with Enlighten.Net's ENet Docs, a cloud, AI-driven solution for data capture and touchless processing. According to the case study summary on CaseStudies.com, it eliminated 98% of its paper, reached touchless processing for 75% of non-direct PO invoices and reduced invoice turnaround to three days.

These results are published by the vendors about their own customers, and these companies are not VirtuaTech clients. What they show is useful anyway: matching invoices to orders and receipts is a mature use of automation, and the people's work shifts from retyping to settling the exceptions that actually need judgment.

A tool built for your rules, not another subscription

Large AP suites are built for large volumes. They bring their own portal, per-user licences and features a mid-size distributor will never use. Often what you need is narrower: matching connected to your ERP and your inbox, using your tolerances, your units of measure and your supplier habits, with approvals in the tools your team already opens every day. A tool built only for that is easier to control, because you know exactly what it can touch.

Where to start and how to measure

  • Pick the three to five suppliers that send you the most invoices.
  • Write down your tolerances: price, quantity, freight, and the amount above which a second approval is needed.
  • Run the agent in shadow mode for a few weeks: it proposes, your team keeps working as usual, and you compare.
  • Measure on your own data: time per invoice, number of exceptions and their causes, invoices blocked for more than a week, price variances caught before payment.
  • Widen to more suppliers only once your team trusts what it sees.

The goal is not to remove anyone from accounts payable. It is to stop spending the morning retyping invoices that match, so the team has time for the ones that do not, and so no price variance gets paid simply because nobody had time to look.