In this guide 6 sections
Tie every payment demand to a milestone. Require a site engineer’s sign-off and a certificate or photo set on file before the milestone turns verified, which is the only event that drafts the demand automatically. Buyers then have little to argue about.
Why billing and site progress drift apart
The site team measures progress in slabs poured and walls plastered. Finance thinks in demand letters and due dates, and no single person owns the space where those two views fail to meet. A milestone is reached on Tuesday. The demand leaves three weeks later.
The opposite also happens: finance raises a demand from the payment schedule, but the slab is not cast, so the buyer visits and sees bare shuttering. Payment stops at once. The quarrel is now about trust.
Both failures share one cause. The schedule in the agreement and the progress on the ground live in two files kept by two teams, and nothing forces a comparison before the letter goes out.
Define milestones in observable terms
Never write “structure complete”. Use checks a stranger could verify, so a plinth milestone needs footing concrete cured, plinth beam cast, backfilling done and the structural engineer’s letter filed.
Write each milestone once, with its evidence list, and attach it to the payment schedule of every unit in that block, so one edit reaches all of them. Changes go through a manager.
Buyers’ lawyers look hardest for a quietly reworded milestone, since a softer test lets the builder bill sooner than the work allows.
- Milestone name and block or tower
- Observable completion checks
- Evidence: photos, test reports, engineer’s letter
- Approver by role
- Percentage of the agreement value due
Make verification a step with an owner
The site engineer marks the milestone ready and uploads evidence, the project manager approves it, and a quality or structural check follows where the agreement requires one. Each step records who acted and when.
Final approval turns it verified. That status is the trigger. Until then finance sees the milestone as upcoming and not billable, so nobody has to chase a verbal message from the site engineer, and nobody bills on hope.
Generate demands from verified milestones
When a milestone is verified, the system lists every unit whose schedule includes it and computes the amount from the agreement for each buyer.
Finance checks each drafted letter, comparing the amount against the agreement and the unit’s carried-over balance, before anything is sent to a buyer. Keep the letter factual.
State the milestone, the date verified, the amount, the due date and the bank details, and attach the certificate or a photo set where the agreement allows it. Buyers who see proof pay faster. They also call the office less often.
- Unit and buyer list per milestone
- Amount from the agreement, not retyped
- Carried-over balance and interest rules
- Letter template with proof attached
- Sent date and delivery status
Track the lag and the disputes
Measure two gaps every month. The first is days between milestone completion and demand sent, and the second is days between demand sent and payment received in the bank account. A long first gap is your problem, whereas a long second gap needs a collector’s follow-up call to the buyer within the week.
Log each dispute by milestone. If three buyers question the same slab, the evidence list for that milestone was too thin, so fix the checklist and not just the letters.
Milestone billing tracker
Rows run milestone by milestone. Columns cover milestone name, evidence required, site engineer, approver, completion date, verification date, demand sent date, units billed, amount due, amount received and dispute notes. A footer totals the average days from completion to demand sent, plus the number of milestones still waiting for verification this month.
Open a blank worksheet to printQuestions owners ask
Who should approve a milestone?
The project manager approves at minimum, plus any independent check the agreement names, such as a structural engineer or a quality auditor from the lender’s side. Finance should not approve site progress.
What if a milestone is only partly done?
Do not bill it. Split large milestones into smaller ones in the plan, so progress can be recognised in honest steps and the payment schedule stays defensible.
Can photos serve as evidence?
Photos often serve well. A photo works as evidence if it carries a date, a location tag and a drawing reference, so a reviewer can match it to the work. Attach any certificate that the agreement or the local authority requires, because a photo cannot replace a statutory sign-off or an engineer’s stamped letter.
How do we handle buyers who pay late?
Keep reminders separate from milestone logic. The system records the due date, sends scheduled reminders and flags overdue demands to a named collector, who logs each call and promised payment date against the unit.