Multi-User Billing: Letting Your Cashier Bill Without Seeing Your Margins

Right now, how does billing actually happen in your shop?

If you’re like ~80% of small Indian businesses, the answer is: one Tally / Vyapar login, shared by everyone. You log in on the shop laptop in the morning. Your cashier uses it at the counter all day. Your salesman borrows it to generate a quotation for a client. Your CA logs in from home for month-end.

One login. No access control. Everyone sees everything.

This works until it doesn’t — and when it stops working, it usually stops noisily.

The three ways single-login billing breaks

1. Your cashier sees margins they shouldn’t

Your buying price for cotton fabric is ₹720/metre. You sell it at ₹850/metre. Your margin is ₹130 — which is fine, legitimate, yours to know.

But when your cashier uses the single-login billing tool, they see that margin on every line item, every day, for a year. Eventually either:

• They mention it casually to a customer (“Actually, this is only ₹720 cost”) — and your pricing goes south
• They leave to start a competing shop with perfect intelligence on your pricing model
• They leak to a supplier who uses it to squeeze you

You can’t un-see margin data. Once seen, it stays.

2. Accidental deletes with no audit trail

Tuesday evening. Your salesman is in the billing tool. He accidentally taps “Delete invoice” instead of “Print invoice.” The customer who was at the counter paid already, took the goods, left. Now the invoice is gone.

With one shared login:

• No way to prove who deleted it (everyone uses the same login)
• Recovery requires a database restore (hope you have backups)
• For audit purposes, it looks like the invoice never existed

With role-based access, you control who can delete. You also get a per-user audit trail of every destructive action.

3. Your CA needs read-only access, not edit

Your CA logs in to pull month-end GST data. They need to read invoices, purchases, reports. They don’t need to:

• Edit prices
• Change tax rates
• Modify customer records

With one shared login, your CA has full edit rights. A mis-click on their end can corrupt your books. A well-intentioned CA once told us they accidentally changed a customer’s GSTIN in a client’s Tally, triggered a GSTR-1 rejection, and spent half a day re-conciling. With read-only access, that can’t happen.

How role-based access should work

A proper multi-user billing tool has roles (pre-defined permission bundles) plus per-user assignment. Not custom permission checkboxes per user — that’s enterprise territory and overkill for SMBs. Four or five well-designed roles cover 95% of use cases.

Here’s the role model 21bill uses (yours should look similar; if it doesn’t, the tool isn’t really multi-user, it’s “multi-login with the same permissions”):

Admin

• Full access — create, edit, delete on everything
• Can invite other users, assign roles, remove users
• Sees margins, costs, profits
• Manages GSTIN, bank details, org settings
• Who: you (the owner). Usually 1-2 people total.

Billing (or “Accountant”)

• Create + edit invoices, purchases, payments, credit notes
• View customers, products, quotations, reports
• Cannot modify org settings, bank details, user permissions
• Cannot delete paid invoices (only void them with a reason)
• Sees margins (their job requires it)
• Who: your CA, your back-office accountant, your trusted finance lead

Sales

• Create quotations, view customers
• Create invoices (but prices are read-only from product master — can’t manually override)
• Cannot see cost prices or margin calculations
• Cannot see purchase records (supplier side)
• Cannot edit customer credit limits or payment history
• Who: your field salesman, your counter salesperson, anyone who closes deals but shouldn’t see financials

Viewer (read-only)

• Read access on everything except user management + org settings
• Cannot create, edit, delete anything
• Who: your CA for scrutiny / filing, an auditor during a compliance check, your spouse/family member who wants to check books without risking a fat-finger edit

Cashier (on the 2026 roadmap)

Planned: a dedicated role for counter staff that can create invoices using existing products, record payments, and little else — no cost prices, no reports, no edits or deletes. Today, counter staff can be assigned the Billing role as an interim (slightly more access than Cashier will eventually have, but it’s the closest match available).

The practical setup for a typical Indian SMB

A small-to-medium business with 5-8 people typically looks like this:

