Defective ITR Notice: How to Read and Respond Carefully

A defective return notice identifies a curable problem. Ignoring it can cause the return to be treated as invalid.

For the connected rule or filing step, see Notice for Non-Filing of ITR: How to Respond.

What the taxpayer should understand

• India’s Income-tax Act, 2025 took effect on 1 April 2026. The 1961 Act continues to govern tax years beginning before that date. Therefore, FY 2025–26 and AY 2026–27 remain governed by the 1961 Act, while tax year 2026–27 beginning 1 April 2026 is governed by the 2025 Act. A notice, return, payment or form must be analysed under the law applicable to the relevant tax year and event—not merely the date on which the portal communication is received.
• The official portal FAQ states that the taxpayer ordinarily receives fifteen days from receipt of the notice, or the period stated in the notice, to rectify the defect.
• The response should address the exact defect code and use the return form and utility applicable to the relevant year.
• The taxpayer can agree and submit corrected return data or disagree with reasons and evidence through the prescribed process.
• Defective-return treatment can arise from incomplete schedules, inconsistent income/TDS reporting, audit information, balance-sheet items or VDA disclosures.

The five-point review

Practical example

How to apply the framework

Recreate the complete return in the applicable utility; changing only one field can create a second inconsistency.

Where the defect is disputed, explain the facts and cite the exact schedule and attached evidence.

Tax-control workflow

Fix the period, governing Act and portal document

Identify the financial year, assessment year or tax year, the date of the underlying event and the statutory document. A communication received after 1 April 2026 may still concern a year governed by the 1961 Act. Record notice, return and mismatch before preparing the response or return.

Reconcile the portal with primary evidence

Start from contracts, certificates, bank statements, broker or property records, foreign statements and prior filings. Then reconcile AIS, TIS, Form 26AS, the return, tax payments and notices. Portal information is a powerful control but can contain gross values, duplicates, timing differences or reporting-entity errors.

Submit through the correct route and retain proof

Use the specific service—return filing, AIS feedback, e-Proceedings, rectification, refund reissue, Form 67, appeal or grievance—rather than uploading the same explanation everywhere. Preserve the filed form or response, computation, annexures, transaction ID, acknowledgement and subsequent portal status.

Implementation checkpoint

Before closing the task, verify the live portal outcome rather than relying only on a submission message. Confirm whether the return is verified, the feedback is recorded, the tax credit changed, the refund was reissued, the notice response shows a transaction ID, the demand was adjusted or the appeal was registered. Record the next deadline and unresolved amount.

Action checklist

• Download notice and original return.
• Decode the stated defect.
• Reconcile all linked schedules.
• Prepare corrected data or reasoned disagreement.
• Submit within the stated time.
• Save acknowledgement and corrected computation.

Evidence to keep

• Defective notice
• Original ITR/JSON
• Revised computation
• Supporting statements
• Response acknowledgement

Warning signs

Finin2min takeaway