A penalty you apply inconsistently is a gift to disputes. Write it clearly and apply it evenly.
Define the trigger and rate
When does a payment become late, and what is charged? Include a grace period if you offer one.
Put it in the system
Propto stores the late-payment penalty and grace settings in sales policy so calculations match your rule.
Document exceptions
If you waive a penalty, record who approved and why. Exceptions without records become precedents.
Why a written penalty policy helps
Late payments affect a developer’s cash flow and construction schedule. A penalty can encourage timely payment, but only if it is clear, fair and applied consistently. Unwritten or inconsistent penalties lead to arguments, favouritism and damaged trust.
A written policy, agreed in the buyer’s documents and stored in the system, makes the rules visible and the calculation automatic.
Defining the trigger
State when a payment becomes late: on the due date, or after a set number of grace days. Grace days give buyers a little flexibility for bank delays and weekends, and reduce disputes over payments that were only a day or two late.
Make sure the due dates in the payment schedule match the agreement exactly, because the trigger depends on them.
Choosing the basis and rate
Decide how the penalty is calculated: a percentage of the overdue amount for each period late, or a fixed amount. State the rate clearly and whether it is simple or compounding. Simple calculations are easier for buyers to understand and verify.
Align the basis and rate with the agreement and applicable law. Have legal counsel review the policy before adopting it.
Setting a cap
A cap limits the total penalty, for example as a percentage of the instalment. Caps prevent penalties from growing to unreasonable levels and make the policy feel fair to buyers.
Show the cap in the policy and in calculations, so buyers can see the maximum they could be charged.
Putting the policy in the system
Store the penalty basis, rate, grace days and cap in the system settings rather than in individual spreadsheets. The system can then calculate penalties consistently for every buyer, and changes apply everywhere at once.
Restrict who can change the settings and keep a history of changes with dates.
Communicating before it applies
Explain the penalty policy before booking and include it in the agreement. Mention it in reminders for overdue payments, so the buyer understands the consequences before the penalty is applied.
Clear communication prevents surprise, which is the most common cause of disputes about penalties.
Documenting exceptions
There will be cases where a penalty should be waived, such as a delay caused by the developer’s own process or a documented emergency. Record each waiver with the approver and reason.
Track waivers over time. Frequent waivers may indicate that the policy or the payment schedule needs adjustment.
Reviewing the policy
Review the policy annually, or when laws or agreements change. Look at how often penalties are applied, how often they are waived and whether they improved on-time payment.
Use the review to refine grace days, rates or caps based on evidence rather than impressions.
A worked example
A policy sets seven grace days, a monthly percentage rate on the overdue amount and a cap as a share of the instalment. A buyer pays twelve days after the due date. The system calculates the penalty from day eight to day twelve, well below the cap, and shows the calculation on the booking.
The buyer asks about the charge, and the executive explains it using the policy from the agreement. The buyer pays without dispute.
Common mistakes
Common mistakes include penalties not mentioned in the agreement, different calculations by different staff, no grace period and waivers granted informally without records. Each invites disputes.
Another mistake is using penalties as the main collection tool instead of good reminders.
Questions teams often ask
Should penalties be automatic? Calculation can be automatic, but communicate before applying and allow recorded waivers.
Can penalties differ by project? They can, if each project’s agreement says so; keep the structure consistent.
A policy checklist
Trigger and grace days defined. Basis, rate and simple or compounding calculation stated. Cap set and visible. Policy reviewed by counsel and included in the agreement.
Settings stored in the system with restricted access and history. Policy mentioned in reminders before penalties apply. Waivers recorded with approver and reason. Annual review based on data.
In practice
Start by comparing your current agreements with how penalties are actually applied today. Close any gaps, write the policy clearly, store it in the system and tell your accounts and sales teams exactly how to explain it to buyers.
Then track on-time payments for a few months to see whether the policy, combined with good reminders, is working.
In short
Define the trigger and grace days, choose a simple basis and rate, set a cap, put the policy in the system, communicate it before it applies, document exceptions and review it every year.
A final thought
A fair penalty policy is one that buyers understand before they need it. Clarity prevents most disputes.
Where is the policy set?
In Settings under sales policy, with brokerage rules and required legal documents.