Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Section 194O rate was cut from 1 percent to 0.1 percent on October 1, 2024, and is deducted on the gross payment (including GST embedded in marketplace fees) while sellers book revenue net of GST. Sellers on multiple marketplaces (Amazon, Flipkart, Meesho) receive separate TDS streams per deductor TAN, and returns, refunds, and settlement timing create recurring reconciliation gaps.
Split Form 26AS entries by operator TAN and reconcile each platform's deductions independently against its settlement statements at the quarter level. Apply rate-by-date logic across the October 1, 2024 transition. Decompose the gross-vs-net gap by computing the expected TDS base as net revenue plus GST on fees, and route timing mismatches from returns or refund reversals to the next settlement cycle.
Per-operator TAN reconciliation queue. Rate calendar with October 1, 2024 transition. Gross-base calculator adding GST on marketplace fees to net revenue for TDS comparison.
Operator-level reconciled TDS credits, decomposed gross-vs-net variance attributed to GST-on-fees rather than genuine error, and clean claim against Form 26AS for each marketplace across the rate-transition boundary.
Section 194O TDS e-commerce India affects every brand or seller receiving payments through marketplace operators—Amazon, Flipkart, Meesho, and others are all e-commerce operators under the Income Tax Act. Finance teams at these companies face a specific reconciliation problem: the operator deducts TDS on a gross basis, the seller records revenue and expenses net of GST, and Form 26AS reflects the deduction only after the operator files its quarterly return.
2026 Migration Update — The Section 194O rate was cut from 1% to 0.1% effective 1 October 2024, so marketplace sellers must run rate-by-date reconciliation across FY 2024-25 settlement files to split H1 deductions from H2 deductions. Under the Income Tax Act 2025 (effective 1 April 2026), 194O maps to a numeric payment code, and FY 2026-27 ledgers will need cross-era matching against pre-migration entries. See the rate-by-date reconciliation guide and the cross-era TDS reconciliation guide.
What Section 194O Covers
Effective 1 October 2020, Section 194O requires every e-commerce operator to deduct TDS at 1% on the gross amount of sales facilitated through its platform, at the time of credit or payment to the seller—whichever is earlier. The deduction applies to all payments including commission adjustments, returns netting, and direct credit for sales.
The threshold for individual and HUF sellers is ₹5 lakh in aggregate receipts from a single operator in a financial year. For companies and partnership firms, no threshold applies—deduction begins from the first transaction. Sellers without a valid PAN on record face a higher deduction at 5% under Section 206AA.
Where Reconciliation Breaks Down
Gross versus net booking mismatch. The operator deducts 1% on the gross payment it credits to the seller, which includes the GST component embedded in marketplace fees and commissions. The seller, however, books marketplace commission as an expense net of GST and records revenue net of returns. The result is that the TDS base in the operator’s calculation exceeds the net revenue figure in the seller’s books—sellers using export reports from marketplace dashboards often find that the TDS figure on the dashboard and the Form 26AS figure differ by the GST component, typically 18% of the MDR or commission.
Multi-platform deduction aggregation. A seller operating on three marketplaces receives three separate 194O deduction streams in Form 26AS, each with a different deductor TAN. The 26AS aggregates all entries, but the seller must reconcile each operator’s deductions independently, matching them to that operator’s settlement statements. Blending data across operators before reconciliation produces an unresolvable variance.
Returns and refund timing. When a customer returns an order after the credit period, the operator may net the refund against the next settlement cycle. TDS may have already been deducted on the original payment; the reversal entry does not automatically generate a TDS credit. The seller’s books show a smaller net receipt while the 26AS shows the full original TDS deduction.
Reconciling Section 194O Deductions: Steps
-
Download Form 26AS and AIS from the income tax portal at the end of each quarter. Filter entries under Section 194O and group by deductor TAN to isolate each marketplace operator.
-
Obtain settlement statements from each platform. Marketplace seller portals provide monthly or bi-weekly settlement reports showing gross sales, commissions, returns, and the TDS deducted. Pull these for the same quarter period.
-
Reconcile TDS deducted to settlement data per operator. For each operator, sum the TDS deducted per the settlement report and match to Form 26AS. Identify whether discrepancies arise from the GST component difference, from returns timing, or from a missing 26QE filing by the operator.
-
Adjust books for GST component. Where the TDS base on the platform report includes GST on fees, recalculate the TDS on the taxable (non-GST) component and book the difference as a reconciling item or raise a query with the platform’s seller support.
-
Flag unmatched 26AS entries. Any TDS shown in 26AS without a corresponding settlement entry is either a timing lag or an incorrect deduction. Pursue operator confirmation before filing the ITR.
Section 194O — Key Parameters
| Parameter | Detail |
|---|---|
| Rate (PAN available) | 1% on gross payment |
| Rate (no PAN) | 5% under Section 206AA |
| Threshold — Individual / HUF | ₹5 lakh per operator per FY |
| Threshold — Company / Firm | No threshold; deduction from first payment |
| Filing form | Form 26QE (by e-commerce operator) |
| Quarterly return deadline | 31 July / 31 Oct / 31 Jan / 31 May |
| Seller visibility | Form 26AS Part A / AIS |
What Automated Reconciliation Changes
TDS reconciliation software with marketplace data connectors ingests settlement files from Amazon, Flipkart, and Meesho directly, normalising each to a common schema before matching against Form 26AS entries. The multi-pass matching pipeline—exact match, composite-signal, tolerance matching, and many-to-many aggregation—handles the GST component adjustment as a configured tolerance rule rather than a manual rework step. Finance teams that previously spent three to four days per quarter correlating settlement PDFs with 26AS downloads reduce this to a same-day exception review.
Reconciliation software India with 24-hour Form 26AS refresh detection flags new operator filings the day they appear, giving sellers time to investigate discrepancies before the quarterly advance tax deadline rather than at year-end ITR filing.