Payment Claim Deadlines in Australia: A Security of Payment Tracker for Contractors.
The time limits for payment claims, payment schedules and adjudication in NSW, Victoria and Queensland from official sources, a tracker you can copy, and an automation where a person confirms every date.
In Australian construction, a payment claim is a clock. Serve it late, answer one late, or miss the window to take a dispute further, and the right you thought you had can be gone. The clocks are set by state law, they use business days, and they are different in New South Wales, Victoria and Queensland. A head contractor who works across borders is running three rule books at once.
Devvista is a software development company that designs workflow automation for contractors, including deadline tracking around payment claims. This page sets out the time limits we verified from official sources for NSW, Victoria and Queensland, a tracker table you can copy, and the system we would design to read contracts and claims, work out candidate dates and put each one in front of a person to confirm. Treat it as general information rather than legal advice. If a dispute is already live, take it to a construction lawyer. To discuss a tracker for your business, describe how claims reach you today.
Why Payment Claim Deadlines Are Strict
Security of payment laws exist so that a contractor can be paid progress claims quickly and argue about the detail afterwards. Their strength is also their risk: the process is strict and the periods are short. A respondent that does not serve a payment schedule in time can end up liable for the full claimed amount. A claimant that is late applying for adjudication can lose that route. Every state sets its own numbers, and in Victoria the numbers changed in 2026.
The tables below give only what we could confirm in a primary source or a state government page opened on 11 November 2026. Where we could not read something, we say so in the next section rather than fill the gap from memory.
Payment Claim and Schedule Time Limits: NSW, Victoria and Queensland
| Step | New South Wales | Victoria | Queensland |
|---|---|---|---|
| Earliest a claim can be served | On the reference date: the date in the contract, or if none, the last day of the month the work was done. One claim per reference date. | On and from the last day of each named month in which work was carried out, with special rules for work in December (s 14A). One claim per named month unless the contract provides otherwise (s 14D). | From the reference date, which is the earliest date a claim can be submitted. |
| Latest a claim can be served | Only work completed in the past 12 months can be claimed. | No later than the day before the latest of: the contract date, 6 months after practical completion, 6 months after the supply of all goods and services (s 14C). | Non-final claim: before the latest of the contract date or 6 months after completion. Final claim: the same, or 28 days after the end of the last defects liability period. |
| What the claim must contain | Written, state the amount, describe the work, goods or services. Record the date the respondent receives it. | Identify the work, state the claimed amount, state that it is made under the Act, plus any prescribed form or information (s 14). | Identify the work, state the amount, request payment. |
| Payment schedule from the respondent | Must reach the claimant within 10 business days after the claim is received (the Act may also allow an earlier contract period; confirm s 14(4) with your adviser). | Within the time the contract requires or 10 business days after the claim is served, whichever is earlier (s 15(4)). | Within 15 business days after receiving the claim, or earlier if the contract sets a shorter period. |
| Payment due | Per the contract, but not later than 15 business days (head contractor), 20 business days (subcontractor), or 10 business days for related exempt residential work. | Per the contract; if silent, 10 business days after the earliest day the claim could be served (s 12). A contract cannot set payment later than 20 business days after the claim. | Per the contract; if none, 10 business days. Contract caps: 25 business days for subcontracts, 15 for commercial building contracts; a longer term is void. |
Adjudication Windows After a Missing or Short Schedule
The adjudication windows are where a missed date is hardest to fix. We confirmed the New South Wales and Victorian windows in full. For Queensland the QBCC pages we opened do not state the adjudication time limits, so we do not give them.
| Situation | New South Wales (s 17, as set out by NSW Government) | Victoria (s 18 of the Act in force from 24 June 2026) |
|---|---|---|
| Schedule served, scheduled amount less than the claim | Apply within 10 business days after receiving the schedule | Lodge within 10 business days after receiving the schedule |
| Schedule served, scheduled amount not paid by the due date | Apply within 20 business days after the due date | Lodge within 10 business days after the due date |
| No schedule served and claimed amount not paid | Notice of intention within 20 business days of the due date; respondent has 5 business days to serve a schedule; apply within 10 business days after that | Notice of intention within 10 business days after the due date; respondent has 5 business days to serve a schedule; lodge within 5 business days after that period ends |
| After lodging | Not covered in the pages we opened | Serve a copy on the respondent within 3 business days of lodging (s 18(5)) |
Notice the difference. In the third row New South Wales gives 20 business days for the notice, Victoria gives 10. A tracker built from one state's rules and applied to another would be wrong in exactly the situation where being wrong costs the most. The sources are NSW applying for adjudication and the Victorian Act, version in force from 24 June 2026.
What Changed in Victoria in 2026
Victoria is the state where you most need a current source. The Victorian Parliament amended the Act through Act No. 43 of 2025, and the legislation.vic.gov.au version history shows a version effective 15 April 2026, replaced by version 015 effective 24 June 2026 (version history). We read the 24 June 2026 version. The margin notes in it attribute the new claim timing, the single monthly claim rule and the 6-month outer limit to No. 43 of 2025.
Three things stand out in the text for anyone building a deadline tool. First, the Act defines a business day to exclude Saturdays, Sundays, public holidays observed throughout Victoria and the period from 22 December to 10 January, so a count that runs across that period is longer in calendar days than it looks (s 4). Second, claims for work from 1 to 21 December can be served from 22 December, and for work from 22 to 31 December from 31 January (s 14A(2)). Third, a claim served before the earliest permitted day is not invalid but is taken to be served on the earliest day, and the time for the schedule does not start until then (s 14A(5)).
We could not confirm from a primary source that every provision of the 2026 reform is already in force. One search result said two provisions were delayed, and we did not read a government notice about it, so we make no statement either way. Check the commencement before you rely on a particular section.
Queensland: What We Read and What We Left Out
Queensland's regime is the Building Industry Fairness (Security of Payment) Act 2017. We read the Queensland Building and Construction Commission's plain-language pages on requesting and responding to payment (QBCC, request payment, QBCC, respond to payment request). They state the 15 business day schedule period, the contract caps and the claim time limits shown in the table above. They also say that failing to pay in full without a schedule, or failing to pay the scheduled amount by the due date, is an offence with a penalty of up to 100 penalty units, and that pay-when-paid provisions are void.
You will see online commentary that Queensland has paused a reform of project trust accounts. The QBCC pages we opened say nothing about it, and the other sources we saw were law-firm summaries, so we have left it out. We also did not read the Act itself, which is served as a script-driven page. Treat the Queensland column as the regulator's summary and confirm any detail in the Act.
Where Manual Tracking Loses Money
Missed deadlines usually trace to how paper moves through a business, not only to not knowing the law.
| Where it leaks | What goes wrong | Why it costs money |
|---|---|---|
| Claims arrive by email to the wrong inbox | The date you received the claim is not the date you noticed it | The schedule period started on receipt, not on noticing |
| The contract was signed months ago and nobody rereads it | The reference date, nominating authority or payment term in the contract is not the default | You count from the default while the contract says otherwise |
| One spreadsheet for every state | A New South Wales rule is applied to a Victorian job | The notice period is 20 business days in one state and 10 in the other |
| Business days counted on a calendar | Public holidays and, in Victoria, 22 December to 10 January are ignored | You think you have two weeks and you have less |
| Your own claims go out late or early | You serve before the reference date, or after the outer limit | The claim can be invalid or out of time, and you lose the adjudication route |
| Nobody records how and when a claim was served | You cannot prove service | A dispute turns on a date you cannot evidence |
Each of these is a record-keeping failure, not a legal puzzle. That is why a tracker helps. It does not make legal decisions. It makes sure the facts a decision needs are on one screen, on time.
A Claim and Schedule Tracker You Can Copy
Here is a tracker layout you can copy into a sheet today. Use one row per claim, whether you sent it or received it.
| Column | What goes in it | Why |
|---|---|---|
| Job and contract reference | Project, contract and the other party | So the right contract terms are checked |
| State and Act | NSW, Vic or Qld, and which Act applies | Decides every other number |
| Direction | Claim received (you are the respondent) or claim sent (you are the claimant) | Different clocks apply to each |
| Reference date or named month | From the contract, or the default | Controls the earliest service date |
| Date served and how | The day it was served and the method | Evidence of service |
| Date received and by whom | The day the respondent received it | Starts the schedule period |
| Schedule due (candidate) | Contract period or the state period, whichever the state rule applies | The date a person must confirm |
| Payment due (candidate) | Contract date or the state default | Drives adjudication windows |
| Adjudication notice and application windows (candidates) | Only if the schedule is missing or short | The costly dates |
| Confirmed by (name, date) | The person who checked the dates against the contract and the Act | Accountability |
| Evidence link | Link to the claim, the schedule and proof of service | The paper trail |
Notice that two columns say "candidate". A tool can propose a date. A person must confirm it. That split is the point of the whole design.
The Automation: Read, Propose Dates, Alert, a Person Confirms
A deadline tracker that reads emails and contracts is a good fit for automation, because the hard part is reading and filing, not calculating. We would design it in six stages.
| Stage | What the system does | Who decides |
|---|---|---|
| 1. Capture | Watches the inboxes you choose and the shared folder where signed contracts are stored. Picks out emails that look like payment claims, payment schedules or adjudication notices, and attaches the PDFs | Nobody: it is filing |
| 2. Read the contract | Claude reads the contract for the reference date or named-month clause, payment terms, any nominated adjudication authority, and the governing state. It writes down each answer with the clause it came from | A person confirms the clause reading, once per contract |
| 3. Read the claim | Extracts the claimant, respondent, amount, work described, any statement that the claim is made under the Act, and the date and method of service | A person confirms the date received |
| 4. Propose the dates | A rules table, written from the sources above, proposes the schedule date, the payment due date and, where relevant, the adjudication windows, using a holiday calendar for the state | A person confirms each date, and approves the rules table when it is first built |
| 5. Alert | Sends reminders at set points, for example when a schedule is due in five business days, and escalates if nobody has acknowledged | The system sends; a person acts |
| 6. Draft support | Prepares a draft payment schedule shell with the claim identified, the heading fields filled in and prompts for the scheduled amount and every reason | A person with commercial and legal authority completes and serves it |
For plumbing we would start with n8n or Make, which connect to email, folders, calendars and accounting systems quickly, and add custom code where a rule is yours alone. Every figure and date the system shows links back to the paragraph in the document it came from, so a reviewer checks the source, not the machine. This is a design description, and no client result sits behind it.
The rules table is the sensitive part. It must be written from the Act and the state guidance, dated, and reviewed by a person who is qualified to review it. When a state changes its Act, as Victoria did in 2026, the table changes, and so does the version on file. We would version it and show which version produced each date.
When Not to Automate
A deadline tracker is not for everyone. Rethink the plan if any of these is true, and we will say so on the call.
| Your situation | What we would suggest |
|---|---|
| You receive a handful of claims a year | A calendar entry and a checklist. A system costs more than the problem |
| A claim is already in dispute or an adjudication is live | Get advice from a construction lawyer straight away. Software will not rescue a missed date |
| You operate in a state or territory we have not covered here | We would research that state's Act first. We have not verified Western Australia, South Australia, Tasmania, the ACT or the Northern Territory for this page |
| You want the system to decide whether a claim is valid | We would not build that. Validity is a legal judgement |
| Your contracts are not stored in one place | Fix the filing first. A tracker built on missing contracts is guesswork |
If a lighter option fits, we will say so. For the broader picture of what else in a contractor's office can be automated, see our AI automation page, and for the same approach written for the US see AI automation for construction companies. The rules differ by country, so only the method carries across.
What a Tracker Build Involves, and What Changes the Quote
A first release is usually small: one state, one inbox, one contract folder. These are the stages we would propose.
- Pick the pilot. One state and one team, ideally the one that feels the pain most.
- Write the rules table with you. From the sources, with the dates and versions shown, then reviewed by your adviser.
- Load a month of old claims. The system proposes dates and you compare them with what actually happened.
- Run beside the current process. Alerts fire and a person confirms each one; nothing is relied on until it checks out.
- Extend. Add a second state or the claims you send, not only those you receive.
We do not publish prices. What moves a quote is the number of states, how many inboxes and contract folders are involved, how contracts are stored, whether you track claims you send as well as claims you receive, and what existing systems the alerts must reach. A short call comes first, and the budget range you have in mind helps us size the tracker. Our custom software development and business management software pages describe how we approach the surrounding systems.
Is This for Your Business? Fit and Next Step
This suits Australian head contractors and subcontractors who serve or receive claims every month, work in more than one state or hold a large contract library. It does not suit a business that wants to be told what the law means for a particular claim. That is a lawyer's job.
| A good fit | Probably not |
|---|---|
| Claims every month across several jobs or states | One or two claims a year |
| A person who will confirm every date | You want dates trusted without checking |
| Contracts and claims arrive digitally | Everything is on paper with no scanning |
| You want an audit trail of who confirmed what | You want a verdict on validity |
To start, use the contact form and tell us the states you work in, roughly how many claims you handle in a month and the budget range you have in mind. We come back after a short call with a proposal. A mobile app for site teams to photograph and send dockets and instructions is another piece we build, described on our mobile app development page. Return to the Australia home page.
Straight Answers.
Tell us how payment claims reach you
Describe the states you work in, how many claims you send and receive each month and where your contracts are stored. Book a call and we will say what to automate and what to leave to a person.
- 30-minute online call
- Honest feedback on fit
- No obligation
- Book a call30 minutes online. Tell us what you want to build.
- Get a straight answerHonest feedback on fit and scope.
- DecideYou choose the next step once the scope is clear.