Nobody wants to think about tax notices until they get one. But the freelancers we have seen deal with them almost always share the same handful of root causes, and every one of them is preventable with habits you can build in an afternoon.
Let us walk through the four we see most often and the year-round habits that keep them from becoming your problem.
Red flag 1: AIS and TIS mismatches
Your Annual Information Statement (AIS) and Taxpayer Information Summary (TIS) aggregate the financial information reported against your PAN by banks, deductors and other institutions. If the income you declare in your ITR does not match what the department already sees in your AIS, that mismatch is often the very first thing that gets automatically flagged, sometimes before a human ever looks at your return.
This happens more easily than people expect.
- A foreign remittance might be reported by your bank in a way that does not obviously map to the invoice you raised for it.
- A payment credited on 2 April belongs to next year even though you invoiced it in March.
- Or you simply forget a small client relationship from earlier in the year.
The fix is unglamorous but effective. Pull your AIS before you file, not after, and reconcile every line against your own records. If something in your AIS looks wrong (banks and deductors do make reporting errors), you can flag it as inaccurate directly on the portal, but you need to notice it first.
We have a complete guide on reading and reconciling AIS here.
Red flag 2: Section 68 and unexplained cash credits
Section 68 lets the department treat any credit in your bank account as unexplained income if you cannot satisfactorily prove where it came from and why. For freelancers, this shows up most often as a foreign payment sitting in your account with no accompanying documentation tying it to a specific client, invoice or service. The rate that applies under Section 115BBE, 60 percent plus surcharge and cess, works out to an effective 78 percent, which is why this one matters more than the others.
The single best protection against this is consistency. Every foreign credit should have a corresponding invoice and a FIRA or e-FIRA, filed together, from the day the payment arrives. This is not about proving your innocence after the fact. It is about never creating ambiguity in the first place.
A credit with a clean paper trail behind it rarely gets questioned under Section 68, and when it does, the answer already exists.
Red flag 3: undocumented stablecoin receipts
If you receive stablecoin payments into a personal wallet and sell them on an Indian exchange, what reaches your bank is INR from an exchange with no FIRA, no purpose code and nothing linking it to your invoices.
Two things follow. Each sale is a Virtual Digital Asset transfer under Section 115BBH, with 1 percent TDS under Section 194S and reporting in Schedule VDA, which pushes you from ITR-4 to ITR-3. And the INR credits themselves, undocumented, are exactly the Section 68 exposure described above. Large undocumented flows through personal wallets can also draw attention beyond the tax department, even when the underlying income was entirely legitimate freelance work.
The fix, again, is documentation at the point of receipt. A settlement route that converts the stablecoin outside India and delivers a foreign inward remittance with a FIRA, rather than a personal wallet with no accompanying record.
Red flag 4: GST mismatch above the registration threshold
If your aggregate turnover crosses ₹20 lakh in a year (₹10 lakh in the special category states), GST registration becomes mandatory, even if all your income comes from export clients and would be zero-rated anyway.
A lot of freelancers assume that because their services to foreign clients are not taxed, registration does not matter. It does. The turnover threshold is about your total turnover, not your GST liability, and failing to register once you have crossed it is a compliance gap that surfaces the moment your income is reviewed against your bank credits, regardless of whether you owed any actual GST.
Track your rolling annual turnover as you go, not just at year end, so crossing the threshold does not catch you unregistered for months before you notice.
Building a documentation habit, not a March scramble
The single biggest shift that prevents all four of these red flags is the same. Treat documentation as part of getting paid, not as a separate task you do later. For every payment, foreign or domestic, keep the invoice, the FIRA or TDS certificate (if any), and the bank statement entry together, filed by month, from day one.
Reconcile against your AIS at least quarterly, not just once a year, so a mismatch gets caught while it is still small and easy to explain rather than compounding over twelve months.
If you do get a notice
Do not ignore it, and do not panic either. Most notices, especially the automated ones triggered by an AIS mismatch, are resolved by responding with the correct documentation and a clear explanation within the timeline given, on the portal.
Read the notice carefully to understand exactly which section it is issued under and what specific discrepancy it is asking about, since the response needed for an AIS mismatch is very different from one needed for a Section 68 query.
If the notice touches on anything beyond a simple reconciliation, particularly Section 68 or VDA classification questions, that is the point to bring in a CA rather than responding yourself, since the wording of your response matters and a CA who handles these regularly will know exactly what documentation satisfies the officer's actual concern.
The cost comparison that makes this an easy decision
Building the habits above costs you, realistically, an hour a month of filing and reconciling. Responding to a tax notice, by contrast, costs you a CA's time (often more expensive than routine filing help, since it is urgent and specific), the stress of a deadline you did not choose, and in genuinely bad cases, penalties or interest on top of the tax itself. This is not close. The hour a month wins every time.
How DashX helps you stay compliant
For every payment settled through DashX, whether by bank transfer into your virtual account or in USDC or USDT, you get an invoice-to-FIRA-to-bank-statement trail that exists from the moment the payment lands. FIRA is issued at no charge on the fiat rail and available on the stablecoin rail, through our AD-1 bank partners (HDFC and JPMorgan), with the RBI purpose code matched to your service. That is exactly the documentation chain that closes off red flags 2 and 3 before they start.
The freelancers who never deal with a tax notice are not the ones who got lucky. They are the ones who made documentation a habit before they needed it. Try DashX.
For the documents that resolve common mismatches, see our AIS and TIS guide, FIRA guide, and ITR-4 guide.
