AIS Mismatches — The #1 Reason CAs Get Section 143(1) Notices in 2026

If you are a Chartered Accountant handling individual or business returns, this is the one development you cannot afford to ignore in Tax Year 2026-27: the Income Tax Department's Annual Information Statement (AIS) is now the single most powerful tool the department has for catching unreported income. And with automated processing under Section 263(1) of the IT Act 2025, mismatches between your client's AIS and their filed return trigger notices faster than ever before.

In this article, we break down what AIS mismatches are, the most common categories that trigger notices, and a practical framework for reconciling AIS data before filing.

What Is the AIS and Why Does It Matter More Than Ever?

The Annual Information Statement (AIS) is an expanded version of the old Form 26AS. While 26AS primarily tracked TDS credits, the AIS captures a much broader range of financial transactions reported to the department by banks, mutual funds, registrars, depositories, and other reporting entities.

Starting TY 2026-27, Form 168 replaces Form 26AS with integrated AIS data, making the AIS the definitive record of a taxpayer's financial footprint as known to the department. Every transaction reported by a third party appears here — whether the taxpayer is aware of it or not.

What the AIS Tracks

• Salary income: As reported by employers through Form 130 (erstwhile Form 16)
• Interest income: Bank FDs, savings accounts, post office deposits, recurring deposits
• Dividend income: From shares and mutual funds
• Securities transactions: Purchase and sale of shares, mutual fund units, bonds
• Immovable property: Purchase or sale of property above specified thresholds
• Foreign remittances: Under the Liberalised Remittance Scheme (LRS)
• Cash deposits/withdrawals: Amounts exceeding ₹10 lakh in savings or ₹50 lakh in current accounts
• High-value transactions (SFT): Specified Financial Transactions reported by banks, mutual funds, registrars
• Crypto/VDA transactions: Virtual Digital Asset transactions (Code 1037)

The 5 Most Common AIS Mismatches That Trigger Notices

1. Unreported Interest Income

This is by far the most frequent mismatch. Many taxpayers maintain multiple bank accounts and fixed deposits across banks. While the bank reports every rupee of interest to the department, taxpayers often forget to include interest from dormant accounts or old FDs. Even ₹5,000 of unreported interest can trigger a Section 263(1) intimation notice.

2. Dividend Income Mismatch

Post the 2020 amendment (continued under IT Act 2025), dividends are taxable in the hands of the recipient. Mutual fund dividends, REIT distributions, and share dividends all appear in the AIS. Taxpayers who held the "dividends are tax-free" belief from the pre-2020 era sometimes omit these entirely.

3. Capital Gains from Mutual Fund Redemptions

When a taxpayer redeems mutual fund units, the registrar reports the transaction to the department. If the taxpayer fails to compute and report the capital gain (or reports it under the wrong head or with incorrect cost of acquisition), the mismatch appears instantly.

4. Property Transactions

Sale or purchase of immovable property above ₹30 lakh triggers SFT reporting. If a taxpayer sells a property but fails to report the capital gain, or reports it with an incorrect sale consideration (lower than the stamp duty value), the AIS will flag it.

5. TDS Credit Gaps

Sometimes the TDS deducted by a payer doesn't match what the taxpayer claims in their return. This can happen due to timing differences (deductor files late), incorrect PAN linkage, or the taxpayer claiming TDS that belongs to a different PAN.

How to Reconcile AIS Data Before Filing

Every CA should build AIS reconciliation into their standard pre-filing checklist. Here is a practical workflow:

1. Download the AIS from the e-filing portal (incometax.gov.in → AIS under "Information" tab)
2. Cross-check every line item against the taxpayer's books, bank statements, and demat holdings
3. Identify mismatches — categorize each as: (a) genuine unreported income, (b) duplicate entry, (c) incorrect amount, or (d) belongs to another PAN
4. Submit AIS feedback for incorrect entries using the feedback mechanism on the portal
5. Report all genuine income in the return, even if it seems small — the department's systems flag everything
6. Document your reconciliation in a working paper for each client — if a notice comes, you have the trail ready

The Risk Pyramid: What Gets Flagged First

Not all mismatches are treated equally by the department's automated systems. Based on publicly available information and practitioner experience, here is a rough risk hierarchy:

The Cost of Ignoring AIS Mismatches

A Section 263(1) intimation is just the beginning. If the mismatch results in additional tax demand, the taxpayer faces interest under Section 234A/B/C (equivalent new sections), and potentially penalty under Section 302 (erstwhile 270A) for under-reporting income. In severe cases involving deliberate concealment, Section 303 (erstwhile 271(1)(c)) penalties can go up to 200% of the tax sought to be evaded.

The math is simple: spending an hour reconciling AIS data before filing can save your client thousands in penalties and months of correspondence with the department.

Conclusion

AIS reconciliation is no longer optional — it is a core competency for every tax professional in the post-IT Act 2025 era. The department's systems are automated, fast, and comprehensive. The only defense is proactive reconciliation before filing. Build it into your workflow, invest in tools that speed up the process, and educate your clients about the importance of complete disclosure.