Why Your GST Invoice Got Rejected — And How to Fix It

Nobody wants to hear this from a client.

"Sorry, our accounts team rejected your invoice. Can you send a corrected one?"

It's awkward, it delays your payment, and if it keeps happening, it starts to color how professional you look, even when the actual work was excellent.

Here's the frustrating part — most invoice rejections come down to small, fixable mistakes. Nothing complicated, just things that got missed in the rush of the day.

Here's the most common reasons GST invoices get rejected in India, and what to actually do when it happens to you.

Reason 1 — Wrong or missing GSTIN

The single biggest reason corporate clients bounce an invoice back.

Either your own GSTIN is wrong, the client's is wrong, or — more common than you'd think — it's just left blank because you weren't sure whether they were registered at all.

Corporate accounts teams run a GSTIN check before processing anything, and if it doesn't match what's on the GST portal, the invoice comes straight back.

Fix it: verify your own GSTIN on gst.gov.in before your first invoice, then save it correctly once so it never gets retyped wrong. For a client's GSTIN, always ask directly the first time rather than guessing off a business card or an old email — save it correctly once, and it auto-fills from there.

Reason 2 — Wrong invoice date or format

GST law has specific requirements here, and the date format is one of them.

Some older templates use DD/MM/YY, others MM-DD-YYYY, and corporate accounting software sometimes just can't parse the non-standard ones and flags the whole invoice.

There's a timing rule too — a service invoice needs to be issued within 30 days of the service being completed (45 for banking and insurance). Outside that window, the invoice technically isn't valid under GST rules at all.

Fix it: stick to DD/MM/YYYY, and issue the invoice the same day the work's done, not a week later when it comes to mind. A tool that auto-formats and timestamps the date at creation removes this entirely.

Reason 3 — Missing HSN or SAC code

This surprises a lot of people. Plenty of freelancers genuinely don't know what a SAC code is, so the field stays blank, or someone grabs a random number off the internet without checking it.

A blank HSN or SAC code makes the invoice non-compliant outright, and a lot of corporate clients will reject on this basis alone — even if they don't, it becomes a problem at GSTR-1 filing or during an audit.

Fix it: every product has an HSN code, every service has a SAC code — look up the right one for your specific work (we've published SAC tables by industry on the blog if you want a starting point). Save it correctly against your service once, and it auto-fills forever after.

Reason 4 — CGST/SGST charged instead of IGST, or the other way round

This is the one that causes the most actual trouble, because the invoice looks correct at a glance — the numbers add up, the percentage is right, but the type is wrong.

You're in Delhi, your client's in Mumbai — that's IGST 18%, not CGST 9% + SGST 9%. Both total the same 18%, but from a filing standpoint they're completely different, and a Delhi client simply can't claim ITC against CGST/SGST from a Delhi-registered business on an inter-state deal. Only IGST works there.

When this slips through, the client's accounts team calls it a compliance issue and sends the invoice straight back.

Fix it: know your client's state before you invoice — same state means CGST+SGST, different state means IGST. Or use a tool that detects this automatically off the client's saved state, which removes the decision (and the mistake) entirely. We genuinely haven't seen a wrong-GST-type invoice from anyone using this correctly — that's not luck, it's just the point of building the logic in rather than relying on memory.

Reason 5 — Invoice numbers not sequential

GST rules require sequential numbering within a financial year — no gaps, no duplicates, no jumping from INV-23 to INV-47 because a few test invoices got deleted along the way.

This matters at audit time specifically — an auditor looking at gaps in your sequence starts wondering what happened to the missing numbers. Corporate clients are also increasingly checking for sequential numbering as a basic compliance signal on their end too.

Fix it: never type invoice numbers manually if you can help it. A system that auto-assigns and tracks the sequence removes gaps and duplicates entirely — even voiding an invoice should generate a credit note rather than creating a hole in the sequence.

Reason 6 — Place of supply left out

More common on B2B service invoices than on goods.

Place of supply decides which state's GST rules actually apply — for goods it's usually the delivery location, for services it depends on the type. A lot of freelancers just don't include this field at all, and stricter corporate compliance teams will reject an invoice missing it.

Fix it: add the place of supply — for most services, it's simply the recipient's location, so a Karnataka client means Karnataka is the place of supply, and IGST applies if you're elsewhere. A tool that pulls this from the client's saved state handles it automatically.

Reason 7 — Invoice amount not matching the PO

Less a GST issue, more a procurement one. A company's procurement team raises a Purchase Order at a specific amount, and their accounts team matches your invoice against it when it arrives.

Show up with ₹1,18,000 including 18% GST when the PO says ₹1,00,000 (quoted without GST, as it turns out), and the mismatch gets flagged regardless of whether the GST math itself was correct.

Fix it: clarify upfront whether your quote is inclusive or exclusive of GST, and send a proforma invoice before the final tax invoice so the client can verify the amount before their PO's even raised — a proforma that shows the base amount and GST clearly separated saves this exact back-and-forth.

What to actually do when an invoice gets rejected

Ask the client exactly what was wrong — "rejected" alone isn't specific enough, you need the actual reason: wrong GSTIN, wrong tax type, missing field, amount mismatch.

Don't reissue with the same invoice number. If the original was already submitted and bounced, issue a proper revised invoice with a new number, referencing the original — or a credit note if that fits the situation better, without breaking your existing sequence.

Fix the root cause, not just this one invoice. Wrong GSTIN? Update it in the client's saved profile so it doesn't happen again. Wrong GST type? Check other recent invoices to the same client for the same mistake.

And call rather than just email. If payment's stuck behind a rejected invoice, a quick WhatsApp message or call to the accounts contact moves things faster than an email thread going back and forth.

Why this actually matters

Rejected invoices aren't just annoying — they're expensive. Every one means delayed payment, and delayed payment means you're effectively funding your client's business with your own cash, interest-free. For a small business or freelancer, that gap can genuinely be the difference between rent being on time or not.

The best way to handle rejections is to not have them in the first place, which sounds obvious but really does come down to a system that gets the basics right automatically every time — correct GSTIN, correct GST type, correct SAC code, correct sequence, correct date — without you having to hold all of it in your head on every single invoice.

That's exactly what GST Maker was built to do.

👉 Try it free at gstmaker.com

Five minutes of setup. Zero invoice rejections after.