What Is Marketplace Reconciliation? A Complete Guide for Sellers

The simple definition

Marketplace reconciliation is the process of comparing the orders you actually shipped against the payments a marketplace like Amazon, Flipkart, or Meesho eventually credits to your bank account — and flagging every place the two don't match.

In theory, this should be simple: you sell a product, the marketplace deducts its commission and fees, and pays you the rest. In practice, every settlement report bundles together hundreds of small deductions — commissions, shipping fees, RTO charges, TDS, TCS, promotional adjustments, returns — and it's extremely easy for errors to hide inside that bundle.

What actually gets reconciled

A proper reconciliation checks several things at once, order by order:

• Was this order paid at all, or is it missing from the settlement report entirely?
• Was the commission percentage correct for this category, or was a higher rate charged by mistake?
• Were shipping and RTO fees charged only once, and at the correct rate?
• If the order was returned, was the refund to the customer deducted correctly — and was any applicable reimbursement paid to you?
• Do the TDS and TCS amounts match what should have been deducted under the applicable rate?

Inside a settlement report: what the line items actually mean

A settlement report isn't a single number — it's a transaction-level ledger, and each marketplace structures it differently, though the underlying logic is the same everywhere: gross order value, minus a stack of deductions, equals net payout.

Amazon calls its report the Payments report, accessible from Seller Central under Payments → All Statements, generated on a rolling settlement cycle (commonly every 14 days, though high-volume sellers can be moved to shorter cycles). Each row is tagged with an order ID, a transaction type (Order, Refund, Adjustment, Service Fee), and a breakdown of item price, referral fee (Amazon's commission, which varies by category from roughly 2% to over 20%), FBA or Easy Ship fulfillment fees, and — critically for compliance — separate line items for TDS deducted under Section 194-O and GST TCS. Amazon also publishes a dedicated Transaction View filtered by 'Service Fee' and a consolidated TDS/TCS certificate under Reports → Tax Reports, which is the quickest way to cross-check the totals a spreadsheet reconciliation surfaces.

Flipkart's equivalent lives in Seller Hub under Payments, and its payout timing depends on seller tier: Gold and Platinum sellers are typically paid around 7 business days after the courier's first mother-hub scan, Silver around 10 days, and Bronze around 15 days, with disbursement batches run on fixed days of the week. The settlement report itself shows, per order, the gross selling price and then each deduction — marketplace commission, TCS, RTO or return adjustments for items reversed within the same cycle, and logistics/shipping charges — before arriving at net payout.

Meesho's Supplier Panel settles on a shorter, delivery-triggered cycle (commonly around 7 days after delivery confirmation) and exposes two files that need to be reconciled together: the Orders CSV (what was ordered, shipped, delivered, or returned) and the Payment Statement XLSX (what was actually paid). The Payments section also carries a separate 'Deductions and Compensations' view for penalties and waivers, and a 'Commission Tax Invoice' tab for the GST invoice Meesho raises on its own commission — a detail sellers often miss because it looks unrelated to the payout itself but affects input tax credit.

The common thread: every marketplace nets dozens of deduction types against gross sales before a rupee reaches your bank account, and the line items that matter most for compliance — TDS and TCS — are usually a single row buried among fee rows, not a headline number.

Why sellers can't just trust the dashboard

Amazon, Flipkart, and Meesho all provide seller dashboards with summary numbers, but summaries are exactly the problem — they show totals, not order-level detail. A settlement report might contain 3,000 line items for a single payment cycle. Spotting a ₹40 shortfall on one order inside that file manually is close to impossible, which is why so many sellers never catch it.

This is also why reconciliation isn't a one-time audit — it needs to happen every settlement cycle, because new orders and new errors are generated continuously.

The TDS mechanic: Section 194-O

Section 194-O of the Income Tax Act, 1961 (inserted by the Finance Act, 2020, effective 1 October 2020) requires every e-commerce operator — Amazon, Flipkart, and Meesho all qualify — to deduct tax at source on the gross amount of sales or services it facilitates for a seller, at the time of credit or payment, whichever is earlier.

The rate has changed: it was 1% from October 2020 until the Finance (No. 2) Act, 2024 reduced it to 0.1%, effective 1 October 2024. If a seller hasn't furnished a valid PAN or Aadhaar, the operator must deduct at 5% instead, under Section 206AA. The deduction doesn't apply at all if a seller's aggregate gross sales through that platform stay under ₹5 lakh in the financial year and a valid PAN or Aadhaar is on file. Deducted TDS is meant to be deposited with the government by the 7th of the following month.

For reconciliation purposes, what matters is this: 194-O TDS is advance income tax, not a marketplace fee. It reduces the cash you receive today, but it's a credit you're entitled to claim back — it shows up in your Form 26AS (usually within 30–45 days of quarter-end) and gets claimed in Schedule TDS of your ITR (typically ITR-3 or ITR-4 for most sellers) against your actual tax liability, TAN by TAN, one row per marketplace. If the amount deducted per the settlement report doesn't match what lands in 26AS, that mismatch either delays your refund or gets you a notice — so reconciling this line isn't optional bookkeeping, it's protecting money that's already yours.

The TCS mechanic: Section 52 of the CGST Act

Separately from income tax, Section 52 of the CGST Act, 2017 requires every e-commerce operator to collect tax at source on the net value of taxable supplies made through its platform — net meaning gross taxable supplies minus returns for that tax period.

This rate has also changed. From July 2017 it stood at 1% (0.5% CGST + 0.5% SGST for intra-state supplies, or 1% IGST for inter-state supplies). CBIC Notification No. 15/2024-Central Tax and Notification No. 01/2024-Integrated Tax, both dated 10 July 2024, halved it: the current rate is 0.5% (0.25% CGST + 0.25% SGST intra-state, or 0.5% IGST inter-state) on net taxable value. Marketplaces file this collection through Form GSTR-8 by the 10th of the following month.

Unlike 194-O TDS, GST TCS doesn't show up in Form 26AS — it flows through the GST system. Once the marketplace files GSTR-8, the TCS collected against your GSTIN appears in your GSTR-2B, and you claim it via the 'TDS and TCS Credit Received' statement on the GST portal, after which it lands in your Electronic Cash Ledger and can be used to offset GST liability. If the TCS on a marketplace's settlement report doesn't match what shows up in GSTR-2B for that period — a common failure mode when a marketplace corrects an earlier filing — the credit simply doesn't reach your cash ledger, and you either underclaim or have to chase it down manually months later.

Both 194-O and Section 52 exist for the same underlying policy reason: they give tax authorities a data trail on income earned through digital platforms, using the marketplace as a collection point instead of relying on the seller alone.

From reconciliation to books: why this isn't just a cash-flow exercise

It's tempting to treat reconciliation as purely a 'did I get paid correctly' check. That undersells what's at stake — the same settlement report feeds two separate compliance obligations, not one.

For GST, your sales figures, the TCS collected against you, and the net taxable value the marketplace reports all need to tie back to your own GSTR-1 and GSTR-3B filings. If your books show a sale the marketplace's settlement report doesn't (or vice versa), your outward supply figures and your TCS credit claim stop lining up — and GST officers do cross-check GSTR-2B against GSTR-3B claims. For income tax, the gross sales figure the marketplace attributes to you under 194-O should reconcile with the turnover you declare, and the TDS credit you claim should match what's actually in Form 26AS, not just what the settlement report says was deducted.

In other words, reconciliation is the bridge between 'what the marketplace says happened' and 'what your books say happened.' Skip it, and errors don't just cost you margin — they propagate into GST returns and income tax filings, where correcting them later is slower and, in some cases, invites scrutiny rather than a quiet fix.

Records: what to keep, and for how long

Reconciliation only works if the source documents survive long enough to be checked against later, and Indian tax law is specific about how long that has to be.

Under Section 36 of the CGST Act, 2017, every GST-registered seller must retain books of accounts and related records — invoices, settlement reports, credit notes — for 72 months (6 years) from the due date of filing the annual return for that financial year, longer still if an appeal, investigation, or other proceeding is ongoing at that point. For income tax, Rule 6F of the Income Tax Rules generally expects books and supporting documents to be kept for 6 years from the end of the relevant assessment year, and Section 149 gives assessing officers the power to reopen assessments for up to 3 years as a default, or up to 10 years where escaped income is claimed to exceed ₹50 lakh — which is a practical reason to lean toward the longer retention window rather than the bare minimum.

In practice this means keeping settlement reports, order-level CSVs, TDS certificates, GSTR-8 data, and your own reconciliation workings — not just the net payout figure — for at least six years, in a form you can actually search rather than a folder of unopened downloads.

Tools and methods: spreadsheets, ERPs, and dedicated software

There are three real ways sellers do this today, and each has a genuine tradeoff — none of them is a strawman.

Spreadsheet formulas (VLOOKUP/XLOOKUP or Power Query merges between your order report and the marketplace's settlement file) cost nothing beyond time and work fine at low volume — a few hundred orders a month, one marketplace, simple fee structures. They break down for three reasons as volume grows: order IDs don't always match 1:1 across files (partial shipments, split settlements, multi-cycle returns), fee taxonomies change without notice when a marketplace updates its report format, and nobody re-derives the TDS/TCS math by hand every cycle, so those columns get eyeballed rather than verified.

ERP integrations (Tally, Zoho Books, SAP Business One with GST/TDS modules) are the right call once reconciliation needs to flow directly into books of account — they can post journal entries automatically and keep your GSTR-3B input tied to what was actually reconciled. The tradeoff is setup cost and rigidity: mapping every marketplace's fee codes into your chart of accounts takes real configuration work, and most ERPs don't natively understand marketplace-specific quirks like Meesho's multi-cycle return deductions or Flipkart's tiered payout timing — they expect clean, already-reconciled data as input, not raw settlement files.

Dedicated reconciliation SaaS (including TheEcomWay's reconciliation engine) sits in between: it ingests the raw settlement and order reports directly from each marketplace, applies marketplace-specific matching logic — including the current 194-O and Section 52 rates — and shows only the orders where something doesn't add up, instead of asking you to build and maintain that logic yourself. The tradeoff is that it's a subscription cost rather than 'free' spreadsheet time, though for any seller past a few hundred orders a month, the hours saved (and the discrepancies caught inside the dispute window) tend to outweigh that cost quickly. The honest comparison: spreadsheets for low volume and full manual control, ERP integration for downstream accounting rigor once volume is high and stable, dedicated tools when the priority is catching discrepancies fast, every cycle, without building the matching logic from scratch.

Manual reconciliation vs. automated reconciliation

Some sellers try to reconcile manually in Excel, matching order IDs between their own sales records and the marketplace's settlement file. This works at a small scale, but breaks down quickly once volume crosses even a few hundred orders a month — the sheer number of fee types and edge cases makes manual matching slow and error-prone.

Automated reconciliation tools like TheEcomWay ingest your settlement and order reports directly and run this comparison in seconds, surfacing only the orders where something doesn't add up — so you spend your time acting on discrepancies instead of hunting for them.