MunshiTo record an Easypaisa, JazzCash or bank payment, open the customer, tap You got, enter the amount and note how they paid, then add the same money as a deposit in a Bank Book account named after your bank or wallet. Munshi does not connect to banks or wallets, so you enter these by hand; the habit that keeps them right is matching your Bank Book to your statement once a week.
Two records, two questions
A payment answers two questions at once, and they live in different books:
- Who paid, and what do they still owe? That is the customer’s account (the khata).
- Where is the money now? That is a Bank Book account (your bank or wallet).
Recording only the first leaves your bank balance wrong. Recording only the second leaves the customer’s balance wrong. Do both. See cash book vs khata vs bank book.
Step 1: record the customer’s payment
- Open the customer’s account.
- Tap You got and enter the amount.
- In the note write how they paid and any reference, for example “Easypaisa, ref 12345” or “bank transfer, HBL”.
The balance goes down. If the customer pays part by wallet and part in cash, make two entries, one for each, with the method in the note.
Step 2: have an account for your bank or wallet
In Bank Book, tap Add bank account. Give it a name you will recognise: your bank’s name, or the wallet you use. You can add an account title and number if you like. You can have several accounts, and Munshi shows your total bank balance at a glance.
Step 3: record the money in and out
- When a customer’s payment reaches your account, add a Deposit for that amount.
- When you take money out, or pay a supplier from it, add a Withdrawal.
If you move money from the drawer to the bank, record the withdrawal from the Cash Book side and the deposit in the Bank Book, so neither balance is out. Paying a supplier from your wallet or bank? Record it on their account as You gave too. See how to track what you owe suppliers.
Step 4: match it every week
Once a week, open your bank or wallet statement and compare it with the Bank Book balance. If they differ, look for a missing deposit, a fee or a withdrawal you did not record. Fix it while it is small. Munshi’s bank reports and statements can be shared as PDF or Excel for any dates; see business reports in Urdu and English.
Common mistakes
- Counting a wallet payment as cash. It did not go into the drawer. Record it in the Bank Book.
- Forgetting fees. A transfer fee is an expense. Record it so your balance matches.
- No note on the method. A short note answers “how did you pay?” months later.
- Mixing personal and business wallets. Use a separate account, or keep personal money in a Personal khata. See Personal khata.
Four common situations, step by step
1. A customer pays their udhaar by Easypaisa. Open the customer, tap You got, enter the amount, and note “Easypaisa” with the reference. Then add a deposit of the same amount in the Bank Book account you use for that wallet. Two records, one payment.
2. A customer pays for goods in full by bank transfer on the spot. There is no udhaar, so there is nothing to record on their account. Record the money as a deposit in the Bank Book account that received it, with a note naming the sale.
3. You pay a supplier from your wallet. Open the supplier’s account and tap You gave for the amount, with the method in the note. Then record a withdrawal in the Bank Book account for that wallet so its balance stays right.
4. You move cash from the drawer to the bank. Record a cash out in the Cash Book, and a deposit in the Bank Book. If you forget one side, one of the balances will be wrong, and the weekly match will catch it.
Reading the weekly match
Once a week, compare each Bank Book account with its statement. If your Bank Book is higher than the statement, you recorded a deposit that has not arrived, or you forgot a withdrawal or fee. If it is lower, a deposit arrived that you did not record. Work through the differences by date, starting from the last time the two agreed. Most gaps turn out to be a transfer fee, a payment recorded twice, or a customer’s payment that went into the wallet while you were busy.
Notes that make the match easy
- Reference numbers. A transaction ID in the note lets you find the matching line on the statement in seconds.
- The sender’s name, if it differs from the customer’s, such as a relative paying on their behalf.
- The purpose, such as “balance of order 114” or “rashan, September”.
Fees and limits
Wallet and bank transfers can carry small fees, and wallets often have daily or monthly limits. Record fees as an expense so that your bank balance matches reality; a Rs 25 fee ignored every day becomes a visible gap by the end of the month. Munshi does not connect to banks or wallets, so it does not know about fees until you tell it.
Keeping personal and business wallets apart
Many people use one wallet for everything. That is workable if you keep records carefully, but it blurs your books. If you can, use a separate account for the business. If you cannot, record personal movements as their own category, or put personal lending in a Personal khata, so that profit and reports are not distorted. See Personal khata.
Trust, receipts and disputes
Digital payments leave a trail, which is useful. If a customer says they paid and you cannot see it, the transaction ID in your note, or in theirs, resolves it. If you recorded a payment that later reversed, add a note and an entry that undoes it, rather than deleting silently. When a customer asks for a record, share a dated statement from their page. The guide on how to settle a dispute with proof shows how to use it kindly.