Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
A multi-channel D2C brand pulls revenue through its own website, two marketplace operators and a direct B2B billing flow, each with a different TDS posture under Section 194O / §393(1) Sl. 8(v). The own-website flow attracts no 194O at all because the gateway is not an operator. The marketplaces deduct 0.1% on gross credited or paid to the brand, but the brand books revenue net of GST and commission and sees a structural gap when comparing the deduction to its ledger. The direct B2B flow runs under buyer-side 194Q at 0.1% above the ₹50 lakh threshold, which is a different mechanism on the buyer's side entirely. Form 26AS arrives with entries split by deductor TAN and the team treats them as one undifferentiated stream, missing per-channel mismatches until the ITR window closes.
Classify every channel as operator-deducts, gateway-only or B2B-buyer-deducts before any reconciliation begins. Split Form 26AS entries by deductor TAN and route each to the matching channel bucket. Recompute the expected 0.1% from the operator's settlement statement on the gross amount credited or paid, applying the rate calendar across the 1 October 2024 cut and the 1 April 2026 code transition. Validate that the own-website channel has no 194O credit at all and treat any entry there as an exception. Track 194Q entries flowing in from B2B buyers separately, keyed to the buyer's TAN and the ₹50 lakh threshold. Maintain a standing variance register at the operator-TAN grain for the audit file.
Per-channel TDS posture map covering own-website, marketplace operator, direct B2B and aggregator 9(5) flows. Operator TAN dictionary with deductor identifiers for Amazon, Flipkart, Meesho, Ajio, Zomato, Swiggy and any other live platform. Rate calendar with the 1 October 2024 rate cut (1.0% to 0.1%) and the 1 April 2026 code migration (194O to §393(1) Sl. 8(v) payment code 1035). Gross-amount calculator that adds GST on marketplace commission and fees back to the net-of-GST ledger figure for like-for-like comparison.
A per-channel TDS reconciliation statement contrasting operator deductions in Form 26AS against operator settlement files, with the own-website and direct B2B channels evidenced as 194O-clean. A 194Q register for buyer-side deductions matched against B2B invoices. A standing variance log routed into the quarterly tax close, ready for the auditor and the ITR claim against Form 26AS.
A Bengaluru-based D2C personal care brand sells the same SKU through three channels in a typical month. Its own Shopify storefront takes ₹1.2 crore of orders settled by a payment gateway. Amazon Seller Central settles ₹2.1 crore after commission and fee deductions. A direct B2B contract with two regional distributors invoices ₹40 lakh on credit terms. The finance team pulls Form 26AS at the end of the quarter and finds three different TDS entries: zero against the gateway, ₹21,000 against Amazon, and a ₹4,000 entry from one of the distributors. The natural question — who deducted what, and why is there nothing on the largest single revenue source — is exactly the question Section 194O answers. E-commerce operator participant 194O India is the rule that splits the deductor obligation between platform, gateway and buyer, and the framework below is the reconciliation discipline that turns that split into a clean quarterly close.
Quick reference
| Aspect | Detail |
|---|---|
| Section under legacy law | Section 194O of the Income-tax Act 1961 |
| Section under Income-tax Act 2025 | §393(1) Sl. 8(v), payment code 1035 (effective 1 April 2026) |
| Current rate | 0.1% on the gross amount credited or paid to the participant |
| Pre-cut rate | 1.0% from 1 October 2020 to 30 September 2024 |
| Rate without PAN/Aadhaar | 5% under Section 206AA |
| Threshold for resident Individual/HUF participants | No deduction if annual gross sales or services in the financial year are Below ₹5,00,000 and PAN/Aadhaar is furnished |
| Threshold for companies, firms, LLPs | No threshold — deduct on every transaction |
| Non-residents | Outside the section |
| Who is the operator | The platform that owns, operates or manages the digital facility through which the sale happens (Amazon, Flipkart, Meesho, Zomato in 9(5) role, Swiggy in 9(5) role) |
| Who is the participant | The resident merchant selling through the operator’s facility |
| Is a payment gateway an operator | Generally no — only if the gateway itself performs the marketplace role (hosting listings, directing buyer demand) |
| Operator-deducted, gateway-deducts-again | No. Where the operator has deducted under 194O, no other section deducts again on the same transaction |
| Reconciles to | Form 26AS (participant side); Form 26QE (operator side); Form 168 statements under the Income-tax Act 2025 |
| GST treatment | GST law unchanged. GST 18% applies on the operator’s commission or platform fee only, as a separate line |
What Section 194O actually does
Section 194O places the deduction obligation on the e-commerce operator at the moment the operator credits or pays the participant, whichever is earlier. The rate is now 0.1% on the gross amount of sales or services, applied to the figure before the operator’s commission and fee deductions. The participant — the resident merchant selling through the platform — receives the net amount and sees the 0.1% as a tax credit in Form 26AS once the operator files its quarterly return on Form 26QE. From FY 2026-27 onward the same credit surfaces under §393(1) Sl. 8(v) with payment code 1035 on the Income-tax Act 2025 successor regime, the rate is unchanged at 0.1%, and the visibility shifts from the 194O label to the new code on Form 26AS and Form 168 statements. A reconciliation engine that recognises only the legacy 194O code will silently miss the new entries from April 2026 onward.
The single critical structural feature is the no-double-deduction rule. Where the operator has deducted under 194O on a particular transaction, the same transaction is not subject to TDS under any other section. The gateway settling the underlying customer payment does not deduct again. The buyer paying the operator does not deduct under 194Q on a payment routed through the operator. The participant claiming the credit does so once, against the operator’s TAN, in the financial year in which the deduction was made.
Why a payment gateway is not, by default, an e-commerce operator
The temptation when a brand uses Razorpay, Cashfree, PayU or BillDesk on its own website is to treat the gateway as the operator and ask why no 194O is being deducted. The legal definition of an operator turns on whether the entity owns, operates or manages the digital or electronic facility through which the sale of goods or services takes place. A pure payment aggregator acquires the customer payment after the sale has already been concluded on the merchant’s own site, and remits the funds to the merchant. It is not the facility through which the sale was brought together. It is therefore not an operator under 194O, and there is no operator-side deduction on the merchant’s own-website channel at all. The merchant pays the gateway’s MDR and platform fee — that is a commercial arrangement, not a TDS deduction.
The exception is the gateway that genuinely performs a marketplace role. If a payments company hosts product listings, surfaces seller catalogues or directs buyer demand to specific sellers, then on those flows it is acting as an operator and the 194O obligation attaches to it on those flows. The categorisation is per-flow, not per-entity. A finance team building its TDS posture map must classify each revenue channel by its actual function, not by the legal form of the counterparty.
What changes when the operator is also the supplier under GST §9(5)
Zomato and Swiggy are e-commerce operators under Section 194O on the restaurant participant’s earnings, and they deduct 0.1% on the gross amount credited or paid to the restaurant. They are also notified under GST Section 9(5) as the deemed supplier of restaurant services on their platforms, and they discharge GST on the restaurant’s supplies on the restaurant’s behalf. The two regimes operate on different layers and one does not switch the other off. A multi-outlet QSR reconciling a Zomato statement sees the gross sale as reported by Zomato, the 0.1% TDS in Form 26AS under Zomato’s TAN, the GST discharged by Zomato under 9(5), and the Zomato commission and platform fee as separate lines. The TDS posture under 194O is therefore independent of the GST treatment under 9(5), and treating them as one undifferentiated deduction is the most common quarterly close error in restaurant accounting.
How does the participant verify what the operator deducted
The participant verifies the deduction through Form 26AS or the Annual Information Statement, both available from the income-tax portal. Each entry in 26AS carries the deductor’s TAN, the section under which the deduction was made, the gross amount on which TDS was computed, and the tax deducted. The reconciliation grain is the deductor TAN. Amazon, Flipkart, Meesho, Ajio, Zomato and Swiggy each file under separate TANs even where they belong to related corporate groups, so per-operator buckets are the only correct way to read the Form 26AS pull.
Within each operator bucket, the participant compares the gross amount credited or paid as reported by 26AS against the gross amount in the operator’s settlement statement for the quarter. The two numbers must reconcile after timing — 26AS reflects deductions only after the operator files Form 26QE, which can lag the actual deduction by 30 to 60 days. The expected TDS is 0.1% of the operator’s gross, recomputed against the rate calendar across the 1 October 2024 cut, and against the §393(1) Sl. 8(v) payment code 1035 transition from 1 April 2026.
When does 194Q apply instead of 194O — the direct B2B channel
The direct B2B channel — a brand invoicing a regional distributor directly, without a platform in the loop — has no operator and is outside 194O entirely. The buyer-side TDS provision under Section 194Q (now §393(1) Sl. 8(iv) under the Income-tax Act 2025) applies on this channel where the buyer’s aggregate purchases from the seller exceed ₹50 lakh in the financial year and the buyer’s turnover in the preceding year exceeded ₹10 crore. The rate is 0.1% on the amount above the ₹50 lakh threshold, and the deduction sits on the buyer. The seller — the D2C brand in this case — receives the 0.1% as a Form 26AS credit under the buyer’s TAN, not under any operator’s TAN. A B2B distributor that does not meet the turnover trigger will not deduct under 194Q at all, and the brand will see no entry in 26AS on that distributor’s flows.
The corollary is the worked discipline: a brand reconciling Form 26AS at the channel grain expects 194O credits only from marketplace operator TANs, 194Q credits only from B2B buyer TANs above the ₹50 lakh threshold, and no TDS at all from its own-website channel. Any cross-contamination — a 194O entry against the own-website gateway, a 194Q entry against a marketplace operator — is a deductor classification error and worth chasing back to the deductor before the ITR claim is filed.
Worked example: D2C brand across three channels
Sera & Co is a Bengaluru D2C personal care brand. In Q1 FY 2026-27, its three revenue channels produce the following gross figures:
| Channel | Gross (₹) | Operator? | TDS section | Expected TDS (₹) | Deductor TAN bucket |
|---|---|---|---|---|---|
| Shopify own website (Razorpay gateway) | 1,20,00,000 | No — gateway is not an operator | None at source | 0 | None expected |
| Amazon Seller Central | 2,10,00,000 | Yes — Amazon is the operator | §393(1) Sl. 8(v) code 1035 at 0.1% | 21,000 | Amazon TAN |
| Direct B2B (Distributor A and Distributor B) | 40,00,000 (Distributor A: ₹62L cumulative; Distributor B: ₹18L cumulative) | No — direct invoice, no platform | §393(1) Sl. 8(iv) code 1034 / 194Q on Distributor A only, above ₹50L | 1,200 from Distributor A on the slice above ₹50L | Distributor A’s TAN |
The expected 26AS pull for the quarter is one entry under Amazon’s TAN for ₹21,000 against ₹2.1 crore gross, and one entry under Distributor A’s TAN for ₹1,200 against the post-threshold slice. The Shopify channel produces no TDS entry at all. If the actual 26AS pull shows a 194O entry against the Shopify-routed gateway, it is a deductor classification error and Sera & Co should raise it with the gateway and the income-tax portal. If the Amazon entry shows a different gross — say ₹2.04 crore against ₹21,000 — the team recomputes 0.1% of the Amazon-reported gross and chases the gap as either a returns-and-cancellations timing difference or a settlement file mismatch.
The reconciliation does not end with TDS. On the same Amazon channel, the GST treatment of the operator’s commission is a separate line: GST 18% applies on Amazon’s commission and fees, not on the underlying transaction value. On the Shopify own-website channel, the Razorpay MDR is a commercial fee unrelated to 194O. On the direct B2B channel, a buyer who deducted 194Q must also file in TDS returns and the seller must claim the credit in ITR. Four separate streams; four separate reconciliation grains; one quarterly close.
Catch a 194O deduction sitting on the wrong channel before it reaches your ITR file
The leakage flag checker isolates suspect deductions — a 194O entry against a gateway, a card-grade MDR on a zero-MDR rail — by routing each settlement line against the right deductor and instrument logic. Use it when the Form 26AS pull and the operator settlement file refuse to agree.
Open the tool →Per-channel reconciliation discipline
The audit framework that holds across operator types is the per-channel posture map. Each revenue channel is classified once, into one of four buckets: own-website-with-gateway (no operator deduction), marketplace-operator (0.1% on gross under 194O / code 1035), aggregator-with-§9(5)-supplier-status (0.1% TDS plus GST discharged by the operator), or direct B2B (no operator, possible buyer-side 194Q at 0.1% above ₹50 lakh). The classification is the one decision that, once made correctly, makes the rest of the reconciliation mechanical.
Within each operator-deducts bucket, the standing discipline at the quarterly close is:
- Pull Form 26AS and split entries by deductor TAN, not by section label
- For each operator TAN, recompute 0.1% on the operator’s reported gross for the period, applying the rate calendar across the 1 October 2024 cut and the 1 April 2026 code transition
- Investigate any gap as a candidate for a returns timing difference, a Form 26QE filing lag, or a gross-amount definition mismatch — never as rounding
- Confirm the own-website channel has no 194O credit at all, and treat any stray entry there as a deductor classification error
- Track 194Q credits separately, keyed to the buyer’s TAN and the cumulative ₹50 lakh trigger
The variance register that comes out of this is the single document the statutory auditor wants when they review the TDS claim against Form 26AS, and the single document the tax officer would look at first in any inquiry into the ITR claim.
What the Income-tax Act 2025 changes — and what it does not
The 1 April 2026 transition replaces the legacy section identifier “194O” with §393(1) Sl. 8(v) and the numeric payment code 1035 on challans, Form 168 statements and Form 141 submissions. The rate remains 0.1%. The threshold for resident Individual/HUF participants remains ₹5 lakh. The no-deduction-by-other-sections rule remains. What the migration does change is the field a reconciliation engine matches against on Form 26AS — the section column for credits made in FY 2026-27 onward will carry the new identifier, not the legacy 194O, and a hardcoded match on “194O” will silently miss every new credit. The rate-by-date calendar must therefore handle both the 1 October 2024 rate cut and the 1 April 2026 code transition simultaneously when reconciling any period that straddles either boundary.
GST law on operator flows is unchanged through these transitions. GST 18% continues to apply on the operator’s commission or platform fee as a separate line, not on the underlying transaction value. The §9(5) deemed-supplier framework for restaurant aggregators is untouched. A reconciliation file that treats GST and TDS as one combined deduction will misclassify both — keep them as two independent reconciliation lines from the start.
Continue reading in this cluster
The Section 194O TDS e-commerce reconciliation guide walks the operator-side Form 26QE filing and the multi-platform reconciliation cycle in detail. The MDR fee reconciliation pillar sets out the broader merchant-fees discipline within which the 194O posture sits, and the Razorpay MDR reconciliation guide handles the own-website gateway channel where 194O does not attach. For the marketplace channel mechanics on a specific operator, see the Amazon SPN GST reconciliation guide and the Flipkart seller settlement reconciliation guide. For the GST §9(5) layer that overlays Zomato and Swiggy on the same restaurant flow, the GST Section 9(5) aggregator restaurant liability guide is the companion piece.
Every revenue channel deserves its own deductor posture map and its own Form 26AS bucket. The brand that runs that discipline closes the quarter cleanly; the brand that does not is the one filing an ITR claim it cannot evidence.
Authoritative reference: Income Tax Department of India — the primary source for Section 194O obligations, the 0.1% rate effective 1 October 2024, Form 26QE filing for operators, and the §393(1) Sl. 8(v) payment code 1035 framework under the Income-tax Act 2025.