Your invoices look fine. Your CA thinks they're fine. Then the GST notice arrives. Here are the seven "small" mistakes Indian businesses make on their invoices without realising, why they quietly fail at GSTR-1 filing or in an audit, and exactly how to fix each one.
Ask any business owner in India whether their invoices are compliant, and almost all of them will say yes. The PDF looks professional. The GST number is on it. The totals add up. The customer paid. As far as anyone can tell, everything is in order.
Then, months or even a couple of years later, a notice lands. A figure in the books does not match a figure in a return. A credit note that was supposed to reduce tax did nothing. An invoice number sequence raises a question nobody can answer. Suddenly the "perfect-looking" invoice is the reason a business is spending evenings reconstructing records and a CA is sending increasingly worried messages.
The uncomfortable reality is that most invoice problems in India are invisible at the moment they happen. They do not throw an error. The invoice still prints, still gets shared on WhatsApp, still gets paid. The cost only shows up later, at filing time or at audit, when the gap between what was issued and what the law expected becomes impossible to hide.
This article walks through the seven that catch people out most often. None of them require fraud or carelessness to happen. They happen to honest, busy people running real businesses, precisely because the rules are detailed and the tools most people use, usually a spreadsheet or a basic invoice maker, do nothing to catch them. (If you want the full picture of getting invoicing right from scratch, our complete 2026 GST invoicing guide for small businesses covers the fundamentals; this piece focuses on the specific errors that slip past most people.)
- The wrong tax split on inter-state sales This is the single most common GST invoice mistake in India, and it is worth understanding properly because it trips up even experienced teams.
The tax you charge depends on the place of supply, which in most ordinary sales is determined by the customer's location relative to yours. If your business and your customer are in the same state, the transaction is intra-state and the GST is split into CGST and SGST. If your customer is in a different state, the transaction is inter-state and you charge a single IGST instead.
The mistake happens when an invoice charges CGST plus SGST for a customer who is actually in another state, or charges IGST for someone in the same state. It is an easy error to make manually, especially when you copy last month's invoice for a different customer and forget to change the tax treatment along with the name.
Why it matters: the tax type on the invoice flows into your GSTR-1, and from there into your customer's ability to claim input tax credit. Get it wrong and you have a mismatch that surfaces during reconciliation, an unhappy customer whose credit is stuck, and an invoice that does not stand up to scrutiny. Correcting it after the fact means amendments, credit notes, and awkward conversations.
How to avoid it: the tax split should never be a manual decision. It should be computed automatically from the customer's state versus yours, every single time. When the system knows both states, there is simply no opportunity to pick the wrong one. (If you ever need to check a figure by hand, our free GST calculator works out CGST/SGST/IGST instantly, no login.)
- Invoice numbers that don't reset at the financial year GST expects your invoices to follow a consecutive, unique series, and that series should restart at the start of each financial year on 1 April. A format like ACME/2025-26/0001 rolling over to ACME/2026-27/0001 is exactly what an auditor expects to see.
The problems are subtle. Some businesses never reset, so the numbers just keep climbing year after year. Others reset but leave gaps, an invoice 0007 followed by 0009 with no 0008 to be found. Others accidentally create duplicates, two different invoices both numbered 0042 because two people were issuing at once, or because a spreadsheet was copied.
To an officer reviewing your records, gaps and duplicates are red flags. A gap suggests a deleted or hidden invoice. A duplicate suggests poor control over your books. Even when the explanation is perfectly innocent, you are now in the position of having to prove it, which is exactly the position you want to avoid.
How to avoid it: numbering should be atomic and automatic. The system should assign the next number in sequence at the moment of issue, prevent two invoices from ever sharing a number, and handle the financial-year reset for you so you never have to remember it on the first of April.
- Missing, guessed, or wrong HSN/SAC codes Every item on a GST invoice is supposed to carry the correct HSN code (for goods) or SAC code (for services). These codes are not decoration. They classify what you sold, and the classification is tied to the applicable tax rate.
The mistake usually sounds harmless in the moment: "I'll just put something close," or leaving the field blank because looking up the right code feels like a chore. But a wrong HSN code can imply a wrong rate, and a wrong rate is a direct compliance problem. A missing code on an invoice that is required to carry one is itself a defect under the invoicing rules.
This gets more dangerous as a business grows, because the threshold for how many HSN digits you must report depends on turnover, and the expectations tighten as you scale. A habit of guessing codes that was tolerable as a tiny shop becomes a real liability as a larger MSME.
How to avoid it: keep the correct code attached to each product or service once, so it auto-fills every time you bill that item, and use a tool with HSN/SAC search built in rather than relying on memory or a stale spreadsheet column. (If you just need a compliant starting point, see our free GST invoice format.)
- Credit notes issued after the Section 34 deadline This one costs real money, and almost nobody knows the rule until it bites them.
When you need to reduce the value of a supply, perhaps because of a return, a discount agreed later, or a billing correction, you issue a credit note. But a credit note only reduces your GST liability if it is issued within the window set by Section 34(2) of the CGST Act: broadly, by 30 November of the financial year following the year of the original supply.
Issue it inside that window and your output tax comes down as expected. Issue it even a day later and the credit note is, for tax purposes, worthless. You can still document the commercial adjustment, but you no longer get to reduce the GST you owe. For a business issuing credit notes against large invoices, missing this deadline can mean absorbing tax that should never have been yours to pay.
How to avoid it: the deadline is calculable per invoice, so it should be calculated for you. The right system knows the date of the original supply, works out the Section 34 cut-off, and stops you from issuing a credit note that would be invalid, before you rely on it.
- Editing an invoice after it has been issued In a spreadsheet, an invoice is just a file, and a file can always be changed. That flexibility is precisely the problem.
Once an invoice is issued to a customer, it is legally final. The correct way to fix something afterwards is through a credit note, a debit note, or a properly documented revised invoice, each of which leaves a visible, defensible trail. What you must not do is quietly open the original file, change a figure, and re-save it.
Silent edits destroy the one thing an audit relies on: a consistent record of what was actually issued and when. When the copy in your books no longer matches the copy your customer received, or the version you filed in your return, you have a discrepancy with no clean explanation. The infamous invoice_final_v3_FINAL.xlsx is funny right up until someone asks which version was the real one.
How to avoid it: use a draft-then-issue workflow. Edit as much as you like while it is a draft. The moment you issue, the invoice should lock, take its permanent number, and become read-only, with any later change forced through the proper credit or debit note route and logged.
- Getting the title of the document wrong Not every billing document is a "Tax Invoice," and using the wrong title is a quiet but genuine compliance error.
A registered business making a taxable supply issues a Tax Invoice. A business registered under the composition scheme cannot charge GST in the normal way and must instead issue a Bill of Supply, with the appropriate declaration. A supply to an unregistered consumer, or certain other cases, may simply be an Invoice. The correct title is dictated by your registration status and the nature of the transaction, not by personal preference or whatever template you happened to copy.
Businesses get this wrong when they grab a generic template and label everything "Tax Invoice" regardless of their actual GST status, or when a composition dealer issues documents that look like standard tax invoices charging GST they are not entitled to charge. Both create problems that are entirely avoidable.
How to avoid it: the document title should follow from your data. If the system knows your registration type and the customer's status, it can title each document correctly on its own, and print the right declarations and footnotes that go with each type.
- Forgetting reverse charge, and the declaration that goes with it Reverse charge mechanism (RCM) is one of those areas that feels niche until it applies to you, at which point getting it wrong is conspicuous.
Under RCM, for certain specified supplies, it is the recipient rather than the supplier who is liable to pay the GST. When an invoice is for a reverse-charge supply, the tax should be handled accordingly and the invoice must carry the specific declaration that tax is payable on a reverse-charge basis. It also needs to be marked correctly so it reports properly in the returns.
The mistake is either ignoring RCM entirely, charging tax normally on a supply where the recipient should be accounting for it, or remembering the concept but forgetting the required declaration on the face of the invoice. Either way the document does not match the law.
How to avoid it: treat reverse charge as a setting on the invoice, not something to remember to type. When RCM is flagged, the tax treatment, the printed declaration, and the way the entry is reported should all adjust together, automatically.
Why these mistakes are so common, and so invisible Look at the seven together and a pattern emerges. None of them is exotic. None requires bad intent. They are the natural result of doing detailed compliance work by hand, in tools that were never built for it.
A spreadsheet does not know which state your customer is in, so it cannot warn you about the wrong tax split. It does not understand financial years, so it will happily let your numbering drift. It has no concept of Section 34, so it cannot stop a late credit note. It treats your issued invoice as just another editable file. Every one of these mistakes is, at root, a tool problem dressed up as a human one.
That is also the good news. A problem caused by the wrong tool is solved by the right one. You do not need to become a GST expert or memorise the CGST rules. You need a system that has those rules built into how it behaves, so the compliant path is simply the default path, the one that happens when you do nothing special at all.
How Apna Invoice is built to catch all seven We built Apna Invoice the other way around from most free billing tools. Instead of making a pretty PDF and hoping the details are right, it is engineered around the specific CGST rules that decide whether an invoice survives a GSTR-1 filing and an audit. The aim is simple: the invoice you issue today should still pass when your CA opens your returns next month, or when an officer reviews your books two years from now.
In practice that means the tax split is computed from your state and the customer's state, so CGST/SGST versus IGST is never a manual guess. Invoice numbering is atomic and resets automatically each financial year, with no gaps and no duplicates. Every line item carries its HSN/SAC code, with search built in. Credit notes are checked against the Section 34(2) deadline per invoice, so you are stopped before you issue one that would be worthless. Issued invoices lock and become read-only, giving you a clean audit trail instead of a folder of "final_FINAL" files. The document titles itself correctly as a Tax Invoice, Bill of Supply, or Invoice based on your data. And reverse charge is a single toggle that adjusts the tax, the declaration, and the reporting together.
When month-end comes, you can export the reports your CA actually asks for, GSTR-1 and GSTR-3B summaries, hand over clean books, and file in minutes rather than days. And because correctness is the default, you get all of this without having to think about any of the seven mistakes above. (Comparing your options first? Our roundup of the best free GST invoice generators in India for 2026 lays out how the leading tools stack up.)
It is free during beta, with unlimited invoices and customers, no credit card required, and your data stays on servers in India in line with the DPDP Act. It is built and actively maintained in India by Datasoft Technologies, with real people on WhatsApp and phone when you need them.
The bottom line The dangerous invoice mistakes are not the obvious ones. They are the quiet ones, the wrong tax split, the numbering that never reset, the credit note issued a week too late, the file edited after the fact, that look completely fine until the exact moment they don't. By then, fixing them costs far more time and stress than getting them right would have.
You can keep crossing your fingers each filing season, or you can let the rules live inside your billing tool so the compliant invoice is the only kind you can issue. If you would rather stop worrying about which of the seven you might be making, that is precisely what we built.
Create your free Apna Invoice account and issue your next GST-compliant invoice in about 60 seconds.
Frequently asked questions What is the most common GST invoice mistake in India? Charging the wrong tax type on inter-state sales. When the customer is in a different state, the invoice must charge IGST, not CGST plus SGST. Place of supply is decided by the customer's state, and getting it wrong makes the invoice non-compliant and can block the customer's input tax credit.
Do GST invoice numbers have to reset every financial year? Your invoice series should restart at the beginning of each financial year using a consistent, unique format, and should never contain gaps or duplicates. Numbering that never resets, or that has missing or repeated numbers, is a frequent audit flag.
What is the deadline to issue a GST credit note? Under Section 34(2) of the CGST Act, a credit note reduces your GST liability only if it is issued by 30 November of the financial year following the original supply. Issued after that, it no longer reduces the tax you owe.
Can I edit a GST invoice after it has been issued? No. An issued invoice is legally final. Corrections should go through a credit note, debit note, or a properly documented revised invoice. Silently editing the original breaks the audit trail and creates discrepancies between your books, your customer's copy, and your filed returns.
How can I avoid these GST invoice mistakes automatically? Use GST-compliant invoicing software that computes the tax split from the customer's state, resets numbering each financial year, keeps HSN/SAC codes on every line, locks issued invoices, and tracks credit-note deadlines. Apna Invoice is built around these rules and is free during beta.