The most common GST invoicing mistakes are missing mandatory invoice fields, applying the wrong CGST/SGST versus IGST split, incorrect HSN/SAC codes, and inconsistent invoice numbering. Each of these seems minor in isolation, but they compound into real problems at return-filing time — mismatched input tax credit claims, notices, and hours spent reconciling invoices after the fact instead of getting them right when they were issued.
Missing mandatory fields
A GST-compliant invoice needs a specific set of fields: your GSTIN, the invoice number and date, the recipient's details (including GSTIN, if registered), a clear description of goods or services, the HSN/SAC code, taxable value, applicable tax rate and amount, and the place of supply. Small businesses using generic invoice templates — a basic Word or Excel format never designed for GST — often miss one or two of these without realizing it, because the template simply didn't have a field for it. This becomes a problem for your customer's input tax credit claim, not just your own compliance, which means it can cost you a client relationship, not just a filing headache.
Getting CGST/SGST vs. IGST wrong
This is one of the most frequent errors and one of the easiest to make without noticing. If the transaction is within the same state, you charge CGST and SGST. If it crosses state lines, you charge IGST instead. Businesses that mostly transact within their own state can end up applying the same split out of habit even when a transaction is actually interstate — say, an unusual order from a customer in another state — and the invoice goes out wrong. The tax collected doesn't match what should have been charged, and that mismatch surfaces later, usually at a worse time than now.
Wrong or inconsistent HSN/SAC codes
Every product or service has a specific HSN (goods) or SAC (services) code tied to a specific tax rate. Using the wrong code — often because a similar-sounding item was used as a template and the code never got updated — means the wrong tax rate gets applied, sometimes without anyone noticing until a mismatch shows up during filing. Businesses selling a mix of goods and services under one umbrella are especially prone to this, because it's easy to copy an old invoice as a starting point and forget the code needs to change for a different item.
Invoice numbering that isn't sequential or consistent
GST requires a consistent, sequential invoice numbering system for a given financial year. Skipped numbers, duplicate numbers, or manually resetting a sequence outside the rules creates a red flag during scrutiny, even when nothing is actually wrong — because the pattern itself looks like it could be hiding missing invoices. This mistake is almost entirely a byproduct of manual invoicing: a spreadsheet or handwritten book with no built-in enforcement lets numbering drift without anyone noticing until an audit forces a reconciliation.
Rounding errors that don't match across documents
Small rounding differences between the invoice, the return filed, and the books can each be individually harmless but collectively create a mismatch that's hard to explain later, especially across a high volume of invoices. This tends to happen when tax is calculated manually or in a spreadsheet with inconsistent rounding rules applied invoice to invoice, rather than one consistent method applied every time.
Why these mistakes are so common
None of these are complicated rules in isolation — the actual problem is that they're easy to get right individually and easy to get wrong consistently, especially when invoices are created manually, one at a time, with a human remembering each rule fresh every time. The businesses that avoid these mistakes reliably usually aren't relying on memory — they're using something that enforces the rules by construction, so a missing field or wrong split simply isn't possible to submit in the first place.
This is a place where a founder's accounting background is directly relevant, worth saying plainly: BuildYume's GST invoice calculator was built with a compliance background behind the tax logic, not guessed at from a generic template — the rules are built into the tool itself rather than left to whoever's filling in the invoice that day.
What to check right now
Pull your last five invoices and check each one against the mandatory field list above. Confirm the CGST/SGST vs. IGST split matches where the customer is actually located, not just your default habit. Spot-check that HSN/SAC codes match the actual item, not a copied-over code from a different invoice. If you find issues, the fix isn't necessarily a new system — sometimes it's tightening the process you already have. If manual invoicing is consistently the source of errors, a purpose-built tool that enforces the rules automatically is worth considering.
FAQ
- Can I fix a GST invoice after it's been issued?
- Corrections are possible through credit or debit notes depending on the nature of the error, but the process is more involved than simply editing the original invoice — prevention is meaningfully cheaper than correction here.
- Do these rules apply the same way to service businesses as to product businesses?
- Mostly yes, with SAC codes used instead of HSN codes for services — the core requirements around fields, tax split, and numbering apply the same way either way.
- Is a spreadsheet-based invoice ever GST-compliant?
- It can be, as long as every mandatory field and rule is applied correctly and consistently every single time — the risk isn't the spreadsheet itself, it's that nothing in a spreadsheet stops a human from making an inconsistent entry.
- How do I know if my current invoicing process has errors I haven't caught yet?
- A quick way to check is comparing your invoice numbering sequence and tax splits against your actual filed returns for the last quarter — mismatches there are usually the first sign something's been slipping through.