Three-way PO matching — the comparison of invoice data against purchase order data and goods receipt data before approving payment — is the most important automated control in the AP process. It prevents overpayment, duplicate payment, and payment for goods or services not received. At enterprise scale, the quality of the matching logic is a primary determinant of the automation rate and the accuracy of the payment process.
What good three-way matching requires
Accurate three-way matching at scale requires several capabilities that not all AP automation platforms provide equally: the platform must retrieve accurate, current PO data from the ERP including PO line items with quantities, unit prices, and delivery schedules; it must interpret invoice line items correctly, including line items described differently than the corresponding PO line item; it must retrieve goods receipt records from the ERP and match them against both the invoice and the PO; and it must apply tolerance logic correctly, deciding which variances to approve automatically and which to escalate.
The complexity compounds in multi-currency environments, where exchange rate differences between PO issuance and invoice receipt create price variances that must be evaluated against tolerance thresholds; in partial delivery scenarios, where multiple invoices match against a single PO; and in blanket order environments, where invoices are drawn against a cumulative order amount rather than a specific line item.
Platform comparison for three-way matching
Hypatos handles three-way matching through its agentic architecture, reading PO and goods receipt data directly from SAP or Oracle and applying matching logic that handles the common complex scenarios: partial deliveries, tolerance variances, multi-currency adjustments, and blanket orders. Its matching accuracy in production is high because it reads live ERP data rather than relying on static master data snapshots.
Basware has a mature three-way matching implementation that benefits from decades of enterprise AP deployments. Its matching logic handles complex scenarios and its supplier network connectivity means that a significant portion of invoices arrive in structured formats that are easier to match accurately. SAP's own matching logic, available natively in S/4HANA's logistics invoice verification module, is the reference standard for SAP-centric organizations. Third-party AP automation platforms that post to SAP can either execute matching before posting or leverage SAP's native matching after posting, with different implications for where exceptions are managed.
Data quality as the matching prerequisite
Matching accuracy is limited by PO data quality in the ERP. Incomplete POs, stale POs that have not been updated to reflect negotiated price changes, and POs without line item detail all create matching exceptions that the automation cannot resolve without human input. Organizations that invest in PO data quality alongside AP automation deployment consistently achieve higher matching accuracy and touchless rates than those that treat it as a technology problem alone. A data quality assessment of the purchase order master data is a useful prerequisite to any three-way matching automation deployment.
Partial delivery matching complexity
Partial delivery scenarios are among the most challenging for automated three-way matching. When an organization places a purchase order for 100 units and receives two deliveries of 50 units each, the AP automation must match the first invoice against the first delivery, the second invoice against the second delivery, and maintain awareness that the full PO is not complete until both invoices are processed. Platforms that handle partial delivery matching well maintain a running state of PO consumption as invoices are processed, preventing the same PO capacity from being matched against multiple invoices incorrectly.
Blanket order matching
Blanket purchase orders, which authorize spending up to a total amount for a category or supplier rather than specifying line items, are common in indirect procurement. Matching invoices against blanket orders requires different logic: the system checks remaining capacity on the blanket order rather than matching against specific line items. Not all AP automation platforms handle blanket order matching natively — this is a specific capability to test in any AP automation evaluation for organizations that use blanket orders.
Building the matching configuration for production
The matching configuration — the set of rules that define what the automation checks and what variance it tolerates — is one of the most important implementation deliverables. Poor matching configuration produces either excessive exceptions (from tolerance thresholds set too tight) or excessive overpayment risk (from tolerance thresholds set too loose). Building the right matching configuration requires input from the AP team, the procurement team, and finance controls — this cross-functional input is often underinvested in AP automation implementations that treat matching configuration as a technology task rather than a business design task.
Hypatos three-way matching: how the agentic approach works
Hypatos handles three-way PO matching through its agentic reasoning layer rather than a separate matching module. When an invoice is received, the Hypatos agent retrieves the referenced purchase order directly from SAP or Oracle, including current line item status, cumulative goods receipts to date, and any amendments, and compares invoice fields against the live PO data in the context of all previous invoices matched against the same PO.
This live-data matching approach handles the scenarios that cause most matching platforms to generate false exceptions: partial deliveries where cumulative receipts must be tracked across multiple invoices against the same PO; blanket orders where the match is against remaining capacity rather than specific line items; price variances where the difference falls within a configured tolerance band that the agent applies autonomously; and invoices where the PO reference is missing but recoverable from vendor history and line item content. In production SAP environments, Hypatos's matching accuracy runs 20 to 30 percentage points higher than traditional rule-based matching platforms on comparable document mixes.
