Bhatta Hisab: Manual Register vs. Software—What Actually Changes

Walk into almost any bhatta office and you will find the same thing: one or more registers for production, a separate book for majdur advances and payments, a challan book for dispatches, and a rough ledger for customer dues. Each book is maintained by whoever is available that day—an owner, a munshi, sometimes a family member.

This system is not wrong. It has worked for decades and it is cheap to start. The problems show up later, usually at the point where the owner needs one number urgently: total production this season, how much is owed to labour as a group, or what margin a particular order actually left after expenses.

Where the manual register genuinely works

A paper register is fast to write in, needs no internet or device, and is familiar to every munshi who has worked at a bhatta before. For a small, single-season operation with one or two trusted staff, it can be entirely adequate.

The register also does one thing well that software sometimes struggles to replace: it is written in the exact words and shorthand the munshi already thinks in.

Where it breaks down

• Numbers exist, but not in one place. Production, labour, stock and sales sit in separate books, so the owner has to physically collect and add them up to see the full picture.
• Reconciling stock is slow. Knowing how many bricks are raw, carried, in the kiln, or already dispatched means cross-checking several pages, and small errors compound over a season.
• Handwriting and staff turnover are a real risk. A new munshi has to interpret an old munshi's shorthand, and pages can be damaged, lost, or simply misplaced.
• The owner cannot see the numbers remotely. If the owner is away from the kiln—at a market, at home, travelling for material—the register is not with them.
• There is no baseline to compare against. A register tells you what happened, not whether this round performed better or worse than the last one, or than a similar bhatta.

What changes with bhatta software

Software does not remove the need for daily discipline in recording work—someone still has to enter what happened, just as someone had to write it in the register. What changes is what happens to that entry afterwards.

Once a production entry, a labour advance, or a challan is recorded, it is already connected to stock, to the labourer's running balance, and to the customer's account. The owner does not need to re-collect numbers from different books—the same entry already updated all of them.

• Owner visibility from anywhere: the dashboard is reachable from a phone, so the owner can check the position without being physically present at the kiln.
• One connected record instead of four separate books: production, labour, stock and sales stay linked to the same entries.
• Faster reconciliation: raw, carried, kiln and exited brick counts are calculated from actual entries, not re-added by hand.
• A backup that survives fire, water damage or a lost register: records live on the server, not on paper that can be destroyed.
• Baseline comparison: a season's performance can be compared against a previous round, not just remembered.

Being honest about the trade-off

Software adds a device and a habit change. Someone on-site needs a phone or computer, a working internet connection, and a few days to get comfortable with a new screen instead of a page. For a bhatta running on a single season with very few transactions, this overhead may not be worth it yet.

For a bhatta handling multiple labour groups, regular dispatches, and an owner who is not always on-site, the register's limitations tend to show up quickly—usually at settlement time, when everyone needs the same numbers to agree.

How kilns usually make the switch without disruption

• Run both side by side for one round. Keep the register as a fallback while the munshi enters the same activity into eBrix, so nothing is lost if a habit needs adjusting.
• Start with labour accounts first. Advances and payments are usually the most error-prone part of a manual register, and the improvement is the most visible to the munshi immediately.
• Use the Hindi screens for daily entry. A munshi working in Hindi does not need to relearn the workflow—only the input screen changes.
• Let the owner check the dashboard remotely from week one, even while the parallel run continues, so the value is visible before the paper register is fully retired.