Amazon GST reconciliation means matching three numbers that rarely look the same at first glance: what you invoiced the buyer, what Amazon actually paid you, and what's recorded in your books. None of these figures is wrong by default — they measure different things — but if you don't reconcile them every month, small gaps compound into a return that doesn't match your bank balance or your GSTR-3B.
This guide sets out what should and shouldn't match, the usual causes of a mismatch, and a repeatable monthly process to close the gap.
The three numbers that must tie out
| Figure | Source | What it represents |
|---|---|---|
| Invoice value | Amazon tax/MTR report | Taxable value + tax charged to the buyer — the basis for GSTR-1 |
| Settlement value | Amazon payment/settlement report | What Amazon actually deposits to your bank, after fees |
| Books value | Your accounting records / bank | What was recorded as revenue and what actually hit your bank account |
These three won't be equal, and that's expected — the reconciliation isn't about forcing them to match, it's about explaining the difference between each pair with a specific, quantifiable reason.
Why Amazon settlements never equal invoice value
Between the invoice value and the amount that lands in your bank, Amazon deducts several categories of fees. A typical breakdown looks like this:
| Deduction | Nature |
|---|---|
| Referral fee | Commission on the sale, category-dependent |
| Fulfilment/shipping fee | Charged if using Amazon's fulfilment or shipping service |
| Closing fee | Fixed fee per unit sold, in some categories |
| Storage and other service fees | Periodic charges unrelated to a specific order |
| Refunds and chargebacks processed in the settlement cycle | Reduce the net payout for the period |
Amazon issues its own tax invoices for these fees, which are relevant to your input tax credit but have nothing to do with the outward supply value you report in GSTR-1. Reconciliation means separating "the gap is fees I have an invoice for" from "the gap is something unexplained" — only the second category needs investigation.
Reconciling TCS credit
Amazon deposits TCS against your GSTIN based on net taxable supplies for the period (sales less returns). This shows up as a credit in your electronic cash ledger, distinct from your GSTR-1 figures. To reconcile it:
- Confirm the TCS credit shown on the GST portal against Amazon's own TCS/tax collection statement for the period, not against your gross sales figure.
- Remember TCS is calculated on net value after returns, so comparing it directly to gross invoice value from your MTR report will show a mismatch by design.
- Where the amounts genuinely disagree after accounting for returns, the discrepancy is worth raising with Amazon support directly rather than adjusting your own books to match an unverified figure.
Common mismatch patterns
| Symptom | Likely cause | Fix |
|---|---|---|
| Settlement is lower than expected even after accounting for known fees | A return or chargeback processed in this settlement cycle for an order invoiced earlier | Trace the specific order in the returns report; net it against the correct invoicing period, not the settlement period |
| Books revenue doesn't match invoice value from MTR report | Revenue booked on settlement/bank date instead of invoice date | Book revenue on invoice date; treat settlement as a separate cash-flow event |
| TCS credit on portal is lower than expected | Returns netted off before TCS calculation, or a timing difference between order date and TCS deposit date | Compare against Amazon's TCS statement for the exact period, not your sales report |
| GSTR-1 taxable value doesn't match GSTR-3B outward supply figure | Manual entries or corrections made in one return but not the other | Reconcile GSTR-1 against GSTR-3B before filing either — see the guide on fixing GST mismatches |
A monthly reconciliation workflow
- Pull the MTR/tax report, settlement report, and returns report for the same invoice-date period.
- Match invoice value to settlement value order by order (or in bulk via order ID), tagging each deduction against a fee category.
- List any settlement line that isn't explained by a known fee or return as an open item for investigation.
- Reconcile TCS credit on the GST portal against Amazon's TCS statement for the period.
- Confirm books revenue reflects invoice date, and that bank receipts tie to settlement batches, not individual orders.
- Close the period only once open items are either explained or formally flagged for follow-up with Amazon.
When a mismatch points to a filing error vs a books error
Not every gap means your GSTR-1 is wrong. A mismatch between settlement and invoice value is almost always a books/cash-flow matter, not a filing error — fees and timing explain most of it. A mismatch is more likely to be a genuine filing issue when the taxable value in your MTR report itself doesn't match what ended up in your GSTR-1 — for example, a row excluded by mistake, or a return netted against the wrong period. Isolate which side of the equation the discrepancy sits on before deciding whether to amend a return or simply fix a books entry.
OneBooks GST imports Amazon sales, returns and settlement data together so invoice value, fees, and net settlement sit side by side rather than in separate downloads, with discrepancies surfaced from Admin > Detailed Reports. If you haven't yet built your GSTR-1 from this same data, start with GSTR-1 filing for Amazon sellers, and use the bank statement parser to match settlement deposits against your bank statement automatically.
Advertising spend and other non-order deductions
Beyond the order-level fees already covered, your Amazon settlement can include deductions unrelated to any single order — advertising spend on sponsored product campaigns, subscription fees, or one-off service charges. These sit outside the order-level fee categories and can be mistaken for an unexplained shortfall if you're only reconciling order by order. Pull the full settlement report's summary section, not just the order-level detail, so these account-level charges are identified and matched against your books separately from product sales.
Keeping a short running log of these account-level deductions by category, updated each settlement cycle, makes it far quicker to spot when a new deduction type appears or when a familiar one changes in size unexpectedly.
Frequently asked questions
Should the amount Amazon settles to my bank match my invoice value?
No, not directly. Amazon deducts referral fees, fulfilment fees, and other service charges before settlement, so the settled amount is always lower than the gross invoice value by a specific, explainable margin.
Why doesn't my TCS credit match my total sales figure?
TCS is calculated on net taxable supplies after returns for the period, not gross sales. Compare it against Amazon's own TCS statement rather than your gross MTR report total.
What's the first thing to check when settlement is lower than expected?
Check whether a return or chargeback for an earlier invoice was processed in this settlement cycle — that's the most common explainable cause beyond standard fees.
Does a settlement-vs-invoice gap mean my GSTR-1 is wrong?
Usually not. That gap is typically explained by fees and timing, which is a books matter. A GSTR-1 error is more likely when the taxable value in your source report itself doesn't match what you filed.
How often should I reconcile Amazon settlements against invoices?
Monthly, aligned to your GST filing cycle, so any unexplained gap is caught and investigated while the underlying order details are still easy to trace.
How OneBooks GST fits into this
OneBooks GST is a GST and accounting platform for Indian businesses. It keeps imported marketplace data, returns and adjustments as separate reviewable figures so a mismatch can be traced to its source row.
OneBooks GST keeps source data, reviewed output and exports as separate records, so a figure can be traced back rather than reconstructed.
