Security of Payment Act: What Construction Payment Claims Need to Show

A payment claim usually fails in the evidence before it fails in the argument. The claimed percentage looks plausible, the invoice has the right project name, and the cover email says the work was done. Then the programme update tells a different story: the data date is unclear, the activities don’t match last month’s file, and the claimed work still has its full remaining duration.

Security of Payment laws exist to keep construction cash flow moving. For the PM, contract administrator, subcontractor, consultant, or owner-side reviewer dealing with the claim, the practical question is narrower: can the claimed progress be tied to contemporaneous records? A structured construction schedule analysis helps because it tests the programme file behind the payment narrative, rather than treating the PDF bar chart as proof.

What Security of Payment Means in Construction

Security of Payment legislation gives construction parties a statutory route to progress payments, payment responses and adjudication when cash flow breaks down. It doesn’t turn a weak progress narrative into a strong one, and it doesn’t remove the need to follow the state or territory rules exactly.

In plain English, the usual workflow starts with a payment claim from the party seeking payment. The other party may respond with a payment schedule stating what it proposes to pay and why. If the parties remain in dispute, the claimant may have an adjudication pathway. Terms such as claimant, respondent, principal, head contractor and subcontractor need to be checked against the relevant Act before anyone uses them in a notice.

Term	Practical meaning for a project team	Evidence question
Payment claim	The written claim for progress payment	What work is being claimed, and at what date?
Payment schedule	The written response to the claim	Which items are accepted, reduced, rejected, or unexplained?
Adjudication application	The statutory dispute step after non-payment or disagreement	Does the file evidence support the progress narrative?
Contemporaneous records	Records created at the time, not rebuilt later	Do diaries, photos, inspections and updates tell the same story?

Table: Security of Payment language is legal language, but the evidence problem is practical: show what was planned, what was done, and what changed.

Security of Payment Acts Are State-Based

Australia doesn’t have one national Security of Payment Act for construction projects. Each state and territory has its own legislation, regulator material and process rules.

The table below points to official sources; it isn’t legal advice. It deliberately avoids deadlines because those dates change, exceptions matter, and a wrong clock can cost more than a weak programme file.

Jurisdiction	Act name	Official information source	Drafting note
New South Wales	Building and Construction Industry Security of Payment Act 1999	NSW Government Security of Payment	Strong claimant and respondent guidance, including payment-claim material
Victoria	Building and Construction Industry Security of Payment Act 2002	Building and Plumbing Commission Security of Payment	Amendments took effect on 15 April 2026; read the regulator’s change notes before relying on older guidance
Queensland	Building Industry Fairness (Security of Payment) Act 2017	QBCC payment protection laws	The Act name differs from the common SOPA wording
Western Australia	Building and Construction Industry (Security of Payment) Act 2021	WA security of payment guide	Regulator guidance is set up as a step-by-step pathway
South Australia	Building and Construction Industry Security of Payment Act 2009	South Australian Legislation	New Regulations were made in 2026; the Small Business Commission handles construction payment enquiries
Tasmania	Building and Construction Industry Security of Payment Act 2009	Building Standards Tasmania	Check whether the project and work type are covered
Australian Capital Territory	Building and Construction Industry (Security of Payment) Act 2009	ACT Planning security of payments	ACT material separates practitioner information from the Act itself
Northern Territory	Construction Contracts (Security of Payments) Act 2004	NT Government payment disputes	The Act title and process language differ from the east-coast pattern

Table: Use official regulator pages to find the current process, then read the Act or get advice before acting on any deadline or notice wording.

The Basic Payment-Claim Workflow

A Security of Payment workflow has a recognisable shape even though the detail changes by jurisdiction. The safest working assumption is that every step needs a current source check before anyone serves a notice or decides not to respond.

Figure: The common workflow shape and its three hold points. Deadlines, wording and consequences must be checked in the relevant jurisdiction.

The first hold point is service. A progress claim sent to the wrong address, in the wrong form, outside the available time or without required wording may create a legal problem before anyone reaches the programme evidence. The second hold point is the response: silence, a late payment schedule, or a thin reason for withholding payment can have consequences that differ by state and territory.

The third hold point is adjudication. By that stage, the evidence pack matters. Suppose a claim says the concrete works were 80% complete. That needs more than a percentage. It needs the contract basis, the claimed scope, the update period, records created at the time, and a programme position that doesn’t contradict the narrative.

