How to Import Amazon MTR Report into TallyPrime (2026)
Every GST-registered Amazon India seller eventually has to move marketplace sales into TallyPrime — for GSTR-1 workings, for the profit and loss account, and for the CA's year-end file. The source document for this is Amazon's Merchant Tax Report (MTR), an invoice-level GST report available in Seller Central. This guide covers what the MTR contains, the three practical ways to get it into Tally, and the verification checks that catch errors before they reach your books.
What the Amazon MTR report contains
The MTR is downloaded from Seller Central's Tax Document Library and comes in B2C and B2B variants. The B2C file includes, per line, your Seller GSTIN, Invoice Number, Invoice Date, Transaction Type, Order ID, SKU, Quantity, Ship To State, Tax Exclusive Gross, the applicable IGST/CGST/SGST rate and tax amounts, and the final Invoice Amount. Transaction Type is the key field: Shipment rows are sales, Refund rows become credit notes, and Cancel rows need their own handling. One order can span several rows — one per SKU — so rows must be grouped by invoice number before voucher creation.
Mapping MTR columns to Tally voucher fields
Whether you import manually or with a tool, the mapping logic is the same:
| MTR column | TallyPrime destination |
|---|---|
| Invoice Number | Voucher number / reference |
| Invoice Date | Voucher date |
| Transaction Type | Voucher type (Sales or Credit Note) |
| Ship To State | Place of supply |
| Tax Exclusive Gross | Sales ledger amount (taxable value) |
| IGST/CGST/SGST tax | Respective duty ledgers |
| Invoice Amount | Party ledger total (incl. tax) |
Whether a sale is interstate (IGST) or intrastate (CGST + SGST) follows from comparing the state code in your Seller GSTIN with the Ship To State. The MTR already splits the tax correctly — your import must simply preserve that split, not recompute it.
Three ways to import the MTR into TallyPrime
- Manual entry. Workable below roughly a hundred invoices a month. Beyond that, typing speed becomes the bottleneck and transposition errors creep into tax amounts.
- Tally Release 7.1 native plug-in. TallyPrime 7.1 ships an Amazon Data Import Plug-In. It is file-based, works for Amazon only, and requires an active TSS subscription. See our detailed comparison at TallySutra vs the Tally Amazon plug-in.
- A converter like TallySutra. You upload the official MTR file, the system validates every row, groups rows into balanced vouchers, and produces Tally-ready XML. Note this is file upload of Seller Central reports — TallySutra does not connect to Amazon's API.
Step-by-step: MTR to Tally XML with TallySutra
- Download the month's MTR from Seller Central — exact menu paths are in our guide on downloading Amazon MTR and settlement reports.
- Upload the file on the Amazon to Tally workspace. The parser detects the report type and GSTIN automatically.
- Review the exception queue. Rows with an unmapped SKU, a missing GST rate, or a state-code conflict are held back instead of being imported wrong.
- Send the batch for CA review if your workflow uses the approval step, so a professional signs off before anything touches Tally.
- Export the XML and load it into TallyPrime — either through Tally's local HTTP interface (the desktop Gateway app pushes vouchers directly) or via Import Data from the file.
- Re-import safely whenever Amazon revises a report. Duplicate detection keys on invoice identifiers, so an overlapping upload does not create a second voucher.
Verify after import — five quick checks
- Voucher count equals the number of distinct invoice numbers in the MTR, not the raw row count.
- Total taxable value in Tally equals the sum of the Tax Exclusive Gross column.
- IGST, CGST, and SGST ledger totals match the MTR tax columns rate-wise.
- Pick one Refund row and confirm it landed as a credit note against the right party and place of supply.
- Run Tally's GSTR-1 preview and compare taxable turnover with the MTR summary.
A clean MTR import is the foundation; settlement reconciliation and fee accounting sit on top of it. How you present specific transactions in returns can depend on your facts, so have your CA confirm treatment before filing. When you are ready to try the workflow, the desktop Gateway and web app are available on the download page.
Frequently asked questions
Can TallySutra pull my Amazon sales automatically via API?
No. TallySutra works in file-upload mode: you download the official MTR and settlement reports from Seller Central and upload them. There is no live API connection to Amazon today, though an SP-API application is in progress. File mode has one advantage — every voucher traces back to an official Amazon report you can show an auditor.
Does the MTR import create one voucher per row?
No. The MTR has one row per SKU, so a multi-item order spans several rows sharing one invoice number. A correct import groups rows by invoice number and creates one sales voucher per invoice, with item or ledger lines inside it. Importing row-by-row inflates your voucher count and breaks invoice-level GSTR-1 reporting.
Which TallyPrime versions accept the generated XML?
TallyPrime imports voucher XML through its local HTTP interface or the Import Data menu, and both routes work on current TallyPrime releases — you do not need Release 7.1 or a TSS subscription for XML import. The native Amazon plug-in in Release 7.1 is a separate, TSS-dependent feature.
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