Purchase order matching is the AP control that connects what a business agreed to buy with what it is being asked to pay. For businesses evaluating whether their current process has this gap, the real cost of manual AP quantifies what unmatched invoices actually cost in practice. Without it, invoices can be approved for amounts that differ from the agreed price, for quantities greater than what was received, or from vendors that were never authorised.
This guide covers how to implement PO matching in practice — two-way and three-way matching, header-level versus line-level comparison, tolerance configuration, where matching breaks in specific industries, and how to integrate matching into an AP workflow without creating bottlenecks.
What PO matching is and what it is not
PO matching compares an invoice against its corresponding purchase order across three dimensions: supplier identity, unit price, and quantity. When all three match within a configured tolerance, the invoice clears the matching check and proceeds to approval. When any dimension falls outside tolerance, the invoice is flagged as an exception.
PO matching is not a payment block. It is a control that surfaces discrepancies for review. The reviewer — typically a procurement officer or financial controller — investigates the exception, determines whether it represents a legitimate variation or an error, and resolves it before the invoice is approved.
The control is simple in concept. The implementation details — which matching level, which tolerances, which exceptions to prioritise — determine whether it works as a genuine control or degrades into a bottleneck that the AP team learns to bypass.
Two-way matching vs three-way matching
Two-way matching
Two-way matching compares two documents: the purchase order and the invoice. It verifies that the invoice is for goods or services that were ordered and that the price and quantity match what was agreed.
Two-way matching catches: invoices at prices higher than agreed, quantities greater than ordered, invoices from suppliers that do not match the PO vendor, and invoices referencing PO numbers that do not exist.
Two-way matching does not catch: invoices for goods that were ordered but never delivered. A supplier could submit an invoice for an order that was placed but not yet received, and a two-way match would pass it. This is the critical limitation.
Three-way matching
Three-way matching adds a goods receipt note to the comparison. The GRN is created when goods are physically received, recording what was delivered, in what quantity, and on what date. Three-way matching requires all three documents to align before the invoice is approved: the PO confirms the order was authorised, the GRN confirms delivery occurred, and the invoice confirms the supplier’s claim for payment.
Three-way matching catches everything two-way matching catches, plus: invoices for goods not yet delivered, invoices for quantities greater than what was received (short deliveries invoiced at full quantity), and timing discrepancies where goods arrived in multiple shipments but the invoice covers the full order.
When to use which
Two-way matching is appropriate for:
- Service invoices where there is no physical delivery to confirm
- Invoices from trusted long-term suppliers where delivery risk is low
- Businesses that do not have a formal goods receipt process in place
- Low-value, high-volume purchases where the cost of three-way matching exceeds the risk
Three-way matching is appropriate for:
- High-value goods purchases where short delivery risk is material
- Construction materials where partial deliveries are the norm
- Wholesale stock purchases where inventory valuation depends on accurate receipt records
- Any purchase where the gap between order and delivery creates payment timing risk
For most Australian SMBs, two-way matching provides a significant improvement over no matching. Businesses that frequently deal with partial deliveries, contested quantities, or high-value inventory should implement three-way matching for those spend categories while using two-way matching for the remainder.
Header-level vs line-level matching
This distinction matters more than most businesses realise, and it is where many PO matching implementations fall short.
Header-level matching
Header-level matching compares the invoice total against the PO total. If the numbers are within tolerance, the match passes. This approach is fast and simple, but it has a critical blind spot: line-level variances that cancel out in the total.
Example: a PO is raised for 100 units of Product A at $10 each and 50 units of Product B at $20 each. Total PO value: $2,000. The supplier invoices for 80 units of Product A at $10 ($800) and 60 units of Product B at $20 ($1,200). Total invoice: $2,000. Header-level matching passes — the totals match. But the business received 20 fewer units of Product A than ordered and is being charged for 10 more units of Product B than ordered. Neither variance is flagged.
Line-level matching
Line-level matching compares each line item on the invoice against the corresponding line on the PO. In the example above, line-level matching would flag both variances: Product A invoiced at 80 units versus PO of 100, and Product B invoiced at 60 units versus PO of 50.
Line-level matching requires more system capability — the AP platform needs to parse individual invoice lines and map them to PO lines, which involves matching on description, product code, or line sequence. But it catches the variances that header-level matching misses.
For wholesale distributors managing stock purchases with multiple product lines per PO, line-level matching is essential. A supplier invoice covering 15 product lines against a PO with 15 lines can have individual line variances that sum to zero at the header level. Without line-level matching, those variances reach the ledger.
For construction businesses managing subcontractor invoices with labour, materials, and plant hire on separate lines, line-level matching catches rate variances on individual trade items that header-level matching would miss.
Why do AP teams skip PO matching and why does that create risk?
The most common reason AP teams skip PO matching is that it requires purchase orders to exist. In businesses where ordering happens informally — by phone, email, or verbal instruction — there is no PO to match against. The matching check cannot function without the input document.
This is not an argument against PO matching. It is an argument for raising purchase orders consistently. Businesses that commit to issuing POs before ordering receive two benefits: a matching check that catches invoice discrepancies, and a documented audit trail of authorised commitments.
The second reason AP teams skip matching is that early implementations create too many false positives. Matching tolerances set too tightly flag every minor price rounding as an exception. When the exception queue fills with trivial variances, reviewers begin approving without genuine investigation — defeating the purpose of the control.
The third reason is that manual PO matching is slow. Looking up the PO, comparing it line by line against the invoice, and documenting the result for each invoice takes several minutes per invoice. At 200 invoices per month, that is 10 to 15 hours of manual matching work. AP teams under time pressure skip the step entirely rather than fall further behind on payment runs.
Automated PO matching eliminates the third reason entirely and, with proper tolerance configuration, addresses the second.
How to configure matching tolerances
Matching tolerances define how much an invoice can differ from the purchase order before triggering an exception. Getting these right is critical — tolerances that are too tight create noise, and tolerances that are too loose let material discrepancies through.
Price tolerance
Allow a variance of 1 to 3 percent before flagging. This accommodates GST rounding, minor price adjustments, and currency conversion differences without generating exceptions on every invoice.
For suppliers with fixed contractual rates (such as subcontractors on agreed day rates), a tighter tolerance of 0.5 to 1 percent may be appropriate. For commodity suppliers where prices fluctuate with market conditions, a wider tolerance of 3 to 5 percent may be necessary to avoid constant false positives.
Quantity tolerance
Zero tolerance is typical for quantity matching — an invoice for 110 units against a PO for 100 units should always be flagged. Some businesses allow a small over-delivery tolerance (3 to 5 percent) for bulk goods where exact quantities vary slightly due to manufacturing tolerances or weight-based pricing.
For construction materials sold by weight or volume (concrete, aggregate, fill), a quantity tolerance of 5 percent is common because the delivered quantity varies from the ordered quantity by nature. For precisely counted items (fixtures, fittings, equipment), zero tolerance is appropriate.
Amount tolerance
Set a minimum dollar threshold below which matching exceptions are not generated. An invoice that is AU$2.50 over the PO amount on a AU$500 invoice does not warrant the same investigation as a AU$2,500 variance on a AU$10,000 invoice. A common floor is AU$20 or AU$50 — variances below this threshold pass without generating an exception.
Reviewing and adjusting tolerances
Tolerance configuration is not a one-time decision. Review the exception rate after the first month of operation and adjust based on what is actually flagged versus what requires genuine investigation.
A healthy exception rate for PO matching is typically 15 to 25 percent of matched invoices. Below 10 percent suggests tolerances may be too loose — material variances may be passing through. Above 40 percent suggests tolerances are too tight or that upstream PO discipline needs improvement — the exception queue fills with noise and reviewers stop investigating carefully.
Track exception resolution outcomes: what percentage are approved as legitimate variances, what percentage result in credit notes, and what percentage reveal genuine errors or overcharges. This data tells you whether the matching check is catching real problems or generating busywork.
Implementing PO matching: the four prerequisites
Before configuring PO matching in an AP automation system, four conditions need to be in place:
1. Consistent PO issuance. PO matching works only when purchase orders are raised for the invoices you want to match. Identify which spend categories consistently have POs (materials, subcontractors, equipment) versus which are typically unordered (ad hoc expenses, utility bills). Implement PO matching for the categories where POs exist before expanding to others.
2. Supplier master data with PO references. The matching system needs to link incoming invoices to the correct PO. This requires suppliers to include PO numbers on their invoices, or for the AP platform to support manual PO association at intake. Work with your top 10 suppliers to ensure PO numbers are consistently included on invoices before go-live.
3. Configured price tolerances in the AP system. Document the tolerance thresholds before configuring the system. Review your last three months of supplier invoices to understand the typical variance range for each supplier category. This data drives the tolerance configuration rather than relying on default settings.
4. A defined exception resolution process. Determine who reviews PO matching exceptions, what information they need (the original PO, the invoice, and the delivery record if available), and what the resolution options are (approve with explanation, reject and request credit note, or approve pending supplier correction). Without a defined process, exceptions accumulate without resolution.
Where PO matching breaks in practice
Consolidated invoices. Suppliers that invoice for multiple POs on a single invoice create a matching challenge. A materials supplier might consolidate three weekly deliveries into one monthly invoice. The AP system needs to support many-to-one matching (one invoice to multiple POs) or the consolidated invoice will not match correctly.
Variations and change orders. In construction and project-based businesses, scope changes are common. An invoice that exceeds the original PO amount by 20 percent may be entirely legitimate if an approved variation exists. PO matching that flags this without context creates unnecessary work. Matching systems that support variation order references alongside PO numbers reduce false positives in project-based environments.
Blanket purchase orders. A blanket PO authorises a supplier to deliver goods or services up to a total value over a period, with individual invoices drawn against the blanket amount. Matching against a blanket PO requires tracking the cumulative invoiced amount against the blanket total, not matching each invoice against a discrete order. An invoice for $5,000 against a $50,000 blanket PO is legitimate — unless the cumulative invoiced total has already reached $48,000, in which case the new invoice exceeds the remaining balance. The matching system needs to track running totals, not just individual comparisons.
New suppliers. Invoices from suppliers not yet in the approved vendor list have no PO to match against. The matching check generates a flag that should trigger both an invoice review and a supplier onboarding verification — two separate controls that PO matching can initiate without stopping the invoice entirely.
Price increases. When a supplier increases prices between the PO date and the invoice date without a formal price agreement update, every invoice from that supplier will generate a matching exception until the PO rates are updated. Monitor exception patterns by supplier to identify this scenario rather than treating each exception individually.
Credit notes and returns. When goods are returned or a credit note is issued against a PO, the matching system needs to adjust the PO’s remaining balance. Without this adjustment, subsequent invoices against the same PO may trigger false exceptions because the system shows the PO as over-invoiced.
PO matching by industry
Construction
Construction AP involves subcontractor progress claims, materials invoices, plant hire, and specialist trade invoices — each with different matching requirements.
Subcontractor invoices are typically matched against a subcontract agreement or a progress claim schedule rather than a standard PO. The invoiced amount represents a percentage of the contract value based on work completed. PO matching in construction needs to support progress-based matching: comparing the claimed percentage against the agreed schedule and the cumulative amount invoiced to date.
Materials invoices are more standard — ordered quantities at agreed rates — but partial deliveries are common. A concrete supplier delivering to a job site may deliver 80 percent of the ordered quantity due to site access or pour schedule changes. Three-way matching with a delivery docket prevents paying for the full order before delivery is complete.
Variation orders are the most common source of PO matching exceptions in construction. A scope change approved verbally by a site manager but not yet formalised as a variation to the contract creates an invoice that exceeds the original PO. The matching system needs to handle these without blocking the payment entirely.
For a deeper look at construction-specific matching challenges, see Why PO Matching Fails in Construction.
Wholesale and distribution
Wholesale AP involves high-frequency stock purchases from a broad supplier base, with invoices that routinely cover multiple product lines, multiple deliveries, and multiple POs.
The primary matching challenge is line-level accuracy at volume. A stock supplier invoice with 20 line items, each referencing a different product code and PO line, requires 20 individual comparisons. At 200 invoices per month, that is 4,000 line-level comparisons — far beyond what manual matching can handle reliably.
Freight invoices present a separate matching challenge. A carrier invoice covering multiple delivery runs cannot be matched against a single PO because each run may correspond to a different customer order or cost centre. Freight matching requires a different approach: matching delivery run references against dispatch records rather than traditional PO matching.
For more on wholesale-specific AP challenges, see Accounts Payable for Wholesale and Distribution Businesses.
Manufacturing
Manufacturing AP involves raw materials purchases, component orders, and outsourced processing — with matching requirements that sit between wholesale (volume and variety) and construction (project-based and progress-based).
The distinctive manufacturing matching challenge is partial receipts against large orders. A raw materials order might be delivered in weekly batches over a month, with each delivery invoiced separately. The matching system needs to track cumulative receipts against the original PO and flag when the total invoiced exceeds what was ordered, even though each individual invoice is within tolerance.
Bill of materials (BOM) complexity adds another layer. A supplier invoice for a manufactured component might need to be matched against the BOM cost estimate rather than a simple PO, particularly for custom or made-to-order components where the final cost depends on actual material usage.
PO matching in Xero and MYOB
Xero
Xero supports purchase orders as a document type. You can create POs, send them to suppliers, and manually convert them to bills when the invoice arrives. However, Xero does not perform automated matching.
Specifically, Xero does not:
- Automatically compare invoice amounts against PO amounts
- Flag price or quantity discrepancies
- Support tolerance configuration
- Route matching exceptions to a review queue
- Track cumulative invoicing against blanket POs
- Perform line-level matching
The PO-to-bill conversion in Xero is a data entry shortcut, not a matching control. It pre-fills the bill with PO data, but it does not verify that the invoice matches the PO. If the supplier’s invoice differs from the PO, the difference is silently accepted unless someone manually checks.
MYOB
MYOB AccountRight includes purchase order functionality and can link POs to supplier bills. Like Xero, the link is a reference association, not an automated comparison. MYOB does not flag discrepancies, enforce tolerances, or route exceptions.
MYOB’s strength for PO-heavy businesses is its inventory module, which tracks stock movements and can record goods receipts. This creates the data needed for three-way matching — but MYOB itself does not perform the three-way comparison. A dedicated AP automation layer is required to use the receipt data as part of an automated matching workflow.
What a dedicated AP layer adds
A dedicated AP automation platform sitting in front of Xero or MYOB performs the matching that the accounting system does not. It pulls PO data from the accounting system, compares incoming invoices at the line level, applies configured tolerances, routes exceptions to the appropriate reviewer, and publishes matched invoices to the ledger only after the matching check has passed.
Pulsify’s PO matching integrates directly with both Xero and MYOB, running two-way matching at invoice intake before invoices enter the approval workflow. Matching exceptions are routed to the exception queue with the original PO and invoice details side by side for efficient resolution.
Integrating PO matching with approval workflows
PO matching works best when it operates upstream of the approval workflow. An invoice that passes the matching check proceeds to approval normally. An invoice that fails goes to a dedicated exception queue for investigation before it reaches the approver.
This sequencing matters. When PO matching and approval happen simultaneously — the approver is expected to both verify the PO match and decide whether to approve — two things go wrong. First, the approver is performing a mechanical comparison (checking numbers against a PO) alongside a judgment decision (is this spend appropriate?). Mixing these tasks reduces the quality of both. Second, when the approver is busy, the PO comparison is the step they skip first.
Separating matching from approval means approvers see clean invoices that have already been verified. Exception investigation is handled by a procurement or AP reviewer before approval, keeping the approver’s queue focused on authorisation decisions rather than discrepancy investigation.
The business case for implementing PO matching
Preventing overpayments
Australian businesses that process 200 invoices per month against purchase orders, with a 3 to 5 percent discrepancy rate, are typically preventing four to ten incorrect payments per month. At an average invoice value of AU$3,000, that represents AU$12,000 to AU$30,000 in potential overpayments intercepted monthly.
The overpayment prevention benefit is immediate and measurable from the first month of operation. Most businesses discover discrepancies they did not know existed — price variances that had been passing through undetected, quantity differences that were absorbed without investigation, and duplicate charges that were paid twice.
Preventing unauthorised purchases
PO matching also catches invoices that have no corresponding purchase order. In businesses with PO discipline, an invoice without a PO reference is an immediate red flag: someone ordered something outside the approved process, or the invoice is fraudulent. Either way, it requires investigation before payment.
This control is particularly effective against phantom vendor fraud — where a fraudster creates a fictitious supplier and submits invoices for goods or services never ordered. The accounts payable fraud vulnerability guide covers this and other common fraud vectors in detail. Without PO matching, these invoices enter the approval queue and may be approved if they appear plausible. With PO matching, the absence of a corresponding PO flags them immediately.
Audit readiness
PO matching creates a documented control that connects authorised purchasing commitments to actual payments. This is the evidence auditors look for when testing the procure-to-pay process: that every payment corresponds to something the business formally agreed to purchase.
For Australian businesses subject to external audit or ATO review, PO matching provides structured evidence that spend was authorised before commitment, verified before payment, and documented at each stage.
Time recovery
The time benefit is often the most immediately felt. Manual PO matching — looking up the PO, comparing it line by line, documenting the result — takes 3 to 5 minutes per invoice. At 200 invoices per month, that is 10 to 17 hours of manual work. Automated matching reduces this to exception review time only — typically 15 to 30 minutes per day for a business processing 200 invoices per month.
For growing businesses where informal ordering is giving way to structured procurement, PO matching implementation is often the catalyst for establishing the purchasing discipline that the AP controls layer requires.
Further reading: Why PO Matching Fails in Construction · AP for Wholesale and Distribution Businesses · Invoice Approval Workflow Software
Sources: ATO eInvoicing for business · ATO Record-keeping requirements · ACCC Targeting Scams Report 2024