Security of Payment explained for subcontractors
What is Security of Payment legislation?
Every Australian state and territory has a Security of Payment Act (SOP Act) — legislation that exists for one reason: to keep money flowing down the contracting chain. It gives anyone carrying out construction work a statutory right to progress payments, a formal payment claim to make them with, and a fast, low-cost process called adjudication to recover them without waiting years for a court.
The SOP Act sits on top of your contract. Whatever your subcontract says, the Act gives you rights the head contractor cannot take away — the Acts expressly prohibit contracting out. That's the point: the protection was written because the industry's standard behaviour was to starve the bottom of the chain.
Why should subcontractors care?
Because unpaid progress claims are the single most common way subcontractors get hurt. The SOP Act changes the balance in three practical ways:
- You have a right to be paid for work done, on a statutory timeline, even where the contract's payment terms are hostile.
- Silence costs the builder. In the East Coast model, if the respondent doesn't answer your payment claim with a payment schedule in time, the claimed amount can become a debt due.
- Adjudication is quick. A decision typically arrives in weeks, not the years a court claim takes — and the decision is enforceable while any wider dispute continues.
Which Act applies to my project?
The SOP Act of the state or territory where the construction work is carried out — not where your company is registered, and not what the contract says. The names are confusingly similar, but the details differ:
| State / Territory | Legislation | Worth knowing |
|---|---|---|
| NSW | Building and Construction Industry Security of Payment Act 1999 | The original East Coast model Act — the template most other states followed. See payment claims under the NSW SOP Act. |
| VIC | Building and Construction Industry Security of Payment Act 2002 | Substantially amended from 15 April 2026: "excluded amounts" abolished, reference dates replaced by a monthly claim entitlement, and a six-month long-stop after completion. See payment claims under the Victorian SOP Act. |
| QLD | Building Industry Fairness (Security of Payment) Act 2017 | Combines the payment regime with Queensland's statutory trust framework for project payments. See payment claims under the QLD BIF Act. |
| WA | Building and Construction Industry (Security of Payment) Act 2021 | WA moved to the East Coast model with this Act; older contracts may still sit under the previous Construction Contracts Act 2004. |
| SA | Building and Construction Industry Security of Payment Act 2009 | East Coast model. |
| TAS | Building and Construction Industry Security of Payment Act 2009 | East Coast model. |
| ACT | Building and Construction Industry (Security of Payment) Act 2009 | East Coast model. |
| NT | Construction Contracts (Security of Payments) Act 2004 | The remaining West Coast model jurisdiction — a different claim-and-response structure to the eastern states. |
Because the Acts differ, the deadlines and claim requirements differ too. A payment claim that's valid in NSW can be defective in Victoria. Always work from the SOP Act for the project's location — the state-by-state deadlines comparison puts every Act's numbers side by side.
Victorian subbies have the most catching up to do, because the reform landed on contracts that were already signed. We've written up what the Victorian reform means for the next subcontract on your desk.
What about pay-when-paid clauses?
Unenforceable — everywhere in Australia. A clause that makes the builder's obligation to pay you conditional on the builder first being paid by the principal is void under every Security of Payment Act. If your subcontract contains one, it isn't a reason to panic, but it tells you something about the drafting: it's a contract written hoping you don't know your rights. SubSync's AI Commercial Reviewer flags pay-when-paid drafting against the void provisions of the applicable state's SOP Act.
How do I actually use the protection?
The regime only works if your paperwork is right. In practice that means:
- Serve a payment claim on time, every time. Inside the window the SOP Act and your contract allow — routinely, not just when things turn sour.
- Make the payment claim valid. Identify the work, the amount and the period; in some states — Victoria included, where it is mandatory — the claim must state on its face that it's made under the Act. Get the basics wrong and the claim can be worthless.
- Diarise the response window. When a payment schedule arrives short, the clock for adjudication starts running immediately — and the windows are strict.
- Keep the paper trail. Notices, delivery records, approved variations, site instructions. Adjudicators decide on documents; the subcontractor with the organised project file usually wins.
Time bars are where good claims die. Your contract's notice clauses interact with the statutory timeline, which is exactly why SubSync's contract notices module tracks both from the contract you actually signed.
Where do subcontractors go wrong?
The patterns are depressingly consistent: claiming late; treating the first missed payment as a relationship issue instead of serving a payment claim; signing subcontracts with hostile payment terms without noticing (the time to check is before you sign, against a subcontract review checklist); and letting claim windows lapse during a dispute because "the lawyers are handling it".
Hostile payment terms are also negotiable while you still have leverage — a departure schedule is how you ask for them to change, and it costs you nothing to send with your price.
The legislation is genuinely subcontractor-friendly. But it rewards process, and it punishes delay — on both sides of the ledger. Upload the subcontract and SubSync will flag the payment terms against the SOP Act for your project's state, free for your first review.