Infrasis

Progress claims and payment schedules on commercial builds

A progress claim says how much of the job is done and what that is worth. Most claim disputes aren't really about money. They're about two people looking at different pictures of the same building, and arguing over percentages neither can prove.

What a progress claim is

On a commercial job, trades and the head contractor are paid as the work goes, usually monthly. Each claim sets out the value of work done to date under the contract, less what has already been paid. Under the security of payment Acts, a claim that identifies the work, states the amount and (in most states) says it is made under the Act starts a statutory clock for the answer.

Claims are cumulative. A subcontractor claiming 60% of the framing on Level 4 this month is claiming the whole 60%, and the previous month's accepted amount comes off. That makes claims self-correcting, but only if everyone agrees what was accepted last time.

What goes into a claim

  • Contract work. The scope broken into lines, each with a value and a percentage complete. The finer the lines (by level, zone and trade), the less there is to argue about.
  • Preliminaries. Site establishment, supervision, cranes and hoists, usually claimed as a lump sum or spread over the programme.
  • Provisional sums. Allowances for work not yet defined, such as signage or a fit-out allowance, claimed as they are spent and reconciled against the allowance.
  • Approved variations. Changes the other party has agreed to, each with its own value. Unapproved variations can still be claimed under the Acts, but expect them to be disputed.
  • Retention. A percentage held back from each payment, up to a cap, as security for completing the work and fixing defects.
  • GST on the net amount, so the claim can work as a tax invoice.

Answering a claim with a payment schedule

If the respondent won't pay the claim in full, it gives a payment schedule: the amount it will pay, and why it is paying less. The reasons matter. An adjudicator will usually only consider reasons that were in the schedule, so “work not complete” is weak where “Level 4 Zone B framing is 45% complete on site, not 60%, and two defects from the 12 May inspection are open” is strong.

The schedule must arrive inside the state's deadline, typically 10 or 15 business days. Miss it and the full claimed amount can become payable. Our guide to security of payment deadlines sets them out by state.

Retention and its release

Retention accumulates claim by claim until it reaches the cap, often 5% of the contract sum. It is usually released in two parts: half at practical completion, and the rest when the defects liability period ends. Several states now regulate how retention is held, including trust or deposit rules for larger head contractors in NSW, Queensland and WA.

The common failures are simple ones: retention that nobody tracks against each contract, release dates that pass unnoticed, and totals that don't reconcile with what each claim actually held.

Claiming up the chain

The head contractor's own claim to the principal is built from the same work its subcontractors are claiming, usually with margin, preliminaries and its own variations on top. Doing the two separately means re-keying the job twice and hoping the numbers agree.

In NSW and Queensland, a head contractor's claim to the principal must come with a supporting statement: a declaration about whether its subcontractors have been paid what is due. A false statement is an offence. To make it honestly, you need an up-to-date list of every subcontract claim that has fallen due, and whether it has been paid.

How Infrasis handles it

  1. Contracts built on the job model

    Each subcontract and the head contract is made of lines: work in a location, preliminaries, lump sums and provisional sums. Approved variations become lines of their own.

  2. Claims start from site progress

    A subcontractor's claim is drafted from what its crews reported on site, so the claimed percentages and the progress your team can see are the same numbers.

  3. Schedules with reasons attached

    The draft payment schedule compares each line with reported progress, inspections and open defects, so reasons for paying less are specific. A person always issues it.

  4. Retention, payments and deadlines tracked

    Retention is held to the cap and released at practical completion, at the end of defects liability, or by amount. Deadlines are counted for the contract's state.

  5. Claim to the principal with the statement

    Your head contract claim draws on the same model. In NSW and Queensland, Infrasis prepares the supporting statement from your payment records and won't declare subcontractors paid while one is overdue.

Questions

Can subcontractors see each other's claims?

No. A subcontractor sees its own contracts, claims and payments. The head contractor sees every subcontract on the job.

Does Infrasis issue payment schedules automatically?

No. It drafts the schedule from site progress, inspections and defects, but a person on the head contractor's team checks it and issues it. Anything touching money waits for a person.

How are variations handled?

A variation is proposed against a contract with a description and a value, then approved or rejected. Once approved, it becomes a line on the contract and is claimed like any other.

Can a claim come in from outside Infrasis?

Yes. If a subcontractor emails a claim, the head contractor records it with the time it arrived, and the deadlines run from then.

Which states does it support?

New South Wales, Victoria, Queensland, Western Australia, South Australia, Tasmania and the ACT. The Northern Territory isn't supported yet.

This page is general information, not legal advice. Contracts and state rules vary, especially for residential work and final claims. See also: the cases that shaped security of payment.

Sources

Try it on your next job.

Infrasis is in early access. Set up a project in a few minutes, then invite your trades when you're ready.