Demand Letters and Collections for Property Developers

After the booking, a developer’s relationship with a buyer becomes a series of payments stretched over the build. Each instalment needs a correct letter, a receipt and an updated balance, for every unit in every tower. On spreadsheets and templates, errors creep in: a demand for the wrong stage, a missed receipt, interest worked out by hand.

Who wrote this guide

This guide comes from the EZ Solutions team, which builds ProjectBook, builder software for real estate developers. It describes good practice in general terms; the agreement with each buyer and the applicable RERA rules are the reference for any project.

What is a demand letter?

A demand letter asks a buyer to pay the next instalment of the payment plan agreed at booking. In a construction-linked plan, instalments fall due as the building reaches set stages, so each completed stage raises a demand to every buyer in that building. The glossary entry gives the short definition.

The actual stages and amounts come from each project’s approved plan.

1. Lock the payment plan at booking

Every demand depends on the plan agreed with the buyer. Lock it at booking, with the agreement value and any changes approved, so later demands follow the plan exactly. A changed price or plan should go through approval, not a quiet edit in a spreadsheet.

2. Raise demands from an approved construction update

The safest trigger for a demand is a construction status update that the site and management have approved. One approval then raises demands for every booked unit in that building, with the right stage and amount. It avoids two common errors: a demand raised before the stage is complete, and a unit missed because its row was skipped.

3. Record every receipt against the ledger

Buyers pay by cheque, transfer or through their home loan bank, sometimes in parts. Each receipt should go against the buyer’s ledger the day it arrives, so the outstanding amount is always right. A clear ledger is also what the buyer’s bank asks for at each loan disbursement.

4. Follow up outstanding amounts on a schedule

Collections slip when follow-up depends on someone remembering. A fixed routine works better:

1. A reminder a few days before the due date.
2. A follow-up on the due date for anything unpaid.
3. A call from the accounts or CRM team a week later.
4. Interest as per the agreement for amounts that stay overdue.

Every message sent, by WhatsApp, SMS or email, should be logged against the buyer, so the team knows what was said before calling.

5. Carry the ledger to possession

At handover, the buyer’s ledger should show every demand, receipt, interest charge and refund. With agreements, registration and documents in the same record, possession becomes a check, not a search through files.

Common mistakes with payment demands

• Demands raised from a template without checking the unit’s own plan.
• Receipts recorded late, so a buyer who paid gets a reminder.
• Interest worked out by hand, differently each time.
• No record of messages sent, so buyers get mixed answers.

How ProjectBook handles demands and collections

ProjectBook runs demands, receipts and the ledger from one source per buyer:

• RERA payment plans: each booking carries its approved schedule.
• Demands from construction updates: approved updates trigger demand letters for the affected units.
• Demands, receipts, outstanding, ledger, interest and refunds from the same record.
• Legal and possession: agreements from the builder’s own draft, registration, documents and handover.
• A Message Center logging every WhatsApp, SMS and email sent to a buyer.
• Tally mapping, with export as Tally XML or Excel for accounts.

Before any of this, the right buyer has to book the right unit; the real estate leads guide covers that stage.

Explore ProjectBook