A three-way match exception is a controlled decision, not an unowned invoice queue. Compare the purchase order, receipt or service confirmation, and invoice; assign the person who can correct the evidence; and require an explicit release decision before payment.
Route match exceptions with clear ownership
Map the evidence, approvals, and handoffs your AP team needs in one work system.
Quick answer
Hold an invoice when the PO, receipt, and invoice do not agree outside approved rules. Classify the mismatch, route it to the evidence owner, preserve the documents and decision, then correct and re-match, obtain a documented policy exception, or reject the invoice. A cleared exception does not bypass normal payment approval.
What three-way matching checks
Three-way matching compares the commitment, evidence of receipt, and supplier demand for payment: the purchase order, goods receipt or service entry, and supplier invoice. The U.S. Bureau of Indian Affairs describes a three-way match as an obligation, receiving report, and invoice; its policy requires those documents before a referencing payment is processed. Read the BIA policy.
This is a control design, not a universal legal requirement. Define when a receipt is required and permitted tolerances in your own policy and contracts.
The exception workflow
Received – Validated – Matched or Held – Assigned – Resolved – Re-matched or Exception-approved – Payment-approved – Scheduled – Released – Settled – Reconciled – Closed.
- Capture and validate. Check supplier, entity, PO reference, duplicate indicators, tax fields, currency, and required attachments.
- Match at line level. Compare PO quantity and price, receipt or service acceptance, and invoice lines. Record the failed rule and variance.
- Place a payment hold. AP owns the queue; the evidence owner owns the cause.
- Classify and assign. Send missing receipts to the receiver, price or scope changes to the buyer/requester, invoice errors to the supplier, and tax questions to the designated reviewer.
- Resolve with evidence. Attach the corrected PO, receipt, invoice, approved change, or policy exception, then re-run matching.
- Reapprove changes. If price, quantity, scope, coding, or terms changed, return to the required approval step.
- Release and close. Retain the exception reason, owner, evidence, approval, and disposition for audit and reconciliation.
Exception control matrix
| Mismatch | Owner | Required evidence | Outcome |
|---|---|---|---|
| Missing receipt | Receiver/service owner | Receipt or service acceptance | Re-match or retain hold |
| Quantity variance | Receiver and buyer | Receipt, return, or approved PO change | Correct and re-match |
| Price variance | Buyer/requester | Contract, amendment, or approved exception | Reapprove or request correction |
| Incorrect invoice | Supplier and AP | Credit, corrected invoice, or rejection | Reject/replace |
Worked example: partial service receipt
A consulting PO authorizes 100 hours at $150. The supplier invoices 100 hours, but the service owner confirms 80 accepted. The invoice is held for quantity variance. The owner attaches acceptance for 80 hours; AP can request a corrected 80-hour invoice or follow an authorized partial-payment procedure. If scope changes, the change is approved before the invoice is re-matched and released.
Set tolerances deliberately
Tolerances reduce manual review; they do not eliminate accountability. Define them by variance type, spend category, and risk appetite. Microsoft documents a configuration that can require approval before posting invoices with price or quantity discrepancies. See the guidance. Treat product documentation as an implementation example, not a required policy.
Where Workhint fits
Workhint can help map the exception intake, attach PO/receipt/invoice evidence, route each mismatch to its accountable role, capture a reapproval, and show status from hold through handoff. Financial decisions and payment execution remain with authorized people and systems.
If your queue spans email, spreadsheets, receiving records, and approvals, describe the workflow in Workhint to structure roles, requests, evidence, and routing.
FAQ
Can AP pay an invoice with a match exception?
Only through the documented exception and approval path your organization authorizes. Retain the reason, supporting evidence, approver, and payment decision.
Is a goods receipt required for every invoice?
Not necessarily. Some purchases use two-way matching or other controls. Define the rule by purchase type and risk.
Who resolves a match exception?
AP manages the queue, but the evidence owner resolves the cause: receiving confirms delivery, the buyer resolves PO changes, the supplier corrects an invoice, and finance reviews coding.
Build a controlled exception path
Make the hold, owner, evidence, approval, and next state explicit. Book a Workhint demo to map the intake and approval path around your invoice exceptions.
Leave a Reply