Guide
The matching guide
2-way and 3-way matching explained, with every check and the one rule that cannot be switched off.
What invoice matching is
Matching decides whether an invoice is safe to pay, checking the PO, goods receipt and invoice — three documents from three different actors.
For receivables the same control runs from the seller’s side: sales order, item fulfilment and customer invoice.
2-way matching
Invoice against purchase order. Checks that prices, quantities and total agree with what was ordered, within tolerance. The goods receipt is not checked.
- Use it for services, subscriptions, utilities and blanket orders — anything nobody receives into a warehouse.
- Residual risk: paying for goods that never arrived.
3-way matching
Invoice against PO against goods receipt: 2-way checks, plus goods must be received and not over-billed.
- Use it for physical goods — the gold standard.
- InvoiceIQ composes the bill from the receipt, consuming its lines, so over-billing is structurally impossible, not just detected.
The complete check catalogue
In InvoiceIQ each 3-way check has a verdict, a plain-English reason, a tolerance and a severity. Switched-off checks still show on the report.
Leg 1 — Invoice against order
| # | Check | Detail |
|---|---|---|
| 1 | The order exists | The extracted, normalised PO number resolves to a real order in the ERP. |
| 2 | The reference is plausible | IR/INV/VEN/SO-style codes are rejected before lookup — a format gate. |
| 3 | Vendor identity | The invoice’s vendor is the order’s vendor. |
| 4 | Price agreement | Invoice line rate against order line rate, within tolerance; variances flagged. |
| 5 | Line identity | Invoice lines paired to order lines on description, quantity, rate and part number. |
| 6 | The order is billable | Approval-blocked or rejected orders stop; linked prepayments route for clearance first. |
| 7 | Not already fully billed | A fully billed or closed order raises a duplicate warning, never a second bill. |
Leg 2 — Invoice against goods movement (3-way only)
| # | Check | Detail |
|---|---|---|
| 8 | Goods were received | There is a receipt against the order for the lines being billed. |
| 9 | Quantity within what arrived | Billed quantity may not exceed received quantity, line by line. |
Always on
| Check | Detail |
|---|---|
| The golden rule | The composed bill must equal the invoice. Enforced one final time after the ERP has the bill; if it fails, the bill is deleted and the post refused. It cannot be switched off — not by policy, not by editing the database. |
| The duplicate guard | Runs on the report and again at posting on a normalised invoice number, so “VS-4410” and “vs 4410” are the same document. |
| Your own rules | Conditions written in plain English over the invoice, the order, the vendor and the bills already posted — backtested against your history before they can block anything. |
Three policies, one setting
The policy comes from a ladder: posting-time choice, then vendor, company, then the system default of 3-way. Invalid requests fall through.
- 3-way — both legs on. For physical goods.
- 2-way — the goods-movement leg is off. Receipts are not consulted at all, nothing is drawn down, and the bill is raised from the order.
- Non-PO — the order and receipt legs are marked not applicable, rather than merely off. The duplicate guard, the golden rule and your own rules still run.
Tax and freight
Tax and freight are not goods, so they go on their own sublist. Placement rules decide where, tested on every charge shape before activating.
The Match Report
Every attempt gets a report: previewable, stored and written onto the posted bill. ERP refusals are translated into plain AP guidance.
4-way matching, for completeness
3-way plus inspection or quality acceptance. Not something InvoiceIQ ships today; it would be one more check row.
Want to see it rather than read about it?
A walkthrough takes an hour and starts with your own documents.