Here is what car bill format actually has to contain under Indian law, what the usual templates get wrong, and a free alternative that issues the same document from records you enter once.
A format is a layout. An invoice is a record.
A template gets the first bill out of the door, and for a business issuing two or three a month that is a perfectly reasonable answer. Nobody needs software to send three invoices.
What a file cannot do is remember. It will not stop you reusing a number, it will not notice that a customer was billed twice, and it will not tell you in April what was still unpaid in February. Every one of those is a matter of record-keeping rather than of layout.
So the useful way to read this page is: get the content right first, because that is a legal question, and only then decide whether a file or a system should hold it.
Counter bills in a shop
A retail bill is a tax invoice produced in seconds while someone waits, and almost every design decision follows from that. The items, quantities, rates and the tax shown separately, your GSTIN and the invoice number — printed, not typed out afterwards.
The constraints that actually bite in a shop are the mixed basket and the walk-in customer. A basket with items at two different tax rates cannot carry one tax figure; it needs the tax computed per line and totalled per head. And a customer with no GSTIN is perfectly normal — the bill is still a tax invoice, it still needs your GSTIN and the HSN codes, and it is reported in the B2C summary rather than invoice by invoice.
Trades with their own wrinkles: jewellery bills carry purity, gross and net weight, making charges and any hallmarking detail, and often precious-metal rates that move daily. Garments are commonly priced across slabs that depend on value. Mobile and computer shops want the IMEI or serial on the line, because the warranty claim will be traced through it.
Barcode scanning matters less for the layout than for the arithmetic: an item scanned carries its own rate and tax, so the bill cannot be wrong in the way a hand-typed one can.
Where a file stops being the right tool
There is a real threshold, and it is worth naming rather than implying. A file is the right answer while one person issues a handful of documents a month and nobody needs to ask what is outstanding.
It stops being the right answer at the first of these: a second person starts billing, the count passes roughly twenty a month, you need an answer to "what is unpaid", or you have to file a return from it. Any one of those is the point at which the file becomes the problem rather than the tool.
Nothing is lost by starting with a file. What is lost is the six months of history that stayed in it, so moving sooner is cheaper than moving later.
What you get here instead of a file
- Every mandatory field present, because the document is built from records rather than typed into a layout.
- One numbering series, issued centrally, consecutive, restarting each financial year — so a number cannot be used twice.
- Customers stored once with GSTIN, address and state, so the details are right on the fortieth invoice too.
- Items stored once with HSN or SAC, rate and tax.
- The tax derived, not chosen — CGST and SGST or IGST, from the place of supply against your registration state.
- A clean PDF to print, email or send on WhatsApp.
- An answer to "what is unpaid", which no template has ever been able to give.
- Your data exportable to CSV, Excel and JSON at any time, on every plan including the free one.
- Free — ₹0, no card, no expiry.
Moving a year of billing off a spreadsheet
- Decide a cut-off date — the start of a month or a quarter is easiest to reconcile against.
- Tidy the spreadsheet first: one row per invoice, no merged cells, GSTINs in their own column.
- Import your customer list, then your item list. Fix what the import reports rather than what you think it got wrong.
- Enter the outstanding invoices only — the unpaid ones. Settled history can stay in the file; you need the balances, not the archive.
- Set the next invoice number to carry on from the last one you issued, so the series stays consecutive across the move.
- Issue everything from the cut-off date onwards in the new system, and keep the old file read-only as an archive.
- Reconcile one month both ways before you stop maintaining the file.
The numbering rule, which is where templates fail first
The invoice number has to be a consecutive serial, unique within the financial year, not more than sixteen characters, and made only of letters, numbers, hyphens and slashes. One series, or clearly separated series if you genuinely need more than one — but each consecutive in itself.
A file cannot enforce any of that. The number is typed, which means it can be repeated, skipped or quietly rolled back when yesterday's invoice is edited into today's. A duplicate is not found at billing time; it is found at return time, in the month after the one it happened in.
The other half of the rule is that a cancelled invoice keeps its number. Deleting the row and reusing the number leaves a gap in your books and a figure in your customer's, and reconciling that is a long afternoon.
This is the single most practical argument for a system over a file, and it has nothing to do with features.
What goes wrong between the file and the return
The return is where billing errors become visible, and they arrive in a predictable order.
Place of supply recorded wrong, so a supply is reported in the wrong state and the tax head is wrong. A missing customer GSTIN, which silently moves a B2B supply into the B2C summary where it cannot be claimed. HSN codes left blank on some lines, so the summary table cannot be built. A combined tax figure that has to be unpicked line by line. And duplicated or missing invoice numbers, which is the one that takes longest to resolve.
None of these is hard to avoid at the moment of billing. All of them are expensive to fix a month later, because by then the customer has their copy and may have filed against it.
That asymmetry — cheap to prevent, costly to correct — is the real case for capturing an invoice properly the first time.
CGST, SGST and IGST — worked out, not chosen
Whether a sale attracts CGST and SGST or IGST is not a preference. It follows from the place of supply: same state as your registration means the tax splits into central and state halves, a different state means one integrated tax at the combined rate.
That sounds simple and goes wrong constantly, because it is a dropdown in most billing software and a dropdown is something a tired person clicks past. In Billixo the split is derived from the state on the customer record against the state on your registration, and it changes the moment either does.
The consequence of getting it wrong is real: an IGST invoice raised as CGST/SGST has to be credited and reissued, and if the return has already gone in, amended.
HSN and SAC codes, and how many digits you need
Every line on a tax invoice needs an HSN code for goods or a SAC for services. How many digits depends on your aggregate turnover in the preceding financial year — smaller businesses report fewer digits than larger ones, and B2B and B2C invoices are treated differently.
Because the requirement is tied to turnover and has been tightened in stages, the practical answer is to store the fullest code you can against each product once, and let the software report at the level required. A six-digit code can always be truncated; a two-digit one cannot be expanded.
Billixo keeps the code on the product record and carries it onto every line automatically, and its AI HSN lookup will suggest one from a plain description when you genuinely do not know.
Bill scanning, in practice
The single largest time cost in most small businesses is not raising invoices — it is entering purchases. A photograph of a supplier bill goes in and a structured draft comes out: supplier, GSTIN, line items, rates, tax split and total.
You check it. That is the workflow, and it is deliberate: an extraction you did not read is a liability, not a saving. But checking a filled form takes fifteen seconds and typing one takes three minutes, and that difference compounds over a month of purchases.
Who it is built for
Small and mid-sized Indian businesses that are registered under GST and bill regularly. One person doing everything, or a counter with three people billing at once and an accountant who needs the month to close cleanly.
The design assumption throughout is that whoever raises the invoice is busy and is not a tax specialist. So the tax is computed rather than asked for, the compliance fields are populated rather than presented as questions, and the report the accountant wants is a download rather than a request.
Try it free — the free plan needs no card and does not expire.
The price, plainly
Free is ₹0 and stays ₹0. The paid plans are bought for a fixed term, paid once, with no auto-renewal and no card kept on file — when a term ends the account drops back to Free until you decide to buy again.
There is no per-invoice charge, no per-user surprise on the free plan, and no feature that is technically included but practically throttled. What the plan says you get is what you get.
Compare the plans on the home page, or just start free now and look at the ceiling from the inside.
Reliability, backups and getting your data out
Cloud billing software is only as good as its worst day. Two things matter more than any feature list: that your data is backed up somewhere you can reach, and that you can export it in a format something else can read.
Exports here are CSV, Excel and JSON, on every plan including the free one, covering customers, products, invoices and payments. That is the honest test of whether software respects you — not what it promises, but what it lets you take when you leave.
Frequently asked questions
Can I keep using Excel for my invoices?
Yes, and plenty of small businesses reasonably do. The point at which it stops working is specific rather than vague: a second person starts billing, the volume passes roughly twenty a month, or you need to answer "what is outstanding" and file a return from it. Until then a carefully built spreadsheet is a legitimate tool.
What is the difference between a tax invoice and a bill of supply?
A tax invoice is issued on a taxable supply and shows the tax separately so the buyer can claim input credit. A bill of supply is issued where no tax is being charged — an exempt supply, or a composition dealer — and must not show a tax amount at all. Issuing the wrong one is a compliance error, not a presentation choice.
Do I need an HSN code on every line?
Every line needs its HSN for goods or SAC for services. How many digits you must show has depended on turnover and has been tightened over time, so check the requirement currently applying to you — but "none" has not been an option for a registered supplier for a long time.
Can I move my existing customers and products in?
Yes. Bulk import from CSV or Excel on any paid plan, and export back out in CSV, Excel or JSON at any time, including on Free. Most people bring their party and item lists across in one pass and carry outstanding invoices as opening balances.
Will my accountant be able to work with it?
That is what the GSTR-1 and GSTR-3B summaries are for. They export in formats a practitioner can open and reconcile without repairing the file first — which, in practice, is most of what a CA wants from a client’s billing software.
See it working on your own bills
The fastest way to judge billing software is to bill with it. Photograph one supplier invoice, raise one sales invoice, and look at the PDF your customer would receive.
Open the software demo → — free account, no card, about a minute to set up.
More details on the home page → — what it does, what it costs, and where the limits are.
Related pages