Three-way matching is one of the most critical controls in accounts payable. It ensures that your organisation only pays for goods and services that were ordered, received, and correctly invoiced. In Oracle Fusion Cloud, three-way matching is a core capability — but without proper configuration and automation, it can become one of the biggest sources of delay in your AP process.
This guide covers everything finance and procurement teams need to know about three-way matching in Oracle Cloud, from foundational concepts to advanced automation strategies.
What Is Three-Way Matching?
Three-way matching is the process of comparing three documents before approving a supplier invoice for payment:
- Purchase Order (PO): The original order placed with the supplier, specifying items, quantities, and agreed prices.
- Goods Receipt (GRN): Confirmation that the goods or services were received, typically recorded in Oracle Fusion Procurement or Inventory.
- Supplier Invoice: The bill submitted by the supplier requesting payment.
The match validates that:
- The invoice references a valid, open purchase order.
- The quantities invoiced do not exceed the quantities received.
- The unit prices on the invoice match the agreed PO prices.
- Tax calculations are consistent across all three documents.
When all three documents align within defined tolerances, the invoice is approved for payment. When they do not, an exception is raised for investigation.
Why Three-Way Matching Matters
Without three-way matching, organisations are exposed to significant financial risk:
- Overpayment: Paying for more goods than were received.
- Price discrepancies: Paying higher prices than were negotiated.
- Fraud and duplicate payments: Invoices without corresponding POs or receipts may indicate fraudulent activity.
- Audit failures: Regulators and auditors expect documented matching controls.
For organisations subject to SOX compliance, ASX corporate governance requirements, or internal audit standards, three-way matching is not optional — it is a regulatory necessity.
How Three-Way Matching Works in Oracle Fusion Cloud
Oracle Fusion Cloud Payables includes native support for two-way, three-way, and four-way matching. The matching level is configured at the purchase order shipment level and can vary by supplier, item category, or business unit.
Configuration Basics
In Oracle Fusion, you configure matching through several components:
- Match Approval Level: Set to three-way for most procurement scenarios.
- Tolerances: Define acceptable variances for quantity, price, and amount. For example, you might allow a 2% price variance and a 5% quantity variance before raising an exception.
- Invoice Validation: Oracle Fusion's invoice validation process checks the invoice against the PO and receipt, applying the configured tolerances.
- Holds: When a match fails, Oracle places the invoice on hold. The hold must be manually or automatically released before payment can proceed.
The Manual Matching Problem
While Oracle Fusion provides the framework for three-way matching, many organisations struggle with execution. Common challenges include:
- High exception rates: Poorly configured tolerances or inconsistent supplier invoicing leads to excessive holds.
- Slow resolution: AP staff must manually investigate each exception, often navigating multiple Oracle screens to compare the PO, receipt, and invoice.
- Backlog accumulation: As exceptions accumulate, cycle times increase and early payment discounts are missed.
Automating Three-Way Matching with AP Automation
This is where AP Automation from Sharpe Project Consulting transforms the process. Built specifically for Oracle Fusion Cloud, SPC3's AP Automation solution automates the matching process end to end.
How It Works
- Invoice Ingestion: Invoices arrive via email, supplier portal, or EDI. The system automatically captures and validates invoice data.
- Automated PO Lookup: The system identifies the corresponding purchase order in Oracle Fusion based on PO number, supplier, or line item details.
- Receipt Matching: The system cross-references the invoice against goods receipts, validating quantities and prices.
- Tolerance Checking: Configurable tolerance rules determine whether the invoice matches within acceptable limits.
- Straight-Through Processing: Invoices that match cleanly are approved and routed for payment without any human touch.
- Exception Routing: Invoices that fail matching are routed to the appropriate person with full context — the invoice, PO, and receipt displayed side by side with the specific discrepancy highlighted.
Results You Can Expect
With SPC3's AP Automation, organisations typically achieve:
- 90% auto-match rate — nine out of ten invoices processed without human intervention.
- 40% reduction in cost per invoice — fewer manual touches, less rework.
- 60% faster cycle times — invoices move from receipt to payment-ready in hours.
- Near-zero duplicate payments — intelligent detection catches duplicates before they are processed.
Best Practices for Three-Way Matching in Oracle Cloud
Whether you are implementing automation or optimising your current process, these best practices will improve matching performance:
1. Get Your Master Data Right
Accurate supplier records, item catalogues, and PO data are the foundation of successful matching. Invest in data cleansing before implementing automation.
2. Set Realistic Tolerances
Tolerances that are too tight generate excessive exceptions. Tolerances that are too loose allow errors through. Analyse your historical matching data to set tolerances that balance control with efficiency.
3. Standardise Supplier Invoicing
Work with your key suppliers to standardise invoice formats, ensure PO numbers are referenced, and align on unit of measure and pricing conventions. This alone can significantly reduce exception rates.
4. Monitor and Adjust
Matching performance should be reviewed regularly. Track your auto-match rate, exception rate, and resolution time. Use these metrics to identify and address recurring issues.
5. Invest in Automation
Manual three-way matching does not scale. As invoice volumes grow, automation is the only way to maintain speed, accuracy, and control.
Next Steps
If your Oracle Fusion Cloud environment is struggling with matching exceptions, slow invoice processing, or high AP costs, it may be time to explore automation.
Sharpe Project Consulting has deep expertise in Oracle Fusion Cloud and has helped organisations across Australia implement AP Automation that delivers measurable results. Our team can also assist with broader procurement and ERP transformation initiatives.
Get in touch with the SPC3 team to discuss your three-way matching challenges and learn how automation can help.