The income tax notice has changed character. It is no longer the product of an officer manually picking a file; it is increasingly generated by a data system that has already cross-checked your return against everything third parties have reported about you. For AY 2026-27, the Income Tax Department flagged close to 1.65 lakh cases for scrutiny, roughly three to four times the usual volume and more than a lakh taxpayers received notices under Section 143(2). The compliance net has widened well beyond high-income individuals.
For startup founders, SME promoters and freelancers, the exposure is higher than for an ordinary salaried filer, because their financial footprint is messier: mixed income streams, ESOP transactions, director remuneration, GST turnover, and high-value current-account flows. Every one of those is a data point the system can match or find a mismatch in. This article explains how the department's analytics actually work, the specific triggers that matter for a startup or SME, the fix for each, and a reconciliation checklist to run before you file. The goal is not fear; it is to file a return that survives an automated match on the first pass.
How the system actually works
It helps to know the machinery, because the triggers make sense only once you do. The department's analytics backbone is Project Insight , supported by two centres: INTRAC (the Income Tax Transaction Analysis Centre), which processes data, monitors quality and generates alerts, and CMCPC (the Compliance Management Centralized Processing Centre), which issues bulk notices and manages follow-up.
The taxpayer-facing output of all this is the Annual Information Statement (AIS) and its summarised cousin, the Taxpayer Information Summary (TIS) . From AY 2023-24, Form 26AS shows only TDS/TCS data; the broader picture - interest, dividends, securities transactions, property dealings, foreign remittances and reported high-value transactions, now sits in the AIS, aggregated from banks, registrars, depositories, mutual funds and other reporting entities through the Statement of Financial Transactions (SFT) mechanism.
On top of this data layer, the department uses AI-assisted analytics to flag high-value transactions, identify PANs linked to suspicious or inconsistent claims, detect patterns across returns, and build a 360-degree view of each taxpayer's financial activity. Scrutiny cases are then selected through CASS (Computer Assisted Scrutiny Selection), and lower-grade mismatches are pushed out under the e-Verification Scheme, which invites the taxpayer to explain the discrepancy or file an updated return before formal proceedings begin. The practical takeaway: by the time you file, the department often already holds the figures it expects to see.
The triggers that matter for startups and SMEs and the fix for each
1. AIS vs ITR mismatch on income
The single most common trigger. Interest on savings and fixed deposits, dividends, and capital gains on shares and mutual funds are all reported into the AIS and are precisely the items founders and busy promoters forget. A return that omits ₹90,000 of FD interest sitting in the AIS is flagged almost automatically.
Fix: Download both the AIS and TIS before filing, reconcile every line against your books and bank statements, and report all of it. Where an AIS entry is genuinely wrong or duplicated, use the AIS feedback facility to flag it rather than simply ignoring it.
2. GST turnover vs income-tax turnover mismatch
For any GST-registered business, the turnover declared in GSTR-3B and GSTR-9 is matched against the turnover in the ITR and tax audit report. A divergence is one of the most frequent business-scrutiny triggers, and the gap is often explainable — exempt supplies, RCM, non-operating income, or timing, but only if you can show the reconciliation.
Fix: Prepare a documented turnover reconciliation between the GST returns, the books, and the ITR before filing. Keep the workings; if a notice arrives, the bridge between the two figures is your answer.
3. High-value and cash transactions reported via SFT
Reporting entities file SFTs for transactions above prescribed thresholds — broadly, cash deposits aggregating ₹10 lakh in savings accounts, ₹50 lakh in current accounts, property transactions of ₹30 lakh or more, and purchases of shares, mutual funds or bonds of ₹10 lakh or more, among others. These land in the AIS whether or not you report the underlying income.
Fix: Treat the SFT entries in your AIS as a checklist of what the department already knows. Ensure the income or source behind each high-value transaction is reflected and explainable - capital introduced, a loan, sale proceeds with documentation kept on file.
4. Unreconciled bank credits and director/partner current accounts
In closely held companies and firms, money routinely moves between the promoter and the business - capital introductions, loans, reimbursements, inter-company transfers. To the system, an unexplained credit can look like unreported income, and Section 68 (unexplained cash credits) is an officer's favourite.
Fix: Tag every significant non-revenue credit correctly in the books - capital, loan, or transfer and maintain the trail (loan confirmations, board resolutions, banking channel evidence). Clean current-account narration is the cheapest insurance against a Section 68 addition.
5. Director remuneration and TDS mismatches
Director salary should reconcile across three places: the company's deduction, the TDS deducted under Section 192 (or Section 194J for professional fees), and the amount reflected in the director's own 26AS and return. A mismatch - salary claimed by the company but TDS or income not matching in the director's record - invites questions on both sides.
Fix: Keep director remuneration, the TDS section applied, Form 16/16A, and the directors' personal returns consistent. Make sure the company has correctly reported itself as a deductor so the credit flows into the directors' 26AS.
6. ESOP and equity transactions
ESOPs create two separate taxable events, the perquisite on exercise and capital gains on sale — and both leave a data trail. Foreign ESOPs add a further layer: the shares are a foreign asset requiring disclosure in Schedule FA, a high-priority area for the department's foreign-asset analytics.
Fix: Report the perquisite on exercise (and apply the Section 192(1C) deferral correctly if the company is an eligible startup), report capital gains on sale, and disclose foreign-held shares in Schedule FA. Non-disclosure of foreign assets carries consequences well beyond an ordinary mismatch.
7. Rental and property income, and HRA cross-checks
Rental income not reported, or HRA claims where the landlord's PAN and reported rental income do not align, are now routinely matched. Where a founder owns property held in a spouse's name but receives the income, clubbing provisions add another layer the system can probe.
Fix: Report rental income in full, ensure HRA claims are backed by genuine rent with the landlord's PAN where required, and apply clubbing provisions correctly where ownership and income diverge.
The pre-filing reconciliation checklist
Run this before you file, not after the notice:
- Download and reconcile the AIS and TIS against books and bank statements; submit feedback on any incorrect entry.
- Bridge GST turnover (GSTR-3B/9) to ITR turnover with documented workings.
- Match every SFT/high-value entry to a reported, explainable source.
- Tag and document all non-revenue bank credits (capital, loans, transfers).
- Reconcile director remuneration, TDS section and 26AS across the company and the directors.
- Capture ESOP perquisite, capital gains and Schedule FA disclosures.
- Confirm rental income and HRA align with reported data and landlord PANs.
- Verify all TDS credits in 26AS before claiming them.
If a notice does arrive
A notice is not an accusation. Much of what the system generates is a Section 143(1)(a) intimation proposing an adjustment, or an e-Verification communication asking you to explain a mismatch — both answerable with a reconciliation. The key is to respond within the stated window rather than letting it escalate to scrutiny under Section 143(2) or reassessment under Section 148. Where a genuine omission has occurred, an updated return under Section 139(8A) — now available within 48 months of the end of the assessment year following the Finance Act 2025 extension — allows you to correct it with additional tax rather than face penalty proceedings.
Conclusion
Data-driven assessment rewards one thing above all: a return that reconciles to the information the department already holds. For a startup or SME with multiple income streams, GST turnover, ESOPs and director flows, that reconciliation is genuine work, but it is work done best before filing, when a mismatch is a correction rather than a notice. The businesses that stay off the radar are not the ones with nothing to report; they are the ones whose numbers tie out.
The author is the founder of Patron Accounting LLP, a multi-disciplinary CA & CS firm headquartered in Pune with offices in Mumbai, Delhi and Gurugram, advising 25,000+ businesses, startups and SMEs on income tax, ITR filing, GST reconciliation and audit. The firm regularly helps companies reconcile AIS, GST and book data before filing to minimise scrutiny exposure.
CAclubindia
