Supplier invoices matched to POs before anyone retypes them

Matching is where most of the value sits, and it is plain code. The model's job ends once fields are extracted and checked.

A 2-way match compares the invoice with the purchase order: same vendor, a valid open PO, unit prices and quantities within tolerance. A 3-way match adds the goods receipt, so you only pay for what arrived. Tolerances are yours to set, for example 2% or $50 per line, whichever is lower, and they live in a table your controller can edit.

Line matching is the hard part. Supplier descriptions rarely match your item master ("Widget blue 10pk" against "WGT-BLU-10"). The pipeline tries SKU and supplier part number first, then quantity and price, and only then asks a model to suggest a match, which goes to review the first time it appears. Once a reviewer confirms it, the mapping is saved and that pair matches automatically from then on.

Invoices without a PO (utilities, software subscriptions, professional fees) skip matching and go to the budget owner for that vendor or cost center. Recurring ones are compared with the last 3 months and flagged when the amount jumps.

If you do not use purchase orders at all, the pipeline still extracts, checks duplicates and routes approvals. That is a smaller build, near the low end of the range. More on the extraction side in intelligent document processing.

The build is a fixed price between $15,000 and $35,000, inside our $12,000 to $40,000 band for document processing. The low end covers one entity, one accounting system, invoices by email and 2-way matching. Three-way matching, several entities or currencies, line-level coding to cost centers and a backfill of open invoices push it toward the top.

Running costs are billed at cost on your accounts:

The cost that matters more is reviewer time. Thresholds start strict, so in the first weeks more invoices go to review. As vendor mappings build up, the share that passes untouched rises. We report that pass rate weekly, because it tells you whether the build is paying back. See how to measure automation ROI.

If you process fewer than a few hundred invoices a month, start with capture tools built for that volume. Dext, Hubdoc and the invoice capture inside BILL and Ramp read invoices into your ledger for a monthly fee, and a person approves each one. That is often all a 30-person company needs.

A custom pipeline is worth the cost when the checks are the hard part: PO and goods-receipt matching, several entities, unusual layouts, or approval rules those tools cannot express. It also makes sense when invoices arrive alongside other documents you want read the same way.

It is the wrong place to start if your vendor master is unreliable. Duplicate vendors and out-of-date bank details mean a large share of invoices gets flagged on day one, and reviewers learn to click through alerts. We clean the vendor list during the Map stage, or ask you to do it first.

If invoices are one part of a bigger document problem (delivery notes, claims, contracts), scope it as intelligent document processing across those document families, so extraction and review tooling is built once. For contract terms, see the contract review assistant. And if the slow part is getting approvals signed off, a business process automation project on the approval chain may be the cheaper fix.