AIS TIS Mismatch: How to Correct Errors and Avoid Tax Notices

The Annual Information Statement (AIS) and Taxpayer Information Summary (TIS) have fundamentally changed how the Income Tax Department identifies discrepancies in tax returns. Since their full rollout, AIS/TIS mismatches have become the single largest trigger for automated processing adjustments under Section 143(1) — generating lakhs of intimation notices every assessment year.

For Chartered Accountants, understanding the AIS/TIS ecosystem is no longer optional. It is the first line of defense against unnecessary notices, demands, and the cascade of compliance issues that follow. This guide covers everything CAs need to know about identifying mismatches, correcting errors at source, and proactively protecting clients.

Understanding AIS and TIS: What They Are and How They Differ

Annual Information Statement (AIS)

The AIS, accessible through the income tax e-filing portal under the Compliance section, is a comprehensive record of a taxpayer's financial transactions as reported by third parties. It replaced the old Form 26AS (which now only shows TDS/TCS data) as the primary information repository.

The AIS captures information from multiple sources:

• TDS/TCS information from deductors and collectors
• Specified Financial Transactions (SFT) reported by banks, mutual funds, registrars, and other specified entities under Section 285BA(1)
• Interest income reported by banks and post offices
• Dividend income reported by companies and mutual funds
• Securities transactions reported by stock exchanges and depositories
• Immovable property transactions reported by registrars
• Foreign remittances reported under Form 15CA/15CB
• GST turnover data shared by GSTN
• Cash deposits and withdrawals above specified limits
• Credit card payments above Rs 10 lakh

Taxpayer Information Summary (TIS)

The TIS is a processed, aggregated version of the AIS. While the AIS shows raw transaction-level data, the TIS groups transactions by category and shows the derived value — the amount the department expects to see in your return. The TIS also shows:

• Reported value: What third parties reported
• Modified value: After any AIS feedback corrections
• Derived value: The department's computed figure after de-duplication and processing

The critical distinction is that the TIS derived value is what CPC uses for Section 143(1) processing. Even if the AIS shows correct individual transactions, a wrong derived value in TIS can trigger a mismatch notice.

The 8 Most Common AIS/TIS Mismatch Types

1. Duplicate Reporting of Interest Income

The problem: The same interest income gets reported by both the bank branch and the bank's central processing unit, or by both the old and new bank after a merger/acquisition. This doubles the interest income in AIS.

How to spot it: Look for two entries with the same amount from the same bank (or related entities) for the same quarter. Check if the SFT reporting entity name differs slightly from the TDS reporting entity.

Fix: File AIS feedback marking the duplicate as "Information is duplicate/included in other information." Retain bank statements and TDS certificates as proof.

2. Wrong PAN Attribution

The problem: A transaction gets attributed to the wrong PAN — common in joint bank accounts, joint property purchases, or when a company's transaction gets tagged to the director's PAN.

How to spot it: Income appearing in AIS that the taxpayer has no knowledge of. Cross-check with the reporting entity.

Fix: File AIS feedback selecting "Information relates to other PAN/year." Contact the reporting entity directly to correct the PAN in their SFT filing.

3. Timing Differences (Accrual vs. Receipt)

The problem: The taxpayer follows accrual accounting and recognizes income in FY 2024-25, but the payer reports the payment in FY 2025-26 when actual payment was made. Alternatively, FD interest accrued but not due appears in AIS based on TDS deduction timing.

How to spot it: Compare AIS amounts with the client's books of account. Look for income recognized in a different year than what AIS shows.

Fix: If the taxpayer has correctly reported the income in the right year, file AIS feedback explaining the timing difference. Maintain detailed reconciliation workpapers.

4. Mutual Fund Redemption Shown as Income

The problem: AIS shows the full redemption amount of mutual fund units as income, whereas only the capital gain component is taxable. This is the most common mismatch for investors and frequently inflates the TIS derived value.

How to spot it: Large amounts appearing under "Sale of securities/mutual funds" in AIS that don't match the capital gains declared in the return.

Fix: File AIS feedback with the correct capital gains figure. Maintain the capital gains statement from the AMC/CAMS/KFintech showing cost of acquisition and holding period.

5. Property Sale Registration Value vs. Actual Consideration

The problem: The registrar reports the stamp duty value of the property, which may exceed the actual sale consideration. The AIS picks up the higher stamp duty value. Under Section 50C, the stamp duty value is deemed consideration — but only if it exceeds actual consideration by more than 10% of the actual consideration..

How to spot it: Property sale amount in AIS is higher than what the client actually received.

Fix: If the actual consideration is within 10% of stamp duty value, no adjustment is needed — the actual consideration is acceptable. If above 10%, the stamp duty value applies. File AIS feedback only if the reporting itself is factually incorrect.

6. Share Trading Turnover Reported as Income

The problem: Stock exchanges report total transaction values (buy + sell) which appear in AIS. This gross turnover figure is vastly higher than actual profit/loss. For frequent traders, this creates massive apparent discrepancies.

How to spot it: AIS shows securities transaction values that are multiples of the capital gains declared in ITR.

Fix: File AIS feedback explaining that the amount shown is gross transaction value, not income. Maintain brokerage contract notes and capital gains computation.

7. Cash Deposits Triggering Scrutiny Flags

The problem: Cash deposits above Rs 10 lakh (savings) or Rs 50 lakh (current account) in a financial year are reported in AIS. These trigger automated flags even when the cash is from legitimate sources — agricultural income, cash sales by small businesses, or reinvestment of withdrawn cash.

