Amazon MTR to GSTR-1 JSON — without the manual re-keying
Amazon's Merchant Tax Report (MTR) is the file you file GSTR-1 from — but it's also the one that trips up every conversion. Upload it to Ankeksha and get portal-ready GSTR-1 JSON in under a minute, with Amazon's specific quirks handled for you.
Try it freeThe Amazon MTR, decoded — where conversions go wrong
- The tax columns are decimal half-rates. Cgst Rate 0.025 + Sgst Rate 0.025 is a 5% supply, not 2.5%. Read it literally and every rate on your GSTR-1 is halved — Ankeksha recombines the halves to the real slab.
- Dates carry timestamps. GSTR-1 wants DD-MM-YYYY; the time is stripped automatically.
- State is uppercase text, not a code. "TAMIL NADU" is mapped to the correct 2-digit place-of-supply (33).
- B2B vs B2C is decided by a column, not a flag. The B2B MTR has a Customer Bill To Gstid column; the B2C file doesn't. Detection keys off that, so invoices land in B2B vs B2CS/B2CL correctly.
- Table 14 (ECO) is the hard part. Amazon operates 15+ state-wise GSTINs; supplies are grouped by operator GSTIN for Table 14 reporting.
How Ankeksha converts it
Upload the MTR and Ankeksha detects it is an Amazon file from the column shape, classifies each line (B2B / B2CL / B2CS / CDNR / CDNUR), aggregates HSN and B2CS, validates against GSTN rules, and outputs portal-ready GSTR-1 JSON. No platform dropdown, no column mapping.
Frequently asked questions
Does it handle both the B2B and B2C MTR?
Yes — it detects which one from the Customer Bill To Gstid column and classifies accordingly.
Will it fix the 0.025 half-rate issue?
Yes — half-rate CGST/SGST columns are recombined to the correct slab automatically.
Does it cover Table 14 for Amazon's state-wise GSTINs?
Yes — ECO supplies are grouped by operator GSTIN.
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 selling on Flipkart or Meesho? GSTR-1 Studio handles every marketplace in one place.
Create an account