A digital khata should answer one question clearly: who owes the shop how much, and which recorded transactions explain that balance? The answer must survive a partial payment, a return and a customer coming back after several weeks.
“Ramesh se kitna lena hai?” ka jawab sirf yaad se nahi, bill aur payment ki history se milna chahiye. Udhaar ki entry aur uski vasooli alag kaam hain.
Set the starting balance before adding new credit
When moving from a bahi-khata notebook, identify each customer’s genuine opening due. Do not enter an old balance as a new stock sale just to make it appear in the software. Keep the old record and note the period the opening amount represents.
Confirm the customer’s identity before merging names. “Ramesh,” “Ramesh ji” and two people with the same first name can easily become confusing records. Search by an existing name or mobile number first. If the person is new, create the customer inside the current bill and return to that transaction.
Record each credit sale against the right customer
A credit bill means a sale happened but the full payment has not been collected. Choose Udhaar and the correct customer when saving the bill. The bill is the sales record; the khata tracks what remains to be collected.
For illustration, a customer starts with ₹500 due, buys another ₹300 on credit and later pays ₹200. Their balance is:
₹500 opening due + ₹300 new credit − ₹200 received = ₹600 due.
The ₹200 collection is not another ₹200 sale. It settles part of the existing receivable. This distinction matters when comparing sales reports with the cash drawer or the UPI settlement.
Record partial payments exactly as received
If the customer pays ₹200 in cash, record cash. If they pay through UPI, verify the payment in your bank or UPI app and record UPI. A promised transfer is not the same as a verified receipt.
The remaining ₹600 stays visible in the customer’s history. Add a useful note when needed, such as which conversation or visit the payment relates to. Do not put unrelated customers’ payments into one “miscellaneous” account; that removes the very detail a khata is meant to preserve.
Treat returns and corrections through the right workflow
A returned item may change a bill and its settlement. Use the relevant return workflow and check the resulting balance. Avoid editing an unrelated payment entry to force the outstanding amount to the number you expect. A visible trail makes disputes and mistakes easier to explain.
Customer receivables and supplier payables should also stay distinct. “Lena” is money to receive from customers; “dena” is money to pay suppliers. Even if one person has both relationships with your shop, do not casually net off balances without a documented transaction and the appropriate workflow.
Make the khata useful at closing time
Review who has an outstanding balance, what was collected today and which payments need a follow-up. Keep contact details accurate and communicate respectfully. An overdue list is a business record, not permission to repeatedly message a customer.
Apna Galla’s Khata keeps customer and supplier histories linked to their business records. Pair it with billing and a daily cash check so sales, collections and money movements remain explainable.