Solutions · Business software
GST billing app: what to decide, build and test.
Planning one? Here's what to settle before you brief anyone, what goes in the first version, how the build runs week by week, how the beta is tested with real people, and the numbers that show it's working.
Own tool or product for other shops? Settle this first
Most billing briefs say "GST billing app" and leave out the one choice that changes the architecture: whose shops will use it?
- Your own outlets, or a product you sell to other merchants. One business with five outlets needs roles and a multi-store view. A product for many merchants needs separate accounts, plan limits, onboarding and support tooling, which is closer to a SaaS build. The first is cheaper and faster; the second can earn a subscription but has to be supported for years.
- Online first, or offline first. If the counter must keep billing when the line drops, bills live on the device and sync later, and you need rules for two counters selling the last packet. Online-first is simpler but stops the queue at the worst time.
- One GSTIN or several. Outlets in more than one state usually mean separate registrations and separate invoice series. Say so up front.
- Credit inside billing or separate. A khata attached to every bill gives you one customer record; a separate ledger is easier to retrofit but splits the data.
- Accountant exports or full accounting. Exports your CA can file from are a small feature. Replacing accounting software is a different product.
Checklist for the brief: number of outlets and GSTINs, counter devices and printer models, items in the catalogue, loose or packed goods, credit customers, who reads the reports, and whether you will resell it.
What the first version bills, and what waits
Our Tillbook concept has two working surfaces, a counter screen and a khata screen, because those two carry a shop's day. Everything else can follow.
| Module | First version | Add later | Why |
|---|---|---|---|
| Counter billing | Search, scan, quick-tap items, split payment, print | Weighing-scale input, hold and recall of bills | Speed at the counter decides whether staff keep using it |
| Item master | Name, price, HSN, tax rate, unit, local-language name | Variants, batches, expiry | Wrong tax on one item repeats on every bill |
| GST invoice | Series numbering, tax split, bill of supply, credit note | E-invoice submission | Add e-invoicing only if your turnover requires it |
| Khata | Balance per customer, statement, reminder message | Credit limits, interest rules | Credit is why many shops want a custom tool |
| UPI and end-of-day | Per-bill UPI amount, closing tally of cash, UPI and credit | Bank statement matching | The day's numbers must agree before shutters close |
| Stock | Deduct on bill, low-stock list | Transfers between outlets, purchase orders | Transfers need conflict rules and a second screen |
| Offline | Bill and print without network, sync later | Conflict screens for managers | Print never waits for the cloud |
| Owner console | Sales, stock, GST summary | Staff performance, margin by item | Reports follow clean data, not the reverse |
| Accountant export | Sales and purchase registers as files | Direct links to accounting tools | Your CA should see a sample before launch |
An 8 to 12 week plan, and what you need to hand us
| Weeks | What gets built | What you supply |
|---|---|---|
| 1–2 | Counter flow prototype tested with your staff; invoice layout | Sample bills you issue today, your item list, GSTIN details |
| 3–5 | Billing, item master, tax logic, printing | Printer, scanner and tablet models you will buy; HSN and rate checks by your CA |
| 5–7 | Khata, UPI amounts, closing tally | Opening customer balances, credit rules |
| 7–9 | Offline mode and sync; owner console; exports | A quiet outlet for a trial, a sample export reviewed by your CA |
| 9–12 | Parallel run beside the old system, fixes, training, handover | Staff time for training; a printed fallback for week one |
How we work with you each week
The same rhythm runs from week 1 to launch, so you always know what's happening and what we need from you.
- Friday: a demo link and a 30-minute call. You open the latest build on your own phone and try it yourself, rather than watching our screen.
- Within 48 hours: your feedback, in writing. In one shared doc, next to the screen it's about. Written feedback is clear, dated and doesn't get lost between calls.
- Monday: triage. Every comment goes into fix now, next week or later. Anything that changes the agreed scope gets a written quote before we touch it.
- Each milestone: two revision rounds, then your sign-off. Sign-off is against the scope we agreed, so it's clear what done means.
- One decision-maker on your side. Most delays aren't build time. They're feedback waiting on several people who disagree.
The full version, including how the beta and user testing work across every kind of project, is on our process page.
The beta: one real counter, side by side with the old system
The beta is the parallel run in weeks 9 to 12. It starts at the quiet outlet used for the week 7 to 9 trial, once a bill can be made, printed and counted in the closing tally without help. Customers walk away with real bills, so the invoice series is agreed with your CA before day one.
- What's in it. Counter billing with search, scan and quick-tap items, split cash and UPI, printing, credit notes, the khata, the closing tally, offline billing with sync, and the owner console with its sales and GST summary.
- What stays out. Stock transfers, purchase orders, weighing-scale input and e-invoicing. Each brings its own failure cases, and none of them tells you whether the counter is faster.
- Who uses it. Two or three cashiers per outlet on their normal shifts, the owner or manager who closes the day, a handful of regular khata customers who receive statements, and your CA, who reviews the first exports. Start with one outlet, add a busier one in the second week.
- How they get it. The counter app runs on the actual tablet, printer and scanner you bought, installed through a Google Play closed test. The owner console opens on a staging link from the owner's own phone.
- How real money is protected. The old system or printed fallback stays at the counter. If anything looks wrong, staff switch back for that bill and note it, and we compare both systems' totals each night.
- How long. Two to three weeks, covering at least one weekend rush and one month-end, so credit collections and the CA export are tested for real.
A new personal Google Play developer account has to run a closed test with at least 12 testers for 14 days before it can publish. Count the outlet staff and owners towards that, or use an organisation account.
What we test with real people, and the tasks we set
We test at the counter, during real trading hours, with staff using their own words for items. Each person gets a task, and we stand back and note what slows them down. About five sessions per role is enough to spot the big snags. We fix them, then hand the same tasks to new people.
| Who | The task | What we watch for |
|---|---|---|
| Cashier | "Bill 2 kg atta, a 1 litre oil pouch and three loose items. The customer pays ₹300 cash and the rest by UPI." | Do they find loose items by their local name? Is the split clear? How long does it take compared with the old system? |
| Cashier | "The internet has just dropped. Bill the next five customers." | Does printing carry on? Do they notice which bills are waiting to sync, and does sync finish without duplicates? |
| Cashier | "A customer returns one soap from yesterday's bill and wants cash back." | Do they issue a credit note against the original bill, or look for a way to edit it? |
| Shop owner | "Sharma ji took ₹1,240 of groceries on credit this week and paid ₹2,000 on Saturday. Send him his statement on WhatsApp." | Is the running balance right? Does the statement read clearly in the language he uses? |
| Manager | "Close the day. Cash, UPI and credit must match the drawer and the UPI app." | Where does a gap show up, and can they trace it to the bill that caused it? |
| Accountant (CA) | "From this month's export, prepare the sales register." | Are HSN codes, rate splits, credit notes and cancelled bills all where the CA expects them? |
The numbers that say it's working
In week 1 you choose two or three of these. Where we can, we take today's figure from the current counter, even if that means timing a few bills with a stopwatch. Tracking is built in before the parallel run. We share the figures at go-live and 30 days on. We don't promise a result; we give you the numbers so decisions rest on them.
| Goal | What we measure | Where it comes from |
|---|---|---|
| The counter moves faster | Time per bill in the busiest hour, new system against old | App timestamps and the week 1 stopwatch baseline |
| Bills are right first time | Credit notes and cancelled bills per 100 bills; tax errors the CA finds | Invoice records and CA review of the export |
| The day closes clean | Daily gap between counted cash and UPI and the app's closing tally | Closing tally screen |
| Offline doesn't lose bills | Bills made offline that sync without conflict or duplicate number | Sync log |
| Credit comes back | Outstanding khata balance and days to pay after a statement is sent | Khata ledger |
| Staff actually use it | Share of bills made in the new system during the parallel run | Outlet bill counts, both systems |
What a billing app costs, and what moves it
A single-outlet counter app with an owner view is close to our one-user-type tier, ₹3–10 lakh for a small studio. Multi-outlet stock, purchases, reports and exports put it in data-heavy business software, ₹12–35 lakh. Both are ballparks from our cost guide; the studio quotes each project.
- Offline sync. Rules for conflicts, retries and reprinting are most of the hard work.
- Hardware. Every printer, scanner and scale model you need to support has to be tested on a real device.
- Report depth. Sales summaries are cheap; tax registers, margin views and filtered exports are not.
- Selling it to others. Separate merchant accounts, plans and support tools raise both cost and the upkeep you carry after launch; see maintenance costs.
GST and counter habits the software must respect
- E-invoicing is turnover-based. It applies to registered businesses above ₹5 crore of turnover, from 1 August 2023, and covers B2B, SEZ and export invoices, not sales to consumers. Businesses from ₹10 crore must report within 30 days of the invoice date. A retail counter selling to walk-in customers normally issues ordinary invoices.
- Bill of supply versus tax invoice. Exempt supplies get a bill of supply. A composition dealer's bill of supply carries a fixed line saying the dealer cannot collect tax. The software needs both document types.
- HSN digits. Four digits up to ₹5 crore of turnover, six above. Invoices to unregistered buyers can omit it for the smaller group.
- Numbering. Invoice and credit-note numbers must not repeat within a financial year. A cancelled bill stays in the series, marked cancelled.
- Rates change. The 22 September 2025 reform moved most items to 5% or 18%. Keep tax rates as editable data with an effective date so the next change is a data edit, not a release.
- Not yet law. The October 2026 GST Council approved only a concept for a lighter return option for small B2C sellers. Do not build for it yet.
- Customer data. A khata stores names and phone numbers. Collect them with a stated purpose; the DPDP checklist explains how.
This is general information, not legal advice or tax advice. GST thresholds and rates change; have your CA confirm what applies to your turnover and registration before you go live. See also our GST billing guide.
Seven billing-software mistakes, and what to do instead
- Demoing on a fast laptop. Test on the cheapest tablet your staff will really use, with a thousand items loaded.
- Hard-coding tax rates. Store them as dated data so a rate change needs no new app.
- Letting staff edit sent bills. Issue a credit note instead and keep the original.
- Forgetting the printer. Connection drops and paper widths cause more counter trouble than the app does. Test your exact model.
- Skipping opening balances. Load credit customers' balances carefully and share statements so they can confirm.
- Cutting over in one day. Run old and new side by side for a few days at a quiet counter.
- Asking for everything at once. Billing, khata and the closing tally first; transfers, purchases and exports next.
Instead: write down your five busiest counter actions, build those to be fast, and give your CA a sample export in week seven. Then send a brief.
Cost and timeline
8–12 weeks for a first version.
Fixed quote within 48 hours of your brief: scope, timeline and price in writing before we start. These are what move the number.
- Number of stores and whether stock moves between them
- Printer, scanner and weighing-scale hardware to support
- Offline billing and sync rules
- Depth of GST and accounting reports
- Payment and messaging integrations
Questions
About your gst billing app.
What does custom billing software cost?
It depends on the number of stores, devices and reports you need. Every project gets a fixed quote within 48 hours of your brief. Our guide to app development cost in India explains typical ranges and what moves them. A single-store counter app costs far less than a multi-store system with stock transfers and accountant exports.
Will billing work without internet?
Yes, if you need it to — and most shops do. The counter app stores bills on the device, keeps printing receipts, and syncs to the owner's console when the connection returns. We design the rules for conflicts, such as two counters selling the last packet of the same item.
Does it work on a basic Android tablet?
Yes. We build for the low-cost Android tablets and phones shops actually buy, with large tap targets, quick item buttons and screens that stay fast with thousands of products. Receipt printers, barcode scanners and cash drawers are tested with the actual models you plan to buy, before launch rather than after.
Can it send GST e-invoices?
We can integrate with the government e-invoicing system through an authorised provider if your business is required to issue e-invoices. Your accountant should confirm which rules apply to your turnover; we build the flow and the reports to match. Smaller shops that don't need e-invoicing still get clean GST invoices and reports.
Who owns the software?
You do. Source code, designs and documentation are handed over in full, so you can run it, sell it or extend it with your own team. There is no per-store licence fee to us, and your sales data lives in your own database and cloud account.
Read next
- BillingGST billing software for shops: features that matter →What GST billing software for Indian shops needs: fast billing, GST-ready invoices, HSN codes, credit ledgers, UPI reconciliation, stock and CA-ready reports.
- MessagingWhatsApp and your app: order updates, OTPs and support →How Indian businesses use the WhatsApp Business Platform with their app: approved templates, opt-in, the 24-hour window, OTPs, team inboxes and costs.
- PaymentsAdding UPI payments to your app: a plain guide →How UPI works inside an app or website: intent, QR and collect flows, payment gateways, refunds, AutoPay mandates and reconciliation, explained for business owners.
- CostHow much does it cost to build an app in India? →Ballpark app development costs in India for 2026, from a simple app to a multi-sided marketplace — what moves the price, and how to get a quote you can trust.
Start a project
Tell us how your business runs. We'll build what it runs on.
Four taps, about a minute. Fixed quote within 48 hours.


