Amazon India settlement reconciliation
Last reviewed·ReconPe Editorial
Upload your Amazon India MTR and bank statement. ReconPe parses Settlement Report V2 (including GST-aware commission deductions and A-to-Z claim dispositions), matches every order via the ACRE probabilistic engine, flags commission variance against your category rate card, and tracks COD remittance age with per-marketplace SLA semantics. Exceptions from past cycles carry forward automatically — so late settlements from last month link to their original exceptions on this month’s run.
Where Amazon reconciliation breaks down manually
MTR volume keeps growing
A single month of Amazon India activity can produce tens of thousands of Merchant Tax Report lines. Manual VLOOKUP against bank statements breaks around 5,000 rows — performance, error rate, and review time all fall off a cliff.
Commission varies by category, tier, and FBA status
Amazon commission percentages shift by product category, seller tier, and whether the order is FBA or Merchant Fulfilled. Small variance per order compounds into meaningful leakage — and catches no one's attention in a spreadsheet.
COD remittances lag by 14–21 days
Cash-on-delivery orders settle on a different cycle from prepaid. Tracking remittance age per order requires stitching together MTR, payment report, and bank statement — across multiple settlement files.
GST on platform fees needs separate matching
Amazon India charges GST on platform fees (commission, closing, shipping) that must reconcile against your input tax credit claim. ReconPe separates fee components and their GST so you can file with confidence.
How ReconPe handles Amazon India
Rate-card aware commission variance
Upload your Amazon category rate card once. Every settlement line gets compared against expected commission, and variance is flagged per order with the exact rupee impact.
Bayesian match confidence per row
Every order ID match between MTR and bank credit gets a 0–100 confidence score using Fellegi-Sunter probabilistic weights — so you know which rows to review and which are safe to approve in bulk.
The details that decide an Amazon reconciliation
The difference between a reconciliation that ties out and one that quietly leaks is in how the Settlement Report is actually shaped. These are the specifics ReconPe handles because it reads the real file, not an idealised one.
Settlement Report V2 is an event stream, not a table
Each order shows up as several rows — Principal, Commission, FBA fees, promo rebates — on separate amount-type lines. ReconPe aggregates them back to one order before it audits anything, the way Amazon actually structures the file.
A-to-Z and SAFE-T are kept out of the order net
Amazon settles A-to-Z guarantee claims, SAFE-T reimbursements and chargebacks as their own adjustment rows, on their own cycle. ReconPe excludes them from the per-order net so a claim does not double-count against the settlement it lands in.
Commission checked against your category rate card
Load your Amazon category rates once and every order's commission is compared to expected = principal × rate%. Anything off by more than the greater of ₹1 or 0.5% is flagged as a slab mismatch, with the exact rupee over- or under-charge.
GST-on-fees and TCS split for your input credit
GST charged on commission, closing and shipping fees is separated from the fees themselves, and TCS collected under Section 52 is isolated — so the input-credit figure you carry into your filing is reconciled, not estimated.
The two files that must agree: MTR vs Settlement Report V2
Amazon India gives you two accounts of the same business. The MTR is the tax truth — invoice-level sales with GST detail, built for filing. The settlement report is the cash truth — fees, taxes withheld, and what was actually paid out. They cover the same orders on different cycles, and they disagree in known ways: an order invoiced this month settles next cycle, returns hit the two files at different times, and promos are cut differently. A complete Amazon reconciliation runs both joins — MTR ↔ settlement per order, and settlement ↔ bank per payout. In ReconPe each is a two-file reconciliation with the formats auto-detected.
Inside the settlement file, every order arrives as several amount-type rows. These are the lines and what each means for your money:
| Amount type | What it means for you |
|---|---|
| Principal | The item price the buyer paid — the base every percentage hangs off |
| Product / shipping tax | GST collected on the sale — passes through to your liability, not your margin |
| Promo rebate | Your funded discounts, netted off the principal |
| Commission | The category referral fee — check it against your rate card, not against memory |
| Closing / fixed fee | Per-item fee on a price-band slab |
| FBA fees (pick & pack, weight handling) | Fulfilment charges on FBA orders only |
| TCS (CGST/SGST/IGST) | 0.5% collected under GST Sec 52 — reclaimable via GSTR-2B/8 |
| TDS (Sec 194-O) | 0.1% income-tax deduction — must appear in your 26AS to claim |
| Adjustments (A-to-Z, SAFE-T, chargebacks) | Claim settlements on their own cycle — keep them out of per-order nets |
And when the bank deposit is smaller than the settlement net: that’s usually the reserve — Amazon holds part of the balance as unavailable, so a payout is settlement net, minus new reserve, plus prior reserve released. Reconciling at the payout level makes the reserve movement visible instead of mysterious.
A worked example: a commission slab error inside Settlement Report V2
Illustrative — one Amazon India order, after ReconPe aggregates its Settlement Report V2 event lines back into a single order. The figures are examples; the variance is the kind that compounds across a category.
- Principal (item price)
- ₹2,199.00
- Commission — category rate card 8.5%
- − ₹186.92
- Commission — actually deducted at 11%
- − ₹241.89
- Closing + shipping fees
- − ₹68.00
- GST on platform fees (for your ITC)
- − ₹55.78
- ReconPe flags
- ₹54.97 commission variance + ₹55.78 GST-on-fees to claim
ReconPe checks the deducted commission against your category rate card per order, and separates GST-on-fees so the input-credit figure you carry into your GSTR-2B is reconciled, not estimated. COD orders on the same report are aged from delivery, so an 18-day remittance shows up as overdue rather than silently lost.
Frequently asked
How often does Amazon India publish the MTR?
Amazon publishes the Merchant Tax Report weekly, with settlement reports on a 7–14 day cycle depending on seller tier. ReconPe auto-detects whether you've uploaded a weekly MTR or a monthly consolidated report and adjusts the matching window accordingly.
Does ReconPe work with Amazon FBA and Merchant Fulfilled orders together?
Yes. Each order line in the MTR carries the fulfilment type, and ReconPe's rule engine applies the appropriate commission and fee expectations per order. You don't need to split files by fulfilment type.
What commission variance does ReconPe detect on Amazon India settlements?
ReconPe compares actual commission charged against your category rate card for every order. It flags three patterns: commission charged at a higher slab than category allows, closing fee charged outside expected range, and shipping fee variance (weight-banded differences).
How does COD remittance tracking work?
Every COD order is tagged with remittance status and age. ReconPe flags orders where remittance is overdue (more than 14 days for most tiers), produces a remittance ageing report, and matches against bank credits to confirm when funds actually land.
Can ReconPe handle returns and RTO deductions?
Yes. Return and RTO (return-to-origin) entries in the MTR are matched against the original order, and ReconPe flags cases where refund amount differs from original settlement or where return shipping was charged.
Do I need to clean the MTR before uploading?
No. ReconPe's schema detection reads MTR files as-is — the format changes Amazon has pushed over the last 3 years are all supported. No column mapping required for first run.
Why is my bank deposit less than my settlement report total?
Usually a reserve. Amazon holds part of your balance as an unavailable reserve (commonly tied to delivery-date policy and account level), so a payout equals the settlement net minus the new reserve plus whatever prior reserve was released. Two other causes: adjustments from earlier cycles (returns, claims) netted into this payout, and non-order charges. Decomposing the payout line by line answers it — which is exactly what reconciling the settlement report against the bank credit does.
What is the difference between the MTR and the settlement report?
The MTR (Merchant Tax Report) is the tax truth — invoice-level sales data with GST detail, built for filing. The settlement report is the cash truth — fees, charges, and what Amazon actually paid you. They cover the same orders on different cycles with different cuts, and they disagree in known ways (timing, returns, promo treatment). Reconciling the two against each other, and the settlement against the bank, is how you know both your filing numbers and your cash are right.
How do I claim back the TCS and TDS Amazon deducts?
TCS (0.5% under GST Section 52) flows into your GSTR-2B/GSTR-8 as GST credit, and TDS (0.1% under Section 194-O) must appear in your Form 26AS as income-tax credit. Both are recoverable only if the amounts the marketplace deducted actually show up in those statements — ReconPe's GST suite triangulates settlement ↔ GSTR-2B/8 ↔ 26AS to confirm they do.
Why VLOOKUP breaks at 2,000 orders a month
A 3am WhatsApp from a Flipkart seller: 'the file crashed again.' Riya opens it — 4,800 rows, OrderID duplicated six times per order. Direct matching dies at this scale. Set matching is the answer.
Reconcile your other settlements
Reconcile your next Amazon India settlement in minutes
Free tier — 5 free reconciliations, 1 marketplace. Upload your next MTR and see variance you were missing in Excel.
Start free