Choosing GST Billing Software in India: What Actually Matters

The features that are genuinely non-negotiable

Most products handle a straightforward B2C invoice. The gaps appear at the edges — and the edges are where penalties live.

• Place-of-supply logic. CGST and SGST within the state, IGST across states, decided automatically from the parties rather than from a dropdown someone might get wrong.
• GSTIN validation at entry. Catching a malformed or inactive GSTIN when the customer is created, not when the return is filed.
• HSN/SAC codes at the required digit level, with correct summary reporting.
• Credit and debit notes properly linked to original invoices. Returns and rate corrections happen constantly, and software that treats a credit note as a negative invoice will produce a mismatch.
• Reverse charge, wherever it applies to you.
• Multiple series and branches, if you invoice from more than one place.
• Exports and SEZ handling, if relevant — with and without payment of tax are different flows.
• Round-off handling consistent with what your CA expects.

E-invoicing and e-way bills

If your turnover crosses the applicable threshold, e-invoicing is not optional and IRN generation should be part of the product rather than a paid extra. What to check before buying:

• Does it generate the IRN and QR code directly from the invoice screen, without re-keying anything?
• Does it handle cancellation within the permitted window, and does it explain what to do afterwards?
• Does it generate e-way bills from the same invoice, including part-B vehicle details and extensions?
• What happens when the government portal is down? Good software queues and retries; poor software loses the invoice and blames the portal.

Thresholds have changed several times and will change again. Confirm the current figure with your CA rather than with a vendor's marketing page — including this one.

What to ignore while comparing

• Invoice template counts. "500 designs" is not a feature. You will use one.
• AI-branded anything, unless the vendor can describe precisely what it does with your data.
• Module lists you will never switch on. They add cost and confusion, not capability.
• Lifetime licence offers from vendors with no visible support operation. Compliance software that stops being updated becomes a liability the moment the rules change.

The questions that decide it

1. What exactly do we hand our CA, and in what format? Ask to see a real export before buying. This is the question that most often changes the decision.
2. What happens when we correct a filed invoice? The amendment path should be obvious in the interface.
3. Can we get all our data out? Invoices, parties, items, history — in a usable format, on demand.
4. What does support look like on the 18th of the month? That is the only day it matters.
5. How does pricing change at twice our current volume or user count?

When off-the-shelf is right — and when it is not

For most retailers, small distributors and service businesses, a mainstream product is the correct answer. Compliance is a solved problem and someone else maintains it as the rules change. Buy it, and spend the saved money elsewhere.

Custom billing becomes justified in specific situations:

• Unusual pricing. Slab rates, dealer-specific pricing, seasonal schemes, quantity-linked discounts and margin structures that no product models properly.
• Billing is entangled with operations. A garage billing off job cards, a transporter billing off trip sheets, a hotel billing off folios. In these cases billing is an output of the operational system, and bolting on a separate product means duplicate entry forever.
• Multi-branch with consolidated reporting and branch-level control that products either omit or price at the enterprise tier.
• Volume that makes per-user licensing painful across counters, branches and field staff.

When that is the situation, billing is usually built as part of the wider accounting and billing system or inside the operational software itself, with statutory filing continuing to run through Tally or your CA's tooling.

A pattern worth copying: keep filing where it already works, and build only the invoice generation that your process actually requires. Rebuilding GST compliance from scratch is effort spent on something that is not yours to differentiate.

Migrating without losing history

• Export parties, items and opening balances first, and reconcile totals against the old system before going live.
• Do not import three years of invoice history unless you genuinely need it in the new system; keep the old system readable instead.
• Switch at the start of a period, never mid-month, and never in the week before a filing deadline.
• Run both systems for one full cycle. It is tedious and it catches the case nobody remembered.
• Confirm the invoice number series continues correctly. Duplicated or skipped numbers create questions you do not want to answer later.

If you are weighing this up

Send me what you invoice for and how your pricing works. If a product covers it, that will be the recommendation — it is faster, cheaper and someone else keeps it compliant. A build is worth discussing when your pricing or your operations genuinely do not fit anything on the shelf.