Skip to content

AP invoice matching

This playbook covers AP invoice matching: entering a supplier’s invoice in the ERP and matching it to its purchase order and receipt, so that it is ready for a person to release for payment. It describes the work today, what our forward-deployed engineers build and who does what at each level of the autonomy ladder.

Supplier invoices arrive as PDFs in an AP inbox. A few still come by mail and are scanned, and some large suppliers send them by EDI. An AP clerk keys each one into the ERP: supplier, invoice number, date, purchase order number, lines, freight, tax and total.

The ERP then does the three-way match of invoice, purchase order and receipt. It checks that the quantity billed is the quantity received, at the price on the purchase order. The ERP matches well once the data is keyed. The work is the keying and the mismatches.

  • The price changed and the purchase order was never updated.
  • The supplier billed the full quantity, and receiving has entered a partial receipt or none yet.
  • Freight, a pallet charge or a surcharge appears that is not on the purchase order.
  • The invoice quotes no purchase order number, or one that is already closed.
  • The same invoice arrives twice, once by email and once by mail.

To resolve a mismatch, the clerk emails the buyer or the receiving lead and waits. Meanwhile the invoice sits, the supplier calls about payment and an early-payment discount lapses. At month end the controller has to estimate what was received and not yet invoiced.

Invoices with no purchase order, such as utilities and services, need coding to a ledger account and an approval from the manager who spent the money.

The work touches the AP clerk, buyers, receiving and department managers. The workflow owner is typically the controller.

  • Screens: an invoice screen that shows the supplier’s PDF beside the entered invoice, with the purchase order lines and receipts it was matched to and each difference marked.
  • Queues: invoices to enter, fed from the AP inbox. Mismatches, routed by reason: price to the buyer, quantity to receiving, a missing purchase order to the person who ordered. Invoices with no purchase order that await coding and approval.
  • Rules: the match tolerances your controller sets for price and quantity. Duplicate checks on supplier, invoice number, date and amount. Which suppliers may bill freight, and how. Who approves an invoice with no purchase order. And one rule with no tolerance: an invoice that shows new bank details or a new remit-to address always goes to a person.
  • Integrations: reads of suppliers, purchase orders and receipts. One write-back: enter the invoice against its purchase order and receipt, through an interface the ERP supports. The ERP still runs its own match and does the posting.

The workflow ends when an invoice is entered and matched. Choosing what to pay and when, and releasing the payment, stay with your controller and AP team at every level.

Level What the agent does What people do
Level 0 (Recorded) Nothing yet. AP keys invoices on a screen that shows the PDF beside the fields and records every correction and the reason for every mismatch.
Level 1 (Assisted) Reads the invoice and drafts the header and lines. Finds the purchase order and the receipts and shows where they differ. AP checks the draft and keys the invoice.
Level 2 (Prepared) Prepares the complete invoice, tied to its purchase order lines and receipts, with each variance explained. For an invoice with no purchase order, proposes the coding from how that supplier was coded before. AP approves every invoice before it is entered. The department manager still approves spend that has no purchase order.
Level 3 (Supervised) Enters invoices that match the purchase order and the receipt within the controller’s tolerances, from suppliers on its list, under an amount limit. AP handles the mismatches and spot-checks a sample of what the agent entered.
Level 4 (Autonomous) Owns matching for invoices backed by a purchase order, including routine follow-up the rules cover, such as asking receiving to confirm a quantity. The controller sets the tolerances and the rules and audits a sample.

Matching invoices that are backed by a purchase order is a strong candidate for Level 3. The rules already exist, in your purchase orders and your tolerances, and the ERP’s own three-way match checks the agent’s work a second time. Level 4 is possible for the same invoices once the controller is satisfied with what the samples show.

Two parts of the work have ceilings of their own.

  • Invoices with no purchase order stay at Level 2 for good. The agent proposes the coding and a person approves every one, because approving spend is a manager’s decision.
  • Releasing payment stays with people. Matching an invoice does not approve it for payment: a person releases payment at every level, including Levels 3 and 4. The agent never releases a payment and never changes a supplier’s bank details. Its access follows the separation of duties you ask of people: whoever enters invoices does not create suppliers or pay them.
Exception Who it usually goes to
The price on the invoice differs from the purchase order by more than the tolerance Buyer
The quantity billed is more than the quantity received, or there is no receipt yet Receiving
No purchase order number, or a purchase order that is closed or fully invoiced AP, then the person who ordered
Freight, surcharge or tariff lines that are not on the purchase order Buyer
A possible duplicate: the same supplier and invoice number, or the same amount and date AP
Bank details or a remit-to address that differ from the supplier record Controller
A statement or a credit memo that looks like an invoice AP
An invoice with no purchase order Department manager
  • Invoices received, by how they arrive, and how many are backed by a purchase order.
  • Time from an invoice arriving to its being entered and matched.
  • How many invoices match with no person involved.
  • Mismatches by reason, by supplier and by buyer.
  • How long each mismatch waits, and on whom.
  • Early-payment discounts offered and discounts taken.
  • Invoices still not entered at month-end close.
  • Corrections after entry: reversals and supplier credits.
  • What the sample reviews find at Levels 3 and 4.

These are things to measure, not targets. The threshold for each level is set with the workflow owner and written down before that level starts.