How To Read Your Form 26AS For Crypto TDS Credits: A 2026 Guide

That 1% TDS on your crypto sell feels like a tiny cut, until you try to claim it and it doesn't show. Then it becomes like a toll receipt you can't find, you paid it, but you can't prove it. For Indian traders and investors, Form 26AS crypto TDS is the cleanest "credit proof" you can rely on while filing ITR (especially when you traded across multiple exchanges, or did a few P2P sells). If you learn to read the right rows and fields, you stop guessing, and you stop leaving credits behind. This guide stays practical, with a running example, and a simple troubleshooting path when credits go missing. Where crypto TDS appears in Form 26AS (and why AIS still matters) Form 26AS is your tax credit statement. It mainly answers one question: what tax got deposited against your PAN. In March 2026, you usually access it from the Income Tax portal, and it redirects to TRACES for viewing or PDF download. If you need the exact "how to view and download" flow, this explainer is a decent refresher: how to view Form 26AS. For crypto TDS under Section 194S (1% on VDA transfers), the entries are generally visible under the TDS parts that list deductor-wise credits. In many cases: You'll see Section code: 194S. You'll see the deductor (exchange or buyer) details. You'll see tax deducted and tax deposited amounts. At the same time, don't ignore AIS. AIS often shows richer transaction details, and sometimes it updates earlier than 26AS. So you use AIS like a "heads-up list", but you use 26AS like the "credit ledger". A good combined view of both documents is explained here: Form 26AS and AIS guide. If you're still building your tracking habit (instead of doing it in June panic), it helps to keep a small monthly TDS ledger, and match it to 26AS later. This XXKK piece fits that workflow well: Tracking crypto TDS credits via Form 26AS. The fields you must read for Section 194S (without mixing dates) People open 26AS and see many columns, then they focus on the wrong one. For Form 26AS crypto TDS, the goal is to identify the correct deductor line, then confirm the credit amount is actually deposited. Here are the fields that matter most, and what they usually mean in real crypto life: Deductor name: This is typically the exchange entity name, or a buyer's name in a direct deal. If you used two platforms, you'll see two names. TAN of deductor: TAN is the deductor's tax account number. It's the best "unique key" to separate Exchange A vs Exchange B, even when names look similar. Section / Nature of payment: For crypto TDS, it should show 194S. If it shows some other section, don't ignore it, but treat it as a mismatch to be checked. Assessment year (AY): Your FY 2025-26 activity normally maps to AY 2026-27. A wrong AY entry makes credits look like they "vanished" when you filter. Amount paid/credited: Many traders misunderstand this. This is usually the gross consideration on which TDS got computed (not your profit, and not your bank payout). Tax deducted vs tax deposited: Deducted is what got cut from your trade proceeds. Deposited is what reached the government and got booked to your PAN. You want deposited to match deducted, otherwise credit can lag. Gotcha that keeps repeating: 1% TDS is on the sale value (gross), not on your gain, and not on "net after fees". So even a loss trade can still show TDS on the full consideration. If you want a plain-language refresher on what Section 194S covers (and why 1% applies the way it does), keep this handy: Section 194S overview. A running example: matching trade date vs deduction date vs deposit date Before the table, set one expectation correctly: crypto platforms can deduct TDS on the trade day, but the deposit and reporting can appear later (often after the deposit and statement filing cycle). So you reconcile in layers, not in one glance. Let's say you traded on two exchanges, plus one P2P sale. FY is 2025-26, and you're checking AY 2026-27. Here's a compact reconciliation view you can copy into a sheet: Month (FY 2025-26) Platform / Deductor Gross sale value (₹) TDS @1% expected (₹) Trade date TDS deduction date shown by platform TDS deposit date shown in 26AS 26AS identifiers to match Oct 2025 Exchange Alpha (TAN: ALPXXXXXX1) 2,50,000 2,500 18-Oct 18-Oct 05-Nov Deductor TAN, Section 194S, amount deposited Nov 2025 Exchange Beta (TAN: BETXXXXXX2) 1,20,000 1,200 02-Nov 02-Nov 07-Dec Deductor name + TAN, AY 2026-27 Dec 2025 P2P Buyer (individual deductor) 80,000 800 21-Dec 21-Dec (if they did it) 25-Jan (if deposited) Deductor TAN (if available), booking status What do you actually do with this? First, match by deductor TAN and section 194S, because dates can be noisy. Next, verify the tax deposited value equals your expected TDS for that month or batch. After that, check the amount paid/credited aligns with your gross sale value (it may be aggregated, so don't panic if one line covers multiple trades). The practical win is this: once your 26AS lines match your ledger, your ITR TDS claim becomes boring, and boring is good in tax season. If you also want your trade records to survive basic checking (FIFO, sale value in INR, swaps, and clean exports), this guide is useful alongside TDS matching: Crypto tax in India for spot trades. Troubleshooting decision tree: not showing in 26AS, only AIS, or not prefilled When something looks off, don't jump straight to "I'll claim it anyway". Use this short decision path and keep proofs ready (trade history, TDS report, order IDs, bank narration for P2P). TDS cut by exchange, but not in 26AS (and not in AIS) Wait a bit if the trade is recent, because deposit and booking can lag. If it stays missing, ask the deductor for confirmation of deposit and statement filing (and whether your PAN was used correctly). Common causes: PAN not verified, wrong PAN tagged, or statement not filed. TDS appears in AIS, but not in 26AS Treat AIS as an alert, not as a claim ticket. Recheck after some time, because 26AS is the credit booking view. If it doesn't move, ask the deductor whether they filed the TDS statement and mapped it to your PAN. TDS appears in 26AS, but it doesn't prefill in ITR Refresh the prefill, and check you selected the correct AY. If still not pulled, manually enter the TDS details exactly as in 26AS (TAN, amount, section), then keep the 26AS PDF saved. TDS appears in 26AS, but values or section look wrong Don't "adjust" it in your head. Follow up with the deductor for a correction statement or revision. Typical reasons: wrong AY, wrong PAN, wrong amount, or duplication. For a deeper breakdown of mismatch patterns and fixes, this is worth reading once: TDS and Form 26AS mismatch causes. One simple caution that saves time later: only claim TDS credit that is actually reflected in Form 26AS (or correctly booked in the system). Claiming "expected" credits often triggers mismatches, and then you spend weeks proving what the deductor didn't file properly. Conclusion Reading Form 26AS crypto TDS is less about tax theory, and more about matching: correct AY, correct TAN, correct section (194S), and the deposited amount that actually got booked. Once you keep a small monthly ledger, 26AS becomes a quick confirmation step, not a mystery file you fear. If your case has heavy volume, P2P buyers who didn't deposit, or cross-platform confusion, talk to a qualified tax professional before filing, because the fixes often depend on the deductor's correction timeline, not your effort alone. The best outcome is simple, your credits show cleanly, and your return stays clean too.