Devtechify
Billing & Invoicing

User Roles and Permissions for Billing Staff in Small Shops

KarthikFounder & Full-Stack Engineer4 min read

A textile shop owner once told us his biggest billing problem was 'trust'. Not a thief, exactly. Just a clerk who edited an old bill to change a rate because a regular customer complained. It was a small, kind act. It also broke the stock count, the day's cash, and the customer's statement.

Permissions are not about suspecting your staff. They are about making it hard to make costly mistakes, and easy to see who did what. Here is a way to think about it without turning your shop into a bank.

Start from jobs, not people

Do not begin with 'Ravi is trusted, Meena is new'. Begin with the tasks that happen in your business, then match each task to the least access needed.

  • Making sales: creating invoices and POS bills.
  • Collecting money: recording receipts against invoices.
  • Buying and stock: purchase bills, orders, stock adjustments.
  • Changing history: editing or cancelling finalised bills, returns, discounts.
  • Seeing the whole picture: profit figures, dashboard, bank balance, all customers' dues.
  • Running the system: adding users, changing settings, deleting data.

In most small shops, the first two go to counter staff. The last three belong to the owner or a very close deputy.

A sensible split for a small shop

We'd start with three tiers and add detail only if you need it.

Owner

Sees everything, can change anything, adds and removes users. In Billy, the owner is a defined role. Keep that login to yourself. If you run the shop day to day, still consider using a separate, more limited login for counter work so you do not leave the owner screen open.

Manager or senior staff

Can approve returns and discounts, record supplier bills, and see stock and dues. Does not need to change settings or see every financial number. Only create this tier if you have someone who really does this work.

Counter staff

Can bill, take payments, and look up customer and product details. Cannot edit finalised bills, give unlimited discounts or see profit.

A word of caution on specifics. Not every billing tool offers fine-grained permissions, and what exists varies. Before you buy, ask the vendor exactly which roles exist and what each can and cannot do. Do not assume. We only describe the owner role in Billy with confidence here, and you should confirm any other detail directly.

Principle of least access

If a person cannot explain why they need to see or change something to do their job this week, they do not need that access yet. It is easy to grant more later and awkward to take it back.

What to restrict first

If you can only control a few things, control these.

  1. 1Editing or deleting finalised invoices. Corrections should happen through a visible route, such as a credit note or a return, not a silent overwrite. See our explainer on credit notes and sales returns.
  2. 2Discounts. A cap per bill, or approval above a limit, plugs a lot of quiet leakage. More on that in discounts and bill edits without revenue leaks.
  3. 3Stock adjustments. Manual stock changes are the easiest place to hide losses.
  4. 4Profit and cost price visibility. Staff who see your cost price may share it with customers or competitors, innocently or otherwise.
  5. 5Adding and removing users. Only the owner.

Habits that matter more than settings

Permissions only work alongside routines. Give everyone their own login so actions can be traced. Never share the owner password. Remove access the day someone leaves. And once a week, look through what was cancelled, returned or discounted. You are not hunting for a culprit. You are looking for patterns, such as one counter with twice the returns of the others.

Be kind in how you introduce it. 'I'm setting this so nobody, including me, can change a finished bill by accident' lands better than 'I don't trust you'. Pair it with proper training on the new system so people understand why the limits exist.

Keep a short written list of who has which login and what they can do, and review it every quarter. In a small shop, roles drift: the temporary helper from Diwali week still has access in March, and the new manager has the same rights as the owner because nobody got round to fixing it. Ten minutes with the list every few months catches most of this.

Needing something more specific?

If your business has approval chains or branch-level rules that standard roles do not cover, that is a case for customisation. Tell us what you need and we will say honestly whether it fits Billy as it is or needs custom work. If you run several counters, billing with several staff and counters is the practical companion to this post.

user rolespermissionsbilling staffinternal controls

Talk to us

Have a project in mind? Tell us about it.

Four quick questions and we'll reply within one business day with an honest view on the fastest way to ship it, whether that's our own products, a custom build or an integration.

DevTechify

Start your project

Let’s build something great

1
2
3
4

Which industry does your business belong to?

Pick the closest match — we'll tailor the rest for you.