Purchase-order and invoice reconciliation becomes difficult when the relevant evidence is spread across procurement, receiving, finance and supplier records. A mismatch does not automatically mean an error or misconduct. It means the transaction needs to be checked against the agreed rules and supporting evidence.
The goal is to distinguish valid differences, data-quality issues and genuine exceptions without making the finance team reconstruct every transaction manually.
What should be reconciled?
In a common three-way matching process, the purchase order states what was ordered, the goods receipt records what was received, and the invoice states what the supplier billed. The exact control depends on the organisation, category and contract.
| Record | What it establishes | Typical mismatch |
|---|---|---|
| Purchase order | Approved quantity, price and terms | Revised PO or incorrect reference |
| Goods receipt | Quantity and date received | Partial delivery or late posting |
| Supplier invoice | Amount billed and tax treatment | Price, quantity or tax discrepancy |
| Credit note | Adjustment to an earlier invoice | Missing or incorrectly allocated credit |
| Contract or price list | Agreed commercial terms | Effective-date or unit-of-measure mismatch |
A unit mismatch can create a false exception. A price quoted per case may be recorded per unit; a delivery may be split across multiple receipts; or a legitimate contract amendment may not be reflected in the original PO.
An evidence-led reconciliation flow
- Start Invoice received
- Find candidate PO and receipt records
- Resolve supplier and reference identities
- Apply quantity, price, tax and tolerance rules
- Within approved rules?
- Yes Record the match with its evidence.
- No Classify the exception and its materiality.
- Assign an owner and request evidence
- Review, approve or reject the adjustment
- Outcome Record the outcome and audit trail
"Mismatch" is not a disposition. The record should say whether the issue is quantity, price, tax, timing, duplication, a missing receipt or an unresolved identity.
The flow should preserve both the result and the reasoning. “Mismatch” is not a sufficient disposition. The record should explain whether the issue is quantity, price, tax, timing, duplicate invoice, missing receipt, unresolved identity or incomplete evidence.
Design an exception queue that helps people resolve work
| Field | Purpose |
|---|---|
| Invoice and supplier references | Identify the transaction |
| Candidate PO and receipt | Show proposed relationships |
| Variance type | Make the reason explicit |
| Value at risk | Prioritise by materiality |
| Rule or tolerance applied | Make the decision reproducible |
| Supporting records | Allow a reviewer to inspect evidence |
| Owner and due date | Establish accountability |
| Status and resolution | Prevent repeated investigation |
Automatic matching should be conservative where the cost of a false match is high. A system can propose a relationship, but an uncertain supplier identity or material price discrepancy may require human review.
Where cross-system intelligence helps
If teams repeatedly export records from different sources, resolve inconsistent supplier references and reapply the same rules, the investigation can be made more repeatable. Qwry.AI’s procurement solutions provide the relevant context for exploring cross-source procurement questions.
A useful assessment should begin with the most common exception types, the current matching policy, and the records needed to validate a match. It should not assume that every mismatch can or should be auto-resolved.
Next step: Review the last month of PO-to-invoice exceptions. Group them by cause, value, recurrence and time to resolve. Use that evidence to decide which rules can be standardised and which cases need human judgement.
FAQ
Frequently asked questions.
Three-way matching compares a purchase order, a goods receipt and a supplier invoice to check whether the order, received goods or services and billed amount align with approved rules.
Not automatically. The response depends on materiality, policy, contract terms, risk and whether an authorised tolerance applies. Exceptions should be routed according to approved controls.
Common causes include partial deliveries, timing differences, unit conversions, amended orders, supplier identity mismatches, tax treatment and missing or late-posted receipts.
Only where the organisation has explicitly approved the policy, controls, access and risk boundaries for that action. High-risk or ambiguous cases should remain subject to review.