What a disputed subcontractor payment claim actually costs a GC

A subcontractor’s progress claim arrives by text, email, or a PDF attached to nothing. Someone on your side thinks the amount looks high for what’s actually been done, so it sits. A few days later there’s a phone call — not documented anywhere — where a number gets talked down, or a scope gets clarified, or nothing gets resolved and the subcontractor just resubmits the same figure and waits again. None of that is a dramatic failure. It’s the ordinary way a payment claim moves through a GC’s week — and it’s also, almost entirely, unrecoverable time and unrecoverable evidence.

The dispute isn’t the expensive part — the ambiguity is

Most payment disagreements between a GC and a subcontractor aren’t really disputes about money; they’re disagreements about what was actually agreed, re-litigated from memory because nobody wrote it down at the time. A claim rejected over the phone, with a reason nobody can point back to later, doesn’t close the disagreement — it just defers it to the next claim, where the same ambiguity shows up again, usually with more frustration attached. The cost isn’t the negotiation itself. It’s that every one of these exchanges starts from zero, because there’s no record of what was decided last time or why.

That matters more under Australian security-of-payment law than it might feel like day to day: a subcontractor’s right to be paid for completed work doesn’t lapse because a project got paused, a relationship got tense, or a claim got rejected without a clear reason. A verbal rejection with no documented basis is a weak position to be in if a claim ever escalates past an internal disagreement — not because the rejection was wrong, but because there’s nothing to show it was reasoned.

What actually changes when a claim comes with a reason attached

A rejection that states the reason — wrong period, quantity doesn’t match what was on site, missing a variation reference — does two things a phone call doesn’t. It gives the subcontractor something specific to fix before resubmitting, instead of a guess. And it leaves a timestamped record of exactly what was communicated and when, which is the difference between "we had a conversation about it" and something you can actually point to if the same disagreement resurfaces two claims later.

The pattern repeats on the approval side too. A subcontractor pricing their own itemised claim — quantities and line items tied to a plain description of the work, not a lump sum guessed at by whoever’s reviewing it — is a materially different starting point for a decision than a round number in a text message. It’s not that GCs are bad at this by hand. It’s that a phone call and a text thread were never designed to hold up as a record, and everyone reviewing a claim eventually forgets they need to.

The other cost: re-entering the same numbers into your books

Even a cleanly approved claim usually isn’t the end of the admin. Someone still has to open the accounting system and enter the same amount as a bill — by hand, from the same numbers already sitting in the approval. It’s not a disputed claim, so it doesn’t feel like a cost, but it’s the same category of problem: a number that exists in one place has to be manually carried into another, and every manual carry is a place a typo or a missed claim can happen.

How Novato handles this

Every subcontractor gets a standing Payment Request link scoped to their assignment — the same link every time, not a fresh token to chase down per claim — and a plain description of the work gets split into line items automatically, with quantities only ever pulled from what was actually stated, never an invented total. Approving or rejecting happens against that record directly: a rejection requires a reason, which is emailed straight to the subcontractor so they know exactly what to fix before resubmitting, and every decision keeps a timestamp either way. An approved claim generates its tax invoice automatically, and if you’ve connected Xero, the same approved claim syncs across as a draft bill — so the number that was reviewed is the number that ends up in your books, without anyone re-typing it in between.