From April 1, 2026, every Indian crypto exchange, custodial wallet, and registered VDA service provider must hand the Income Tax Department a periodic, user-level statement of every reportable transaction. The legal basis is Section 509 of the Income Tax Act 2025, and the price of getting it wrong is Section 446, which carries a Rs.200 per day penalty for late or missing reports and up to Rs.50,000 for inaccurate disclosure that the platform fails to correct.
For retail investors, this rule changes everything quiet about Indian crypto. The data your exchange shares about you flows directly into your Annual Information Statement (AIS), where it is matched against your Schedule VDA in the Income Tax Return (ITR). Any gap becomes a notice. This guide walks through the exact data fields, the timing, the penalty architecture, and the practical steps individual users should take before the first reporting cycle closes. Crypto carries leveraged volatility risk; do not invest more than you can afford to lose.
The Legal Spine: Section 509 of the Income Tax Act 2025
The crypto reporting April 2026 India regime did not emerge by surprise. Budget 2025 created Section 509 inside the recodified Income Tax Act, and the Finance Bill 2026 set the April 1, 2026 commencement date. The architecture mirrors how stockbrokers report Statement of Financial Transactions to the department, only adjusted for the asset-specific quirks of crypto.
Who counts as a “prescribed reporting entity”
The provision uses the term “prescribed reporting entity” to describe any platform that facilitates the transfer of a virtual digital asset. In practice this captures domestic exchanges, custodial wallet providers, OTC desks registered under the Prevention of Money Laundering Act, and intermediaries who hold customer balances on behalf of users.
What “reportable transaction” means
A reportable transaction is any transfer of a VDA carried out on the platform that crosses a notified de-minimis threshold. The CBDT is expected to set per-user, per-period thresholds via notification, but industry guidance suggests every PAN-linked transaction will be reported in aggregate even if individual trades are small.
How the data reaches you, the taxpayer
The information flows from the reporting entity to the Central Board of Direct Taxes systems, where it populates your AIS. You see the same data when you log in to the income tax portal. When you file your return, the department’s matching engine compares your Schedule VDA disclosure to the AIS row by row.
The Exact Data Fields Exchanges Now Share
The CBDT notification under Section 509 prescribes the data schema that every reporting entity must follow. The fields are intentionally exhaustive: the goal is full reconciliation, not sampling.
Account-holder identifiers
Each statement carries the full legal name, residential address, date of birth, PAN, and Aadhaar reference (where consented) of every user who transacted during the reporting period. For non-resident users, passport details and tax identification numbers in the home jurisdiction are included.
Transaction-level fields
For each reportable trade, the platform sends: transaction date and timestamp, asset name and contract address, direction (buy or sell), gross consideration in INR, quantity of the asset, fiat or crypto counterparty, fee paid to the platform, and the 1% TDS deducted under Section 194S. Withdrawals to unhosted wallets are reported as separate events, with the destination wallet address attached.
Beneficial-ownership and counterparty data
Where a corporate user transacts, the beneficial owners (above the 10% threshold) are named. For peer-to-peer trades brokered on the platform, the counterparty’s PAN is also disclosed.
| Data category | Sample fields shared with IT Dept |
|---|---|
| Account holder | Full name, address, PAN, Aadhaar (consented), DOB, residency status |
| Trade | Date, timestamp, asset, contract address, side, INR consideration, quantity, fee |
| TDS | Section 194S deduction per trade, deposited challan reference |
| Withdrawals | Destination wallet address, value, timestamp |
| Counterparty | Counterparty PAN (P2P), beneficial owners for corporates |
Section 446: The Penalty Stack That Forces Compliance
Section 446 of the IT Act 2025 is the enforcement teeth behind Section 509. It is not directed at retail users, but its second-order effect on retail is enormous because exchanges, to avoid the penalty, will tighten KYC and over-collect data.
The Rs.200 per day non-reporting penalty
If a prescribed reporting entity fails to file its statement within the notified due date, Section 446 imposes a penalty of Rs.200 for every day the default continues. For a large exchange handling millions of users, a delay of even a week translates into material exposure once aggregated, and the meter keeps running until the filing is made.
The Rs.50,000 incorrect-disclosure penalty
If the statement is filed but the data is inaccurate, and the platform does not correct the inaccuracy within the timeline specified in Section 509(4), or if it fails the due-diligence duty in Section 509(5), a penalty of up to Rs.50,000 may be imposed per default. Repeated or wilful failures can be compounded.
Why the penalty design matters for users
To stay clear of Rs.200-a-day exposure, exchanges will collect more KYC, ask more questions about source of funds, and reject transactions that look incomplete on paper. To stay clear of Rs.50,000 exposure for inaccurate filing, exchanges will lean on the side of over-reporting borderline trades. Both behaviours push more of your information into AIS, where it is visible to the assessing officer.
How the Data Flows Into Your AIS and ITR
Understanding the data path matters because it tells you exactly where reconciliation will fail.
From exchange to CBDT
Reporting entities upload statements through a notified e-filing utility, similar to the SFT mechanism. The CBDT ingests, validates, and matches against PAN before pushing the data into the AIS database.
From AIS to your return
Once in AIS, every VDA transaction shows up under a dedicated information code. When you open the ITR utility and start Schedule VDA, the form already knows how many transactions the department expects to see. If you under-report, the variance appears in the “AIS mismatch” summary that the assessing officer sees alongside your return.
What a mismatch triggers
Small mismatches typically trigger a Section 143(1) intimation asking you to reconcile. Larger or wilful gaps trigger Section 270A penalties of 50% to 200% of the tax shortfall, on top of the 30% VDA tax and 4% cess. The Section 270A penalty alone often exceeds the underlying tax, which is why under-reporting is a poor strategy.
Reporting Frequency and Due Dates
The CBDT has signalled a quarterly cadence for the first year of operation, with a likely move to monthly once the platforms’ systems stabilise. Each cycle has a hard due date, and Section 446 begins ticking from the day after.
Quarterly statement timing
For the inaugural year, reporting entities are expected to file statements within 30 days of the quarter end. Quarter one (April-June 2026) returns are due in late July 2026, quarter two (July-September 2026) returns are due in late October 2026, and so on.
Year-end consolidated filing
A consolidated annual statement, mirroring the year’s transactions in one file, is also expected, with a due date that aligns to the SFT cycle. The annual filing is what the AIS uses for matching, so any quarterly errors must be corrected before the year-end submission.
Correction window
Section 509(4) gives the reporting entity a notified correction window, expected to be 30 days, to fix inaccuracies flagged by the CBDT or self-discovered. If the correction is not made within the window, the Rs.50,000 penalty becomes leviable.
What Individual Investors Should Do Before April 1, 2026
The retail-investor checklist is short but consequential. Treating it as optional is the most common mistake in the first compliance cycle of any new tax-information rule.
- Confirm your PAN is updated and verified on every exchange you have ever used, including ones you no longer trade on. Stale PAN data is a leading cause of mismatch.
- Download a complete transaction CSV for FY 2025-26 from every exchange by April 30, 2026, even if you have already filed earlier returns from the same exchange.
- Reconcile each transaction’s TDS entry against your Form 26AS for FY 2025-26, and flag any missing entries with the exchange’s customer support in writing.
- Close dormant accounts where you no longer hold balances; an inactive account that mis-reports your residency status can trigger an AIS row you have to explain.
- Maintain a separate spreadsheet that converts every crypto-to-crypto swap to INR at the swap timestamp, using a reputable price feed.
- If you use offshore platforms, get the INR-equivalent ledger now, because the foreign exchange will not file a Section 509 return for you and you bear the 1% TDS-collection burden directly.
Common Misconceptions About the Reporting Rule
A regulation this new attracts a predictable set of myths. Several deserve direct refutation before they harden into rules of thumb in WhatsApp groups.
“The reporting only catches large traders”
The reporting captures every PAN-linked transaction on a prescribed entity’s platform, irrespective of size. A Rs.5,000 swap is reported the same way as a Rs.50,00,000 trade; it just appears as a smaller row in your AIS.
“I will avoid reporting by withdrawing crypto to a private wallet”
Withdrawals to unhosted wallets are themselves reportable events under Section 509, complete with destination wallet address. The reporting does not stop at on-platform trades.
“Offshore exchanges are exempt”
Offshore exchanges are outside the direct scope of Section 509 because the Indian government cannot compel a foreign platform to file. However, India is moving toward the OECD’s Crypto-Asset Reporting Framework (CARF), which the country is expected to join from 2027, and at that point foreign-platform data will flow through inter-government channels.
“The penalty is on me, the user”
The Section 446 penalty falls on the reporting entity, not on the individual user. The user-facing risk is Section 270A under-reporting penalties (50% to 200% of the tax shortfall), which kick in when AIS mismatch is established during assessment. Both designs converge on the same outcome: full reporting is the only path of least cost.
How This Connects to India’s Path to CARF 2027
The April 2026 framework is not an end state. India has formally signalled its intent to join the OECD’s Crypto-Asset Reporting Framework, the global counterpart of the Common Reporting Standard for banking.
What CARF adds on top of Section 509
CARF extends reporting beyond the domestic perimeter. Once India joins, expected from 2027, foreign-resident Indian taxpayers’ crypto activity on overseas exchanges will be reported to the Indian authorities by partner-country tax administrations, and vice versa. The April 2026 domestic rule is the rehearsal; CARF is the live concert.
Why the timeline matters for individual investors
For most retail users, the practical impact is that “moving funds to a foreign exchange” stops being a strategy. Coupled with the 30% tax under Section 115BBH and the 1% TDS under Section 194S, the new reporting infrastructure makes a clean, fully disclosed return cheaper than any avoidance scheme.
Working Example: What Your AIS Will Look Like
Consider Rohit, a Bengaluru-based developer who made three trades on a domestic exchange in April 2026.
Trade 1: Bought Bitcoin for Rs.2,00,000
AIS shows: “Acquisition of VDA, asset = BTC, quantity = 0.02, consideration = Rs.2,00,000, exchange = [name], 194S TDS = 0 (purchase, no TDS).”
Trade 2: Sold Bitcoin for Rs.2,50,000
AIS shows: “Transfer of VDA, asset = BTC, quantity = 0.02, consideration = Rs.2,50,000, 194S TDS = Rs.2,500 (1% of gross), exchange = [name].”
Trade 3: Withdrew remaining USDT to private wallet
AIS shows: “VDA withdrawal, asset = USDT, quantity = 100, destination wallet = [hash], INR equivalent = Rs.8,400, exchange = [name].”
What Rohit must do
Rohit’s Schedule VDA in his FY 2026-27 return must report all three rows. The gain on Trade 2 (Rs.50,000) is taxed at 30% under Section 115BBH; the TDS of Rs.2,500 is claimed as a credit; the withdrawal in Trade 3 is disclosed but does not create a taxable event by itself.
The Bottom Line for Retail Crypto Users
The April 1, 2026 reporting rule is not a tax rate change, but it is the most consequential crypto-tax development since Section 115BBH itself. The rule transforms an honour-system disclosure regime into a verified-data regime. Reconciliation, not avoidance, is the only viable response.
Three habits to build now
First, treat every exchange interaction as if it will appear in your AIS the next morning, because most will. Second, store INR-equivalent valuations for every crypto-to-crypto trade in a separate ledger. Third, file Schedule VDA row by row, never as a summarised single entry.
One final risk note
Crypto carries leveraged volatility risk; do not invest more than you can afford to lose. Add a tax-compliance burden that now operates with full information asymmetry on the department’s side, and the case for treating crypto as a small, disclosed, well-documented portfolio slice becomes obvious.
Frequently Asked Questions
When does the new crypto reporting rule take effect in India?
The reporting obligation under Section 509 of the Income Tax Act 2025 begins on April 1, 2026. Prescribed reporting entities, which include domestic exchanges and custodial wallet providers, must file user-level transaction statements with the Income Tax Department from that date onward.
What data fields do exchanges send to the IT Department?
Exchanges send full account-holder identifiers (name, PAN, address, DOB, residency), per-transaction details (date, timestamp, asset, INR consideration, quantity, fee), Section 194S TDS deducted, withdrawals to unhosted wallets with destination addresses, and counterparty information for peer-to-peer trades and corporate users.
What is the penalty if an exchange fails to file the statement?
Section 446 imposes a penalty of Rs.200 per day on the reporting entity for every day the default continues. If the statement is filed but contains inaccurate information that is not corrected within the notified window, an additional penalty of up to Rs.50,000 can be imposed per default.
Does the reporting penalty apply to individual investors?
No. Section 446 falls on the reporting entity, not on the individual user. However, individuals whose Schedule VDA filings do not match the AIS data face Section 270A under-reporting penalties of 50% to 200% of the tax shortfall, on top of the 30% VDA tax and 4% cess.
Can I avoid reporting by moving crypto to an offshore exchange?
Offshore exchanges are outside Section 509’s direct scope today, but India is moving to join the OECD’s Crypto-Asset Reporting Framework from 2027, which will share foreign-platform data with the Indian authorities through inter-government channels. Indian tax residence already pulls global income into the tax net, so the 30% rate applies regardless of platform location.
Related LearnFineEdge guides on Schedule VDA filing, Section 115BBH math, and choosing a compliant Indian crypto exchange are forthcoming and will be linked here as the cluster expands.
