Submit valid payment claims
The only software built from the ground up for subcontractors and main contractors to comply with the Building Industry Fairness (Security of Payment) Act 2017 (Qld), the Building and Construction Industry Security of Payment Act 1999 (NSW), and the Building and Construction Industry Security of Payment Act 2002 (Vic).
| 2.0 | Bulk earthworks | 1,240 m³ | $12,410.00 |
| 3.0 | In-ground services | 318 m | $48,720.00 |
| 4.0 | Concrete structure | 412 m³ | $96,300.50 |
| V-02 | Rock excavation | Approved | $18,890.00 |
| This claim incl. GST | $184,254.92 | ||
- Reference date 28 February is valid under the contract and has not been claimed befores 75
- Served within six months of the work being carried outs 75(4)
- Claim states the amount claimed and requests payments 68(1)
- Two lines are described by percentage alone and do not identify the works 68(1)(a)
- Supporting statement attacheds 75(3)
More than a third of adjudications end with nothing
Across 1,582 Queensland adjudication decisions made under the current Act, 567 ended with the claimant recovering nothing at all. Not reduced. Nothing.
Under the Act it replaced, that figure was one in seven. It has since held at about one in three, and the last two and a half years look the same as the ten before them.
Counted from 7,601 Queensland adjudication decisions published between November 2004 and June 2026. A nil decision is not always a jurisdictional one; what these numbers measure is the money recovered.
Built for compliance
Three things have to be right before a claim goes out: what is in it, whether it meets the requirements on its face, and when it is served. Paystruct handles each of them in turn.
Build the claim from the contract
The breakdown lives on the contract, so every claim starts from the same items and the same numbering. You enter progress; the arithmetic follows.
- Quantities and units on every line, not percentages alone
- Previously claimed, this claim and claimed to date always reconcile
- Variations, adjustments and retention carried through automatically
- Your item numbering, headings and sub-items kept intact
| Ref | Description | Qty | Progress | This claim |
|---|---|---|---|---|
| 2.0 | Bulk earthworks | 1,240 m³ | 100% | $12,410.00 |
| 3.0 | In-ground services | 318 m | 85% | $48,720.00 |
| 3.1 | Stormwater, RCP 375 | 96 m | 60% | $14,880.00 |
| 4.0 | Concrete structure | 412 m³ | 60% | $96,300.50 |
| V-02 | Rock excavation | 210 m³ | 100% | $18,890.00 |
| This claim incl. GST | $184,254.92 | |||
Check it against the requirements
Before anything is served, Paystruct works through what the legislation asks of a payment claim on its face, and shows the section it is working from.
- Reference dates worked out from the contract, and checked against earlier claims
- Timing measured in business days, on the calendar for your State
- Descriptions tested for whether they identify the work
- Anything it cannot decide is put to you rather than assumed
- Reference date 28 February is valid under the contract and has not been claimed befores 75
- Served within six months of the work being carried outs 75(4)
- Claim states the amount claimed and requests payments 68(1)
- Two lines are described by percentage alone and do not identify the works 68(1)(a)
- Supporting statement attacheds 75(3)
Know where you stand on dates
Once a claim is served the clock is running. The calendar shows what has been served, what is owed back, and how long is left to respond.
- Response window counted from the date served
- Public holidays and the December shutdown excluded
- A running position on every contract, not one claim at a time
- The date, method and proof of service kept against the claim
Set the contract up once
The contract holds the parties, the dates, the security and the breakdown. After that a claim is a period and a set of figures, not a document rebuilt from scratch.
Set up the contract
Build the claim
Check it before it goes
Serve it and record it
How people do this today
Most claims are put together in something that was never built for it. Here is what each approach does and does not give you.
| Paystruct | Generic invoicing software | Claim portal run by the party paying you | Spreadsheet | |
|---|---|---|---|---|
| Built around a contract breakdown that carries claim to claim | Yes✓ | No✕ | Partly– | Partly– |
| Reference dates and response windows worked out for you | Yes✓ | No✕ | Partly– | No✕ |
| Business days counted on your State’s calendar | Yes✓ | No✕ | Partly– | No✕ |
| Checks the claim before it is served | Yes✓ | No✕ | No✕ | No✕ |
| Supporting statement produced with the claim | Yes✓ | No✕ | Partly– | No✕ |
| Claim pack with attachments appended in one document | Yes✓ | No✕ | Partly– | No✕ |
| Record of what was served, when and how | Yes✓ | Partly– | Partly– | No✕ |
| You keep the record if the relationship ends | Yes✓ | Yes✓ | No✕ | Yes✓ |
| Works the same across Qld, NSW and Vic | Yes✓ | No✕ | No✕ | No✕ |
A general description of common approaches, not a statement about any particular product. Paystruct is software, not a law firm, and nothing here is legal advice.
Common questions
Which States does Paystruct cover?
Does Paystruct tell me whether my claim is valid?
Is this legal advice?
Do I have to move everything across to start?
What counts as a contract?
What does it cost?
Can I still use my own claim format?
What happens to my records if I stop paying?
Set up your first contract
The first one is free. You can have a claim ready to serve today.
