An Indian crypto trader reportedly received a ₹88 lakh tax notice even though the overall investment result was a loss. Publicly reported details say the trader put in about ₹9.6 lakh, but repeated buying and selling pushed total transaction turnover past ₹80 lakh. That gap is central to the case. The reported trigger was not profit, but whether the trading activity, funding trail, and tax filings could be matched cleanly.
Losses did not stop scrutiny because turnover became the focus
According to the source material, tax authorities examined the source of funds, complete bank transaction trails, alignment between exchange data and income tax return disclosures, and whether TDS records matched Form 26AS and AIS. The case was said to fall under Section 69, which covers unexplained investments. If authorities cannot verify where the money behind large transaction activity came from, they may treat that activity as unexplained income.
That is where many traders get the framework wrong. A negative final P&L does not automatically remove tax exposure. The article notes that in some historical cases, the effective tax burden under this route has reached 60% to 78% after surcharge and cess. Standard loss logic offers no protection if the records themselves fail.
India's crypto tax regime is already strict before record gaps appear
The source also points to Section 115BBH, under which crypto gains are taxed at a flat 30%, with 1% TDS applied on every transaction. Losses cannot be set off against gains, and they cannot be carried forward to future years. For active traders, that means final account balance is only one part of the picture. Cost basis, trade history, wallet transfers, and exchange records all matter.
Once those records are incomplete, the problem grows quickly. A trader may know they lost money. The tax system still asks for a documented trail that explains every major inflow, outflow, and swap.
Exchange reporting and AI checks tighten the net
The material says Indian exchanges now report detailed data directly to tax authorities, including transaction volumes, PAN-linked activity, TDS deductions, wallet movements, and bank linkages. The Income Tax Department then runs AI-based scrutiny systems that compare this information with AIS records, Form 26AS, bank statements, and income tax return filings. A mismatch can trigger a notice automatically.
That is why the reported ₹88 lakh notice is being framed as a documentation failure rather than a profit issue. From the authority's side, data consistency comes first. Profit or loss is not the only lens being used.
Crypto-to-crypto swaps, DeFi wallets, and OTC trades are part of the reporting picture
Another point highlighted in the source is that crypto-to-crypto swaps are taxable events. BTC to ETH, ETH to SOL, or SOL to USDT may never touch a bank account in INR, but each swap still creates a reportable transaction. Users trading across Indian platforms and exchanges such as Binance face a more complicated paper trail, which raises the burden of recordkeeping.
The same reporting obligations were said to extend to DeFi wallets and OTC trades. The article states that India has already issued thousands of crypto-related notices in recent years using exchange data, PAN linkage, and automated AI scrutiny. The message from this case is narrow but clear: enforcement is driven by data inconsistency, not just portfolio size. Even a trader with a ₹5 lakh portfolio could face scrutiny if turnover patterns and records match the flagging criteria.