Security of Payment for Subcontractors: The Basics

This is general information about how security of payment law works, not legal advice. It doesn’t account for your specific contract, state, or dispute. Get advice from a lawyer or your industry association before you rely on any of it.

What is security of payment legislation?

Security of payment legislation is a set of state and territory Acts that give you, the subcontractor, a statutory right to be paid for construction work as it’s done — separate from, and on top of, whatever your contract says. Every state and territory in Australia has one. If a builder or head contractor won’t pay, these Acts give you a fast, purpose-built process to force the issue, instead of your only option being a slow and expensive court claim.

That’s the reason they exist. Before this kind of legislation, a sub with a genuine payment dispute had one real option: sue, in a court, over months or sometimes years, for money owed on a job that had usually finished long before the case was heard. Security of payment law runs a parallel track — a payment claim, a response, and an independent adjudicator’s decision if it’s disputed — built to produce a result in weeks, not years.

It’s often shortened to “SOPA” (Security of Payment Act), even though the actual Act name is different in every state.

Which Act applies in your state

The core idea is the same everywhere, but the legislation itself is separate in each state and territory, with different names, different mechanics, and different deadlines. As of this article, the current Acts are:

• New South Wales — Building and Construction Industry Security of Payment Act 1999 (NSW)
• Victoria — Building and Construction Industry Security of Payment Act 2002 (Vic)
• Queensland — Building Industry Fairness (Security of Payment) Act 2017 (Qld)
• Western Australia — Building and Construction Industry (Security of Payment) Act 2021 (WA)
• South Australia — Building and Construction Industry Security of Payment Act 2009 (SA)
• Tasmania — Building and Construction Industry Security of Payment Act 2009 (Tas)
• Australian Capital Territory — Building and Construction Industry (Security of Payment) Act 2009 (ACT)
• Northern Territory — Construction Contracts (Security of Payments) Act 2004 (NT)

Most of these get amended every few years — Victoria’s, for one, has had a significant overhaul recently — so don’t assume a name or a rule you read somewhere five years ago is still current. If you’re relying on the detail of your state’s Act for a real dispute, pull the current version from your state or territory’s legislation website, or ask someone who deals with it regularly.

Worth flagging: the Northern Territory’s Act runs on a different underlying model to the others (closer to what’s sometimes called the “West Coast model”), so its process doesn’t map onto the claim-and-schedule pattern below quite as neatly as the rest. If you’re in the NT, check your Act’s specific process rather than assuming it works exactly like a claim you’ve seen from an eastern-state job.

How the payment claim process actually works

Strip out the state-by-state detail and the general machinery is the same everywhere:

1. You submit a payment claim. This isn’t just any invoice or progress claim — it’s a claim made to meet your state’s Act, usually needing to identify the work, the period, and the amount, and often needing to say (or be able to be read) that it’s made under the Act.
2. The other side can respond with a payment schedule. This is their formal response: how much they intend to pay, and if it’s less than you claimed, why. If they don’t respond in time, the consequences can be serious — in most states, failing to reply properly and on time can be treated heavily in your favour.
3. If it’s disputed, either side can refer it to adjudication. An independent adjudicator — not a judge, not a mediator — looks at both sides’ paperwork and hands down a binding decision on what gets paid, usually much faster than litigation would.
4. The adjudicator’s decision is enforceable. If the other side still doesn’t pay, you generally have ways to enforce it much like a court judgment, without having to start a full civil case from scratch.

That’s the shape of it in every state. The exact wording of what has to be in a payment claim, how a payment schedule has to respond, and what happens if someone misses a step, is where the states genuinely differ — which is exactly why this article won’t give you a single number to memorise.

If you’re not sure what actually separates an everyday progress claim from a payment claim that can trigger this process, we’ve written a full explainer on progress claims vs payment claims vs invoices. And if you want the mechanics of assembling a claim your builder will actually pay against, see how to write a progress claim.

Why paperwork discipline is what makes these rights usable

None of this helps you if your claim doesn’t hold up. Security of payment law gives you the right — but the right only works if your paperwork does its job.

In practice that means:

• The claim itself has to meet the Act’s requirements. A vague claim, or one that doesn’t clearly identify the work and the amount, is an easy target for a builder trying to knock it back or drag out a response.
• You need evidence behind the number. If it goes to adjudication, the adjudicator is working off documents — what was claimed, what was scheduled, and whatever evidence either side puts in. “Trust me, it was done” doesn’t survive contact with an adjudicator who’s never been on your site.
• Dates matter more than they feel like they should. When a claim was submitted, when a response was due, when a response actually arrived — these aren’t formalities. They’re often what decides who’s in the stronger position before an adjudicator even looks at the substance of the dispute.
• Everything needs to be kept, not just sent. Emails, photos, sign-offs, the claim as submitted, any response received — if you can’t produce it later, it’s the same as not having it.

The subs who get the most out of security of payment law aren’t the ones who know the Act back to front. They’re the ones whose claims are clean, on time, and backed by records every time — so if a dispute does end up in adjudication, there’s nothing to reconstruct under pressure.

Timeframes are strict — and unforgiving

Every state’s Act runs on strict timeframes: how long you’ve got to respond to a payment claim, how long before you can apply for adjudication, how long an adjudicator has to decide. These aren’t guidelines. Missing one can mean losing rights you’d otherwise have had — sometimes as serious as losing the ability to dispute a claim at all, or losing your window to take a non-payment to adjudication.

The actual day counts are different in each state, and some of them have changed in recent amendments, which is exactly why this article isn’t going to quote you a number. Check your state’s current Act, or ask someone across it, before you let a date slip because “that sounds about right.” A missed deadline is one of the most common and most avoidable ways subs lose ground under legislation that’s meant to protect them.

Again — this article explains the general shape of security of payment law, not the specific rules for your job. Timeframes, thresholds, and required wording all vary by state and change over time. Talk to a lawyer, your industry association, or your state’s building authority before you act on a real payment dispute.

Where WNDW fits

WNDW doesn’t touch the legal process — that’s between you, your contract, and your state’s Act. What it does is give you the paperwork discipline that makes these rights usable in the first place: claims built from stages your crew actually marked off, timestamped photos attached as evidence, and a record of what was claimed and when, kept automatically instead of buried in an inbox. If a claim ever needs to go further, you’re not scrambling to reconstruct it. See how it fits into your claims process on the progress claims page.

FAQ