A customer transfers three lakh on a Tuesday, from his own bank account, with no reference in the description.
Nobody is expecting it that day. The CR executive who handles his file is on leave. The money sits in the company’s account, correct and unidentified.
On Thursday an overdue reminder goes to that customer.
He does not reply to the message. He calls the sales manager who sold him the flat, two years ago, and he is not polite about it.
The sales manager has no access to collections, so he calls the accounts man, who asks for the transaction reference. The customer does not have it to hand; he paid from his phone. Three people spend a morning on a payment that was never in doubt.
The customer now believes the company does not know what it has received. And this time he is right.
A full statement — everything paid, everything due, with dates.
It takes three days, because it does not exist anywhere. Somebody opens the register, copies the rows into Excel, cross-checks the bank, finds two entries that do not match, asks a colleague, and sends a PDF on Friday afternoon.
The customer reads it carefully, because he is now the kind of customer who reads things carefully. He finds one instalment dated wrongly. He is not being difficult — it is wrong.
| What happened | What it cost |
|---|---|
| A payment with no reference | A morning of three people’s time |
| A reminder sent to someone who had paid | The customer’s trust, which was free until then |
| A statement built by hand | Three days, and an error the customer found |
| An error the customer found | Every future figure is now doubted |
| Nothing written down about any of it | The next customer gets the same experience |
Every company that has this problem already asks its people to be careful. They are careful. The register is neat.
The problem is that the record lives in one place, the money lives in another, and a human being joins them at the end of the month. Between the two there is a gap, and payments fall into it in both directions: money that arrives and is not matched, and money that was never received but looks paid.
Every instalment has a due date on the sale, so Tuesday’s money is expected. A payment is recorded against the schedule with a reference — required even for cash — and the customer gets a numbered acknowledgement on his own phone within a minute, which he confirms. Accounts match it against the bank the same day, and the money receipt follows. His statement updates itself.
No reminder goes to a man who has paid, because the system knows he has.
Sofia Estate CRM keeps credit realization on the same record as the sale: the schedule, the dues, reminders before the date, the acknowledgement the customer confirms from his own phone, the accounts check against the bank, and a statement that is current without anybody preparing it. Letters for overdue instalments, dishonoured cheques and full clearance print on your company’s letterhead.
A reference is required when the payment is recorded — cash memo, cheque number or transaction ID — which is what makes it findable later.
Yes, from a link on his own phone, whenever he wants, with no app to install.
The schedule does. A paid instalment is not due.
Yes — the customer ledger in Excel, with the accounts notes.
Yes. Book a live demo and bring one file with a messy payment history.