GSTR-1 Mistakes Meesho Sellers Make — And How to Avoid Notices

Most GST notices to Meesho sellers trace back to one root: the GSTR-1 was filed from memory or rough totals instead of from the platform's own sales report. The department cross-checks your filing against what Meesho reports about you — TCS filings, e-commerce supply data — and mismatches surface automatically. The five mistakes below cause nearly all of it, and a 30-minute pre-filing routine prevents every one.

Key Takeaways

Your GSTR-1 is cross-checked against Meesho's own filings — mismatches surface on their own.
File from the downloaded GST/sales report, never from memory or bank credits.
Returns need credit notes — skipping them inflates your reported sales.
Wrong or missing HSN codes are avoidable notice bait.
Reconcile TCS every period — accept what matches, question what doesn't.

The Five Mistakes

Mistake	Why it triggers trouble	The fix
Sales don't match Meesho's report	Cross-check with TCS/operator data flags the gap	File from the downloaded report, always
No credit notes for returns	Reported sales stay inflated; tax overpaid	Raise credit notes for return-adjusted orders
Wrong or missing HSN	Rate/classification queries	Fix HSN once per SKU, at listing level
TCS never reconciled	Operator-reported figures diverge from yours	Match TCS credits every filing period
GSTR-1 vs GSTR-3B mismatch	The two returns disagree on the same month	Build 3B from the same workings as GSTR-1

Notice that none of these are exotic — they're all versions of "the filing didn't come from the report", which is why the fix is one routine, not five disciplines. A mismatch you find is a correction in the next period's return; a mismatch the system finds is a notice with a deadline.

Match the Meesho Report Before Filing

The pre-filing routine is mechanical. Download the period's GST/sales report from the panel — the GST report download guide shows where — and treat it as the source of truth for taxable value. Adjust for returns via credit notes rather than by quietly shrinking the sales figure: the gross-sales-minus-credit-notes structure is what keeps your filing explainable when questioned. Then carry the same workings into GSTR-3B so the two returns can never disagree. The full filing calendar and flow is in GST return filing for Meesho sellers — GSTR-1 typically lands by the 11th monthly, or the 13th after the quarter under QRMP.

TCS and HSN — the Quiet Notice Triggers

Meesho collects TCS under GST on your supplies and reports it against your GSTIN; those credits appear on the portal for you to accept. Reconcile them every period — download the TCS certificate and match it to your own sales workings; a divergence means one side is wrong, and you want to find it before the system does. HSN discipline is simpler: assign the correct code per product once, using HSN codes for Meesho sellers, and reuse it consistently in filings. Both checks depend on the same foundation: order-level numbers you trust. A tool like TrackEcom does this automatically — it reconciles every order, flags each deduction, and shows your real per-order profit so nothing slips through.

FAQs

Why did I get a GST notice as a Meesho seller?

Usually a mismatch: your GSTR-1 disagrees with what Meesho reported about your sales through TCS filings, or your GSTR-1 and GSTR-3B disagree with each other.

Should GSTR-1 sales match the Meesho sales report exactly?

Yes in structure: gross supplies from the report, with returns handled as credit notes — so the department's cross-check against operator data reconciles cleanly.

How do I handle returns in GSTR-1?

Through credit notes against the original supplies, not by silently reducing the sales figure — the paper trail is what makes the numbers defensible.

What is TCS reconciliation for GST?

Matching the TCS Meesho collected and reported against your own sales workings each period, and accepting the credits on the portal — divergences are early warnings of a filing mismatch.