What Evidence Supports a Construction Payment Claim?

The programme is one record in a wider evidence set. It helps connect dates, planned sequence and reported progress, but it doesn’t replace site records or the contract.

Evidence	What it can show	What to check before relying on it
Accepted baseline or current accepted programme	Planned sequence, planned dates and milestone logic	Whether it was actually accepted, and for what purpose
Monthly update file	Status at the data date, progress, remaining duration and forecast dates	Data date, native file integrity and whether logic changed
Update narrative	Reasons for progress shortfall, out-of-sequence work and recovery steps	Whether the explanation matches the native file
Site diary and daily records	Labour, plant, access, weather, instructions and work fronts	Whether entries are contemporaneous and project-specific
Photos, inspections and test records	Physical progress and completion of work items	Whether dates and locations match the claimed activities
Delivery dockets and subcontractor records	Materials, off-site work and package progress	Whether the claim relies on stored or unfixed materials
Correspondence and instructions	Change, access, delay and dispute context	Whether the record supports the timing asserted in the claim

Table: A payment-claim evidence pack should make the progress story testable from more than one source.

For schedule-specific records, the data date is the first test. If the update doesn’t say when progress was measured, the reviewer can’t safely compare it with diaries, photos or invoices. The second test is continuity: activity IDs, WBS, names and logic should be stable enough that this month’s claim can be compared with last month’s file.

That continuity links payment evidence to delay evidence. If the payment dispute overlaps with a delay narrative, the same programme update may later appear in an extension of time claim analysis. Keep the payment claim file pack clean enough that it can survive that second use.

Where Schedule Evidence Helps, and Where It Doesn’t

Schedule evidence helps when the dispute turns on progress, sequence and timing. It can show what work was planned in the claim period, which activities were under way, whether a claimed activity still carried its full remaining duration, and whether the completion path moved between updates.

Suppose a subcontractor claims a façade package is substantially complete at the end of the month. The native programme can show the activity status, remaining duration, data date and successor logic. Site photos and inspection records then test whether the reported status matches what was visible on site.

Schedule evidence also helps the respondent. A reviewer can compare the current programme with the prior update, identify added activities or renamed work, and ask why a package moved later while the claim says it progressed normally. For that task, use a baseline vs current schedule comparison rather than relying on two exported PDFs.

It doesn’t help with everything. A programme doesn’t serve the payment claim, decide whether the notice wording is valid, or prove entitlement by itself. It also doesn’t decide whether a legal consequence follows from a late payment schedule. Those questions belong with the Act, the contract and legal advice.

What the High Court said: In Probuild Constructions (Aust) Pty Ltd v Shade Systems Pty Ltd [2018] HCA 4, a head contractor asked the NSW Supreme Court to quash an adjudicator’s determination over a liquidated damages deduction from a subcontractor’s payment claim. On 14 February 2018 the High Court held that the NSW Act doesn’t allow a determination to be quashed for a non-jurisdictional error of law on the face of the record. The same day, Maxcon Constructions Pty Ltd v Vadasz [2018] HCA 5 reached the same result under the South Australian Act.

What it means: In NSW and South Australia, the adjudication is the hearing that counts. Short of a jurisdictional error, a determination with a legal error in it can still stand, so the evidence has to be right when the application or response is lodged, not tidied up for a later court challenge. Review rights differ in other jurisdictions; the ACT Act, for example, allows review with the court’s leave for an error of law on the face of the record.

Review the Programme Before Relying on It

A payment claim that leans on programme progress should be tested before anyone treats the update as evidence. Start with file integrity, then move to the progress narrative.

1. Confirm the file type and source. Native P6, MS Project or Powerproject files carry more checkable information than a PDF.
2. Check the data date. The programme position should line up with the claim period.
3. Compare activities with the prior update. Renamed or renumbered activities need explanation.
4. Review remaining duration against percentage complete. Progress and remaining work should tell a coherent story.
5. Check logic and constraints. A forced finish date can hide slippage behind a clean bar chart.
6. Read the update narrative beside the file. The explanation should match the change record.

A ScheduleLens comparison report shows the kind of baseline-vs-current changes, critical-path movement and delay drivers a reviewer can extract from native schedule files before relying on a programme update.

