Purchase order matching sounds straightforward. Invoice comes in, you check it against the PO, amounts match, you approve. In retail or distribution this works reasonably well. In construction it falls apart almost immediately.
The problem is not that construction businesses lack POs. Most use them. The problem is that construction invoices and construction POs are almost never a clean one-to-one match. Subcontractor payments bill progressively. Materials arrive in partial shipments. Variation orders change the agreed scope mid-project. Costs need to be split across multiple cost codes.
Standard PO matching logic was not built for any of this. Which is why most construction finance teams either abandon matching entirely or drown in manual exception handling. For how to implement matching that works, see our guide on purchase order matching in AP workflows.
How finance teams currently handle PO matching
Before looking at what breaks, it helps to see what construction businesses are actually choosing between:
| Approach | How it works | What it misses |
|---|---|---|
| Spreadsheet or email-based matching | Manual cross-check of PO, invoice, and delivery note | Time-consuming, error-prone, no audit trail |
| Accounting platform native (Xero/MYOB) | Basic bill-to-PO comparison at header level | Line-item variance, partial deliveries, variation orders |
| Dedicated AP automation with PO matching | Automated line-level comparison with exception flagging | Requires clean data input and PO discipline upstream |
| Construction-specific project management integration | Procore or Jobpac generates POs, invoices reconcile at project level | Integration gaps between project and accounting systems |
Most Australian construction SMBs sit in the first or second row. The third is where the real operational improvement happens, but getting there requires understanding why the gap exists.
How does PO matching specifically break down in construction?
Progressive billing against milestone POs
Subcontractor contracts are typically structured around milestones or percentage completion - not discrete line items. A subcontractor invoices progress claims at 30% upon structural completion, 50% upon rough-in, and so on. The invoice amount is correct relative to the contract but does not map cleanly to a line item on the original PO.
Standard matching treats this as a discrepancy. Your AP team has to manually verify the milestone, confirm completion with the site manager, and override the system. Multiply this by the number of subcontractors on a project and it becomes a significant time burden.
Partial deliveries against materials POs
Materials orders - steel, timber, concrete, fittings - are rarely delivered in a single shipment. A supplier delivers what is available, invoices for that portion, and delivers the remainder later with a second invoice. Each partial invoice is a valid charge against the same PO.
Without a system that tracks cumulative invoicing against the PO total and flags when the running total exceeds the order value, two things happen: some partial invoices get rejected as duplicates, and others get approved past the PO limit without anyone noticing.
Variation orders that change the agreed amount
Variations are endemic to construction. Client changes scope, site conditions require additional work, design issues emerge. Each variation gets approved and documented - eventually - but the original PO value rarely gets updated in the accounting system before the invoice arrives.
So when a subcontractor invoices for the variation work, the invoice exceeds the PO and the match fails. In practice this means either someone manually overrides it without verifying the variation was actually approved, or the invoice gets held until the PO is updated - which can take days if the approver is on site.
Multi-project cost splitting
Some invoices in construction need to be split across multiple projects or cost codes. A shared plant hire invoice covers two sites. A material delivery is split between two jobs. The invoice is legitimate but it does not match any single PO - it needs to be partially allocated across several.
Most AP systems do not support this natively. The workaround is manual split coding, which is slow and inconsistent.
Retention amounts
Construction contracts commonly include retention - typically 5 to 10 percent of each invoice held back until practical completion. A subcontractor invoices their full claim, but payment is the invoice amount minus retention. The invoice amount and the payment amount are different by design.
AP systems that match on invoice amount rather than payable amount will consistently flag retention-adjusted payments as discrepancies.
Why the process breaks: root causes
Three structural issues underpin most PO matching failures in construction:
PO discipline degrades under site pressure. Purchase orders get raised after work starts on urgent jobs. The PO number on the invoice does not match anything in the system because the PO was created retroactively. Finance is then reconciling documentation after the fact, not before payment.
Supplier invoice formats are inconsistent. One subcontractor invoices using the PO number as a reference. Another invoices with a claim number. A third sends a tax invoice with a narrative description and no structured data at all. Automated matching requires consistent reference data. Construction invoices rarely provide it.
The approval chain and the matching chain are separate. In most construction AP workflows, the project manager approves the scope and the variation. Finance approves the invoice. These two approval events do not share data. Finance is approving payment based on the invoice; they may not know whether the project manager approved the underlying variation. This separation is where approval workflows need to bridge the gap.
Why the standard advice does not work
The usual recommendation is to implement three-way matching - match invoice, PO, and goods receipt. In theory this catches most discrepancies. In construction it creates as many problems as it solves.
Goods receipts in construction are site-based processes. Delivery dockets are often paper, held by a site foreman, and may not reach the finance team for days. Requiring a confirmed goods receipt before invoice approval creates payment delays that strain subcontractor relationships and, in some states, may conflict with security of payment legislation.
Rigid three-way matching also cannot accommodate the variation order problem. You can match the invoice to the PO and to the delivery docket perfectly - and still have an invoice that is over the original contract value because scope changed.
What Actually Works: Flexible Matching with Project-Aware Rules
The solution is not to abandon matching. It is to implement matching logic that reflects how construction actually works.
Track cumulative invoicing against PO value
Instead of matching each invoice to a specific line item, track the running total of all invoices against the PO or subcontract value. Flag when cumulative billing exceeds the contract amount. This catches overbilling on progressive claims without rejecting legitimate partial invoices.
Build variation order workflows
Variation approval needs to happen before the invoice arrives, not after. This means giving project managers a way to approve variations in the same system that processes invoices - so that when a subcontractor bills for the variation, the AP system knows it has been sanctioned and can approve it without a manual override.
Separate goods receipt from invoice approval where needed
For materials, goods receipt confirmation is important. For subcontractor progress claims, it is often impractical. Your matching rules should distinguish between invoice types - requiring delivery confirmation for materials orders and using milestone verification for subcontractor claims.
Handle retention at the coding stage
Retention should be handled systematically - a retention liability account that accumulates as invoices are processed, with payment triggered at practical completion. This removes retention from the matching problem entirely and keeps it in the accounting layer where it belongs.
Enable multi-project allocation
Invoices that span multiple projects should be splittable at the coding stage without requiring separate invoices from the supplier. Your AP system should allow a single invoice to be partially allocated across cost codes or project numbers before it is posted to Xero or MYOB.
The Role of Your Accounting System
Xero and MYOB are the dominant accounting systems for Australian construction SMEs. Both have purchase order features. Neither handles construction-specific complexity well - progressive billing tracking, variation workflows, retention accounting, and multi-project splitting all require workarounds or manual processes.
This is why construction businesses typically need an AP automation layer that sits above the accounting system and handles the matching, routing, and coding logic before passing approved invoices through. The accounting system records the outcome. The AP layer manages the process.
The downstream impact when matching fails
When PO matching breaks down in construction, the first consequence is reporting lag. Job costing is inaccurate because invoices are held in the AP queue while someone manually resolves the mismatch. Project profitability reports do not reflect actual committed costs.
The second consequence is payment delay. Subcontractors in Australia regularly face late payment issues — according to Xero Small Business Insights, 53% of invoices from SMBs to large businesses are paid late, on average 23 days overdue. When the matching process is broken, finance teams cannot confidently approve for payment, so invoices sit longer than they should.
The third consequence is fraud exposure. When variation invoice overrides become routine, the habit of bypassing the control becomes normalised. A fraudulent invoice constructed to look like a variation claim, with changed bank details, gets processed with the same manual override that legitimate variation invoices receive. This is a well-documented AP fraud vulnerability in construction.
Signs your current PO matching process is not working
- Your team regularly overrides matching failures without investigating them
- Variation order invoices always get held until someone manually checks
- Partial delivery invoices create duplicate detection false positives
- You have no visibility into cumulative invoicing against contract value
- Subcontractors regularly call chasing payment on invoices stuck in review
- Month-end requires significant rework to reconcile project costs
What Structured Construction AP Looks Like
When PO matching is configured for how construction actually works - progressive billing, variations, retention, partial deliveries - the AP team’s job shifts from chasing exceptions to reviewing a small number of genuinely anomalous invoices.
Subcontractor relationships improve because payment cycles become predictable. Project cost visibility improves because invoices are coded correctly at the point of processing rather than corrected at month-end. And the risk of overbilling or duplicate payment drops significantly because the matching logic is doing its job consistently, not selectively.
For more on how Pulsify handles PO matching for construction and project-based businesses, see the feature overview.
Sources: ATO eInvoicing statistics · ACCC Targeting Scams Report 2024
Further reading: How to Implement Purchase Order Matching in AP Workflows · Three-Way Matching vs Two-Way Matching · Best AP Automation Software Australia 2026