Marketplace Reconciliation: A CA's Settlement Playbook

Marketplace reconciliation is the process of proving, order by order, that the amount a marketplace deposited into your bank account equals what it actually owed you after every fee, tax deduction, return and adjustment. For an Indian seller on Amazon or Flipkart, this is not optional housekeeping. Your GST liability is computed on gross sales, your income is recognised on accrual, and the settlement credit hitting your bank is neither of those numbers. If your books record the net deposit as revenue, your financials are wrong, your GSTR-1 is wrong, and you are almost certainly leaking margin to deductions nobody is verifying.

This playbook covers how a Chartered Accountant reads an Amazon settlement report and a Flipkart settlement report, the full reconciliation process from order report to bank credit, the deduction heads that cause mismatches, and how to dispute and recover money when they do.

What Marketplace Reconciliation Actually Means (and Why Settlement ≠ Sales)

A settlement is a net figure. The marketplace takes your gross collections, subtracts marketplace commission and closing fees, logistics charges, refunds, taxes it is required to withhold, and prior-period adjustments, adds reimbursements, and pays out what remains. Three documents therefore tell three different stories:

• Order report — what customers bought, at gross value.
• Settlement report — what the marketplace computed as payable, with every deduction line by line.
• Bank statement — what actually arrived, sometimes split across cycles, sometimes reduced by a reserve.

Marketplace reconciliation is the discipline of tying all three together at order level. Every order ID should trace to either a payment, a deduction you can verify, or an explained open item such as a return in transit or a dispute. Getting this right matters because your books must show gross revenue, fee expenses, input credit for GST on marketplace fees, and receivable balances for taxes withheld — none of which is visible if you only book the bank credit.

Anatomy of an Amazon Settlement Report: Every Line Item Decoded

Download the date-range or flat-file settlement report from Seller Central (Payments → Reports Repository). The key columns are settlement ID, transaction type, order ID, amount type, amount description and amount. Read them in this order:

• Order lines — product charges, shipping charges collected from the customer, gift wrap. This is your gross.
• Refund lines — amounts debited back for customer returns and cancellations, referencing the original order ID.
• Fee lines — referral fee (commission), fixed closing fee, Easy Ship or weight-handling fees, FBA fulfilment and storage fees where applicable.
• Other transactions — reimbursements, corrections, and service fee adjustments.
• Withholding lines — TCS collected under GST law and TDS under income-tax law, both deducted before payout.
• Reserve and transfer summary — any account-level reserve withheld and the final deposit amount.

One practical note: the settlement report shows fee amounts net of embedded tax splits. The GST component on each fee is detailed in the marketplace's fee invoice, and you need both documents to claim input credit correctly.

Anatomy of a Flipkart Settlement Report: Key Fields and Deduction Heads

Flipkart's settlement files from the Seller Hub are order-item-level. Each row typically carries the Order ID and Order Item ID, sale or invoice amount, settlement value, and the deduction heads applied to that line:

• Commission, fixed fee, collection fee
• Forward shipping fee and reverse shipping fee on returns
• Offer adjustments, distinguishing marketplace-funded discounts from seller-funded ones
• Seller Protection Fund credits where a claim was approved
• GST breakup on each fee, plus TCS and TDS withheld

Returns appear as negative settlement rows against the original order item, which makes them traceable — but only if you reconcile at order-item level rather than settlement-total level. Verify the fees against the rate card applicable to your category and fulfilment model, because rate cards are revised and category mapping errors are a common source of overcharging.

The Step-by-Step Reconciliation Process: From Order Report to Bank Credit

1. Export three files per marketplace, per cycle: the order report, the settlement report and your bank statement.
2. Normalise the data into one row per order item per transaction type. Sign conventions differ between marketplaces, so standardise refunds and fees as negatives before matching.
3. Compute the expected settlement per order from the applicable rate card: selling price minus expected commission, closing fee, logistics fee and taxes withheld.
4. Match actual versus expected and bucket every variance — fee variance, tax variance, return variance, or an order settling in a later cycle.
5. Tie the settlement to the bank. The net of each settlement ID should equal a bank credit; watch for partial transfers, reserves and amounts carried forward.
6. Post the accounting entries: gross sales, fee expenses with GST input credit, TCS and TDS as receivable balances, and the net receipt to bank or a merchant clearing account.
7. Age every open item and either dispute it or write it off with approval. Nothing should sit unexplained.

The Deductions That Cause Mismatches: Commission, Closing Fees, TCS, TDS, Returns and Logistics Charges

Most settlement mismatches trace back to a small set of heads:

