Best Accounting Software Australia: How Subcontractor Invoice Approvals Differ From Standard SMB Workflows

The best accounting software in Australia is designed around standard commercial invoicing - a bill arrives, it gets coded, it gets approved, it gets paid. Subcontractor invoice approvals in construction operate under a fundamentally different set of rules, timelines, and documentation requirements. Finance teams that apply standard SMB approval workflows to progress claims are not just inefficient - they are exposed to legal risk they may not realise they carry.

What Makes Subcontractor Approvals Structurally Different

A standard SMB invoice approval involves four steps: receive the invoice, verify it matches what was ordered, approve it, pay it. The control points are simple because the relationship between the purchase and the payment is direct.

A subcontractor progress claim in Australian construction involves a legally defined payment framework under the Security of Payment Act (SOPA), a certification process involving the project manager or superintendent, retention amounts, variations that may not yet be formally documented, and response deadlines that, if missed, can make the full claim payable by default.

Under SOPA, a principal must respond to a progress claim with a payment schedule within 10 business days, or in some cases within the timeframe specified in the contract. A payment schedule delivered even one day late means the full claimed amount becomes payable. This is not an accounting software problem - it is a workflow timing problem that accounting software alone cannot solve.

The Current State: Where Standard AP Workflows Fall Short

Problem 1: Progress claims are not standard invoices

A subcontractor's progress claim is a formal payment request tied to a contract schedule, certified work stages, and agreed milestones. It references:

• Contract value and total claimed to date

• Work completed in the current period

• Approved variations included in the claim

• Retention amounts withheld to date

• Any disputed amounts from prior claims

None of this information is contained in the invoice itself. An accounting software tool that reads a PDF and matches it to a purchase order is looking at the wrong document. The relevant information is in the contract, the variation register, the site certification, and the retention schedule.

An AP coordinator at a head contractor in Newcastle described the problem directly: their subcontractor invoices were being processed through the same approval workflow as materials and equipment hire bills. Progress claims that required site superintendent certification and a comparison against the contract schedule were sitting in a standard invoice queue alongside $800 tool hire invoices. The approval steps were the same. The information requirements were not.

Problem 2: Variation invoices require a separate approval chain

When a subcontractor performs work that falls outside the original contract scope, a variation is issued. The variation goes through its own approval process - agreed in principle by the site supervisor, documented in a variation order, priced and approved by the project manager - before it can be included in a progress claim.

When a progress claim arrives that includes variation amounts, the finance team needs to verify:

• Has the variation been formally approved and documented?

• Does the variation amount in the claim match the approved variation order?

• Has the variation been included in any prior claims?

A standard AP approval workflow has no mechanism for this verification. The best accounting software in Australia for standard businesses will record the variation once it reaches the ledger, but it does not manage the upstream approval process.

Problem 3: Retention complicates the payment calculation

Retention is a percentage of each progress payment withheld by the principal until project completion. For a subcontractor's invoice, the amount payable is not the gross claim amount - it is the gross claim minus retention, minus any amounts withheld for disputed work.

For a finance team processing this through standard AP software, the calculation is manual. The accounting system records the payment made; the retention liability sits in a separate schedule. If the retention schedule is maintained in a spreadsheet or outside the accounting system, it is easy for the amounts to get out of sync when multiple claims have been processed across a project's life.

Problem 4: SOPA response deadlines create time pressure standard workflows aren't designed for

Standard AP workflows assume that approval timing is an efficiency question: faster is better, but the consequence of slow approval is a delayed payment and a supplier relationship that suffers. Under SOPA, slow response to a progress claim has legal consequences. Missing the payment schedule deadline makes the full claimed amount payable, regardless of any disputes or shortfalls.

A finance team that routes a progress claim through its standard approval queue - which might take seven to ten days for a high-value invoice to move through threshold approvals - may inadvertently miss the SOPA response window. The consequence is not a slow payment relationship. It is a legal liability.

What Best Accounting Software Australia Should Do for Construction

The accounting platform records the financial outcome. The workflow before it needs to be configured to handle construction-specific complexity.

The right accounting software - whether Xero or MYOB - needs to be paired with an approval workflow that can handle the documentation and timing requirements of construction AP specifically.

What the Approval Workflow Needs to Include

For construction businesses processing subcontractor progress claims through a structured workflow, the key requirements are:

• Intake that captures supporting documentation alongside the invoice - certification, variation orders, and payment schedules need to be attached and accessible to the approver

• SOPA response deadline tracking - the workflow should record when a claim was received and flag the approaching response deadline automatically

• Approval routing that includes site certification - the financial approval should be preceded by a certified site confirmation, not processed independently of it

• Retention schedule integration - the approved payment amount should automatically deduct retention from the approved claim, with the retention liability recorded separately

• Variation verification as a prerequisite - the workflow should confirm that all variations included in the claim have been formally approved before routing to financial approval

For finance teams reviewing their approval workflows in the context of subcontractor management, the purchase order matching step also works differently - the relevant comparison is against the contract and variation register, not a standard purchase order.

The Fraud Dimension in Subcontractor AP

The construction sector is a primary target for payment redirection fraud. A Victorian construction company was defrauded of AU$900,000 in 2024 when an attacker compromised a supplier's email and sent a fake progress claim with altered bank details. The claim appeared legitimate in every other respect. The fraud was not detected until after payment was made.

The ACCC identifies construction as one of the sectors most frequently targeted due to high transaction values and frequent invoicing from multiple subcontractors. Subcontractor payment redirection fraud is specifically noted in Australian Federal Police reporting on BEC targeting patterns.

Supplier bank detail validation - automated comparison of payment details against historical records for that supplier - is the specific control that addresses this risk. It should be applied to every subcontractor payment, not as an exception check for suspicious invoices.

Frequently Asked Questions

How does subcontractor invoice approval differ from standard SMB invoice approval?
Subcontractor progress claims reference a contract schedule, include certified work stages, contain retention amounts, and must be responded to within legally defined SOPA deadlines. Standard SMB approval workflows are designed for purchase-order-based invoicing and do not manage any of these elements. Construction AP requires a workflow that handles documentation, response timing, and variation verification as distinct steps.

What is SOPA and how does it affect progress claim approvals in Australia?
The Security of Payment Act (SOPA) is state-based legislation that gives subcontractors the right to receive payment for construction work and governs the timeline for responding to progress claims. A principal must provide a payment schedule within 10 business days of receiving a claim, or the full claim amount becomes payable by default. Finance teams processing subcontractor claims need to track these deadlines as part of the approval workflow.

Does the best accounting software in Australia handle subcontractor progress claims?
Xero and MYOB can record the financial outcomes of subcontractor payments, but neither manages the workflow complexity of progress claim certification, SOPA response tracking, variation verification, or retention schedule management. These require either a construction-specific project management tool or a configurable AP workflow that handles construction billing complexity.

How should retention be handled in accounting software for construction?
Retention amounts withheld from progress payments should be recorded as a separate liability in the accounting system - not just as a reduced payment against the invoice. Each payment should deduct the retention percentage automatically, with the cumulative retention balance tracked as a payable to the subcontractor until project completion and release conditions are met.

What audit trail does a subcontractor invoice approval need?
Beyond the standard approval record, the audit trail for a subcontractor progress claim should include: the site certification document, the variation register entries relevant to the claim, the retention calculation, the SOPA response date, and any amount withheld with the reason. This trail is relevant for both financial audits and any SOPA adjudication that may arise from disputed claims.