Most Australian small businesses that use purchase orders do so informally. The PO exists — in a spreadsheet, in Xero’s basic module, or as an emailed document — but when the supplier invoice arrives weeks later, no one runs a systematic check against it. Someone approves the invoice based on a general sense that the amount looks right. The PO and the invoice are never formally reconciled.
This works until it stops working. A plumbing contractor pays a supplier for 200 metres of copper pipe when 160 metres were delivered because the invoice says 200 and no one checks the delivery docket. A wholesaler pays an invoice at last quarter’s unit price because the supplier did not update their pricing and no one noticed until a margin review six weeks later. A construction business pays a subcontractor variation that was never formally approved because the variation order was discussed verbally and the original PO was never updated.
These are not random errors. They are predictable consequences of a PO process that stops at order creation and does not extend to invoice matching. Purchase order software, properly understood, is not primarily about creating purchase orders — it is about closing the loop when invoices arrive.
What Purchase Order Software Actually Does
The PO lifecycle has four stages, and the value of software is different at each one.
Stage 1: Creating and Sending the Purchase Order
The first stage is the one most businesses are familiar with. A purchase order is a formal document that commits the business to buying a specified quantity of goods or services from a supplier at an agreed price. It communicates to the supplier exactly what is being ordered, establishes the legal and commercial basis for the transaction, and creates an internal record that an authorised person approved the spend before it was committed.
Xero’s native PO module handles this adequately for most businesses. You create a PO, specify the line items, apply the relevant account codes, and send it to the supplier. MYOB AccountRight has similar functionality. For businesses creating fewer than 30 to 40 purchase orders a month, the native tools in either platform are sufficient for this first stage.
Stage 2: Tracking Open Orders
Once a PO is sent, the business has a committed spend that has not yet been invoiced. Tracking open orders — what has been ordered, from whom, at what total value, and when delivery is expected — is a cash flow management function as much as an AP function.
Xero shows open purchase orders in the system, but does not automatically alert when a PO has been outstanding for longer than expected, or flag when a supplier has partially invoiced against a PO and the balance remains open. MYOB AccountRight offers slightly more visibility for businesses tracking purchase commitments against budgets. For businesses with high PO volumes or long lead times between order and delivery, a dedicated PO management layer provides better visibility than either native tool.
Stage 3: Receiving and Matching Invoices
This is where most businesses fall down, and it is where dedicated PO software provides its most significant value.
When a supplier invoice arrives, it needs to be checked against the original purchase order. The matching check covers:
- Supplier identity: Is the invoice from the same entity named on the PO?
- Unit price: Does the invoiced price per unit match the agreed rate?
- Quantity: Does the invoiced quantity match what was ordered (or received, if running a 3-way match)?
- GST treatment: Is the GST coding on the invoice consistent with the PO and the expected tax treatment?
Xero does not perform this match automatically. When an invoice arrives in Xero’s Bills section, it is entered and coded, and then approved. The question of whether it corresponds to an approved PO, and whether the amounts match, is a manual step that relies on whoever is processing the invoice to cross-reference the two documents. At low volumes, this works. At 50 invoices a month against 40 open POs from multiple suppliers, it does not.
Stage 4: Managing Exceptions and Completing the PO
When the invoice matches the PO within the configured tolerance — typically within 2 to 5 percent on price, and within an agreed quantity tolerance — the invoice clears and proceeds to payment. When it does not match, it needs to be routed to whoever can resolve the discrepancy: the person who raised the PO, the project manager, or the supplier.
Exception management is where manual PO processes create the most friction. An invoice that does not match a PO either gets paid anyway (because the approval process does not check the PO), gets held indefinitely (because no one knows who should resolve it), or generates a supplier call that takes the finance person 20 minutes to resolve because they cannot see the original PO and the approval history simultaneously.
Two-Way vs Three-Way Matching: Which One Your Business Needs
Two-Way Matching
Two-way matching compares the supplier invoice against the purchase order. It checks that the supplier is the one named on the PO, that the price per unit matches, and that the quantity invoiced matches the quantity ordered. When all three align within tolerance, the invoice clears matching.
Two-way matching is the appropriate control for:
- Service businesses where there is no physical delivery to confirm
- Businesses without a formal goods receiving process or documented delivery records
- Construction subcontractor invoices billed against milestone or progress claim values
- Businesses where supplier relationships are established and price variances are rare
Two-way matching provides meaningful AP fraud protection. An invoice from a supplier not on the approved vendor list, or at a price above the agreed rate, will be caught before it reaches an approver. The gap it leaves open is payment for goods ordered but not delivered — which requires a three-way match to detect.
Three-Way Matching
Three-way matching adds a goods receipt note (GRN) to the comparison. The GRN is generated by whoever receives the goods — a warehouse manager, a site foreman, or a stores person — and records what was actually delivered. The matching check confirms that the invoice and the PO align, and that the GRN confirms delivery.
Three-way matching is appropriate when:
- The business handles significant physical goods volumes where delivery quantities can be verified
- A warehouse management system or inventory platform already generates GRNs as part of normal operations
- The business has experienced disputes with suppliers over quantities invoiced versus quantities delivered
- Invoice values are large enough that the cost of implementing a formal receiving process is justified
For most Australian SMBs, two-way matching implemented well provides better AP control than three-way matching implemented poorly. A three-way match system that relies on informal receiving records — a signature on a paper docket that never makes it into the system — creates exception queues that cannot be resolved and slows down legitimate payments.
What Breaks in Construction Environments
Construction is the sector where standard PO matching fails most predictably. The specific problems are structural, not accidental.
Variation Orders
A variation order changes the scope or price of work after the original PO has been issued. In construction, variations are routine. A concrete pour requires additional formwork because site conditions were different from the specification. A fitout contractor encounters existing services that require a design change. The subcontractor completes additional work and submits an invoice that includes both the original scope and the variation.
A standard two-way match will flag this invoice as a mismatch because the invoiced amount exceeds the original PO value. The correct response is to approve the variation and update the PO — but if the variation order was not formally documented and approved, the system flags what is actually a legitimate charge as an exception.
PO software that handles construction environments needs to support variation order management: a process for documenting, approving, and recording scope changes so that the updated PO value reflects what was actually agreed. Without this, every variation creates a manual exception that blocks payment and frustrates subcontractors.
Partial Deliveries
When a supplier delivers part of an order — half the steel reinforcing on a construction site, or a partial stock shipment from a wholesaler — the invoice may cover only the delivered portion of the PO. A standard two-way match will flag the invoice as a quantity mismatch because 60 tonnes were invoiced against a PO for 100 tonnes.
PO software needs to support partial invoice matching: the ability to mark a PO as partially fulfilled, record the invoiced quantity against the PO line, and leave the remaining PO balance open for future invoicing. Without partial delivery handling, every partial shipment generates a manual exception or gets processed without any matching at all.
Progress Claims
Progress claims — the mechanism by which subcontractors bill for completed work at project milestones — do not map cleanly onto traditional PO matching. The claim is for a percentage of the total contract value based on assessed completion, not for a specific quantity of a specific good delivered on a specific date.
PO matching software used in construction needs to handle contract value management: tracking the total contracted amount, the percentage billed to date, and the retention amount (typically 5 to 10% held back until practical completion). A standard goods-receipt model does not apply to this invoice type.
The GST Implications of PO Matching
When a purchase order is raised, the GST treatment of the underlying supply should be established at that point. A PO for materials from a GST-registered supplier is raised inclusive of GST. A PO for a GST-free supply — fresh food, certain medical supplies, exported goods — should be raised on a GST-free basis.
When the invoice arrives, the GST treatment on the invoice should be consistent with the PO. If the PO was raised inclusive of GST and the invoice is coded as GST-free, the input tax credit claim is incorrect. If the PO was raised for a GST-free supply and the invoice includes GST, the BAS will overclaim credits.
PO matching software that validates GST treatment at the matching step — comparing the GST coding on the invoice against the GST treatment recorded on the PO — catches these inconsistencies before they reach the ledger. For businesses lodging monthly or quarterly BAS, catching GST errors at invoice processing rather than at BAS review saves significant rework. The ATO’s data-matching capabilities mean that BAS amendments triggered by input tax credit errors increasingly attract compliance scrutiny.
For businesses importing goods, the GST treatment is more complex: GST on imports is paid at the border (administered by Australian Border Force) and then claimed as an input tax credit in the BAS period when the import entry is processed. PO matching for imported goods needs to reconcile the original PO value against both the supplier invoice and the import declaration, accounting for freight costs and duty that were not part of the original purchase order.
When You Actually Need Dedicated PO Software vs Xero’s Built-In PO
The decision is driven by three factors: volume, complexity, and error cost.
Stay with Xero or MYOB Native If
- You raise fewer than 20 to 30 purchase orders a month
- You have a stable supplier base where prices do not change frequently
- Your business deals in services rather than physical goods (so there is no delivery to verify)
- Your invoices are simple enough that a manual cross-reference against the PO takes less than two minutes per invoice
Consider Dedicated PO Software If
- You raise 30 or more purchase orders a month and spend meaningful time manually matching invoices to POs
- Your business operates in construction, wholesale, or manufacturing with partial deliveries, variation orders, or progress claims
- You have experienced payment errors — overpayments, duplicate payments, or payments at incorrect prices — that originated from a breakdown in the PO-to-invoice check
- You need to enforce a formal approval process for PO creation, not just for invoice approval (so that spend is committed only when an authorised person raises the PO)
- Your suppliers invoice on different schedules and one PO may be partially invoiced over multiple billing periods
The Cost of Getting It Wrong
Industry research consistently puts the cost of processing a manually handled supplier invoice in Australia at AU$27.67 per invoice. For a business processing 80 invoices a month against 50 open POs, that is over AU$26,000 a year in processing cost, before any payment errors.
Payment errors in a manual PO matching environment are not rare. A 2024 survey of Australian mid-market businesses found that 68 percent had experienced at least one duplicate payment in the prior 12 months, and 24 percent had experienced a payment at an incorrect price due to a PO matching failure. The average recovery time for a duplicate payment was 23 business days — nearly a full month of working capital tied up in a supplier credit that should not have existed.
What to Look For in PO Software for Australian SMBs
When evaluating PO software options, the relevant criteria for Australian businesses are:
Xero or MYOB integration depth. The PO system needs to push approved invoices cleanly to the accounting system, maintain consistent supplier records, and support the chart of accounts structure without requiring a manual rekeying step. Integration quality matters more than whether integration exists at all.
Configurable matching tolerances. Price and quantity tolerances should be configurable by supplier, category, or dollar threshold. A 2% tolerance on a $50,000 steel order is different from a 2% tolerance on a $200 consumables purchase. Rigid tolerance rules produce exception queues full of trivial variances that slow down legitimate payments.
Partial PO matching. Essential for any business that receives goods in multiple shipments or bills progress claims against a contract value. The system needs to track what has been invoiced against each PO line and leave the balance open for subsequent invoices.
Variation order support. For construction and project-based businesses, the ability to formally record, approve, and update a PO for scope changes — and have the updated PO value reflected in the matching check — is not optional.
GST validation at the matching step. Not just at invoice entry. The matching step should confirm that the GST treatment on the invoice is consistent with the PO, and flag inconsistencies before they reach the ledger.
Exception routing. When a match fails, the exception should route automatically to whoever can resolve it — the PO owner, the project manager, or the supplier — with the PO and invoice visible in the same screen. Manual exception management degrades into email chains that create their own audit gap.
Audit trail. Every PO creation, approval, variation, and invoice match should be recorded with a timestamp and user identity. For ATO compliance purposes and internal governance, the audit trail is the record that purchases were authorised before they were committed and that invoices were matched before they were paid.
Where Pulsify Fits
Pulsify’s PO matching capability covers two-way matching for Australian businesses using Xero or MYOB. Purchase orders are matched against incoming supplier invoices at the line level — comparing supplier identity, unit price, and quantity — with configurable tolerance thresholds and automatic exception routing.
When an invoice matches the PO within tolerance, it proceeds directly to the approval workflow. When it does not match, it is routed to the relevant approver with the PO and invoice presented together, along with the specific line items and values that triggered the exception. Approved invoices are published to Xero or MYOB as clean, coded bills without a manual rekeying step.
For construction and project-based businesses where partial deliveries and variation orders are routine, Pulsify’s exception routing ensures that legitimate mismatches — partial shipments, approved variations — are resolved quickly rather than blocking the payment queue indefinitely.
The starting point for most businesses is not software selection. It is understanding where the current PO-to-invoice process actually breaks. That is usually not at PO creation — it is at the matching step when the invoice arrives three weeks later and no one remembers what was ordered.
Sources
- ATO: Tax invoices and GST
- ATO: Importing goods — GST and customs duty
- ATO: eInvoicing for business
- ACCC National Anti-Scam Centre: Targeting Scams Report 2024
- Deloitte Access Economics / ATO: Cost of processing emailed PDF invoices in Australia (AU$27.67 per invoice benchmark)