Use three way matching to compare each invoice line with the approved purchase order and the recorded receipt before routing it through your payment controls. For a hypothetical order covering 100 units with only 60 recorded as received, an invoice for all 100 has a quantity discrepancy even when its unit price agrees. The missing evidence needs an owner before the invoice moves through the exception process.
Keep price, quantity, and approval results separate. A missing receipt can mean a delivery has not arrived, receiving has not posted it, or the invoice is linked to the wrong receipt. Inspect those possibilities before deciding which record needs correction. Matching supports the review; accounting policy, payment terms, and approval authority still govern the resulting action.
Set the matching policy before reviewing exceptions
Oracle’s match approval level documentation distinguishes the evidence required: two-way uses purchase order and invoice quantities; three-way adds receipt quantities; four-way also includes quantities accepted through inspection. Oracle applies the configured tolerances to those quantities. Four-way matching therefore adds an acceptance check when receipt alone is insufficient evidence under the purchasing policy.
Price checks depend on the implementation as well. Microsoft’s three-way matching policies compare invoice prices with purchase order lines and invoice quantities with selected product receipts. Its examples also make approval to post with discrepancies configurable. Inspect the effective policy for the company, supplier, item, and order instead of assuming that a label guarantees a payment block.
Have finance approve tolerances and exception authority, with purchasing and receiving agreeing on the evidence they maintain. Define how service acceptance, deposits, and non-PO purchases enter their own approval paths. A physical-goods receipt rule cannot establish that consulting work was accepted or that a contractual advance is due.
Link the invoice to the authorized line and receipt
Accounts payable should establish the supplier, buying entity, purchase order line, and applicable receipt references before comparing values. Check currency and units of measure along with the item. A receipt in cartons and an invoice in individual pieces need a supported conversion; matching descriptions or header totals alone can conceal a line assigned to the wrong order.
Use the approved order revision as the commercial reference, including authorized changes. The purchase requisition versus purchase order distinction explains why approval of an internal request does not prove that the supplier was issued the same order. Retain the version being matched so a later price amendment does not erase the reason for an earlier exception.
Keep each receipt’s identity and its allocation to invoices. Reusing a receipt quantity already matched elsewhere can make a second invoice appear supported by the same delivery. Include earlier invoices, corrections, and reversals in the review, with a clear cutoff for when source records were last refreshed.
Work a partial receipt through the quantity check
Consider a hypothetical order for 100 identical units at $10 each. Assume receiving has recorded 60 units against that line, with no earlier invoices, returns, receipt reversals, or inspection requirement. The supplier invoices 100 units at $10. Tax, freight, discounts, and currency conversion are excluded to isolate the goods comparison. This example applies the receipt-quantity method described in Microsoft’s policy documentation above.
| Evidence | Quantity | Unit price | Goods amount |
|---|---|---|---|
| Approved purchase order | 100 units | $10 | $1,000 |
| Recorded receipt | 60 units | $10 PO reference | $600 at the PO price |
| Supplier invoice | 100 units | $10 | $1,000 |
| Invoiced quantity without recorded receipt | 40 units | $10 PO reference | $400 at the PO price |
Quantity difference = 100 invoiced - 60 received = 40 units. The unit prices agree, but the full invoice lacks receipt support for those 40 units. The $600 receipt value is not an automatic instruction to approve or pay that portion. Finance must determine whether the configured workflow and agreed terms permit a partial resolution or require the invoice to remain on hold.
Receiving owns confirmation of what arrived and whether a receipt was omitted. Purchasing owns the supplier follow-up if the remaining delivery is outstanding or the invoice needs correction. If another receipt arrives later, link it to the existing review and rerun the match. Do not enter a second copy of the invoice to restart processing or alter the source document to make the difference disappear.
Test price differences separately from missing quantities
A price tolerance answers a price question. In a separate hypothetical variation, an invoice unit price of $10.20 against a $10 order price creates a ($10.20 - $10) ÷ $10 × 100 = 2% increase. That arithmetic does not decide whether the increase is allowed. Apply the approved tolerance and commercial terms, and keep any receipt-quantity discrepancy open.
Microsoft’s invoice matching overview distinguishes net unit price, price totals, invoice totals, and charges matching. Its invoice-total checks can include sales tax, while freight and other charge codes have their own configuration. Record which check failed; an invoice total by itself cannot explain whether the difference arose from price, quantity, tax, or freight.
Preserve policy-defined tax, freight, and service exceptions as separate review items. A shipping charge can have a different approval path from a goods quantity, and service evidence may be an approved milestone or time record. The authorized owner should resolve the applicable charge or acceptance rule without treating it as a physical delivery.
Retain returns, credits, and duplicate-invoice checks
A later return changes the evidence behind an earlier receipt. Keep the returned quantity, original receipt, invoice, and expected credit linked so the reviewer can distinguish a goods movement from a financial adjustment. Microsoft’s purchase return process copies original invoice lines into a return order and records goods shipped back. Follow the supported correction process without deleting the original receipt history.
Have accounts payable confirm that a supplier credit was received and applied to the intended invoice. Purchasing should track any replacement obligation separately. A credit can reduce the financial claim without proving that the missing replacement has arrived; a return shipment does not prove the supplier has issued a credit.
Run duplicate checks alongside the match. Oracle’s additional duplicate-invoice check, when enabled, uses supplier, invoice type, amount, currency, and date rather than relying on the invoice number alone. Treat a suspected duplicate as a review case. A matching amount can also belong to a legitimate separate delivery.
Assign an exception owner and retain the decision
Route each unresolved difference to a named owner with the supporting records, next action, and review date. Keep receipt correction, supplier dispute, and authorized exception approval as distinct outcomes. A reason such as “approved” cannot explain which discrepancy the reviewer accepted or the authority used.
Reviewers need both the earlier result and the evidence available at the time of their decision. A later receipt (posted after the review cutoff) should explain a changed match result without overwriting the earlier exception. The purchase order tracking process covers the separate task of following open supply obligations through delivery and closure.
If you are selecting a purchasing tool, use these cases as a demonstration script. The construction purchase-order software comparison examines field receiving and office invoice handoffs. A tool choice still needs proof that its receipt, exception, and accounting handoffs fit the process you intend to run.
Where Permute fits in invoice exception reporting
Permute sells connected business data, custom applications, and AI grounded in business records. We support permitted source connections, uploaded records, and reusable transformations. A scoped exception report can combine supplied purchase orders, receipts, and invoices while retaining the source references used to compare each line.
We apply your declared definitions of received quantity, matched quantity, and review status. Supplier and order-line identities need resolution before totals can be compared. Verify source fields, historical coverage, and refresh behavior for the implementation; the existence of a source connection does not establish access to every purchasing record.
An accounts payable lead could use the scoped report to inspect invoices whose billed quantities exceed supported receipts, with the source rows behind each difference. A review application can be designed around those exceptions and the permissions of its users. Missing evidence should remain visible until the responsible person resolves it.
Explore a line-level exception report
Start with permitted order, receipt, and invoice samples and the matching policy your team already uses.
Keep accounting policy and payment authority separate
We read connected records for this reporting workflow. It does not authorize payment, post an invoice, change an ERP receipt, or choose accounting treatment. Finance retains its existing policy and exception authority; any action in a source system needs a separately supported, permissioned, and approved workflow.
Match the authorized order, applicable receipt, and invoice at line level, keeping price and quantity results distinct. In the partial-delivery example, 40 billed units still lack recorded receipt support even though the unit prices agree. Resolve that difference through evidence correction, supplier follow-up, or an authorized exception under the existing policy. Retain the decision and rerun affected checks before the invoice proceeds through its remaining controls.
Review the handoff behind an unresolved invoice
Bring a partial receipt and its invoice to assess source gaps, exception ownership, and the report your reviewers need.
Questions about invoice matching exceptions
What if one invoice covers several purchase orders?
Allocate invoice lines to the applicable order and receipt references using the supported process. Preserve the allocation rather than matching the invoice total to a combined total. An excess on one order can otherwise conceal a shortage on another.
What if the invoice has no purchase order?
Identify whether it is a permitted non-PO purchase or a missing reference that needs investigation. Route permitted non-PO spending through the company’s designated approval process. Do not invent an order or receipt merely to produce a passing match.
Can I raise the tolerance to clear old exceptions?
Treat a tolerance change as a policy decision with an authorized owner and a recorded reason. Review its effect on other invoices before applying it. Clearing a backlog does not establish that its underlying discrepancies were acceptable.