Home › Court cases

Court cases · Security of Payment · NSW

NSW court cases on payment claims and payment schedules

Each of these cases turned on one step: a contract clause the Act overrode, a payment claim served the wrong way, or a payment schedule or suspension that didn’t follow the Act. Each page explains what happened, what the court decided, and how to avoid the same mistake.

The contract

  1. A-Civil v Meso Solutions (2023) — A subcontract said the head contractor need not pay until the subcontractor sent its paperwork. The court held the Act made the payment due 20 business days after the claim anyway, and the $366,813.76 adjudication stood.

Serving the claim

  1. Roberts Co v Sharvain Facades (2025) — A subcontractor emailed its payment claim at 7:18pm on a Friday. The Court of Appeal held it was served that Friday, not the Monday, so the builder’s payment schedule was late and it was liable for the whole $3,207,999.03 claim.
  2. Rewais v BPB Earthmoving (2025) — Owners had used an email address to pay and dispute a contractor’s invoices. The Court of Appeal held a payment claim sent to that address was served when it arrived, even though nobody read it, and the $277,007.16 adjudication stood.
  3. Reform Projects v Burge St (2026) — A builder had emailed its payment claims to the owner’s representative for years, and they were paid. The court held the address had been specified for service, so the final $260,737.82 claim sent there was served, and the owner, which served no payment schedule, had to pay it.
  4. Kumar v Frankies Cranes (2025) — A crane company emailed its payment claim to a man who had only handed over his business card. The court held the claim was never served, so the $142,120 adjudication was void.
  5. MGW Engineering v CMOC Mining (2021) — A contractor left its payment claims at a mine’s gatehouse at 5.15pm. The court held they were served the next day, so the mine’s payment schedules were in time and it did not owe the full $6.16 million.

The Act

  1. Forte Sydney v Lin Betty (2018) — A head contractor gave its payment schedule late, then served nothing in the 5 business days after the subcontractor’s notice under s 17(2). The court held the late schedule did not count, and the subcontractor’s $314,463.49 adjudication stood.
  2. Joye Group v Cemco (2021) — A builder emailed that it would not pay until all the works were finished. The Court of Appeal held that gave no reason for not paying, so it was not a payment schedule, and gave the subcontractor judgment for the full claim.
  3. Witron v Turnkey (2023) — A builder’s reply to an $804,154.63 claim gave a reason for the base work but none for $304,230 of variations. The Court of Appeal held the reply was not a payment schedule.
  4. Manariti Plumbing v Universal Property (2025) — A builder served no payment schedule on a plumber’s $221,901 claim. The Court of Appeal gave the plumber judgment for the full amount.
  5. Duffy Kennedy v Galileo Miranda (2020) — A contractor gave notice to suspend work on the day a late payment reached it, then kept work suspended after its right to suspend had ended. The Court of Appeal held the suspension was wrongful, and upheld the principal’s decision to take the remaining work out of the contractor’s hands.

Stop it before it gets this far

Every one of these cases turned on one step done wrong. eSiteOffice is built to stop those mistakes. It starts with the contract, carries through to the claim and its service, and only then turns to the Security of Payment Act.

1 · Contract. Drafted, reviewed and signed in the app, with the special conditions you choose.

2 · Claim. Drafted the way the contract requires, with the proof the stage needs.

3 · Service. Checked against the contract and the Act before anything is sent.

4 · The Act. Only if they still don’t pay: every date counted, every notice drafted.

Opens December.

These pages explain court decisions. They aren’t legal advice about your contract.