Common GST Notices for E-commerce Sellers
GST notices to e-commerce sellers are rarely the result of an officer taking personal interest in your business. Most are system-generated: automated comparisons between your returns, the marketplaces' filings, and your suppliers' data throw a difference over a threshold, and a notice goes out. That is oddly good news — a data-triggered notice is answerable with data. This guide covers the notice types marketplace sellers actually receive, what triggers each, and a response discipline that resolves them at the first reply.
The notices, and what fires them
| Notice theme | Trigger | Marketplace-seller flavour |
|---|---|---|
| GSTR-1 vs GSTR-3B difference | Liability declared in GSTR-1 exceeds tax summarised in 3B (or vice versa) | Credit notes reflected in one return but not the other; auto-population overridden manually |
| ITC mismatch (3B vs 2B) | Credit claimed beyond what GSTR-2B supports | Fee invoices booked but platform filed late; platform credit notes not reversed |
| Operator data vs your returns | Marketplace GSTR-8 supplies exceed your declared sales | Net-payout booking, missed report imports, returns netted inconsistently |
| Non-filing / late filing | A return not filed for a period | Dormant additional-state GSTINs from warehouse programs, forgotten after volumes moved |
| Scrutiny / audit intimation | Risk parameters, or persistent smaller flags | Accumulation of unexplained differences over periods |
Notice the pattern: four of the five are pure reconciliation failures. Sellers who run the monthly disciplines in our mismatch guide mostly meet these notices pre-answered.
Also mind how notices arrive. Service happens through the portal and registered contact details, and a notice sitting unread in the portal's notices section is still a served notice with a running clock. Build a routine of logging into every GSTIN you hold — including quiet warehouse-state registrations — at least monthly, and keep the registered email and mobile current, because a stale contact on a dormant GSTIN is how sellers first learn of a problem at the recovery stage rather than the query stage.
The response discipline
- Read the notice literally. Identify the exact provision, period, amount, and the data comparison being made. Half of a good reply is answering the question actually asked.
- Note the deadline and respond within it — on the portal. Notice replies generally go through the portal, and an unanswered notice escalates by default. If time is short, a reasoned request for extension beats silence.
- Rebuild the comparison yourself. Reproduce the department's two numbers from your own data. The difference will decompose into timing, policy, and error components.
- Reply with a reconciliation, not a narrative. A period-wise table walking from your figure to theirs, with each difference labelled and evidenced (report extracts, credit-note registers, 2B downloads), resolves data notices. Assertions without workings invite the next notice.
- Pay what is genuinely due, promptly. Where the rebuild reveals real short-payment, voluntary payment with your reply generally positions you far better than contesting the undeniable — your CA will weigh interest and procedure.
- Route everything through a professional. A qualified CA or tax professional should settle the legal characterisation, draft the reply, and decide what to concede versus contest. This article prepares you for that conversation; it does not replace it.
What makes replies fail
- Replying with marketplace report screenshots instead of books-based reconciliations — the department compares returns, not portals.
- Explaining one period's difference with an argument that contradicts the previous period's reply.
- Missing the deadline and converting a data query into an assessment.
- Conceding amounts without decomposition, paying for timing differences that were never liabilities.
The cheapest notice is the one that never issues
Every trigger in the table is a comparison you can run before the department does. Books that tie to marketplace settlements monthly, credit notes reported on time, ITC claimed strictly against 2B, and TCS reconciled before acceptance leave the automated systems nothing to flag. That bookkeeping layer is what TallySutra automates — converting Amazon, Flipkart, and Meesho reports into balanced, settlement-reconciled TallyPrime vouchers with a CA review step, so your returns are filed from books that already agree with the operators' data. For the deeper preparation exercise, see audit preparation for e-commerce sellers.
Notice forms, monetary thresholds, and procedural timelines evolve, and this article deliberately quotes none of them. Treat it as educational orientation — the moment a notice arrives, engage a qualified CA or tax professional and respond through them within the stated deadline.
Frequently asked questions
Why did I get a notice when my totals look right to me?
Most notices are system-generated from specific comparisons — GSTR-1 vs 3B, 3B vs 2B, or your returns vs marketplace GSTR-8 data — over a period. Rebuild the exact comparison cited, and the difference usually decomposes into timing and reporting-basis items.
Can I ignore a small-value GST notice?
No. Unanswered notices escalate by default regardless of amount, and a pattern of ignored queries feeds scrutiny risk. Reply within the deadline with a reconciliation, even if the answer is a two-line timing explanation.
Should I pay the amount demanded immediately?
Pay promptly only what your own rebuild confirms is genuinely due — voluntary payment of real short-falls positions you well. Do not pay for differences that are timing or reporting-basis artefacts; decompose first, and let your CA drive the call.
TallySutra turns Amazon, Flipkart and Meesho reports into reconciled, reviewed TallyPrime vouchers — duplicate-safe, with every rupee traceable to its source row.
Book a 30-minute demo