MunshiWholesale credit is two books that must stay in the same week: shops that owe the distributor, and suppliers the distributor still has to pay. Munshi, from DIGIT, holds both as ordinary accounts. A buying shop is a Customer. A mill, importer or company is a Supplier. The phone will not merge those roles, and you should not either, even when one man owns a shop and also drives a supply van. This page does not repeat the basic udhaar method. That sits in how to keep an udhaar ledger. The supplier buttons, in detail, sit in the supplier khata. What follows is the distributor’s week.
Why both sides on the same afternoon
Imran sells packets to thirty kiryanas and buys from two companies. If he only writes what the kiryanas owe, he feels rich on Thursday and cannot pay the company on Friday. If he only writes the company bill, he chases nobody and the kiryanas drift. The useful picture is both totals on Home: what he will get, and what he will give. Those totals are only as good as the round he typed today. A van that returns at night with the numbers on a scrap of cardboard will lose one shop. He types before he locks the van, or he types while the shopkeeper is still looking at the goods.
A shop that takes goods
Each kiryana is added once, Add account, Customer, the owner’s name and the WhatsApp number of the person who pays, not the boy who only unloads. When that shop takes goods and does not pay, Imran taps You gave for the amount of this drop. The note can say “Thursday round” or the areas he remembers. He does not type carton counts into a stock field, because there is not one. Munshi does not manage stock, invoices or barcodes. A dispute later is about the amount and the date, settled with a statement, not about a barcode the app never stored.
A part payment on the pavement is You got for the notes they handed him. If those notes go into his bag, he also taps Cash in. If they transfer to his bank while he watches, he taps You got and a Deposit. He does not tap Cash in for a transfer. The bag and the bank are different pots, and the daily version of that rule is in the daily cash book routine.
Opening the book for the first time means one You gave per shop for what they owe today, note “opening”. He does not retype a year of settled drops. The paper day book can sit in the van for a week while he compares.
A company he has not paid
The company is a Supplier. Goods that arrived and are not paid are You got on that supplier, so the screen can say he owes them. This is the mirror of a customer, and it feels odd for a day. He reads the sentence on the account, not his guess about the colour of the button. A payment he makes is You gave on the supplier. From the bank, he also adds a Withdrawal. From the bag, he also adds Cash out. Skipping the money-pot line keeps the person’s balance honest and the cash or bank false. Skipping the supplier line does the opposite, and he will pay the company twice.
He does not enter the company’s invoice as if Munshi were an invoicing program. The note can hold their bill number if that number is how they talk. The product still has no invoice register and no barcode scan. Promising a company a printout of “their invoice from the app” will embarrass him. A statement of the account, PDF or Excel, is the honest document: dates, amounts, balance.
The week’s order of work
Monday and Tuesday are for drops: You gave as he leaves each shop. Wednesday he looks at who is oldest, opens Reminders, and sends a short WhatsApp draft himself. The app does not send it. Tone and timing are in polite payment reminders, and the taps are in the reminder steps. Getting a route to pay on a rhythm is in getting paid faster.
Thursday he lists what he owes the two companies and pays the one he promised, then types You gave the same hour. Friday he counts the bag, compares it with the Cash Book, and moves a chosen amount to the bank with Cash out plus Deposit. He does not pay a company from a drawer he has not counted. A distributor who pays from an uncounted bag is guessing.
If one route is a different legal business, with different customers who must not see each other’s world, he adds another business, up to five, and switches from the name on Home. He does not keep “route B” as a customer named Route B. That trick collapses the moment someone on route B pays.
What he refuses to fake
He does not type a stock balance. He does not scan barcodes. He does not keep two accounts for one shop in order to hide a private discount from himself. A discount given is a smaller You gave, or a You got if he is reducing an old balance, with a note “less, damaged tins” if that was the reason. A silent edit of last month’s line destroys the only proof he has. Wrong entries are fixed by a new line or by the method in fixing a wrong entry.
Comparisons with other ledgers, if he is still choosing, include Munshi and Khatabook and Munshi and OkCredit. He should test a real route, not a demo shop: five customers, one supplier, one bag count. Munshi is free to download. Ads marked Ad pay for it and stay away from the entry screen, sign-in, unlock and the reminder. Names, numbers and amounts are not shared with advertisers. Offline entry matters on a staircase with no signal. The line syncs later. That, plus both directions of credit, is the distributor’s use of the app.