Most GST trouble starts with small, repeated errors
GST is a self-assessed tax: you decide the rate, compute the liability, claim the credit and file the return, and the department reads the result later. That design rewards good process. It punishes carelessness. The penalties that reach a business usually trace back to a handful of mistakes repeated month after month rather than one dramatic error.
This guide sets out the errors that show up most often in practice for Indian businesses, what each one costs, and the routine checks that keep them out of the books.
Why the same errors survive
- Change is constant. Rates, forms, thresholds and portal features are notified and amended through the year.
- The work is done under time pressure. Invoices are raised, stock moves and returns fall due while the team is doing everything else.
- Manual entry spreads the same figure across the invoice, the return and the books, and every retyping is a chance for the numbers to differ.
- Ownership is unclear. Sales raises the invoice, accounts files the return, and the purchase register belongs to nobody in particular.
Error 1: the wrong HSN or SAC code
The Harmonised System of Nomenclature (HSN) classifies goods and the Services Accounting Code (SAC) classifies services, and the code decides the rate. A plausible-looking code that belongs to a nearby product can quietly create a short payment on every invoice for a whole year. Confirm the classification for each line you sell, record it against the item in your system, and review the list once a year and whenever a rate or entry changes.
Error 2: input tax credit that does not match the portal
Input tax credit (ITC) is not automatic. Credit for an invoice appears in your electronic credit ledger only after the supplier reports it, and the monthly credit figure is now pre-filled from the supplier's filing. Three failures cause most of the damage:
- Claiming credit on an invoice the supplier never reported. The credit is reversed later, usually with interest.
- Claiming credit on a document that is not a valid tax invoice. A bill of supply, a delivery challan or an invoice without the supplier's GSTIN will not support the claim.
- Claiming the same invoice twice when the purchase register and the return are handled by different people.
The cure is a monthly reconciliation of the purchase register, the invoices in hand and the pre-filled credit statement, done before the return is filed rather than after a notice arrives.
Error 3: credit on blocked items
Some purchases carry tax that is simply not creditable - motor vehicles used for personal travel, food and beverages, club and health memberships, goods lost, stolen or written off, and anything used for personal consumption, among others. Claiming this tax is a common error because the invoice looks like every other purchase. Mark such expenses as blocked in the accounting system so the credit is never offered to the return in the first place.
Error 4: invoices your customer cannot use
Your buyer needs your invoice to claim credit. A missing GSTIN, a serial number broken by a manual book, the wrong place of supply, or a rate stated without the tax amount all give the buyer a reason to reject the invoice and a reason to delay payment. Keep one numbering series per financial year per place of supply, print every required field, and let the software fill the invoice from the same data that feeds the return.
Error 5: place of supply and inter-state treatment
The place of supply decides whether a transaction is intra-state, charged as CGST plus SGST, or inter-state, charged as IGST. Billing a customer in another state as a local sale puts the tax under the wrong head, and correcting it later means credit notes and revised returns. For services the default rule and its exceptions are not always intuitive, so check the rule for the service before you raise the first invoice of a new kind.
Error 6: reverse charge and self-invoices
On notified supplies - goods transport by a road transporter, certain legal and professional services, and imports of service, among others - the recipient pays the tax instead of the supplier and must raise a self-invoice where the law requires one. Businesses miss it because no tax appears on the supplier's bill. Build a short list of your reverse-charge categories into the purchase approval step.
Error 7: late filing and mismatched returns
Every return has a due date, every late day carries a late fee, and interest runs on tax paid late. The more expensive problem is the mismatch: figures in the outward-supply return that do not agree with the summary return invite notices that take months to close. File from one reconciled set of books rather than an estimate typed at the last minute, and close each month before the next begins.
Error 8: ignoring e-invoicing, e-way bills and the annual return
e-invoicing applies above the notified turnover threshold, an e-way bill is needed for the movement of goods above the prescribed value, and the annual return and reconciliation statement fall due once a year. Each has its own threshold and its own consequence for non-compliance. The thresholds are revised from time to time, so confirm the current entry against the portal rather than an old note.
The monthly routine that prevents all of this
- Record every purchase invoice on the day it is received, with the supplier's GSTIN.
- Reconcile the purchase register with the pre-filled credit statement and mark blocked credits.
- Check the outward register against the invoices actually issued, including credit and debit notes.
- Confirm the place of supply and the tax head on every inter-state bill.
- File on time, then keep the working papers with the return for the period the law requires.
Let the books and the return share one source
Almost every error above becomes less likely when the invoice, the ledger and the return read from the same data. Finxora's GST verification tool lets you check a GSTIN before you raise the first invoice, and the balance sheet module groups ledger figures into schedules and notes from the trial balance, including a direct import of the trial balance exported from Tally as XML. See the tools at /tools, the balance sheet module at /balance-sheet-software, and the sample outputs at /samples.
