AnkekshaGet startedMeesho report to GSTR-1 JSON — tax split computed for you
Meesho's report is the fiddliest of the three: the tax split often isn't spelled out, invoice numbers can be missing, and returns live in a separate signal. Ankeksha handles all three so the GSTR-1 comes out clean.
Try it freeThe Meesho report, decoded
- The tax split must be computed. Unlike Amazon or Flipkart, Meesho often does not hand you CGST/SGST/IGST directly — Ankeksha derives the split from the taxable value, rate, and place of supply.
- Detection keys off sub_order_num + eco_tcs_gstin. That pairing is how a Meesho file is recognised.
- Returns key off cancel_return_date. The returns file is matched on that field and routed to credit notes.
- Invoice numbers are often missing. Ankeksha falls back to the sub_order_num so every line still has a stable reference for the return.
How Ankeksha converts it
Upload the Meesho file and it is detected by sub_order_num and eco_tcs_gstin, the tax split is computed, returns are matched on cancel_return_date, lines are classified (B2B / B2CL / B2CS / CDNR / CDNUR), validated, and portal-ready GSTR-1 JSON comes out.
Frequently asked questions
Meesho does not show the tax breakup — will it still work?
Yes — the CGST/SGST/IGST split is computed from taxable value, rate, and place of supply.
What about Meesho returns?
The returns file is matched on cancel_return_date and classified as credit notes.
My Meesho export has no invoice numbers.
It falls back to sub_order_num, so lines are still uniquely referenced.
Does it export Tally XML?
Tally XML export is on the roadmap; today it produces portal-ready GSTR-1 JSON.
See the JSON in under a minute
Also on Amazon or Flipkart? GSTR-1 Studio handles every marketplace in one place.
Create an account