Construction was Australia’s highest-insolvency industry in 2024-25, accounting for more than 28% of all company insolvencies according to ASIC data. The causes are discussed constantly: cost escalation, fixed-price contracts, labour shortages, supply chain disruption. What’s discussed far less is the AP control layer - the invoice processing failures that drain cash before a business knows there’s a problem.
Three AP failures are structurally common in Australian construction bookkeeping. They aren’t exotic or unusual. They happen in businesses with competent finance teams and established processes. They happen because construction has requirements that standard SMB accounting tools and workflows weren’t designed for.
Variation Claims Paid Without Proper Approval
A variation claim is a subcontractor’s request for payment for work that falls outside the original contract scope. Unlike a standard progress claim, the amount isn’t pre-agreed in the contract schedule. The project manager needs to assess the variation, approve the value, and authorise payment before the invoice goes anywhere near the AP queue.
In practice, this approval step is frequently informal. The project manager tells the site administrator to “pay it”, the administrator enters it into MYOB or Xero, and the payment goes out. No written record of the approval exists. No comparison against the original contract schedule happens. When the same variation claim arrives the following month because the subcontractor assumed it wasn’t processed, the administrator pays it again.
The scale of the problem is easy to underestimate. A construction business running six concurrent projects, each with two or three active subcontractors submitting monthly progress claims and occasional variations, is processing a lot of invoices. At 200 invoices per month, manually cross-referencing each one against its approved variation schedule isn’t realistic. The process fails not because of negligence but because it wasn’t designed for the volume.
What construction bookkeeping needs is a PO matching step that operates at the line level: comparing each invoice line against the approved contract or variation schedule before routing to approval. Not a comparison of the total invoice amount against a total contract value, which catches large discrepancies but misses line-item errors. Line-level matching surfaces variation claims paid without a corresponding approved variation order.
Pulsify’s PO matching layer handles this comparison before an invoice reaches the approval queue, flagging mismatches for review rather than requiring the approver to identify them manually.
Subcontractor Payment Redirection Fraud
Business email compromise (BEC) targeting construction businesses follows a specific pattern. An attacker monitors email communication between a builder and a subcontractor, then sends a fraudulent invoice that looks identical to a legitimate one: same supplier name, same ABN, similar amount, but a changed bank account number.
Construction is particularly exposed to this because bank detail changes are frequent and often legitimate. Subcontractors restructure their business entities, change banks, and update payment details when they change accountants. A business processing 300 subcontractor invoices a month from 50 suppliers will see genuine bank detail changes regularly. Training AP staff to always verify bank changes doesn’t scale when changes arrive during end-of-month crunch alongside 40 other invoices.
According to the ACCC’s National Anti-Scam Centre, payment redirection fraud cost Australian businesses AU$152.6 million in 2024. Construction businesses are structurally over-represented in that figure because of the combination of high per-invoice values and high supplier turnover.
The control that prevents this isn’t a training program. It’s automated bank detail comparison: the AP system compares the bank account number on each incoming invoice against the account on record for that supplier and holds the invoice for manual review if a change is detected. That check needs to run on every invoice, not just on new supplier onboardings, not just when the amount is over a threshold. If the system doesn’t do this automatically, the check gets skipped.
For an overview of how AP automation handles this validation step in practice, the feature page covers the specific control logic involved.
Duplicate Invoices Across Job Cost Codes
Construction invoices are unusually susceptible to duplicate payment because of how they’re structured. A subcontractor invoicing for work across multiple cost codes on the same project submits invoices referencing the same project, the same supplier, and similar amounts month after month. When a duplicate arrives, it can look indistinguishable from a legitimate invoice without a careful comparison against the full invoice history for that supplier and project.
The problem amplifies at month-end and financial year-end, when invoice volumes spike and approval pressure increases. Duplicate detection that requires a reviewer to search the supplier’s invoice history manually doesn’t hold up under that pressure. Detection needs to happen before the invoice reaches the approval queue: a system-level check across invoice number, supplier, amount, and date.
What makes construction particularly difficult is that duplicate detection can’t rely on invoice numbers alone. Subcontractors reuse reference numbers across projects, use project codes that change between billing cycles, and occasionally submit handwritten invoices with no reference number at all. The detection logic needs to operate across multiple fields simultaneously.
The Real Cost of Getting This Wrong
The three control failures aren’t independent problems. They compound. A construction business that lacks variation approval controls, bank detail validation, and duplicate detection is exposed on all three fronts at once. Any one of them can cause a significant loss; all three together create consistent, low-level cash leakage that rarely appears as a single identifiable event in the accounts.
Consider a residential builder with eight concurrent projects processing 250 invoices per month. In a given month, two variation claims are paid without a corresponding approved variation order (AU$8,400 combined). A subcontractor’s bank detail change request is processed without verification because it arrived in the last week of month-end (AU$14,200 payment to a fraudulent account). One duplicate progress claim from a regularly used tiler goes undetected (AU$3,600). None of these appear obviously in the general ledger. They look like ordinary subcontractor payments.
That’s AU$26,200 in a single month from three control failures that each have a straightforward automated solution.
What Construction Bookkeeping Actually Requires
The practical solution isn’t switching to a new accounting platform. Construction businesses stay on MYOB or Xero for good reasons: job costing, progress billing, payroll integration, retention management. The requirement is a dedicated AP layer sitting in front of the accounting system and handling the pre-approval controls: variation claim matching, bank detail validation, and duplicate detection before any invoice reaches a human approver.
That layer also needs to handle approval routing correctly. A subcontractor invoice for site materials might need project manager approval for amounts under AU$5,000 and CFO approval above that. A variation claim needs project manager sign-off before it can be approved at any amount. Getting this routing right and enforcing it automatically is the difference between controls that work and controls that exist on paper.
For a full evaluation of construction accounting software on these AP criteria, the construction accounting software buyer’s guide covers vendor-by-vendor assessment.
What Volume Changes About This Problem
A business processing 20 supplier invoices a month can manage AP with native accounting software features and a careful person reviewing each invoice. At that volume, manual review works. Construction changes that equation quickly.
A mid-sized residential builder with 8 to 12 concurrent projects might process 200 to 400 invoices per month from 50 to 80 distinct subcontractors and suppliers. Every manual step is a potential failure point. The person doing the check is under pressure. Invoices arrive in batches. Month-end creates a predictable crunch that everyone in the office knows about.
The ASIC insolvency data for construction reflects businesses that ran out of cash. AP control failures don’t always show up as obvious fraud losses. Sometimes they look like slow margin erosion from overpaid variation claims, from duplicate invoices that were eventually caught (sometimes recovered, sometimes not), and from bank detail fraud discovered months after the payment cleared. None of these show up as a clean line item. They show up in the cash position, usually when it’s too late to do much about them.
The businesses in ASIC’s insolvency data weren’t necessarily processing invoices carelessly. Many had experienced bookkeepers and established accounting systems. What they often didn’t have was an AP layer that treated invoice verification as a mandatory system step rather than something a person was supposed to remember to do during a busy month-end.
Sources: ASIC - Corporate Insolvency Statistics · ACCC National Anti-Scam Centre - Targeting Scams Report 2024 · ACCC - Business Email Compromise guidance
Further reading: Construction Accounting Software Australia 2026: Buyer’s Guide · Why PO Matching Fails in Construction · Best AP Automation Software Australia 2026