India’s crypto-compliance framework is moving beyond tax deducted by exchanges toward more detailed crypto-asset service-provider reporting. Rule 243 describes information to be maintained and reported for covered users and transactions, subject to the provider scope in Rule 242 and due-diligence procedures in Rule 244.
The rule applies for relevant calendar years beginning on or after January 1, 2026. It does not mean every wallet automatically reports to India or that every blockchain transfer is taxable. It does mean users should expect compliant providers to collect and reconcile more identity, residence and transaction data.
Who has the reporting duty?
Rule 242 defines reporting crypto-asset service providers and connects the duty to relevant transactions and branches. Section 285BAA authorises prescribed reporting entities to furnish information on crypto-asset transactions.
The legal duty belongs to the covered provider, but a user may be asked for self-certification, tax identification and controlling-person information so the provider can complete due diligence.
Users should identify the exact entity serving them. A global brand may have an Indian branch, an overseas company or several entities with different reporting connections.
What Rule 243 requires providers to report
The official text includes identifying information for reportable users, such as:
- name and address;
- country or countries of residence;
- tax identification number or numbers;
- date of birth for an individual; and
- place of birth when required under the stated conditions.
For entities, reporting can include controlling-person details. The rule also covers account and transaction information specified in its clauses.
Read the complete rule and definitions rather than relying on this summary. Whether a user, controlling person, asset or transaction is reportable depends on the connected rules.
Reporting is not the same as tax liability
A provider can report a transaction that does not itself create taxable income, or report gross information that does not show the user’s cost basis. For example, a transfer between wallets controlled by the same person may be economically different from a sale to another person.
The tax result depends on the facts and applicable law. Rule 243 is an information-reporting rule; Section 115BBH and other provisions govern tax computations.
That distinction is why personal records remain necessary.
Records every crypto user should keep
For each purchase, sale or swap, retain:
- timestamp and time zone;
- token quantity and trading pair;
- rupee value and pricing source;
- order type and execution identifier;
- trading fee and the asset used to pay it;
- exchange name and legal entity; and
- invoice or contract for an off-exchange transaction.
For deposits, withdrawals and personal-wallet transfers, retain:
- sending and receiving addresses;
- transaction hash;
- network and token contract;
- quantity sent and received;
- network or bridge fee;
- account ownership at both ends; and
- the purpose of the transfer.
A block explorer shows the technical movement but normally does not prove who controlled each address or why the transfer occurred. Maintain a private address register without storing seed phrases or private keys in it.
Track more than spot trades
Create separate labels and evidence for:
- staking and validator rewards;
- mining receipts;
- airdrops and promotional distributions;
- gifts sent or received;
- payments for work or goods;
- liquidity-pool deposits and withdrawals;
- wrapped-token and bridge transactions;
- token migrations and redenominations;
- exchange rebates; and
- assets lost in a hack or platform failure.
Do not force every transaction into “buy” or “sell.” Some on-chain activity contains multiple legal and economic steps that require professional review.
Reconcile exchange data with tax data
At least quarterly:
- export order, trade, deposit and withdrawal files;
- reconcile transfers between platforms and wallets;
- investigate unmatched deposits or withdrawals;
- compare TDS with Form 26AS and the Annual Information Statement;
- identify missing cost basis;
- preserve exchange-rate evidence; and
- create an encrypted, read-only backup.
Monthly exports are safer for active users because an exchange may limit historical access or close. Screenshots alone are difficult to search and may omit timestamps or identifiers.
Offshore platforms and self-custody
An offshore exchange is not a recordkeeping shortcut. Indian tax-residency and foreign-asset obligations can apply independently of where a platform is incorporated. International crypto reporting frameworks also increase cross-border information exchange.
Self-custody can remove an exchange counterparty but not a tax or evidence obligation. The user becomes responsible for preserving transaction history and proving ownership across addresses.
Privacy and security precautions
Tax records are sensitive. They can expose balances and a map of wallet addresses.
- Encrypt local and cloud backups.
- Use a password manager and strong account authentication.
- Limit the data shared with portfolio tools.
- Prefer read-only API permissions where an integration is necessary.
- Revoke unused API keys.
- Never put a seed phrase or private key in accounting software.
Verify any request for KYC or tax documents through the provider’s official domain. A fake compliance email can be a phishing attempt.
A year-end handoff for a tax professional
Provide the professional with:
- original CSV exports;
- reconciled transaction ledger;
- address ownership notes;
- TDS and AIS records;
- details of foreign platforms;
- valuations and price sources;
- reward, gift and payment evidence; and
- a list of uncertain transactions.
Ask which return, income head and disclosure schedules apply. Do not delete source files after producing a summary report.
Bottom line
Rule 243 expands the information covered providers maintain and report from calendar year 2026. It increases the chance that incomplete personal records will conflict with third-party data.
The practical response is a repeatable export, reconciliation and backup routine. Read our India crypto tax guide for the separate tax framework.
This article provides general information and is not personal tax or legal advice.
Advertisement
Sources and review
This article was checked against the primary or authoritative sources below on .
- Rule 242: Reporting crypto-asset service providers — Income Tax Department, Government of India
- Rule 243: Crypto-asset transaction reporting — Income Tax Department, Government of India
- Section 285BAA: Reporting of crypto-asset transactions — Income Tax Department, Government of India
- ITR-2 frequently asked questions — Income Tax Department, Government of India
Frequently asked questions
It specifies information that reporting crypto-asset service providers must maintain and report for reportable users, controlling persons and relevant transactions, subject to Rules 242 and 244.
The published rule applies for each relevant calendar year beginning on or after January 1, 2026. Reporting mechanics and deadlines depend on the connected provisions.
No. Investors still need cost, transfer, wallet, fee and tax records to reconcile the platform's data and prepare their own returns.
Yes. Keep dates, quantities, fees, addresses and transaction hashes so beneficial ownership and movement can be demonstrated later.
Advertisement