How to run an udhar book without losing money
An udhar book works when every credit sale is recorded immediately, every payment is matched to the right customer, and every balance has a clear next action. The danger is not offering credit itself. The danger is allowing small unrecorded amounts, unclear names and open-ended promises to grow until neither the shopkeeper nor the customer agrees on the total.
You do not need complicated accounting to control this. You need one customer identity, one running ledger, a sensible credit limit and a routine for reviewing overdue balances. The method below works in a paper register or a digital ledger, although digital search and automatic totals reduce arithmetic mistakes.
Record the sale before the customer leaves
Write the udhar entry at the counter, not at the end of the day. Capture the customer’s full name, a reliable phone number, date, amount and a short description such as “monthly groceries” or “motorcycle repair parts.” If two customers share a first name, add an identifier such as area, shop, vehicle number or phone suffix. Never keep several people under a label such as “Raju” and expect memory to separate them later.
Give the customer a visible confirmation. This can be a written slip, a WhatsApp message that contains only the necessary amount and date, or a ledger view shown on the screen. Confirmation prevents a later argument about whether the sale was cash or credit. It also gives the customer a chance to correct an entry immediately.
Avoid subtracting a payment by editing an old sale. Enter the payment as a separate line. A proper ledger shows what was purchased, what was received and how the current balance was calculated. Separate lines also make partial payments easy to understand.
Set a due date and a reason for the credit
“Pay later” is not a due date. Agree on a practical trigger: salary date, weekly market day, completion of a job, delivery of the next order or a specific calendar date. Record that expectation with the entry. A customer who normally pays on the fifth of each month should not receive a reminder on the first, but the balance should not remain untouched after the agreed date either.
Credit should solve a genuine timing problem, not hide an unaffordable purchase. Regular household customers may need a monthly cycle. A contractor may pay when a client releases money. A one-time visitor requesting a large amount has a different risk. The amount and period should match what you know about the customer’s payment pattern.
When a due date changes, record the conversation rather than deleting the old date. A short note such as “Customer requested extension to 12 August; no new credit until payment” preserves the decision and helps anyone reviewing the ledger understand why collection paused.
Worked example: one month of controlled udhar
Suppose Meena buys ₹1,250 of groceries on 3 July and agrees to pay after salary on 7 July. You record:
- 3 July: credit sale, ₹1,250
- 5 July: additional milk and staples, ₹380
- 7 July: UPI payment received, ₹1,000
The pending balance is ₹630, not ₹1,250 and not ₹1,630. The ledger keeps both purchases and the payment. Meena asks to clear ₹630 on 10 July. You note the new promise and avoid giving another ₹1,500 of credit before that payment arrives.
If Meena pays ₹630 on 10 July, enter a second payment line and close the cycle at ₹0. If she pays only ₹400, the balance becomes ₹230 and remains visible. Do not mark the account “paid” merely because some money arrived.
This example also shows why verbal totals fail. Four events occurred in seven days. A shopkeeper remembering only the first sale or latest payment will quote the wrong balance.
Review balances in three groups
Review the udhar list at least once a week and separate it into three groups:
- Not yet due: no collection pressure is needed.
- Due soon or recently due: send a polite reminder with the amount and agreed date.
- Long overdue or above limit: stop new credit and make a direct collection plan.
The groups stop you from treating every customer as a defaulter. Good customers should receive respectful reminders, while repeated broken promises require firmer limits. Review the total amount outstanding as well as individual accounts. Ten customers owing ₹800 each tie up ₹8,000 of shop cash even if no single balance appears large.
Track how much of your monthly sales are becoming udhar. If sales look strong but supplier payments are difficult, excessive customer credit may be the reason. Profit on paper cannot pay a wholesaler until the customer pays you.
Collect without damaging the relationship
Start with a factual message: date, current balance and the agreed payment point. Avoid public embarrassment, threats or repeated calls at unreasonable times. Ask for a specific response: full payment date or a smaller instalment today. If a customer cannot clear ₹3,000, an agreed ₹750 weekly plan is more useful than another vague promise.
After each conversation, update the note. If the customer pays by UPI, verify the transaction in the correct account instead of accepting a screenshot alone. Record cash payments while the customer is present and confirm the new balance.
When promises are repeatedly broken, stop fresh credit calmly: “Your pending balance is ₹2,400. Please clear ₹1,500 before the next udhar purchase.” A consistent rule is easier to defend than a decision made in anger.
Prevent the common leaks
Most udhar losses begin with ordinary habits: sales written on loose paper, payments not entered, family members using different customer names, or balances carried forward without checking. Use one ledger system for everyone at the counter. If a temporary paper note is unavoidable during a rush, transfer it the same day and mark the paper as entered.
Never combine household withdrawals with customer credit. If the owner takes ₹700 of stock home, record it as an owner withdrawal or household use according to your accounting method, not under a fake customer. Otherwise customer reports and stock figures become misleading.
Back up the ledger according to your system, but verify that a backup belongs to the correct signed-in account before restoring it. A backup is useful only if it preserves the ownership and transaction history accurately.
Practical takeaway
Use this five-step rule for every udhar sale: identify the customer, record the sale immediately, agree on a due date, enter payments as separate lines, and review overdue balances weekly. Set a maximum amount before the customer reaches it, and stop new credit when an overdue account crosses the rule.
Begin today by checking the ten largest balances. Confirm each total, add the next promised payment date and send a polite reminder where due. Then read the guides on setting customer credit limits and payment-reminder scripts to turn the ledger into a consistent collection process.