• Marketplace commission and closing fees. Charged per the category rate card. Mismatches arise from rate revisions mid-cycle or SKUs mapped to the wrong fee category. Verify per order, not in aggregate.
• GST on marketplace fees. Every fee carries GST, which is claimable as input credit — but only against the fee invoice. Reconcile marketplace fee invoices to GSTR-2B every month.
• TCS under Section 52 of the CGST Act. Collected by the marketplace on your net taxable supplies at the notified rate. It reflects in your GSTR-2A and the annual GSTR-8A, and is available as electronic cash ledger credit. If the marketplace's GSTR-8 filing is delayed, your credit is delayed.
• TDS under Section 194-O. Income-tax withholding on the gross sales facilitated through the platform, at the rate in force. Verify the credit against Form 26AS and the AIS, and reconcile with the quarterly Form 16A. Rates under both provisions have changed since introduction, so confirm the current rate with your CA rather than relying on memory.
• Returns and refunds. Refund debits plus reverse logistics charges. If the returned item never reached your warehouse or arrived damaged, that is a recovery case, not a cost.
• Logistics and weight disputes. Shipping fees are computed on actual or volumetric weight; erroneous weight measurement inflates fees and is disputable with evidence.
• Storage, removal and reserve amounts — smaller individually, material in aggregate.

Raising Disputes and Recovering Money: SAFE-T Claims and Flipkart Seller Support Escalations

On Amazon, the primary recovery route is the SAFE-T claim (Seller Assurance for E-Commerce Transactions), filed from Seller Central for refund deductions where the item was not returned, was returned damaged, or where the deduction is otherwise covered by seller assurance. File within the window shown on the claim page — claims have time limits — and attach return tracking, images and weight proof. Lost or damaged FBA inventory follows a separate reimbursement case flow.

On Flipkart, raise issues through Seller Support with the order item IDs, and use Seller Protection Fund claims for return abuse, empty-box returns and similar cases. Escalate unresolved tickets through your account manager with the full ticket trail.

Whichever the platform, maintain a dispute register with claim IDs, amounts and ageing. Follow up weekly. Write off only after escalation is exhausted, and have your CA sign off on write-offs so the treatment is consistent in the books.

When to Move Off Excel: Automating Settlement Reconciliation into Tally or Zoho Books

Manual reconciliation in Excel works at low order volumes on a single marketplace. It breaks when you sell on several marketplaces, add a D2C store with payment gateway settlements, or when matching consumes days of finance effort every cycle. Spreadsheet matching also leaves no audit trail, handles cycle-boundary orders poorly, and depends entirely on one person's VLOOKUPs.

Automation changes the shape of the work: settlement and order files are ingested automatically, matching happens at order level, expected-versus-actual variances are flagged instead of discovered, and summarised entries post directly into your accounting system.

Marketplace reconciliation software like LogiRecon is built for exactly this. LogiRecon is a CA-led product — founded by a Chartered Accountant, with customer success staffed by CAs and finance professionals. It supports Amazon, Flipkart, Myntra and 10+ marketplaces along with Shopify and WooCommerce D2C stores, and Indian payment gateways including Razorpay, Cashfree, PayU and Easebuzz. It auto-posts reconciliation entries to Tally, Zoho Books and custom ERPs, commits monthly books by the 10th of every month, and cuts reconciliation time by up to 75% — which is what turns the playbook above from a monthly firefight into a routine close.

Frequently asked questions

What is marketplace reconciliation?

Marketplace reconciliation is the process of matching every order on a marketplace to the corresponding settlement line and bank credit, verifying each deduction — commission, fees, taxes withheld, refunds — against what should have been charged. It confirms that the net payout equals gross sales minus legitimate deductions, and isolates variances for dispute or recovery.

Why does my Amazon settlement amount not match my total sales?

Because the settlement is a net figure. Amazon deducts referral and closing fees, shipping and fulfilment charges, refunds for returns, TCS under GST law and TDS under income-tax law, plus adjustments and any reserve, before paying out. Your total sales are the gross starting point; the deposit is what remains after these heads. Reconcile line by line to verify each deduction.

What is the difference between TCS and TDS deducted on marketplace payouts?

TCS under Section 52 of the CGST Act is a GST collection by the marketplace on your net taxable supplies; it appears in your GSTR-2A and GSTR-8A and is usable as cash ledger credit. TDS under Section 194-O is income-tax withholding on gross facilitated sales; its credit appears in Form 26AS and the AIS and offsets your income-tax liability. Both apply at notified rates, which your CA should confirm.

How often should an e-commerce seller reconcile marketplace settlements?

Every settlement cycle, without exception — and a consolidated monthly close that ties all cycles to the bank and to your GST returns. Deduction disputes have time limits, so reconciling only at month-end or quarter-end means discovering recoverable amounts after the window to claim them has closed.

Can marketplace reconciliation be automated with Tally or Zoho Books?

Yes. Reconciliation software ingests settlement and order files, performs order-level reconciliation, flags variances and posts summarised entries directly into Tally or Zoho Books. LogiRecon, for instance, auto-posts entries to Tally, Zoho Books and custom ERPs and commits monthly books by the 10th of every month, replacing manual spreadsheet matching entirely.