Who should be allowed to edit the books

On 3 October a customer pays ₹6,000 against an udhaar balance of ₹9,400. The boy at the counter takes the cash and writes the entry himself. On the 7th the balance reads ₹4,400 instead of ₹3,400. Somebody has changed something, and the hand that took the money is the hand that keeps the book.

In a shop pushing fifty credit entries a day through Navratri, plenty goes wrong without anybody being dishonest: a figure typed twice, a payment filed against the wrong name. Split the man who records money from the man who can change the record and you can tell a mistake from a story. Hold both jobs yourself and you are guessing, and guessing turns a ₹1,000 gap into a family matter.

Pull that customer's entries for 1 to 7 October and read them against the days he remembers paying. Check each row for who entered it and when — not the date written on it, the date it was written. Then set the 3rd's total against the cash you counted that evening. A gap of exactly ₹1,000 is nearly always the same ₹1,000 entered twice, a payment filed against the wrong name, or a figure written short.

Alone at the counter there is nobody to split with, so the substitute is a book with its own history: write in pen, never tear a page out, and when a figure is wrong strike it through, write the right one beside it and date the fix. The date is the half that earns its keep: a customer can see whether you fixed it the same evening or three weeks after he complained. On a phone, check whether an edit leaves the old figure visible anywhere. If it does not, the notebook is doing something your app is not.

Adding only goes forward: a new row at the bottom, and a wrong one corrected by another. Changing a row reaches backwards into a number somebody has already seen and agreed to. Your partner pays a mason ₹1,200 and a helper ₹900 on 12 September and records only the mason. On the 19th he puts it right by editing the ₹1,200 up to ₹2,100 instead of adding a second row. The labour total moves by ₹900 a week late, the figure you settled with him from was ₹900 short, and the ledger on the 20th reads ₹2,100 as though it always had.

Edit is one switch, not two. Hand it over and that man can reach any row in the book, including a September row three people have agreed to; withhold it and he cannot fix his own typo from an hour ago. No book, paper or phone, grants a same-day-only edit. The rule you want — same-day typos fixed, a three-week-old row reversed instead — is a house rule, and a glance down the changed rows at month end makes it real.

Much of the editing in a shop book is undoing a date. A ₹2,000 advance promised on the 4th and received on the 9th, written on the 4th, is why a month closes ₹2,000 short and somebody goes back to change a number. Mark it promised-but-not-moved instead: listed, visible, never counted in the balance. In Khatamel that is a pending entry; in a notebook, a column of its own that never enters the total. Settling it later is still a change to that entry, so it falls to whoever holds the edit rights — in most shops, you, at cash-up.

In a paper book, and in anything that keeps no log, a deletion leaves nothing at all, and nobody notices an absence. A record that notes the deletion is better, but it still will not tell you what the row was for.

Your month's credit total comes out at ₹1,86,000 when it should be ₹1,91,000. There is no wrong row to find. There is no row. To know anything is missing you would have to remember a ₹5,000 sale from three weeks ago on your own.

Keep deletion with yourself and give everybody else the reversing entry. A ₹1,800 credit went in twice on 1 October: add a ₹1,800 debit dated today, noted "reverses duplicate of 1 Oct", and the balance comes right with both rows standing. The cost is that the month now reads ₹1,800 high on credits and ₹1,800 high on debits, which is why the note matters more than the row. Tag reversals Correction so a report can separate them out, and date one inside the same month, or a November fix throws October out too.

Delete the duplicate your own thumb made two seconds ago. Reverse everything else.

Your brother-in-law collects from four customers in the next town every Tuesday. Better he records them himself, on the day, with the customer's name on the entry: you stop being a typist and the row carries the time it was made. He should not be able to file an entry under another name. The day he can, a ₹7,000 collection lands against your cousin, who never touched the cash. The group total is right, so nothing looks wrong — but your cousin reads ₹7,000 better off than he is, your brother-in-law ₹7,000 worse, and they find out only at month end, when they settle. The row says who typed it. It does not say who has the money. Whatever you keep the book in should treat those as two settings; Khatamel does.

Most people in your book need no rights at all: the dairy customer carrying a ₹1,250 running balance does not log in and never will. Four people may need a login. The other sixty do not.

A book nobody is allowed to correct stops being kept. The helper enters ₹600 where he meant ₹60, cannot change it, cannot be bothered to find you, and writes it on a slip to tell you later. The slip stays in his pocket. Within a week there are two records of the shop's day and one of them is in his trousers.

Take a twelve-member committee at ₹5,000 a month, ₹100 a day on a late payment. A member says she paid on the 5th; the book shows nothing until the 9th, so ₹400 is on the table and she is being told, politely, that she has misremembered. The row is dated the 5th but was entered on the 9th by the organiser. Nothing there is dishonest, and the late charge drops. Now the argument is about a four-day recording gap, not about whose memory is better. One of those you fix by writing entries on the day. The other ends friendships.

A permission list alone will not do it. If the organiser can edit and the edit is silent, you have only narrowed the list of people who can change history unseen. What works is narrow rights plus a record: one or two people can change a number, and the record says who and when.

Credit, debit and withdraw are three kinds of entry, records rather than instructions to any bank. This division of who writes them and who changes them holds up in most small shops and committees.

• You, the owner: everything, including deletion, and the only one who may post an entry under another member's name.
• Your partner, or whoever opens the shop when you are away: credit, debit and withdraw entries, and edit only if you accept that the same switch reaches a September row. He quotes balances to customers, so he must be able to correct his own figures the same day. No deletion, and you read the changed rows at month end.
• The counter helper: credit and debit entries only. Corrections come to you.
• Family who only want to see the balance: no rights at all. Seeing is not recording.

Review that list once a quarter: the help you took on for Diwali should not still be adding entries in January. And when an entry is wrong, reverse it rather than hide it, where people can see you do it to your own mistakes.

The ledger says ₹4,400, somebody insists it should be ₹3,400. Can you find out tonight which rows make up that figure, who entered each one and when, and whether any has been touched since? If you can, your permissions are roughly right. If not, no goodwill will settle that ₹1,000, and it will be back next month.