In real projects...

Three-way match is a control, not a checkbox: PO, receipt, and invoice must reconcile under tolerance—with exceptions routed. Tie upstream to sourcing and supplier governance.

A common issue we see...

Receipts lag or are blanket-accepted, so invoices auto-match to fantasy quantities.

For example...

  1. Define tolerances by category and document escalation paths.
  2. Require goods receipt before invoice approval for stocked items.
  3. Queue price/quantity variances with reason codes.
  4. Monitor duplicate invoice detection and vendor bank changes.
  5. Monthly review of override patterns by approver.

Common mistakes (and how to avoid them)

  • Letting AP override receiving to “keep suppliers happy.”
  • Ignoring freight/tax lines in match rules.
  • Weak segregation between buyer and receiver roles.
  • Skipping periodic statement reconciliations.

Note: Representative scenarios for education; validate controls with internal audit.

Methodology: This article is an educational guide built from public ERP documentation and widely used implementation patterns. Any mini “scenario walkthroughs” are illustrative and not client-specific.

Three-way match prevents payment for goods not received and for prices not agreed. This walkthrough builds the controls that make the match process reliable at volume without creating a processing bottleneck.

  1. Create a purchase order in the ERP approved by the relevant authority tier, with price and quantity locked before the order is placed.
  2. Record the goods receipt against the purchase order on the day of delivery—not when the invoice arrives.
  3. Receive the supplier invoice and route it to the ERP's matching engine to compare quantity, price, and purchase order reference.
  4. If the match succeeds within tolerance, automatically release the invoice for payment processing.
  5. If the match fails, generate an exception record, classify the exception type, and route it to the appropriate owner: procurement for price disputes, receiving for quantity discrepancies.
  6. Resolve all exceptions before payment is released, and archive the exception record with the resolution evidence.

Artifacts to expect:

  • Purchase order with approved price, quantity, and supplier.
  • Goods receipt record dated on day of delivery.
  • Invoice-to-PO match result with tolerance check.
  • Exception record with type classification and resolution evidence.
  • Payment release record linked to matched invoice.

What usually goes wrong (failure modes)

  • Goods receipts are posted late, creating invoice-ahead-of-receipt exceptions for most invoices
    Receiving staff post goods receipts weekly or when they get around to it, so most invoices arrive before the receipt exists and cannot be matched.
    Mitigation: Establish a receiving timeliness policy: all goods receipts must be posted in the ERP on the day of delivery. Measure receipt timeliness weekly and escalate consistently late departments.
  • Invoice exceptions are worked individually rather than by root cause, creating recurring match failures
    The same supplier consistently generates price exceptions because the PO price is not updated when the supplier changes their price, and each invoice is corrected individually.
    Mitigation: Analyse exceptions by supplier and by exception type monthly. A high exception rate for a specific supplier indicates a PO template or pricing update issue—fix the root cause to eliminate recurring exceptions.
  • Tolerances are set too tightly for legitimate price movements, generating excessive false exceptions
    Matching tolerances were configured for stable commodity prices, but when prices move, almost all invoices generate an exception and the review team is overwhelmed.
    Mitigation: Review tolerance settings when exception volumes spike. A temporary tolerance adjustment for volatile categories with documented rationale is preferable to bypassing the match requirement entirely.

Controls and evidence checklist

  • Require purchase order approval before any supplier order is placed.
  • Record goods receipts on the day of delivery.
  • Use the ERP's automated three-way match engine rather than manual matching.
  • Classify all match exceptions by type and assign resolution ownership.
  • Release payments only for fully matched invoices or approved exceptions.
  • Run a monthly exception analysis by supplier and type to identify root causes.

Implementation checklist

  1. Confirm that goods receipt timeliness policy is agreed and communicated before the match process goes live.
  2. Configure matching tolerances per commodity category using representative historical invoice data.
  3. Test the matching engine with sample POs, receipts, and invoices covering each exception type.
  4. Train receiving staff on the same-day receipt posting requirement and explain its link to payment.
  5. Monitor exception rates weekly for the first month and identify the three highest-volume exception causes.
  6. Address root causes systematically before expanding the three-way match scope to additional spend categories.

Frequently asked questions

Where do teams usually lose time in ERP three-way match workflows?

Most time is lost when goods receipts are posted days or weeks after delivery, so invoices arrive before the receipt exists in the system and cannot be matched. Establishing a receiving process where goods receipts are posted on the day of delivery—or by the end of the same business day—is the single most effective control for reducing three-way match exceptions. Measuring receipt timeliness by department weekly and making it a performance metric drives the required behaviour change.

What exception patterns should we investigate most urgently?

Review match exception rates by supplier and by commodity category. A consistently high exception rate for a specific supplier usually indicates a pricing or unit-of-measure discrepancy in the purchase order that needs to be corrected at source, rather than resolved individually for each invoice. Fixing the PO template or pricing list for that supplier resolves the recurring exceptions more efficiently than exception-by-exception review, and reduces the total exception volume materially.

When should we adjust matching tolerances?

Adjust matching tolerances when commodity prices are volatile or when new categories of spend are added to the three-way match scope. Tolerances set for stable commodity prices may trigger excessive exceptions during a period of significant price movement—a temporary tolerance adjustment with documented rationale is preferable to bypassing the match requirement entirely. Review tolerances annually and recalibrate based on actual invoice price variance data from the prior year.

Sources

Conclusion and next steps

Three-way match reliability in ERP depends on receiving timeliness, well-configured tolerances, and systematic exception root cause resolution—not on exception-by-exception manual review.

Measure receipt timeliness and exception rate by cause for the first month. Those two metrics identify the highest-value improvements faster than any configuration review.