Note
Read Billing Stages Before You Sign
Most billing friction on a live project starts earlier than anyone notices. It starts at the table where the contract was signed.
The stage description that lets the main contractor query your invoice, the acceptance condition that gives them discretion over when the clock starts, the retention clause with no defined release date: all of these were agreed in writing before your first crew arrived on site. Reading the contract for these four clauses before signing does not guarantee smooth billing, but it tells you exactly where the problems will come from.
Why the stage description matters more than the stage value
A stage’s description is the boundary of your invoice. When you submit a payment application, the main contractor’s accounts team matches your invoice description against the contract wording. If the wording is vague, they have to interpret it before releasing payment. Interpretation takes time, and when two people read the same words differently, you get a query sitting in an email thread for a week.
Compare these two descriptions covering the same scope of work:
Vague: “Completion of wall works, Zone A.”
Specific: “Installation of all lightweight partition walls in Zone A, sections A1 to A8, per drawing SK-21, to a finished and painted condition, accepted by the main contractor’s site engineer.”
The vague version invites questions: which walls exactly? What does “completion” mean? Who decides when Zone A is done? The specific version makes those questions unnecessary. The accounts team can match your invoice against the contract without a follow-up call.
You can usually ask for tighter wording before signing. The main contractor’s site team has no commercial reason to refuse; their concern is scope, not wording. The accounts team benefits from specificity too. Asking at the contract stage costs nothing. Asking after the first query has been sent is a different conversation entirely.
What makes an acceptance condition enforceable?
The acceptance condition answers three questions: who has the authority to sign off the stage, by what method, and within what timeframe?
If the contract says “when work is accepted to the satisfaction of the main contractor” and stops there, the main contractor can delay acceptance indefinitely without technically breaching any term. No named role, no method, no clock.
Look for three things in the clause:
Named role rather than named person. “The main contractor’s site engineer” rather than an individual whose name changes when staff move.
Method of acceptance. A signed inspection form or written notice rather than a verbal confirmation that leaves no paper trail.
Timeframe. “Within five working days of the contractor’s written notification” gives you a date to push against. Without a timeframe, there is nothing to push against and no breach possible if they take a month.
How do credit terms compound the billing gap?
“Payment within 30 days of invoice” is common in subcontract work. The better version for cash flow is “payment within 30 days of acceptance.” The difference is that the main contractor controls the acceptance step.
If they take 14 days to inspect and issue an acceptance form, and the 30-day clock runs from the invoice date, your invoice has been sitting for 14 days before the payment period even starts. Total wait: 44 days, not 30.
Some contracts specify payment within 30 days of the main contractor’s own “payment certificate.” If the contract does not define when that certificate must be issued, there is effectively no payment clock. The 30 days only runs from a date they control.
Worked example: same stage value, different cash flow
Two contractors each win a fit-out subcontract with identical stage values.
Contractor A: “Payment within 30 days of invoice; acceptance at main contractor’s discretion.” On submission day, the accounts team returns a query requesting an inspection form not specified in the contract. The contractor spends 10 days locating and getting it signed. The 30-day clock restarts on resubmission. Payment arrives 50 days after the original invoice.
Contractor B: “Payment within 30 days of acceptance; acceptance by written inspection report within 7 working days of contractor’s written notification.” The contractor notifies on completion. The form arrives on day 7. The 30-day clock runs from there. Payment arrives 37 days from the completion notification.
Same scope. Same stage value. Contractor B’s contract produces a better outcome because the acceptance path is written down.
What does a retention clause worth checking actually look like?
Most subcontracts hold back a percentage of each payment as a performance guarantee. The rate and the release conditions vary. Three things are worth checking before you sign:
The release trigger. Is retention released automatically when the defects period expires, or does it require a written release notice from the main contractor? A release that requires their active step will stay unreleased until someone asks for it in writing. Many contractors have retention sitting overdue for months because nobody filed a formal release request.
The release timeframe. “Upon expiry of the defects liability period” is a trigger without a date. “Within 30 days of the end of the 12-month defects period” is a date you can put in your calendar and chase two weeks before it falls due. That distinction matters more than it looks.
Whether a retention cap is written down. If the contract holds a percentage on every stage across a long project, the cumulative withheld amount can grow beyond any reasonable performance guarantee. A retention cap stops the total at a fixed ceiling regardless of how many stages are paid.
FAQ
Can I ask for tighter stage descriptions on a standard-form subcontract?
More often than most contractors expect. The main contractor’s project team has no commercial reason to resist tighter wording; their concern is scope, which a specific description captures better. The accounts team benefits from clarity too. Bringing a marked-up stage schedule to the contract meeting is one of the most practical steps before signing, and it rarely draws objection.
What if the contract has no defined release trigger for retention?
Send a written request for release once the defects period ends, citing the contract clause and the end date by name. No defined trigger does not mean no right to release; it means you need to initiate it. Date your request, keep a copy, and follow up in writing if there is no response within a reasonable period. A dated request creates a paper trail that a verbal reminder does not.
Does the acceptance step belong on the project timeline?
Yes. When the main contractor’s inspection needs to happen before the billing pin can move, that step should appear on the schedule between the install bar and the billing date. If it is invisible, the billing date looks achievable right up to the day you discover the inspector has not been to site. Mapping the acceptance step explicitly makes delays visible at least a week early instead of the day they are already expensive.
If you want to read through a live contract together and mark the clauses that will shape every invoice you send, a 45-minute call is the right format. You leave with the specific questions to ask before the signing date, and the numbers that belong on your billing calendar.