Khata and Udhar Management: 10 Best Practices for Small Shops

Khata is built on trust, but trust works better with accurate records. A paper notebook can be misplaced, handwriting can be misunderstood and one payment may be remembered differently by the customer and shopkeeper. The result is not only delayed money; it can damage a long-standing relationship.

DukaanAdda maintains customer-wise due, overdue, paid and transaction information. It supports Due bills, manual ledger entries, payment modes, running balances, account filters, manual reminder actions and PDF statements. These features become useful when the business follows the same credit process for every customer.

A Khata ledger should answer five questions without guesswork: who took the goods, when the amount was added, how much was paid, which payment mode was used and what balance remains. Each entry needs a customer, date, amount and understandable description.

In DukaanAdda ledger language, a sale or debit entry increases the customer's outstanding amount. A payment or credit entry reduces it. The transaction list shows sale, payment and opening entries with a running balance, while the customer account stores current due and overdue amounts.

Duplicate customer profiles split one person's sales and payments across multiple balances. Accounts such as “Raju”, “Raju Shop” and “Raju New Number” may belong to the same person, but the operator cannot know during a busy sale.

Search the customer list before creating a new profile. Use the real name, active mobile number and business name where relevant. DukaanAdda also supports email, alternate phone, GSTIN, customer type, address, location, notes and an optional image.

• Use the customer's real name and active mobile number.
• Add business name and GSTIN when relevant for business buyers.
• Store address, city, state and pincode when collection depends on location.
• Set a credit limit as an internal reference, not a substitute for approval.
• Choose agreed payment terms and explain them to the customer.
• Add notes for authorised buyers, collection preferences or special terms.

Credit should be a business decision, not an automatic response to every request. Decide which customers qualify, the maximum amount the shop is comfortable carrying and when payment is expected. Explain the rule before goods leave the counter.

DukaanAdda customer profiles include a credit-limit field and payment terms such as Due on Receipt and Net 7, 15, 30, 45 or 60 Days. Treat these as stored account information. Do not assume that entering a credit limit alone blocks every future sale or that payment terms automatically send reminders.

When moving from a paper Khata to DukaanAdda, the customer may already owe money. Add that verified amount as the opening balance when creating the customer. The app seeds an opening ledger entry so the starting point appears in transaction history.

Do not add the same old dues again as a manual debit. That would double the outstanding balance. Before migration, calculate the paper total, subtract payments already received, confirm any returns or cancelled sales and ideally show the customer the agreed starting figure.

A Due bill without a customer is an amount with no collection owner. In DukaanAdda Fast Bill, the Due/Credit mode requires a customer. Select the profile carefully, especially when several people have similar names.

Confirm the customer name and phone before saving. If a family member or employee collects the goods, keep the bill under the agreed account and add suitable information through the available invoice or customer notes workflow. Avoid creating a temporary account merely to finish the sale faster.

“I will enter it later” is one of the biggest Khata risks. At closing time, a shopkeeper may remember the amount but forget the customer, or remember the customer but not whether ₹500 was cash received or more goods supplied.

Use the invoice flow for real sales. For a valid ledger-only situation, DukaanAdda also provides a transaction dialog: a payment received is recorded as credit, while an amount or goods added to what the customer owes is recorded as debit. Select the date, mode and customer, then add notes and reference where useful.

Use a manual debit only when there is a real, documented reason. Normal product sales should still use billing so invoice and stock records remain consistent.

The amount alone is not enough for reconciliation. Record whether the customer paid through UPI, Cash, Bank or Card. DukaanAdda's payment workflow stores the selected mode and allows reference notes such as a UPI ID, bank reference or cheque information.

Before recording UPI or bank payment, confirm that money reached the actual account. A screenshot shown by the customer is not the same as a successful credit. For cash, count the money and complete the entry while the customer is present.

A payment above the current balance can create a negative or confusing account. DukaanAdda validates the amount against due plus overdue and rejects a payment that exceeds the total outstanding.

When both overdue and current due exist, the verified balance update applies payment to overdue first and then to current due. The payment amount is also added to Paid This Month for account reporting.

If a customer pays an advance above outstanding, do not force it through the due-payment field. Follow the business's separate advance-payment and accounting process.

Collection works best when the customer knows the due date and receives a clear, factual reminder. Start before the account is very old: confirm the bill, remind near the agreed date and escalate only according to the shop's written policy.

DukaanAdda customer details provide Call, SMS and WhatsApp actions. The WhatsApp action prepares an outstanding-balance reminder that the user chooses to send. This is a manual workflow, not an automatic reminder service.

Never share one customer's balance with another person. Confirm identity before discussing transactions, and keep the message professional: name, outstanding amount, relevant period and a request to contact the business if the record differs.

Calling customers in random order wastes time. The DukaanAdda Khata dashboard shows Total Customers, Total Receivable, Overdue Amount and Paid This Month. Tabs separate All Accounts, Receivable, Overdue and Paid.

Sort accounts by Recently Active, Name, High Dues, High Overdue or High Paid This Month. Start with high overdue where follow-up is needed, then review large current dues approaching their agreed date. Search by customer information instead of scrolling through the full list.

When the customer asks, “How did this balance become ₹8,400?”, answer with dated entries rather than memory. The DukaanAdda ledger screen can filter Last 7 Days, Last 30 Days or All Time, and All Transactions, Sales Only or Payments Only.

Export a PDF statement for the chosen scope. It includes customer details, total added, total paid, current balance and a table of date, particulars, type, amount and running balance. Review it before sharing so the selected period contains the entries needed to explain the account.

At day end, compare recorded Cash, UPI, Bank and Card payments with the actual cash drawer and financial accounts. A ledger can balance internally while the selected payment mode is wrong, so collection reconciliation matters.

1. 1

   Create or verify the customer

   Confirm name, mobile number and business details.

2. 2

   Set the account context

   Add credit limit, payment terms and opening balance if verified.

3. 3

   Create the Due sale

   Select the customer and Due payment mode in billing.

4. 4

   Review the ledger

   Confirm that the sale and running balance appear correctly.

5. 5

   Record collection

   Choose the customer, amount and real UPI, Cash, Bank or Card mode.

6. 6

   Add evidence

   Use reference notes that make the payment easy to verify.

7. 7

   Check the new balance

   Confirm overdue and due were reduced by the saved payment.

8. 8

   Export when needed

   Filter the right period and download the PDF statement.

Assign responsibility for collection and ledger corrections. Staff may record a payment, but only an authorised person should resolve disputed balances or add manual debit entries without a bill.