ScheduleLens analyses uploaded programmes; it doesn’t draft payment claims, serve notices, track statutory deadlines, provide legal advice, or decide whether a claim is valid under any Security of Payment Act.

Common Mistakes in Payment-Claim Evidence

Weak payment evidence often looks orderly on the surface. The invoice is formatted, the Gantt chart is attached, and the percentage complete has been typed into a column. The problem appears when the records are compared.

Mistake	Why it creates risk	Better record habit
Claiming from a PDF Gantt only	The reviewer can’t test logic, calendars, float or changed relationships	Keep the native file with the claim pack
No clear data date	The claim period and programme status can’t be aligned	Record the update cut-off date plainly
Activity IDs change every month	Progress continuity disappears	Keep stable IDs, or explain replacements
Percentage complete conflicts with remaining duration	The file says progress was claimed but the work still drives successors	Reconcile physical progress with remaining work
Programme acceptance is treated as entitlement	Acceptance may have a narrower contractual effect	Check the contract wording and get advice
Site records are gathered later	Rebuilt records carry less evidential weight	File diaries, photos and inspections as the work happens

Table: Six payment-claim evidence mistakes, why each one weakens the claim or the response, and the habit that prevents it.

Programme acceptance deserves particular care, and the contract’s programme requirements set what acceptance means. An accepted update might be useful evidence that a reviewer had a progress position at a date. It may not mean the employer accepted every activity date, every claimed quantity, or the legal entitlement behind a payment claim. Treat acceptance as a defined contractual step, not a shortcut to entitlement.

The same discipline applies to payment schedules. If the respondent rejects part of a claim, the reasons should be tied to records: the native update, the inspection record, the site diary, the contract measure, or the correspondence. A thin statement that the work is “not complete” is weaker than a record-backed explanation of what was checked and what didn’t match.

How to Read a Payment Claim Against the Programme

A useful review starts with the claim schedule, not with the programme. List each claimed item, the amount or percentage claimed, the location, and the period covered. Then map each line item to the activity or group of activities that supposedly supports it. If a claimed item can’t be mapped to the programme at all, record that gap before judging the amount.

The next step is to compare the claimed position with the update file at the same cut-off date. The reviewer should ask four plain questions. Was the activity started? Was the activity finished? Did the remaining duration change in a way that matches the claimed progress? Did the successor logic show the work was ready for the next trade or stage? These checks don’t decide legal entitlement, but they stop the file from being treated as decoration.

Claim line (hypothetical)	Programme activity	Status at the data date	Record that confirms it	Review note
Level 3 slab, 100%	A-240 Pour L3 slab	Started, 10 working days remaining	Inspection record unsigned	Overstated: activity not finished
Façade zone B, 60%	F-110 Install façade zone B	55% complete, logic intact	Photos dated in the claim period	Five points apart: agree the measurement basis
Off-site joinery, 100%	J-300 Fabricate joinery	Not started	Delivery docket missing	Check the contract’s unfixed-materials provisions

Table: A hypothetical claim mapped line by line to the programme. Each review note points at a record, not an opinion.

For disputed items, write the reason in evidence language. Instead of saying only that the claim is overstated, state that the programme shows activity A-240 still had ten working days remaining at the data date, the inspection record for that zone was unsigned, and the site photos show the follow-on trade had not accessed the area. That kind of record can be read by a contract administrator, an adjudicator, or a later delay analyst without guessing what the reviewer meant.

The same discipline helps claimants. If the programme status understates genuine progress, fix the update narrative and supporting records before the claim goes out. Explain split activities, partial completions, out-of-sequence progress and work done under instruction. A payment claim supported by clean programme evidence is easier to review, and a rejected claim supported by clean reasons is easier to understand.

Records to Keep Before the Dispute Starts

The best payment-claim file is built during the month, not after the dispute starts. Each update period should leave a clean audit trail: what work was planned, what happened, what changed, and what records prove it.

Figure: Programme evidence is strongest when it sits beside site records created at the time.

For the person reviewing the programme, the practical standard is simple: could another reviewer open the file pack and understand why the claimed progress is supported or disputed? If the answer depends on someone’s memory, the records aren’t ready for a Security of Payment dispute.

A final legal boundary matters. Confirm deadlines, wording and service requirements with a construction lawyer or the official regulator for the relevant state or territory before serving or responding to a payment claim. The programme evidence can support the story; it can’t repair a missed statutory step.