Collections rarely fail in one dramatic moment. They fail through small delays: a demand note that was never sent, a cheque that nobody matched, a buyer who was promised a callback and did not get one. A weekly rhythm that everyone follows prevents most of these.
Begin with a payment schedule on every booking
Nothing is overdue if nothing was due. The first step is a dated schedule attached to each booking: the initial amount, each instalment and the milestone it relates to. When a booking is confirmed, the schedule should be created at once, not when someone finds time.
In Propto CRM, a rule can create the payment schedule when a booking is confirmed and message the legal and accounts teams. Even without automation, the principle is the same: a booking and its schedule are born together, so the finance team never starts from a blank page.
Make remaining balances visible to everyone who talks to buyers
The question “how much is left?” should have one answer. A remaining-payments view that shows total investment, paid amount, remaining amount and a due status lets accounts, sales and customer care speak with one voice.
Share this view with sales on purpose. A salesperson who knows a buyer’s instalment is critical will handle a call differently. Customers also notice when two teams quote two numbers, and it costs trust that is hard to rebuild.
Set a calendar for the week
A simple weekly pattern works well. Monday: review overdue and due-this-week items and decide who calls whom. Midweek: check cheques and transfers against bookings and update statuses. Friday: send reminders for next week’s dues and review what escalated.
Write the pattern down and put it in the team’s calendar. The point is not to be clever. It is to make collections a routine rather than a reaction.
Reminders should feel like service
Buyers pay more readily when they feel informed. Send a friendly reminder a few days before the due date with the amount, the date and how to pay. After the due date, a short follow-up the next day, a call after that, and a firmer message later if needed.
Rules can run this ladder: a message on the due date, a repeat at a set interval and a task for accounts if nothing happens. Preview the rule before enabling it and read the log afterwards, so you can see exactly what buyers received.
Know your escalation path and policy
Decide in advance what happens when a payment is late: who calls, when a manager joins, when a formal notice is considered. Write the late-payment penalty basis, rate, grace days and cap in the sales policy so that it is applied evenly.
Consistency protects you in disputes. If you waive a penalty, record who approved it and why. A policy applied to everyone is far easier to defend than an exception remembered by one person.
Run a shared weekly review with sales
Collections and sales are not opposing teams. Sales knows the buyer’s situation, accounts knows the balance. Fifteen minutes together on the critical list each week, with the booking record on screen, solves problems that emails never do.
Close the loop at the end. List who will do what by when and check the list next week. Over a quarter, you will see overdue amounts shrink because every item had an owner and a date.
A worked example: a Monday collections huddle
Imagine a developer with three projects and about two hundred active bookings. On Monday at ten, the accounts lead opens the remaining-payments view and filters by due status. Twelve bookings are flagged critical, thirty are due this week and the rest are on schedule. She assigns each critical booking to a named person, including the sales executive who knows the buyer.
By Wednesday the owners of the critical bookings report back in the booking record: one buyer is waiting for a bank disbursement, one has a cheque ready, one disputes a charge and needs legal. Each outcome is written where everyone can see it, and Friday’s review starts from facts. The point is not the numbers in this example, which are illustrative, but the pattern: one list, named owners, outcomes recorded.
Mistakes that make collections harder
The first mistake is keeping separate balances in sales and accounts. Buyers hear two figures and trust neither team. The second is reminding only after the due date, which feels like pressure rather than service. The third is waiving penalties casually without recording who approved them, which creates precedents you cannot defend later.
Also avoid treating collections as an accounts-only problem. Many delays come from missing documents, unsigned agreements or construction questions. When legal, site and sales share the booking record, you can see why a payment is late and fix the cause instead of repeating the reminder.
A short checklist for next Monday
Before your next collections huddle, check four things. Does every active booking have a dated payment schedule? Can anyone in sales open the remaining balance for a buyer in under a minute? Is there one named owner for every critical item? And is there a place where the outcome of each call gets written down? If any answer is no, fix that first. The rest of the routine works only when these four basics are in place, and each can be set up in a few days rather than a few months.
How often should collections be reviewed?
Weekly works well for most developers, with a short daily check on critical items.