The supplier invoice is correct only if the receipt agrees
For Finance controllers, CFOs and accounts teams · Plan implementation
TL;DR — what you’ll learn
- Compare invoice lines with the purchase order and relevant receiving evidence.
- Keep unit, quantity, price and charge differences separate so each reaches the right owner.
- Treat extraction as a draft; matching and payment approval remain distinct steps.
- Pilot with partial receipts, credit notes and repeated uploads before increasing the scope.
The purchase order says 100 cases. Receiving records 96, with four rejected at the dock. The supplier bills 100. Accounts payable can recognise the invoice perfectly and still pay the wrong quantity if the automation stops at extracting text.
What should three-way invoice matching check in a food business?
Match the invoice with the relevant purchase order and receiving evidence at line level. Compare units, quantities, prices and authorised charges separately. Route differences to the team that can resolve them before finance approves the next step.
- 01Capture the invoiceSupplier, lines and references
- 02Link order and receiptQuantity, price and unit
- 03Review differencesTolerance and authorised exceptionsDoes the match satisfy the approved rules?YesApprove the next stepNoRoute the specific price, quantity or receipt exception for review.
- 04Approve the next stepRetain the matched evidence
Illustrative information flow. The article explains the evidence, exceptions and responsible decisions. Diagram: NextEdge Labs.
A document match is not a quantity match
In this illustrative case, the supplier, order number and total may all look plausible. The unresolved difference sits on the receipt line. Establish how your business distinguishes physically received, accepted and disputed quantities, then specify which evidence the matching rule uses. Do not silently treat a quality rejection as a clerical shortage.
Microsoft's three-way matching documentation compares invoice quantities with product receipts and prices with purchase-order lines. Use that as a capability reference. Your own tolerances, charge treatment and approval rules require the finance team's agreement.
Source: Microsoft Learn · Quantity, unit-price and total-price matching. Reference details
Route the exception to its source
Receiving can confirm what arrived. Purchasing can explain an agreed price change. Quality can clarify a rejected quantity. Finance should not have to guess which team owns a mismatch from a single 'failed' status. Keep the disputed line, supporting records and decision history together.
For variable-weight purchases, compare the agreed pricing basis as well as the carton count. A case-to-kilogram conversion taken from the wrong pack can create a difference that looks like overbilling. Preserve the original invoice unit while displaying the normalised comparison.
A partially delivered order needs a remaining balance
Suppose an illustrative order covers 100 cases at ₹500 each. The first accepted receipt is 60 cases and the supplier invoices those 60. A later receipt brings another 36 accepted cases, with four rejected. The second invoice for forty cases should expose a four-case difference. Matching both invoices only against the original order quantity would miss that the second invoice exceeds the remaining accepted receipt.
Maintain the quantities already matched against each receipt and purchase-order line. A receipt should not satisfy several invoices repeatedly unless the remaining quantity supports them. The review screen needs the current invoice, earlier allocations and residual quantity together. This is particularly useful when suppliers send several small invoices against one order or consolidate several receipts into one invoice.
Tolerances should explain a business decision
A rounding difference and a missing delivery are not the same type of exception. Define tolerances by the relevant comparison and obtain finance approval. Show the tolerance applied and the actual difference. A broad percentage tolerance on the invoice total can conceal a material error on one line when another line happens to offset it.
For an authorised price change, link the revised agreement or order approval to the affected lines. Do not solve a recurring mismatch by widening tolerances until it passes. That changes the control without explaining the underlying difference. Track how often exceptions are resolved by correcting source data, accepting a documented commercial change or requesting a supplier correction.
Make the handoff to posting explicit
The matching service should produce a clear result: ready for the authorised next step, awaiting evidence, or requiring a named review. Keep missing documents out of the ready queue. A draft created in the ERP needs a stable reference to its source invoice and match decision so a repeated import can find the existing draft rather than create another.
Payment remains a separate authorised process. The implementation brief should identify the posting permissions, approval boundaries and recovery procedure if the ERP is unavailable. Test a successful match followed by a failed posting response. Finance must be able to tell whether a transaction exists before retrying. That recovery behaviour is part of the business workflow, not an optional technical detail.
A practical first implementation
Start with one supplier group, purchase-order invoices and the receipt records already available in the ERP. AI can draft line extraction and suggest item matches. Deterministic checks then identify missing receipts, duplicate invoice references and arithmetic differences. A reviewer handles ambiguity before any approved posting or payment workflow begins.
Test partial receipts, a credit note, a repeated upload and an invoice received before the goods. Report extraction corrections separately from commercial disputes so the team can see where effort remains. Bring representative redacted documents and the current exception categories to scope the integration; payment authority should remain with the existing finance controls.
Summary
Three-way matching is useful when the records describe the same item, unit and receipt boundary. The automation should make each difference easy to investigate and preserve the resulting approval. Faster document reading helps only when the underlying commercial and receiving checks remain intact.
What to do next
- Collect a redacted invoice, purchase order and receipt for one clean case and one disputed case.
- Agree which quantity and price fields control matching, including variable-weight items.
- Test exception routing and duplicate prevention before allowing approved transactions into the ERP.
Scope this automation around your operation
Tell us your current systems, transaction volume and the exception you need to resolve. We can discuss a bounded first release, its review controls and how to measure the result.
Sources and further reading
Sources checked 15 October 2026. The worked examples and software evaluation suggestions are NextEdge Labs’ editorial analysis.
- Three-way matching policiesMicrosoft Learn · Dynamics 365 Finance documentation, accessed October 2026
Illustrates invoice, purchase-order and receipt matching. The example tolerances in the documentation are not recommendations for your business.
Visual credits
AI-generated illustration created for NextEdge Labs; it does not depict a client facility. Workflow diagram by NextEdge Labs. Icons from Lucide (ISC licence).
