Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Amazon Pay has two distinct settlement modes: marketplace sellers face weekly payouts net of referral fee, FBA fulfilment, returns, and 1% Section 52 TCS, while external-website merchants receive T+2 payment-gateway payouts with only MDR and 18% GST on MDR. Mixing the two causes misposted TCS credits and GSTR-8 versus GSTR-2B mismatches.
Mode classification routes every Amazon credit to the correct pipeline. Marketplace reconciliation joins Amazon MTR settlement report against bank credit and matches TCS line items against GSTR-8 plus GSTR-2B Part II plus Form 26AS Part F. External-merchant Amazon Pay reconciliation runs the standard payment-gateway pattern on settlement_id plus UTR plus net amount.
Pipeline router on merchant type, TCS matcher keyed on GSTIN plus tax period plus order ID, referral-fee category rate table, and FBA fulfilment-fee decomposer.
Marketplace sellers get a reconciled TCS credit aligned to GSTR-2B, disaggregated revenue per order net of referral and FBA fees, return-adjustment trail. External merchants get order-level revenue and MDR ITC claim.
Amazon Pay settlement reconciliation differs depending on whether you are a third-party seller on Amazon’s marketplace or a merchant using Amazon Pay as a checkout method on an external website. For marketplace sellers, the TCS deduction under GST Section 52 — applied at 1% on the taxable value of each transaction — creates a compliance reconciliation step that pure payment gateway settlements do not have. Understanding which mode applies is the first step in setting up the correct reconciliation workflow.
The Two Modes of Amazon Pay Settlement
Mode 1: Amazon Marketplace Seller Settlement
Sellers on Amazon.in receive weekly payouts that cover sales proceeds minus a set of deductions: Amazon’s referral fee (category-dependent), fulfilment fees for FBA sellers, advertising charges, return and refund adjustments, and — critically — TCS at 1% of the net taxable value of each transaction under Section 52 of the CGST Act.
This settlement is not a pure payment gateway settlement. The deduction structure is more complex, the cycle is weekly rather than T+2, and the compliance obligations extend to GSTR-8 reconciliation.
Mode 2: Amazon Pay on External Websites
When Amazon Pay is deployed as a payment method on a merchant’s own website — outside Amazon’s marketplace — it functions as a standard payment aggregator. Settlement follows a T+2 cycle, MDR is deducted at the applicable rate, GST at 18% applies to MDR, and the merchant receives a settlement report through the Amazon Pay dashboard. TCS under Section 52 does not apply in this mode, because the merchant is not selling through Amazon as an e-commerce operator.
How Amazon Pay Settlement Reconciliation Works
Marketplace Mode: Step-by-Step
Amazon provides sellers with settlement reports through Seller Central under Reports > Payments. Each report covers one settlement period and includes: Order ID, transaction date, product type, sales amount, referral fee, fulfilment fee, advertising deduction, TCS deduction, and net settlement amount. The settlement_id in Amazon’s report corresponds to the NEFT credit in the seller’s bank account.
The TCS deduction line is the component that distinguishes this reconciliation from a standard payment gateway process. Amazon deducts 1% TCS on the taxable value and files GSTR-8 by the 10th of the following month. Until Amazon’s GSTR-8 is filed, the TCS amount appears only in the settlement report — not yet in GSTR-2B. Sellers should not credit TCS against output liability in GSTR-3B before confirming the amount in GSTR-2B.
External Merchant Mode: Step-by-Step
For merchants using Amazon Pay on their own websites, the reconciliation follows the standard gateway pattern: download the settlement report from the Amazon Pay dashboard, match the settlement_id to the NEFT bank credit, and match each transaction in the report to the corresponding order in the OMS using Order ID or Amazon Pay Transaction ID.
Amazon Pay Settlement: Comparison of Two Modes
| Dimension | Marketplace Seller | External Merchant (Amazon Pay gateway) |
|---|---|---|
| Settlement cycle | Weekly (post-shipment) | T+2 working days |
| MDR deducted | No (referral fee model) | Yes (rate varies by instrument) |
| GST on MDR | No | Yes, 18% on MDR |
| TCS Section 52 | Yes — 1% on taxable value | No |
| Referral fee | Yes (category-dependent) | No |
| GSTR-8 reconciliation | Required | Not required |
| Primary match key | Settlement ID + Order ID | Settlement ID + Payment/Order ID |
Deduction Structure: Amazon Marketplace Settlement Example
| Deduction Component | Rate / Basis | Example (₹10,000 sale) |
|---|---|---|
| Amazon referral fee | 5–40% depending on category | ₹500 (5% example) |
| TCS under Section 52 | 1% of net taxable value | ₹100 |
| Return adjustment | Per returned order | ₹0 – ₹N |
| Net settlement to seller | After all deductions | ₹9,400 (before returns) |
India-Specific Compliance in Amazon Pay Reconciliation
The TCS reconciliation requirement for Amazon marketplace sellers is governed by Section 52 of the CGST Act. Amazon files GSTR-8 by the 10th of the following month, and the TCS amounts auto-populate in the seller’s GSTR-2B under Part II. The reconciliation task is to verify that TCS in the settlement report for Month M matches the GSTR-2B entry for Month M — any difference must be investigated before the GSTR-3B is filed.
Form 26AS also carries TCS data in Part F. Sellers who reconcile TCS only from the settlement report and skip GSTR-2B and Form 26AS risk claiming incorrect TCS credits. The correct sequence is: settlement report → GSTR-2B (after 10th of following month) → Form 26AS → GSTR-3B.
For FBA sellers, the return and adjustment entries in settlement reports require matching each deducted amount to a return authorisation number in the OMS. High return-rate categories — electronics, apparel — generate disproportionate exception volumes from return adjustments, making systematic exception classification essential.
Finance teams managing both Amazon marketplace and Amazon Pay external gateway transactions benefit from a payment gateway reconciliation platform that handles both settlement structures and routes TCS exceptions to the compliance workflow separately from MDR exceptions. For organisations with multi-platform operations — including Amazon alongside Razorpay or Cashfree — reconciliation software India deployed with ISO 27001:2022 certified infrastructure provides a single exception queue with variance taxonomy (FEE_DEDUCTION, TAX_DEDUCTION, ROUNDING) and a full audit trail for every match and override.
Auditing Amazon Fees for Overcharges
Amazon’s fee structure contains several areas where systematic overcharges accumulate if not actively audited.
SAFE-T claims. The Seller Assurance for E-Commerce Transactions (SAFE-T) programme allows sellers to file reimbursement claims for warehouse damage, lost inventory, or incorrect fee deductions. The filing window is 90 days from the event date — claims submitted after this window are automatically rejected. Once a SAFE-T claim is filed, sellers have 3 days to respond to any information request from Amazon. If Amazon denies the claim, the seller has one appeal window of 7 days. Critically, if a customer files an A-to-Z Guarantee claim on the same order, the SAFE-T claim is blocked — the A-to-Z process takes precedence and must resolve first.
Commission category errors. Amazon’s referral fee ranges from 2% to 22% depending on product category. The most costly fee error is incorrect category classification — a product listed under a 15% commission category that should be classified under a 7% category loses 8% of revenue on every unit sold. Sellers should audit their category assignments quarterly against Amazon’s published fee schedule.
Volumetric weight overcharges. For FBA sellers, shipping fees are calculated on actual weight or volumetric weight (Length x Width x Height / 5000, in centimetres), whichever is higher. Incorrect package dimension data in Amazon’s system — often from the initial catalogue entry — results in inflated volumetric weight charges across every shipment. Correcting dimension data retroactively requires filing a remeasurement request.
Settlement report retention. Amazon retains settlement reports for only 90 days in Seller Central. Finance teams that do not download and archive reports within this window lose access to the transaction-level detail needed for annual reconciliation and tax audit support.
November 2025 closing fee change. From November 2025, Amazon revised the closing fee policy so that closing fees on returned orders are no longer reimbursed to the seller. Previously, if a customer returned an item, the closing fee was credited back. This change increases the effective cost of returns and must be factored into return-adjusted profitability calculations.
The Reserve Bank of India regulates Amazon Pay India’s payment aggregator operations, setting the settlement and nodal account requirements that govern how payout timing is structured for external merchants using Amazon Pay as a checkout method.
Frequently asked questions about Amazon Pay settlement reconciliation are answered below.