Invoicing mistakes are rarely about carelessness. They are about asking a human operator to remember, on every invoice, things a system should decide: which HSN applies, how the tax splits, what was already billed. The pattern in all ten mistakes below is the same — the fix is a control, not a reminder. For the foundations, start with our pillar guide to what GST billing software is.
1. Wrong or missing HSN code and GST rate
The classic. An item is billed at 12% that should be 18%, or with an HSN that belongs to a different product family. The cost arrives twice: the customer's input-credit claim breaks (souring the relationship), and the shortfall surfaces at filing or assessment with interest and penalty exposure.
The control: map every item to its HSN and rate once, in the item master — bulk import the item↔HSN↔GST mapping if you have hundreds of items — so each invoice line picks the code and rate automatically. When rate notifications land, update the master once, with your CA, instead of hoping every operator heard the news. See GST Tax Invoicing.
2. The wrong CGST/SGST vs IGST split
An intra-state sale charged as IGST, or an inter-state sale split into CGST and SGST. The totals may even match — which is what makes it dangerous. The returns will not reconcile, and the buyer's credit lands in the wrong ledger.
The control: the split should be decided by the system from the buyer's GSTIN and delivery state against your registration — never typed. If your software asks the operator to choose the tax type per invoice, it is a template, not billing software.
3. Missing or invalid buyer GSTIN
A B2B invoice without the buyer's GSTIN — or with a mistyped one — cannot support the buyer's input-credit claim, and it degrades your party-wise GST reporting at return time. It usually happens when parties are created in a hurry during billing.
The control: capture GSTINs in the party master, validate the format at entry, and bulk-import them when onboarding many parties. At filing time, the party-wise GST report — covered in the essential billing reports — makes missing GSTINs visible before your CA finds them.
4. Billing from memory, not against the dispatch
The invoice is typed fresh — items, quantities, rates — instead of being pulled from the order or dispatch it bills. Every fresh keying is a chance for quantity drift ("we shipped 96, billed 100"), rate drift, or a wrong item variant. Worse, an invoice with no reference to its source document cannot be reconciled against it later.
The control: raise every invoice against its source — pick the order or dispatch, and let the lines flow in with an against-dispatch reference. The invoice is then a financial view of a real movement, not a re-typing exercise.
5. Double billing the same dispatch
Two people bill the same delivery, or a part-billed dispatch is billed in full a second time. The customer catches it (embarrassing), or does not (worse — the reversal comes months later as a disputed credit note).
The control: a used-quantity guard. The system tracks, per dispatch line, how much has already been invoiced, and a new invoice can only bill the remainder. In Fast Billing this is structural — the same dispatched quantity cannot be billed twice, and cancelling an invoice releases its quantity so re-billing stays correct. The mechanics are detailed in invoice cancellation and audit controls.
6. Shipping and never billing
The mirror image of mistake 5, and quieter: goods leave on a challan, the invoice is "to be raised", and never is. Nothing looks wrong — there is simply revenue missing. Most SMEs discover these at stock-take or year-end, long after the customer relationship has moved on.
The control: a weekly order-vs-billed (pending-to-bill) report that lists every order or dispatch with an un-billed remainder. Every line is either an invoice to raise today or a conversation. It is the single highest-value report in the billing report stack.
Want these controls instead of reminders?
See the double-bill guard, against-dispatch invoicing and the pending-to-bill report live on your own items — in a 30-minute Fast Billing Software demo.
7. Editing or deleting an invoice instead of cancelling it
A posted invoice turns out wrong, so someone edits it in place — or deletes it. Now the printed copy in the customer's hands disagrees with the system, the invoice series has a hole, and the audit trail is broken. Auditors and GST officers both read gaps as red flags.
The control: posted invoices are immutable. The two legitimate paths are a formal cancellation (the invoice moves to a cancelled state, visible in the register, its dispatched quantity released for re-billing) or a credit/debit note that adjusts the value while leaving the original intact. Which applies can depend on filing status — confirm with your CA. Full treatment in invoice cancellation, audit trails and controls.
8. Credit notes floating free of their invoices
Goods come back and a credit note is raised "for the party" — with no reference to the invoice it reverses. The ledger stops reconciling invoice-by-invoice, GST returns show credits that match no supply, and six months later nobody can say which delivery the credit was for.
The control: credit notes raised automatically on the sales return, against the original dispatch and invoice. The link exists by construction, the ledger stays clean, and returns reconcile. See Credit & Debit Notes.
9. Forgetting charges, rounding and amount in words
Freight is paid but never billed; packing is billed to some parties and forgotten for others; totals are hand-rounded inconsistently; the amount in words is missing or does not match the figure. Individually small, collectively these erode margin and invite disputes — an invoice whose words and figures disagree is a document a customer can sit on.
The control: charge heads (freight, packing, insurance) configured once and applied per invoice; automatic rounding; and the total converted to words in Indian numbering by the system, so words and figures can never disagree. A monthly charges report shows what was actually recovered.
10. Unrecorded receipts, unadjusted advances — and re-keying it all into Tally
The billing side looks fine, but payments live in a diary: receipts not recorded against specific invoices, advances never adjusted, and the outstanding report fiction. Then, at month-end, someone re-types every invoice into accounting — introducing a second layer of drift between what was billed and what the books say.
The control: record every receipt against the invoices it pays, adjust advances systematically, and let the billing system post invoices, receipts and notes to Tally as vouchers with GST — no re-keying, no drift. Receipt discipline is the foundation of collections, covered end-to-end in how to reduce outstanding receivables; the mechanics live in Payments, Receipts & Follow-up and Accounts, Vouchers & Expenses.
The summary table — mistake, cost, control
| # | Mistake | What it costs | The control |
|---|---|---|---|
| 1 | Wrong HSN / rate | Broken input credit, interest & penalty exposure | Item↔HSN↔GST master, bulk import |
| 2 | Wrong CGST/SGST vs IGST | Returns that never reconcile | Split decided from GSTIN & state, never typed |
| 3 | Missing / invalid GSTIN | Buyer's credit claim fails | Party master validation, bulk GSTIN import |
| 4 | Billing from memory | Quantity and rate drift, no reconciliation | Invoice raised against order / dispatch |
| 5 | Double billing | Disputes, delayed reversals | Used-quantity guard |
| 6 | Shipping, never billing | Silent revenue loss | Pending-to-bill report |
| 7 | Editing / deleting invoices | Broken trail, series gaps | Formal cancellation + credit note paths |
| 8 | Unlinked credit notes | Unreconcilable ledger and returns | Auto credit note against the invoice |
| 9 | Charges / rounding / words | Margin erosion, disputable invoices | Charge heads, auto rounding, amount in words |
| 10 | Unrecorded receipts, re-keying | Fictional outstanding, drifting books | Receipts against invoices, Tally voucher posting |
What fixing the top three leaks is typically worth
Take a distributor raising 200 invoices a month on templates. If even 1% of dispatches ship un-billed, that is two invoices a month gone — often the difference between a good and bad month's margin. Add one double-billing dispute a quarter (a delayed credit note and a frostier customer), and one GST mismatch per filing cycle (hours of CA time to trace a mistyped rate). Moving the same volume onto linked, against-dispatch billing with an HSN master removes all three failure classes structurally — not by working harder, but by making the errors impossible to save.
Frequently asked questions
What are the most common invoicing mistakes Indian SMEs make?
The ten that cost real money: wrong or missing HSN code and GST rate; the wrong CGST/SGST vs IGST split; missing or invalid buyer GSTIN; invoices raised from memory instead of against the order or dispatch; billing the same dispatched quantity twice; shipping goods and never billing them; editing or deleting a wrong invoice instead of cancelling it or raising a credit note; credit notes that do not reference their invoice; forgetting charges, rounding and amount in words; and not recording receipts and advances, then re-keying everything into accounting. Each is preventable by a software control rather than operator memory.
What happens if I use the wrong HSN code or GST rate on an invoice?
You either overcharge the customer (who disputes it) or undercharge tax (which surfaces at filing or assessment with interest and penalty exposure), and the buyer's input-credit claim can break. The fix is structural: map each item to its HSN and rate once in the item master — bulk import if you have many items — so every line picks the correct code automatically. Review the mapping with your CA when rates change.
How do I prevent double billing the same dispatch?
Structurally: raise every invoice against its source dispatch or order, and let the system track how much of each dispatch line has already been invoiced. A new invoice can then only bill the un-invoiced remainder — the same quantity physically cannot be billed twice. Fast Billing Software implements exactly this guard, and cancelling an invoice releases its quantity for correct re-billing.
Should I edit or delete a wrong invoice?
Neither. A posted invoice is a tax document — editing breaks the audit trail and deleting leaves a series gap auditors will question. Cancel it formally (releasing the dispatched quantity for re-billing) if it should never have existed, or raise a credit or debit note against it if the value needs adjusting. Which path applies can depend on filing status — confirm with your CA.
Why must a credit note reference the original invoice?
Because a credit note adjusts a specific invoice. Unlinked notes make the ledger unreconcilable invoice-by-invoice, put credits in your GST returns that match no supply, and turn disputes unresolvable. Good software raises the credit note automatically on the sales return, against the original dispatch and invoice, so the link exists by construction.