MunshiTo fix a wrong entry in your khata, open the customer, open the entry and choose Edit entry to correct it, or Delete entry to remove it; a deleted entry can be restored from the Recycle bin within 14 days. Everyone makes slips at a busy counter: a wrong amount, the wrong customer, a duplicate, an entry deleted by accident. None of them need to be a problem if your app can correct them clearly.
Wrong amount or note: edit the entry
- Open the customer from your Accounts list.
- Open the entry you want to change.
- Choose Edit entry, change the amount or the note, and save.
The balance updates at once. It is a good idea to tell the customer if the change affects what they owe.
A duplicate or a mistake: delete the entry
Open the entry and choose Delete entry. In Munshi the entry moves to the Recycle bin and can be restored within 14 days, so a wrong delete is not final.
Deleted by accident: restore it
- Open Settings, then Recycle bin.
- Find the entry. You can filter by kind: Accounts, Cash Book, Bank or Expense.
- Tap Restore.
The Recycle bin holds deleted ledger, Cash Book, Bank and Expense entries for 14 days, then removes them for good. If an entry cannot be restored because the customer, bank account or category it belonged to no longer exists, Munshi tells you why.
Recorded under the wrong customer
Delete the entry from the wrong person, then add it again under the right one with the correct date and note. The deleted one waits in the Recycle bin, so nothing is lost.
A balance reads the wrong way round
If Ali is shown as owing you when you actually owe him (or the reverse), the entries were probably recorded with the buttons swapped. Instead of editing every entry, use Flip who owes whom on that account. Munshi shows what it reads now and what it will read after flipping, and every entry’s direction flips together. You can flip it back at any time.
Two accounts for the same person
If “Ali” and “Ali Raza” are separate accounts, settle one into the other by recording the amounts in the one you keep, then archive the settled account. Munshi warns you when a phone number is already used by another account, which helps you avoid duplicates in the first place.
Deleting a customer
Only a customer with no entries can be deleted. If an account is settled (balance zero), you can archive it instead, which hides it without losing its history.
Be open about corrections
If a correction changes what a customer owes, tell them and, if needed, share an updated statement. Honest corrections build trust. If a disagreement continues, see how to settle a dispute with proof.
Make mistakes rarer
- Check the amount before saving. The new balance is shown as you type.
- Confirm the customer’s name at the top of the screen.
- Add a short note so a wrong entry is easy to spot later.
More habits are in seven small habits of a khata that always balances, and a full day-to-day routine in how to manage udhaar digitally.
A decision guide: which fix for which problem
| What went wrong | Best fix |
|---|---|
| The amount or note is wrong | Edit the entry |
| The entry should not exist (duplicate, test) | Delete the entry; it waits 14 days in the Recycle bin |
| Deleted by accident | Settings → Recycle bin → Restore |
| Recorded under the wrong person | Delete it there and add it to the right person |
| The whole account reads backwards | Flip who owes whom |
| The balance disagrees with its entries | Use Correct on that account |
| Two accounts for the same person | Record into one, settle and archive the other |
Before you fix: take a quick snapshot
If a fix will change what a customer owes, take ten seconds first. Note the current balance, and, if it is a large account, share yourself a statement for the relevant dates. After the fix, compare. That small habit means you can always explain what changed and why, and it protects you if a customer later asks. It also makes it easy to spot if a fix did more than you intended.
Examples from real counters
The extra zero. A rush at closing: Rs 500 recorded as Rs 5,000. The balance looks wrong the next morning. Edit the entry to the right amount and, if the customer has already seen the wrong figure, tell them.
The double tap. A slow connection, two taps on Save, two entries. Delete the duplicate. Recent versions guard against this, but older habits still produce duplicates if you retype an entry you think failed. Check the list before you retry.
The wrong Ali. You have two customers called Ali. Credit went to the wrong one. Delete the entry from the wrong account and add it to the right one with the same note and date. Then use phone numbers or fuller names so it does not repeat.
The backwards balance. A new helper recorded payments with the credit button. Balances now read backwards. Rather than editing every entry, use Flip who owes whom on each affected account, check the new reading, and teach the helper the two buttons.
What not to do
- Do not change entries quietly when the change affects a customer. Tell them.
- Do not use a fix to hide a missing entry. If money was received and never recorded, record it properly with the right date and a note.
- Do not delete an account to “start fresh”. Only accounts with no entries can be deleted, and settled accounts can be archived instead, which keeps their history.
- Do not ignore a warning. If Munshi says a balance does not match its entries, deal with it the same day.
Preventing the next mistake
Most mistakes come from hurry and similar names. Slow down for ten seconds on large amounts, check the name at the top of the screen, and use notes. The new balance is shown as you work, so glance at it before you leave the page. Then use the habits in seven small habits of a khata that always balances. When a mistake does reach a customer, how to settle a dispute with proof shows how to put it right with respect, and the Correct button guide covers balances that drift.