Practical guides and field notes on loan collection, reducing defaults, and running lending operations that scale.
A borrower settled the overdue window and got their vehicle back. We closed the loan. The owner told us the remaining seven instalments were still theirs.
A ₹500 visiting charge and the ₹300 paid against it were both invisible on screen. The column held what was owed now and nothing about how it got there.
Mobile said ₹2,400 paid. The PDF said ₹2,450. Same loan, same database, same moment — and both numbers were computed from a defensible definition.
A collector visits a home, not a loan. When Barath has a daily loan and a chit instalment due, two cards is one too many — and the second one gets missed.
A UPI-only payment rail works until a client abroad tries to pay you, or you want to stop chasing an invoice every month. How we swapped gateways without a cutover.
We built reusable loan configurations so owners stop retyping the same charges. Then an owner asked for a switch to turn the whole thing off.
A chit foreman says his commission is five percent. That sentence has two different answers, and the software was quietly picking one of them.
A recurring deposit customer remembers one number — what they get at the end. We compute it the way the owner quotes it, not the way a bank would.
Our per-tenant database isolation held. The leak was in a config merge, where an absent flag key quietly inherited the previous company's value.
A seizure is not a settlement. How we model repossession — the loan untouched until the vehicle sells, an immutable valuation, and a shortfall that stays visible.
Search "finance management app" and you get budgeting apps and accounting software. If you lend money and collect it back, here is what to check instead.
If you rent out cycles, push carts or equipment, you are not lending money — you are chasing rent on things. Here is how to track who has what, and what they owe.