TDS Under Section 194-O for E-commerce Sellers
Alongside GST TCS, there is a second statutory deduction hiding in every marketplace settlement: income-tax TDS under Section 194-O. It is smaller, quieter, and more frequently mis-booked than its GST cousin. This article explains what 194-O is, how it differs from TCS, where to find it in your Amazon, Flipkart, and Meesho reports, and how to make sure every rupee deducted actually reduces your income-tax bill.
What Section 194-O says
Section 194-O of the Income-tax Act requires an e-commerce operator to deduct TDS at 0.1% of the gross amount of sales of goods or services facilitated through its platform, at the time of crediting or paying the e-commerce participant (you), whichever is earlier. A few practical consequences follow:
- It is deducted on gross sales, before marketplace commissions and fees are subtracted — not on your net payout.
- It is income tax, not GST. The deduction is against your eventual income-tax liability and has nothing to do with your GST returns.
- The operator deducts and deposits it, then reports it against your PAN. You do nothing to trigger it — but you must track it to benefit from it.
Certain small individual or HUF sellers may be outside the deduction's scope subject to threshold conditions; because thresholds and conditions can be amended, confirm your position with a qualified CA rather than assuming an exemption applies.
TDS 194-O vs GST TCS: the side-by-side
Sellers constantly conflate the two deductions because both appear on the same settlement statements. They are entirely different animals:
| Aspect | TDS u/s 194-O | GST TCS u/s 52 |
|---|---|---|
| Law | Income-tax Act | CGST/SGST/IGST Acts |
| Rate | 0.1% of gross sales | 0.5% of net taxable value |
| Base | Gross amount facilitated | Taxable value net of returns |
| Where the credit appears | Form 26AS / AIS against your PAN | GST portal TDS/TCS statement against your GSTIN |
| How you use it | Adjusts against income-tax liability in your ITR | Flows to electronic cash ledger after acceptance |
A quick worked example makes the separation concrete. Suppose a marketplace facilitates Rs. 1,00,000 of gross sales for you in a month, and customers return goods worth Rs. 10,000. TDS under 194-O is computed on the gross Rs. 1,00,000 at 0.1%, while GST TCS is computed on the net taxable value of Rs. 90,000 at 0.5% — two different bases, two different laws, and two different destinations for the credit. Booking both from the same settlement rows without separating them is how ledgers become unreconcilable by year-end, so build the split into your posting routine from day one.
For the GST side of this pair, read our explainer on TCS under Section 52.
Booking 194-O correctly in your accounts
The correct treatment is to book TDS deducted as an asset — typically "TDS receivable u/s 194-O" — not as an expense. A clean monthly routine looks like this:
- Pull the settlement or payment report from each marketplace for the month.
- Identify the TDS line items (marketplaces label them variously — look for "TDS", "194-O", or "income tax deducted").
- Post the amounts to the TDS receivable ledger, marketplace-wise.
- Quarterly, match your ledger against Form 26AS/AIS. Differences usually trace to timing (deduction in one quarter, deposit reported in the next) or to a PAN mismatch on the marketplace's records.
At return-filing time, your CA claims the accumulated TDS against your tax liability. If your books never captured it, the claim depends entirely on 26AS — workable, but you lose the ability to challenge operator errors, and your P&L quietly absorbed money that was never an expense.
Why sellers get this wrong at scale
A seller doing a few hundred orders a month across two or three marketplaces faces thousands of settlement rows, with TDS and TCS interleaved among commissions, shipping fees, ad charges, and adjustments. Manual bookkeeping tends to collapse all deductions into one lump, destroying both the 26AS reconciliation and the GSTR-8 reconciliation in one stroke. TallySutra addresses exactly this: it reads Flipkart, Meesho, and Amazon reports and produces balanced TallyPrime vouchers that split every deduction to its proper ledger — TDS receivable, TCS receivable, commission expense with its GST component — with an exception queue for rows that need a human decision. See the full capability list on our features page.
The compliance caveat
This article covers the standard mechanics of Section 194-O for education. Rates have been revised in the past, exemption thresholds carry conditions, and interplay with other TDS sections can arise in specific structures. Before relying on any exemption or finalising your tax computation, have a qualified CA or tax professional review your facts.
Frequently asked questions
Is 194-O TDS deducted on gross sales or on my payout?
On the gross amount of sales facilitated through the platform, before commissions and fees are deducted. This is why the TDS figure looks larger relative to your actual payout than the 0.1% rate suggests.
Can I use 194-O TDS credit to pay GST?
No. TDS under 194-O is income tax and adjusts only against your income-tax liability via your ITR. GST liabilities are paid from your GST ledgers, where the separate TCS under Section 52 lands.
Where do I verify the TDS the marketplace deducted?
Check Form 26AS and the AIS on the income-tax portal — deductions reported against your PAN appear there. Reconcile them quarterly with the TDS line items in your marketplace settlement reports.
TallySutra turns Amazon, Flipkart and Meesho reports into reconciled, reviewed TallyPrime vouchers — duplicate-safe, with every rupee traceable to its source row.
Book a 30-minute demo