Three-way matching compares supplier invoice information with the purchase order and relevant receipt records. Define matching units, tolerance rules and exception authority before treating a matched status as payment readiness. The software should show the discrepancy and supporting records rather than hiding it behind one unexplained pass or fail label.
Let’s plan your invoice matching rules.
Bring your workflow, constraints and open questions. We’ll help you define the requirements and work through a practical next step.
Establish the comparison basis
Microsoft's invoice-matching overview distinguishes two-way and three-way matching and explains configurable discrepancies. Your implementation still needs the organisation's approved rules for scope, tolerances and review.
Agree line references, quantities, units, currencies and applicable order versions. Avoid comparing totals alone when line differences matter. A matching total can conceal an incorrect item or unit conversion.
Write a discrepancy matrix
| Difference | Information to show | Responsible decision |
|---|---|---|
| Price differs | Invoice and applicable order value | Approved tolerance or correction |
| Quantity exceeds receipts | Invoiced and eligible received quantity | Receiving investigation |
| Partial receipt | Which receipt balance supports this invoice | Allocation and remaining quantity |
| Extra charge | Source and inclusion rule | Authorised finance review |
| Duplicate reference | Existing invoice candidates | Duplicate investigation |
| Order amended | Version and effective change | Correct comparison basis |
Tolerance amounts and tax treatment require approval from the responsible finance professionals. This guide does not prescribe accounting policy or legal treatment.
Preserve the decision and its evidence
For a hypothetical invoice spanning two deliveries, show which receipt quantities were matched and what remains available for later matching. Prevent the same receipt balance being consumed inconsistently by concurrent users.
If an authorised reviewer accepts a variance, record the reason, actor and relevant version. Do not silently alter the purchase order to make the discrepancy disappear.
Test corrections after matching
Correct a receipt or amend an order after an invoice was reviewed. Verify which conditions require renewed review and how downstream records retain their history.
Distinguish matched, approved, posted and paid according to the actual process. A successful comparison is only one control; payment authority and confirmed payment outcome remain separate.
Matching questions
Does a match mean the invoice is definitely valid?
It establishes only the checks actually performed under the defined rules. Other reviews may still be necessary.
Should small differences always be ignored?
Use approved tolerance and escalation rules. The implementation should not invent an acceptable financial difference.
Connect the comparison to receiving states, and review the matching worksheet with Drema's ERP developers.
This article explains what to build, not legal advice. Rules change; confirm against the current official text before relying on it.