How to spot it: Cash deposit entries in AIS that the taxpayer can explain but that the CPC might flag during 143(1) processing.

Fix: No correction needed in AIS (the reporting is factually correct). The defense is in the return itself — ensure the source of cash deposits is properly explained in the ITR, and maintain documentation including bank statements, cash flow statements, and source evidence.

8. GST Turnover Mismatch

The problem: GST turnover data shared by GSTN with the Income Tax Department may not match the income declared in ITR due to timing differences, credit notes, or different methods of revenue recognition under GST vs. Income Tax.

How to spot it: Compare the turnover figure in AIS (sourced from GSTR-3B or GSTR-9) with the turnover declared under "Business or Profession" in the ITR.

Fix: Maintain a detailed reconciliation between GST returns and income tax returns. Common differences include credit notes issued after GST filing, revenue recognition differences for long-term contracts, and GST on advances received.

Step-by-Step AIS Feedback Process

When a mismatch is identified, the correction process follows these steps:

Step 1: Login and Access AIS

Login to the e-filing portal (www.incometax.gov.in) with the client's credentials. Navigate to Services > Annual Information Statement (AIS). Select the relevant assessment year.

Step 2: Identify the Incorrect Entry

Review each category of information. Click on any entry to see the detailed transaction-level data. Compare each entry against the client's records.

Step 3: Submit Feedback

For each incorrect entry, click the Feedback button. Select the appropriate feedback type:

• Information is correct: Confirms the entry (no action needed)
• Information is not fully correct: Partial correction — enter the correct amount
• Information relates to other PAN/year: Wrong attribution
• Information is duplicate/included in other information: Duplicate entry
• Information is denied: The transaction did not occur

Provide the correct value where applicable and submit.

Step 4: Track Feedback Status

After submission, track the feedback status. The AIS will show the Modified Value reflecting your feedback. The TIS derived value should update within 2-4 weeks, but in practice it can take longer.

Step 5: Verify TIS Update

After feedback is processed, check the TIS to confirm the derived value has been corrected. If not, the mismatch will persist and CPC may still issue a 143(1) adjustment.

Step 6: Maintain Documentation

Keep screenshots of the AIS feedback submission, the original and corrected values, and all supporting documents. If a 143(1) intimation is still issued, this documentation is essential for the rectification or appeal.

How AIS Mismatches Trigger Section 143(1) Adjustments

The CPC at Bengaluru processes returns under Section 143(1) using automated algorithms. The process works as follows:

1. Return is filed with declared income figures
2. CPC pulls TIS derived values for the same PAN and assessment year
3. Automated comparison flags differences exceeding thresholds
4. Adjustment proposed under Section 143(1)(a) — the intimation notice shows the addition with a specific code
5. If no response within 30 days, the adjustment becomes final

The key insight for CAs: the comparison is between your ITR and the TIS derived value, not the raw AIS data. This means:

• Even if AIS feedback is filed, if TIS is not updated in time, the mismatch persists
• CPC does not manually review feedback — it is algorithmic
• The 30-day response window to a proposed adjustment is critical and non-extendable

Proactive Protection: A Checklist for CAs

The best defense against AIS-triggered notices is prevention. Here is a systematic checklist for every client:

Before Filing the Return

1. Download and review AIS/TIS for the relevant assessment year
2. Compare every category against the client's books and records
3. File AIS feedback for every incorrect or duplicate entry
4. Wait for TIS derived values to update before filing the return if possible
5. Where TIS shows incorrect amounts that cannot be corrected in time, maintain detailed reconciliation notes
6. Ensure the ITR includes all income shown in AIS — even if it is exempt or taxed differently
7. Use the reconciliation schedule in ITR forms where available

After Filing the Return

1. Re-check AIS/TIS 30 days after filing to confirm no new information has been added
2. If new entries appear, file revised return if within the time limit
3. Monitor the e-filing portal for any proposed adjustments under Section 143(1)
4. Respond to proposed adjustments within 30 days — do not let them become final by default

For High-Risk Clients

High-risk profiles include clients with multiple bank accounts, significant investment activity, property transactions, or business income with GST registration. For these clients:

1. Maintain a monthly AIS monitoring schedule
2. File AIS feedback promptly for any errors — do not wait until return filing season
3. Prepare a comprehensive AIS reconciliation statement as part of the audit/return preparation workpapers
4. Educate clients about reporting thresholds that trigger SFT filings

How AI Tools Can Help With AIS/TIS Compliance

The volume of AIS data makes manual review impractical for firms with large client bases. AI-powered tools can assist in several ways.

TaxNoticeAI automatically extracts AIS/TIS data from uploaded documents and cross-references it with the notice being responded to. When a 143(1) intimation references an AIS mismatch, the system identifies the specific category and suggests the appropriate correction strategy — whether it is an AIS feedback issue, a timing difference requiring documentation, or a genuine unreported income that needs to be addressed.

For CAs handling dozens or hundreds of 143(1) intimations triggered by AIS mismatches, the ability to quickly identify the mismatch type, generate the correct response, and cite relevant precedents (such as cases where ITAT has deleted additions based on unverified AIS data) saves significant time. The system's legal corpus includes ITAT and High Court decisions specifically dealing with AIS/TIS reliability, duplicate reporting, and the burden of proof in automated assessments.

Proactive AIS monitoring and early correction remains the best strategy. But when notices do arrive, having AI-assisted analysis ensures that no mismatch goes unaddressed and no deadline is missed.