Crypto tax notices in India are often triggered by mismatches, not by one dramatic mistake. A taxpayer may file an otherwise complete return, but if Schedule VDA is missing, TDS under section 194S does not line up with Form 26AS, or the return shows net gain where the portal is seeing gross sale consideration, the filing can start to look inconsistent.
That is why crypto ITR filing is no longer just about “declaring gains.” The return now sits inside a system that cross-checks Schedule VDA, special-rate income, TDS credit, AIS information, and validation rules. For AY 2026–27, the safest approach is still the simplest one: pick the right ITR form, disclose VDA transactions properly, and make sure the numbers in the return match the reporting trail that already exists on the tax portal. The Income Tax Department’s own ITR help pages say VDA income is disclosed transaction-wise in Schedule VDA in ITR-2 and ITR-3, and the notified ITR-2 and ITR-3 forms for AY 2026–27 are already in place.
Key takeaways
- VDA income is disclosed transaction-wise in Schedule VDA in ITR-2 and ITR-3, and taxed at the special 30% rate under section 115BBH.
- ITR-2 is for individuals and HUFs not having income from profits and gains of business or profession, while ITR-3 is for individuals and HUFs having business or professional income.
- AIS is broader than Form 26AS, and the portal allows feedback where reported information is duplicated, incomplete, or wrongly attributed.
- The department’s defective-return guidance says gross receipts shown in Form 26AS on which TDS credit is claimed should be disclosed in the relevant income schedules. For VDA, it also says set-off of losses is not allowed against VDA income.
- Validation rules continue to tie Schedule VDA back to Schedule CG, which means internal inconsistencies inside the return can trigger problems even before any notice arrives.
|
Table of contents |
No credit card required
Why crypto returns get flagged
The tax department is not reading your return the way an individual trader reads a PnL sheet. It is comparing different reporting trails. Your return has Schedule VDA, special-rate tax treatment, and TDS claims. The portal also has Form 26AS, AIS, and validation checks that test whether the disclosed income and the reported tax-credit trail make sense together.
That is why a crypto return can attract attention even when the taxpayer thinks the final tax paid is roughly correct. If the wrong form is used, if Schedule VDA is incomplete, or if a taxpayer reports only profit while section 194S TDS reflects a much larger gross transaction value, the return can start to look defective or under-reported. The department’s own material says this directly in the context of TDS-linked gross receipts and VDA disclosures.
The seven filing mistakes that cause trouble
Using the wrong ITR form
This is one of the most common starting errors. Many crypto users assume that all crypto reporting belongs in ITR-2 because Schedule VDA appears there. That is only partly true. ITR-2 is for individuals and HUFs not having income from profits and gains of business or profession. ITR-3 is the form for individuals and HUFs who do have business or professional income.
So if your crypto activity is being reported on business account, or your overall return already includes business income, ITR-3 may be the correct route. A taxpayer who belongs in ITR-3 but files ITR-2 can create structural mismatches before even getting to Schedule VDA.
Leaving Schedule VDA incomplete or blank
The department’s ITR-2 FAQ says VDA income is disclosed transaction-wise in Schedule VDA in ITR-2 and ITR-3. That is the core reporting schedule for most individual crypto filers. If you omit the schedule, enter only one consolidated figure without the required underlying details, or leave out some exchanges, the return becomes hard to reconcile against the rest of the portal trail.
This is also where older accounts and small exchanges create problems. Taxpayers often report the exchange they currently use and forget the one they used earlier in the year. That can leave TDS, AIS, or gross receipt traces hanging in the system without a matching disclosure in the return.
Reporting net profit where gross sale consideration is expected
This is one of the biggest crypto reporting mistakes in India. Taxpayers often think the return should show only final profit after deducting cost. The tax computation does need gain and loss logic, but Schedule VDA also needs transaction-wise disclosure, and the portal’s defective-return guidance specifically warns that gross receipts shown in Form 26AS on which TDS credit is claimed must be disclosed in the relevant schedules. For VDA filings, that mismatch often appears when the return reflects only net profit but the portal already has a section 194S trail tied to a much larger transaction value.
The practical takeaway is simple: do not confuse taxable income with sales consideration. They are related, but they are not the same number.
Claiming section 194S TDS credit without matching Form 26AS
A taxpayer may claim VDA-related TDS credit in the return, but if the related gross receipts are missing or understated, the return can become vulnerable. The defective-return FAQ says that if income is not offered to tax in the year, the corresponding TDS credit should generally be claimed in the year in which the income is offered. It also says gross receipts shown in Form 26AS on which TDS credit is claimed should be disclosed in the respective income schedules.
Taxpayers often claim the crypto TDS credit as reflected in Form 26AS but fail to report the corresponding crypto transactions in Schedule VDA. This omission creates a mismatch between the data reported in the Income Tax Return (ITR) and Form 26AS.
Ignoring AIS when it already shows crypto-linked information
AIS is not just a duplicate of Form 26AS. The Income Tax Department’s AIS FAQ says AIS is broader and lets taxpayers submit feedback. It also shows both reported value and modified value after feedback is given.
That means ignoring AIS is a mistake even when Form 26AS looks fine. If AIS shows duplicated, incomplete, or wrongly attributed crypto-linked information, you should review it rather than hoping it will not matter. A mismatched AIS entry may not always mean the return is wrong, but it does mean you need to understand what the system is seeing before you file or revise.
Claiming loss set-off in a way section 115BBH does not allow
This is another major filing error. The department’s defective-return FAQ says that set-off of losses will not be allowed against income from transactions in virtual digital assets, and that taxpayers must disclose sales consideration, purchase consideration, date, and other VDA details in Schedule VDA.
In practice, this means taxpayers get into trouble when they try to use crypto losses the way they would use ordinary capital losses or business losses elsewhere in the return. Losses from Virtual Digital Assets (VDAs) are not eligible for set-off. They cannot be adjusted against gains from VDAs, nor should they be considered for set-off in any other manner across the return.
Failing to reconcile Schedule VDA with the rest of the return
The validation rules matter more than many taxpayers realize. The current validation materials continue to tie Schedule VDA back to Schedule CG. The rules say the VDA values must reconcile internally, including the calculation inside Schedule VDA and the mapping back into capital gains in Schedule CG.
That means a taxpayer can still create trouble even after disclosing crypto. If the figures inside Schedule VDA do not match the special-income and capital-gains structure elsewhere in the return, the filing can trigger validation warnings or later scrutiny. This is why “I filled Schedule VDA” is not enough by itself.
Table that makes the mistakes easier to spot
| Filing mistake | What usually goes wrong | What to check first |
| Wrong ITR form | Business-style crypto activity filed in ITR-2 instead of ITR-3 | Whether the return includes business income |
| Schedule VDA left blank or incomplete | Trades exist, but VDA disclosure is partial or missing | Full transaction inventory across all exchanges |
| Net reported instead of gross sale consideration | Return shows profit only, while section 194S trail reflects larger transaction values | Schedule VDA rows and Form 26AS side by side |
| TDS credit claimed without matching disclosures | Credit taken, but linked VDA receipts are missing or understated | TDS entries in Form 26AS and Schedule VDA receipts |
| AIS ignored | Source-reported information is duplicated or inconsistent | AIS review and feedback tab |
| VDA loss set-off claimed incorrectly | Return tries to use VDA losses in a way section 115BBH does not permit | Schedule VDA and special-rate treatment |
| Internal validation mismatch | Schedule VDA totals do not tie to Schedule CG | Return validation logic before filing |
One clear example
Suppose your exchange deducted TDS under section 194S on crypto transfers worth ₹10 lakh during the year. Your actual taxable profit after cost may be much lower than that. The mistake happens when the return shows only the final gain figure and does not properly disclose the related sales consideration in Schedule VDA.
In that situation, the taxpayer may think the return is accurate because the final tax seems right. The portal may see it differently. Form 26AS already carries a TDS-linked gross receipt trail. If Schedule VDA does not reflect the transaction structure properly, the return can start to look incomplete or defective. The answer is not to report ₹10 lakh as taxable gain if that is not the correct income. The answer is to make sure the transaction-wise VDA disclosure explains why the gross transaction value and the final taxable amount are different.
How to fix a crypto ITR mistake before it grows
If you spot a problem before filing, fix the data first and the return second. Pull the complete transaction history from every exchange and wallet you used. Then match those records against Form 26AS, AIS, and your TDS claims. Only after the transaction file is complete should you rebuild Schedule VDA and pick the final ITR form.
If you already filed, do not rush straight into a random revised return. First compare:
- the Schedule VDA disclosures
- section 194S TDS entries in Form 26AS
- AIS-reported information
- the ITR form actually used
- the way VDA losses and gains were treated
That sequence matters because many crypto ITR errors are not isolated errors. One wrong form often comes with one wrong schedule, one wrong TDS claim, and one AIS mismatch behind it.
How cryptact helps
Crypto ITR mistakes usually begin as reconciliation problems. The law may be clear enough, but the filing still fails because data is scattered across exchanges, wallets, TDS traces, and portal records. That is where cryptact helps in a practical way. It brings transaction history together, helps you review gross receipts against actual gains, and makes it easier to prepare cleaner Schedule VDA reporting before filing.
For Indian users, the biggest value is not simply automation. It is being able to see why a number in AIS, Form 26AS, or Schedule VDA does not line up before that mismatch turns into a filing problem.
Conclusion
A clean crypto ITR filing for AY 2026–27 starts with three basics: pick the right form, fill Schedule VDA properly, and make sure your return matches the tax-credit and portal trail already sitting behind it.
Most crypto tax notices do not begin with hidden law. They begin with visible mismatches. Wrong ITR form. Missing Schedule VDA rows. TDS credit without matching gross receipts. AIS ignored. VDA losses treated like ordinary losses. Once those mistakes are removed, the return becomes much easier to defend.
That is where cryptact adds real value. It helps turn scattered exchange records into a usable VDA filing record, so you can catch mismatches before filing, clean up the return structure, and reduce the risk of avoidable notices later.
