Billing softwareProductTatva ERP
Why billing software should be keyboard-first, and what that means in practice
The operator who bills fastest never touches the mouse. What a keyboard-first system actually requires, why most web software is not, and the shortcut map we built Tatva ERP around.
- Author
- Kentron Technologies
- Published
- Reading time
- 5 min read
Keyboard-first means every action in the software has a key, the cursor is always where the next input goes, and a full bill can be entered from the first keystroke to the printed copy without the hand leaving the keyboard. It is the single largest difference between software that a billing counter adopts and software that a billing counter resents. It is also the thing most web-based billing products get wrong, because a web form is built for a mouse by default and has to be deliberately built otherwise.
Why this matters more in India than the feature list suggests
A generation of Indian accountants and billing staff learned on desktop accounting packages that were entirely keyboard-driven. They can enter a purchase bill with twenty lines in under a minute, and they know it. When a business moves to a browser-based system, the owner sees the reports and the operator sees the speed. If the speed drops, the operator is right and the system will be worked around: bills written by hand and entered in the evening, which is the beginning of the end of accurate stock.
So keyboard-first is not nostalgia. It is the condition under which the data stays correct, because the fast path and the correct path have to be the same path.
What it actually requires
- Enter moves to the next field and Shift with Enter moves back, everywhere, in the same way.
- Typing in a party or item field searches as you type, with the arrow keys choosing and Enter selecting. No dropdown that needs a click.
- A key to create a master that does not exist, prefilled with what has already been typed, returning to the same field with the new record selected.
- A key to finish the bill that opens discount, charges and payment in sequence, and a final Enter that saves.
- Escape that always means back or cancel, never something else.
- A shortcut to reach any screen without a menu, and a shortcut to switch company, branch or financial year.
- Visible focus. The operator must always be able to see where the next keystroke will land.
The map we settled on
| Key | Action |
|---|---|
| F8 / F9 | New sale / new purchase |
| Ctrl F8 / Ctrl F9 | Sale return / purchase return |
| F6 / F5 / F4 / F7 | Receipt / payment / contra / journal |
| F3 | Switch company, branch or financial year |
| Ctrl K | Go to any screen by name |
| Alt C | Create the customer, supplier or item you just typed |
| End | Finish the bill: discount, charges, payment, save |
| Ctrl S / Esc | Save / close and go back |
| Ctrl P / Ctrl E / Ctrl J | Print / export to CSV / download GSTR-1 JSON |
| Alt R / Alt K / Alt H | Sale register / stock summary / dashboard |
The function keys follow the conventions the people using them already know, because a shortcut map is only valuable if it does not have to be learned twice. The rest are chosen so that the common path through a working day, bill, receipt, register, is reachable without a menu.
What keyboard-first is not
It is not a hostile interface. Every action still has a button, a menu and a mouse path, because the owner who opens the software twice a week should not have to memorise anything. The shortcuts are for the person who is in it for six hours a day, and the software should teach them quietly: the key printed next to the button, the panel of shortcuts that can be collapsed once it is no longer needed.
It is also not an excuse for skipping validation. Speed without checks produces bills that are fast and wrong. A GSTIN that fails its checksum, an expiry date in the past, a negative stock movement or a purchase without the supplier's bill number should stop the entry at the moment it happens, when fixing it costs five seconds instead of at the month end when it costs an hour.
How to test it before you buy
- Ask for a demo login and enter one real bill yourself, with the mouse pushed out of reach.
- Count how many times you are forced to reach for it. More than twice in one bill is a fail.
- Try to create a customer who does not exist, in the middle of that bill, and see whether you keep the bill.
- Enter a purchase with ten lines and time it. Compare it with what your staff do today.
- Let the person who will actually use it do the same, without you standing over them, and listen to what they say afterwards.
Tatva ERP was built to pass that test, because the businesses it is for already have staff who are fast. The prices are published in what GST billing software costs.
Frequently asked questions
Can web-based billing software be as fast as desktop software?
For data entry, yes, if it is built that way: the browser handles keystrokes as fast as any desktop application, and the work is in the design rather than the platform. Where a browser is genuinely different is a dropped internet connection, which a desktop package survives and a web application does not. That is a question of connectivity planning, not of typing speed.
Do my staff have to learn shortcuts before they can use it?
No. Everything is clickable from day one. Shortcuts get learned in the first fortnight by anyone who bills all day, because they are shown next to the actions they replace. The owner and the accountant usually never learn more than four of them, which is fine.
What happens to speed when the internet drops?
Billing stops until it returns, which is why a shop with unreliable connectivity should keep a second connection on a mobile hotspot and a rule for the gap: write the bill by hand, enter it the same day. Anyone promising you a web application that bills with no connection at all is describing a different kind of product.