GST-Compliant Invoicing for Small Businesses: What the Software Actually Needs to Do

If you're running GST invoices out of Word or a spreadsheet template, you've probably already had the moment where a customer's accountant reads down a line item and asks a question you can't answer cleanly — wrong HSN code, a tax split that doesn't match the place of supply, or an invoice number that doesn't run in sequence for the financial year. None of that gets caught by "looks like a proper bill." GST invoicing has a specific legal shape, and most software that advertises itself as GST-ready only gets the cosmetic part right: a GSTIN field and a tax-percentage dropdown. Here's what the rules actually require, and where invoicing tools built without input from someone who's reconciled a GSTR-1 tend to fall short.

What Rule 46 Actually Requires on Every Invoice

Rule 46 of the CGST Rules sets out the mandatory fields on a tax invoice, and it's more specific than most templates assume:

• Invoice number and date, unique and sequential within a financial year
• Supplier's name, address, and GSTIN
• Customer's name and address, and GSTIN if registered (or clearly marked as unregistered if not)
• Place of supply, including the state name and code for an interstate sale
• HSN or SAC code for each line item
• Description, quantity, and unit for goods, or a description of the service
• Taxable value per line, before tax
• Rate and amount of CGST, SGST, IGST, or cess, shown as separate line items, not bundled into one "GST" figure
• Whether tax is payable under reverse charge
• Signature of the supplier or an authorised representative, physical or digital

Miss any of these and the invoice is technically non-compliant even if the total is correct. The two mistakes we see constantly in software built without domain input: combining CGST and SGST into a single "tax" line instead of splitting them, and treating the place-of-supply field as an afterthought rather than the thing that actually determines which tax type applies.

HSN and SAC Codes Aren't Optional Details

A lot of small-business invoicing tools treat HSN/SAC as a free-text field, which is how you end up with a GSTR-1 return that doesn't reconcile against your own invoices. HSN codes for goods and SAC codes for services aren't a formality — they're what the GST portal uses to validate your return, and the number of digits required depends on your turnover, not on your product catalog. Software that lets the field sit blank, or fills it with a generic placeholder code, is setting you up for a mismatch notice later, not saving you time now. If you're evaluating invoicing software, ask directly whether HSN/SAC is validated against a lookup table or just stored as whatever was typed in.

e-Invoicing: When It Applies, and What Actually Changes

Above a certain aggregate turnover threshold, e-invoicing isn't optional: you have to generate an Invoice Reference Number (IRN) through the government's Invoice Registration Portal before the invoice is legally valid, and attach the resulting QR code. That threshold has been lowered several times since e-invoicing was introduced, so don't trust a number you read a year ago — check the current CBIC notification rather than assuming your business is comfortably under the limit. What actually changes operationally is easy to underestimate: your invoice data has to go out as a structured JSON payload in the government's schema (INV-01), which is stricter about formatting than most people expect — dates in DD/MM/YYYY rather than ISO format is a common integration bug we've seen trip up otherwise solid systems. And once an IRN is generated, you don't get to just edit or delete the invoice: there's a 24-hour window to cancel it through the portal, and after that your only option is a credit note. Software that treats e-invoicing as "generate a QR code image" rather than "submit to a government API and handle whatever it sends back" will work fine right up until you need to cancel something.

Where "GST-Ready" Software Actually Falls Down

Beyond the fields on the invoice itself, most compliance problems show up in parts of the workflow nobody demos:

• Rounding at the invoice level, not the line level — GST rules round the final payable amount, not each intermediate line calculation, and rounding every line separately produces a total that doesn't match what an accountant expects
• Sequential numbering that resets correctly at the start of a financial year, per registered place of business, without silently skipping or repeating a number when two people bill at the same time
• Credit and debit notes that reference the original invoice number and carry their own compliant fields, rather than a generic "adjustment" line item
• HSN summary tables for GSTR-1 that actually match what's on your invoices, generated from the same data rather than maintained as a separate manual list
• The correct CGST+SGST vs IGST split based on the actual place of supply, not just whatever billing address happens to be on file

Composition Scheme Changes What "Compliant" Even Means

If you're registered under the composition scheme, none of the tax-invoice rules above actually apply to you in the way most software assumes. Composition dealers can't charge GST separately to customers, which means they can't issue a "tax invoice" at all — the correct document is a Bill of Supply, and it explicitly does not show a tax breakdown, because the tax is being paid by the dealer out of a flat turnover-based rate, not collected line by line from the customer. We've seen invoicing software let composition-scheme businesses generate documents that look like tax invoices, complete with a CGST/SGST split, which is exactly backwards and can create real problems if a customer tries to claim input tax credit against something that was never a valid tax invoice to begin with. If a tool doesn't ask which scheme you're registered under before generating your first document, that's worth noticing before you rely on it.

The same distinction matters for a related but different question: whether you're even required to register at all. Small businesses under the applicable turnover threshold for their state and category can operate without GST registration entirely, and software that forces a GSTIN field before you can invoice anyone is solving a problem you might not have yet.

A Short Checklist Before You Trust Any Invoicing Tool

If you're choosing software rather than building it, these are worth asking directly:

• Does it validate GSTIN format, including the checksum digit, not just field length?
• Is HSN/SAC a validated lookup, or free text?
• Does it round at the invoice level, not per line?
• Can it generate an IRN and handle e-invoicing if you cross the threshold later?
• Does it produce a GSTR-1-ready HSN summary automatically?
• Can you issue a compliant credit note against a specific invoice, not just a manual adjustment?

This is exactly the workflow we're building into GreenFrog CRM — GST-compliant invoicing generated straight from an order, not bolted on as a separate export step. It's still in development, and we've been deliberately specific about what it needs to do rather than shipping a generic invoice template with a tax field on it. If you're building or buying invoicing software for an Indian small business and want a second opinion on whether it actually holds up, see what we're building on the GreenFrog CRM page, or talk to us about a custom build.