AI in purchase order matching without a purchasing department

5 days ago
3 min read

Introduction

Three-way matching — order against delivery against invoice — is the standard control over what a business pays for. It catches the invoice for goods never received, the price that differs from what was agreed, the quantity that arrived short, and the charge for something nobody ordered. In large organisations it is automatic and unremarkable.

In small businesses it usually does not happen, because there is no purchase order to match against. Somebody phones a supplier, the goods arrive, the invoice is paid because the goods are here. Automating the matching is straightforward once the documents exist, which means the real project is usually establishing purchase orders rather than the matching itself.

1. AI in purchase order matching needs a purchase order to exist

The precondition.

If half your purchases have no order, matching covers half your spend and the uncontrolled half is where the problems are. Introducing simple purchase orders above a value threshold is the prerequisite. Set the threshold low enough to cover the spend that matters and high enough that nobody raises an order for a box of screws.

2. Keep the order process light

Or it will be bypassed.

A number, a supplier, a description, a quantity, a price and an approver. Anything more elaborate in a small business generates workarounds, and a bypassed process controls nothing. A form that takes ninety seconds gets used; one that takes ten minutes gets skipped and then backfilled inaccurately.

3. Record receipt at the point of delivery

The second document.

Someone confirms what arrived, in what quantity, and in what condition. Signing a delivery note without counting is the most common failure and it makes the whole control notional. Short deliveries that are signed for are almost never recovered, because the supplier's record says you accepted them.

4. Set sensible tolerances

Perfect matching is unworkable.

Small variances in quantity, price and delivery charges are normal. Define what passes automatically and what is queried, or the exception queue fills with items nobody should be spending time on.

5. Query the price differences specifically

Where money is recovered.

An invoice priced above the order is either an unagreed increase or an error, and both should be challenged before payment. This is the check with the most direct financial return. Suppliers correct these readily when challenged and almost never volunteer them.

6. Watch for the invoices with no order at all

The category to monitor.

These are where duplicate payments, fraudulent invoices and unauthorised commitments concentrate. Track them as a proportion of total invoices and drive it down.

7. Keep the approval separate from the receiving

As far as you can.

Even in a small team, the person who confirms goods arrived should ideally not be the person who authorises payment. Where that is impossible, a periodic review by someone else is the substitute.

8. Use the matched data to check your prices

An additional benefit.

Once orders and invoices are matched, you have a clean record of what you paid for what, by supplier, over time. That is the dataset that makes supplier price comparison and negotiation possible.

9. Report the exception rate and its causes

The management measure.

How many invoices matched automatically, how many were queried, and why. A rising exception rate points at a supplier problem, an ordering problem or a receiving problem, and the categories tell you which.

Be careful about paying disputed invoices to keep a supplier relationship comfortable. Once paid, recovery depends on the supplier's goodwill, and the discipline of querying before payment is what makes the control worth having.

Conclusion

Establish purchase orders first, because matching cannot work without them.

Keep the ordering process light enough that it is not bypassed, record what actually arrived at the point of delivery, set tolerances so the exception queue contains only meaningful differences, challenge every price variance before payment, monitor invoices arriving with no order as a category in its own right, separate receiving from approval as far as your team size allows, use the matched history as the basis for supplier price negotiation, and report the exception rate with its causes each month.