Person	Role	Why
Owner	Admin	Obvious.
Spouse / business partner	Admin	Redundancy — if owner is on holiday, billing doesn’t stop.
Cashier (shop counter)	Cashier	Writes invoices all day, can’t leak margin.
Field salesman	Sales	Creates quotes at customer locations; can’t see financial totals.
Back-office accountant	Billing	Records payments, issues credit notes, runs reports.
External CA	Viewer	Month-end filing data extraction; can’t accidentally edit anything.
Owner’s son/daughter learning the business	Viewer → Sales → Admin	Progression over time as trust grows.

At 21bill’s Business tier (₹299/month), you get 5 users. Most businesses this size fit. If you have 6-8 people all actively in the tool, bump to the Pro tier (₹599/month) for unlimited users.

The migration from single-login — how to actually do it

If you’re currently running everything through one shared login, here’s the switch:

1. List out every person who touches the billing tool. Include people who log in even rarely (CA, spouse, once-a-week salesperson).
2. Assign each person a role from the 5 above. Err on the side of less access — upgrading is easy, downgrading after someone has seen data is impossible.
3. Create one user account per person. Each gets their own login via their own email.
4. Revoke the shared login. Change its password to something nobody knows. Or better, delete it entirely if your tool supports it.
5. Train for 30 seconds: “You each have your own login now. Click ‘Logout’ at the end of your shift. If you can’t do something, it’s because your role doesn’t allow it — tell the owner, they’ll adjust.”

The whole migration takes under an hour if you’re organised. The benefit compounds from Day 1 — every action is now attributable to a specific person with a specific role.

The objections you’ll hear

”My cashier’s not going to remember their own password.”

Valid. In practice: a piece of paper taped under the cash drawer with their login + password. Or a shared password manager. Or they log in once and tick “Keep me logged in” on the shop tablet. The goal isn’t military-grade security — it’s separating their actions from yours so you have an audit trail.

”This is a lot of work for a small shop.”

It’s an hour, one time. Once done, it silently protects you forever. A single avoided margin leak pays for the Business tier for a decade.

”Can’t I just trust my people?”

Of course. But role-based access isn’t about distrust — it’s about limiting blast radius when someone makes a mistake. Your most trusted accountant will still accidentally delete an invoice sometimes. Your most loyal cashier will still mis-tap. Role restrictions catch the accidents; trust covers the rest.

”Tally doesn’t really let me do this.”

True. Tally’s multi-user story requires Gold edition (~₹54k) and even then the role model is shallow. It wasn’t built for multi-user from day one; it was retrofitted. Modern cloud billing tools (21bill, Zoho Books) are built multi-user from the first line of code.

What 21bill specifically does

• 5 roles available today: Admin, Manager, Billing, Sales, Viewer. A dedicated Cashier role is on the roadmap; kirana-style businesses currently put counter staff on the Billing role.
• Audit trail on destructive actions against key tables (invoices, payments, role assignments). Admins can see who did what and when.
• Role switching is one click by an Admin — no re-setup needed when your cashier gets promoted.
• Session revocation: an Admin can disable a user account, which blocks future logins. Active-session force-logout (kicking someone off mid-session) is on the roadmap.
• Granular cost-price hiding for the Sales role is planned for 2026. Today, role separation is primarily navigational (what the sidebar surfaces) — which covers most practical leak vectors but isn’t yet field-level backend enforcement.

Priced at 21bill: Starter (₹99/mo) is single-user. Business (₹299/mo) gets you 5 users. Pro (₹599/mo) unlimited. Most SMBs sit comfortably in Business.

---

The single most under-discussed benefit of a modern billing tool isn’t speed or cloud access — it’s role discipline. Your business grows safely when the person adding line items at the counter can’t also see your profit margins or delete paid invoices. That separation doesn’t exist at ₹0 with a shared Vyapar login. It’s ₹200/month away with 21bill Business.

21bill is invite-only. Request access if you’d like to evaluate the role model for your team — we’ll send a short setup guide if it helps.