There are two ways to ask a customer for an instalment.
The first: the due date passes, nobody notices for a week, and then somebody rings to say the payment is late. The customer, who had forgotten, now feels accused. The call is about blame, and the money arrives slowly, if at all.
The second: three days before the date, a short message says the instalment is due on the 5th, for this much, for this unit. The customer pays, or asks for a week. Either way the company knew first.
Same money. Entirely different company.
A reminder is not a demand letter. It should be short enough to read on a phone while standing up:
No threat, no total of everything the customer has ever owed, no three paragraphs of policy. The purpose is to help somebody pay on time, not to prove they were going to be late.
A statement is the customer’s copy of the truth. Every payment, every receipt number, every amount still due, with dates.
Most companies prepare one when a customer asks. That takes a day, during which the customer assumes the worst, and a figure is typed by hand that may or may not match the books.
A statement that is always current removes that whole conversation. The customer opens it from their own phone whenever they want to, and because it is the same record the company works on, there is nothing to reconcile.
| When somebody prepares it | When the system keeps it | |
|---|---|---|
| Who asks | The customer, by phone | Nobody — it is always there |
| How long it takes | A day, sometimes two | It is open before the call ends |
| Where the figures come from | A register and somebody’s memory | The same record accounts work on |
| What a disagreement becomes | A meeting | A line in the statement, with a date |
| What the company learns | That a customer is unhappy | That the customer looked |
The strongest trust-builder is the smallest document: an acknowledgement, on the customer’s own phone, within a minute of paying.
It says how much was received, by what method, against which unit, with a number in the company’s own series. It asks one question — “was this payment made by you?” — and the customer answers yes or disputes it.
Three things follow from that. The customer has proof the moment they hand money over. The company learns about a mistake in a minute rather than a year. And when a cheque is involved, the acknowledgement can say plainly that a money receipt will follow once the cheque clears — which is honest and stops a second argument before it starts.
Documents are never edited. If an acknowledgement is wrong, it is cancelled with a reason and keeps its number, and a correct one is issued. The number series has no gaps, so a missing number means a missing document, not a quiet deletion.
Customers never see this rule. They feel it, in the fact that the company’s papers always agree with each other.
In Sofia Estate CRM, reminders go out before the due date, the acknowledgement reaches the customer’s own phone for confirmation, and the statement is current at all times — all on the same record as the sale, the schedule and the accounts check. Letters for overdue instalments, dishonoured cheques and full clearance are ready to print on your company’s letterhead. Sofia can send the messages by SMS or email.
Far enough for the customer to act — most companies settle on three to seven days. It is your setting, not ours.
No. The acknowledgement and the statement open from a link on their own phone.
No. The documents carry your company’s name and your company’s number series.
They say so on the acknowledgement itself. It is flagged, accounts look, and nothing is edited behind the scenes.
Yes. Book a live demo and bring one customer’s file with you.