Overdue payments rarely fix themselves. A defined ladder keeps responses calm and consistent.
Step one and two
A reminder message, then a call from the owner. Many cases end here when contact is quick and polite.
Step three
Escalate to a manager with the payment history. Collections-escalation rules can create a task automatically.
Step four
Apply your late-payment policy and, if needed, a formal notice through legal. Keep each step recorded.
Why escalation needs steps
Overdue payments are stressful for both developers and buyers. Without defined steps, some buyers receive aggressive calls while others are ignored for months, and decisions about penalties or cancellations vary by who is involved. A clear escalation path is fairer and more effective.
Steps also protect your team, because everyone knows what to do next and when.
Step one: friendly reminders
The first step is a friendly reminder around the due date, by message, with the amount and payment options. Many overdue payments are simply forgotten and resolve at this stage.
Check that the payment has not already been received before sending, to avoid unnecessary irritation.
Step two: a call
If payment has not arrived a few days after the due date, call the buyer. Ask about the reason, listen and agree a new date. Record the reason and the promise on the booking.
A call shows care and often reveals solvable problems, such as a delayed loan disbursement or confusion about the amount.
Step three: manager involvement
If the new date passes without payment, involve a manager. A conversation with someone more senior signals that the matter is important, while still offering help. Discuss options within your policy, such as a short extension.
Make sure the manager has full context before calling, so the buyer does not have to repeat themselves.
Step four: formal notice
For long-overdue amounts, a formal written notice may be necessary, explaining the amount, the penalty under the agreed policy and the consequences of continued non-payment. Have legal review templates for formal notices.
Formal notices should be consistent with the agreement and applicable law, and should be sent only after earlier steps have been tried.
Applying penalties consistently
If your agreement includes late-payment penalties, apply them according to the written policy: basis, rate, grace days and cap. Record any waiver with the approver and reason.
Consistency is essential. Waiving penalties for some buyers and not others invites disputes and damages trust.
Using automation wisely
Rules can send reminders, create tasks for each escalation step and alert managers when payments stay overdue beyond set periods. This keeps the process moving without relying on memory.
Keep human judgement in the loop. Automated messages should never replace a call when a buyer is facing genuine hardship.
Reporting overdue amounts
Report overdue amounts by age band, such as within thirty days, thirty to sixty days and beyond, and by project. Older and larger items need more senior attention.
Review the report weekly and make sure each overdue item has an owner and a next step.
A worked example
A buyer’s instalment is two weeks overdue. The executive’s call reveals a job change and a delayed salary. The manager approves a short extension within policy, recorded on the booking. The buyer pays within the agreed time, and no penalty is applied because the extension was formally approved.
Another buyer ignores repeated contact for two months; legal sends a formal notice using an approved template, and the buyer responds with a payment plan.
Common mistakes
Common mistakes include escalating too quickly without understanding the reason, inconsistent penalties, escalation without context and formal notices sent without legal review.
Another mistake is having no owner for overdue items, so they drift for months.
Questions teams often ask
When should cancellation be considered? Only according to the agreement and after the escalation steps, with legal advice.
Can extensions be granted? Within a written policy and with recorded approval, yes.
In short
Use clear escalation steps: reminder, call, manager, formal notice. Record reasons and promises, apply penalties consistently with recorded waivers, automate the routine but keep people in charge of difficult cases, and review overdue amounts by age weekly.
An escalation checklist
Day zero: friendly reminder with amount and payment options, sent after checking receipts. A few days later: a call, with the reason and new date recorded.
After the new date passes: manager involvement with full context and options within policy. Long overdue: a formal notice from an approved template, reviewed by legal.
Throughout: penalties applied by written policy, waivers recorded with approver and reason, an owner and next step for every overdue item, and a weekly review by age band. Printing this sequence and sharing it with accounts and sales keeps everyone working the same way.
In practice
Begin by agreeing the four steps and the people responsible for each, then apply them to every overdue booking this month. Review the results after four weeks, adjust timings where needed and keep the sequence consistent so buyers experience the same fair treatment.
Fairness and consistency are what buyers remember.
Is there an overdue view?
Yes, the dashboard shows overdue instalments and legal files can be filtered by overdue.