Meesho GST Report Guide for Suppliers
Meesho suppliers file GST on the strength of one export: the GST sales report from the supplier panel. It is the invoice-level record of everything you supplied, returned and had RTO'd, with the tax math already done per row. Suppliers who understand this file stop fearing GSTR-1; suppliers who do not end up reverse-engineering their own sales at filing time. Here is the report explained, and how to get it into TallyPrime so filing becomes mechanical.
What each row contains
One row describes one event on one sub order:
| Column | Meaning | Used for |
|---|---|---|
| Sub Order No | Unique sub order identifier | Traceability, duplicate detection, return matching |
| Order Date | When the order was placed | Period allocation |
| Event Type | Sale, Return or RTO | Voucher type: sales voucher vs credit note |
| GST Rate | Slab applied to the item | Rate-wise sales ledger selection |
| Taxable Value | Pre-tax supply value | GSTR-1 taxable turnover |
| IGST / CGST / SGST | Tax amounts by type | Output tax ledgers |
| Total Invoice Value | Taxable value plus tax | Party ledger amount |
| End Customer State | Delivery destination | Place of supply; drives IGST vs CGST/SGST and state-wise tables |
Three columns that decide your filing accuracy
Event Type is first: Sale rows become sales vouchers, while Return and RTO rows become credit notes reversing value and tax; miss the reversals and you over-declare turnover and overpay tax. The distinct handling of RTO, including stock re-entry, is covered in our RTO treatment guide. End Customer State is second: intra-state supplies carry CGST+SGST, inter-state carry IGST, and GSTR-1's B2C tables want state-wise summaries, so the state must survive into your Tally vouchers as place of supply. GST Rate is third: rate-wise reporting is mandatory, so your books need one sales ledger per slab rather than a single sales account.
From report to GSTR-1-ready books
- Post every Sale row as a sales voucher at Total Invoice Value: rate-wise sales ledger for Taxable Value, output tax ledgers for the IGST or CGST/SGST split, Meesho party ledger for the total.
- Post every Return and RTO row as a credit note referencing the original sub order.
- At month end, Tally's rate-wise sales summary should equal the report's totals by rate, and the place-of-supply summary should equal the report's state-wise totals. Any difference is a missed or duplicated row, findable by Sub Order No.
- Cross-check TCS: Meesho collects 0.5% u/s 52 on net taxable supplies, and the credit surfacing on the GST portal should correspond to your net figure; the reconciliation lives in our TCS and TDS compliance guide.
Importing without retyping
The report is designed for humans to read, not for Tally to ingest, and Meesho offers no public seller API to fetch it programmatically. The practical bridge is file-based conversion: TallySutra accepts the GST sales report exactly as exported from the supplier panel, validates every row (tax split must sum to Total Invoice Value, GST Rate must be a real slab, Sub Order No must be new), and generates the sales vouchers and credit notes as balanced Tally XML with place of supply preserved. Failures queue as exceptions for CA review rather than entering your books, and re-uploading a corrected export is duplicate-safe. One boundary stated plainly: TallySutra prepares books; it does not file GST returns. Filing stays with you or your CA, working from Tally data that finally matches the marketplace record. See pricing for what volume-based plans look like.
The habits that keep you compliant
- Export the report monthly, immediately after month end, and archive the original file.
- Never edit the export; corrections happen in Meesho's system and get re-exported.
- Reconcile books to report to portal in that order, before filing.
- Route rate or classification doubts to your CA before they multiply across thousands of rows.
The GST report is the closest thing a Meesho supplier has to a single source of truth. Build your books directly from it, verify the totals mechanically, and GSTR-1 becomes a report you print rather than a puzzle you solve.
As volumes grow, add one more monthly comparison: the count of rows by Event Type in the report against the count of vouchers by type in Tally. Value-level ties can mask offsetting errors, but counts rarely lie, and a mismatch of even one row points to a specific missing document rather than a vague discrepancy. It is the fastest sanity check available and takes under a minute once books are posted item-wise from the report.
Frequently asked questions
Can I prepare GSTR-1 directly from the Meesho GST report?
It contains what GSTR-1 needs for your Meesho supplies: taxable values, rate-wise tax splits, credit-note events and End Customer State for place of supply. Best practice is to route it through your books, import into Tally, reconcile totals, then prepare the return, so books and filing never diverge. Combine with other sales channels and file via your CA or filing software.
Why must End Customer State be preserved in my Tally vouchers?
Because it determines tax type and reporting geography. Supplies delivered within your registration state carry CGST plus SGST; other states carry IGST; and GSTR-1's B2C tables are summarised state-wise. If the state is dropped during import, your Tally tax ledgers may still balance, but the state-wise summary will not reconcile with the report, and errors surface as portal mismatches later.
Do RTO rows affect my GST turnover?
Yes. RTO rows represent supplies that failed and were reversed, so they reduce net taxable turnover through credit notes, just as customer Return rows do. Ignoring them means declaring and paying tax on sales that never completed. The reversal documentation and its timing across filing periods should follow a consistent pattern agreed with your CA, especially when RTO events land in a later month than the sale.
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