Defective Return Notice Under Section 139(9): Why It Happens and How to Fix It
A defective return is not a rejected one. It is a fixable paperwork problem with a short clock attached, and ignoring it is what turns it serious.
CA Helper Editorial Team
Tax & Compliance Desk
Published · 6 min read
Key takeaways
- A 139(9) notice flags a fixable defect, but ignoring it converts a paperwork problem into a non-filing.
- You normally have 15 days, extendable on request through the portal if you ask before the window closes.
- The most common defect by far is claiming TDS credit without reporting the income on which it was deducted.
- Respond through Pending Actions and e-Proceedings, not by filing a separate fresh return.
- Verify the corrected return afterwards, since an unverified response leaves you exactly where you started.
A notice under Section 139(9) tells you that your return has been examined, found internally inconsistent or incomplete in a specific way, and can be fixed. That is genuinely all it means. It is not an allegation, it is not scrutiny, and it does not suggest anyone suspects you of anything. What makes it dangerous is the clock: you normally have 15 days to respond, and a return left uncorrected past the window is treated as though it was never filed. A minor formatting problem, ignored, becomes a non-filing.
How a Defect Differs From a Demand
It helps to place 139(9) among the notices you might receive, because the correct response differs sharply. An intimation under Section 143(1) is the department's computation of your return set beside your own, and it may show a refund, a demand, or agreement. A 139(9) notice comes earlier and is different in kind: the return cannot be processed properly at all until the defect is cured, so no meaningful computation has happened yet.
| Section 139(9) | Section 143(1) | |
|---|---|---|
| What it says | Your return has a fixable defect | Here is our computation against yours |
| Stage | Before proper processing | After processing |
| Typical window | 15 days, extendable on request | 30 days to respond to any demand |
| If you ignore it | The return is treated as never filed | The demand hardens and can absorb future refunds |
| How you respond | Correct and resubmit the return | Rectification, revised return, or a demand response |
The Seven Defects That Cause Almost All of These
- TDS credit claimed without the corresponding income being reported. This is the single most common cause: the system can see tax deducted on an amount that never appears in your income, and treats the return as incomplete.
- The wrong ITR form for your income profile, such as filing the simplest form despite having capital gains, more than one house property, or non-resident status.
- Gross receipts or turnover in the return not matching what is reported against your PAN in Form 26AS and your Annual Information Statement.
- Mandatory schedules left blank where your income requires them, or a profit and loss account and balance sheet omitted where business income is declared.
- Tax payable per the return not actually paid, so the return is filed showing a liability that was never discharged.
- An audit report required under the Act not filed, or filed after the return that depends on it.
- Basic identifying or bank details missing or internally inconsistent, which prevents the return from being processed or any refund from being issued.
The first of these deserves particular attention because it catches honest filers. A freelancer whose client deducted TDS on a payment, or a saver whose bank deducted TDS on interest, claims the credit visible in Form 26AS but omits the underlying receipt from their income. The claim and the income have to move together. If you want the credit, the corresponding income has to be in the return, which is precisely what our guide to reconciling Form 26AS and AIS is about.
Responding on the Portal
- Log in to the e-filing portal and open Pending Actions, then e-Proceedings, where the notice will be listed against the relevant assessment year.
- Open the notice and read the stated defect code and description. It names the specific problem rather than leaving you to guess, and the fix follows directly from it.
- Decide whether you agree. If the defect is real, prepare a corrected return. If you believe the return was already correct, you can respond disagreeing and explaining why, which is a legitimate option rather than a confrontational one.
- Where you agree, prepare the corrected return in the appropriate utility, keeping the original acknowledgement number and filing it in response to the notice rather than as a fresh return.
- Submit the response within 15 days. If you genuinely need longer, request an extension through the portal before the window closes rather than after.
- Verify the corrected return, since a response that is submitted but not verified leaves you in the same position you started in.
- Track the status until the notice shows as closed and the return moves into normal processing.
One point on mechanics that people get wrong: a 139(9) response is filed in response to the notice, not as a standalone revised return. Filing a fresh return instead of responding through the e-Proceedings route can leave the original defect open on the system while a second return sits alongside it, which produces a messier problem than the one you started with.
If the 15 Days Have Already Passed
The consequence of a lapsed window is that the return is treated as invalid, as though it was never filed. Everything follows from that: no processing, no refund, no carry-forward of losses, and the exposure that comes with non-filing where filing was required. In practice the department may still permit a late response in some cases, so it is always worth checking whether the notice remains open on the portal and responding if it does. Where the window has genuinely closed, your remaining options depend on the calendar. If the belated return window is still open, you can file a belated return, accepting the fee and the loss of the old regime option. If it has closed, the route narrows to an updated return, which cannot produce a refund, or a condonation application under Section 119(2)(b) where a refund or loss claim is at stake. Our comparison of revised, belated, and updated returns sets out which applies.
The reliable way to never see one of these is unglamorous. Pull Form 26AS and your AIS before filing rather than after, reconcile every TDS entry against a corresponding line of income, and choose the return form from the nature of your income rather than from what looks simplest. Almost every defect notice traces back to one of those three steps being skipped.
Frequently asked questions
Sources and official references
Rules and rates change. These are the primary sources for the topics covered above, and the place to confirm anything before you act on it.
Disclaimer
This article is for general informational purposes only and does not constitute professional tax, legal, or financial advice. Rules and rates change, so consult a qualified Chartered Accountant for advice specific to your situation.
Related reading
Condonation of Delay Under Section 119(2)(b): The Last Route to a Missed Refund
An updated return can never give you a refund. When the money is owed to you and the deadlines have gone, this is the one door still open.
How to E-Verify Your ITR: Every Method and the 30-Day Rule
An unverified return is not a late return. It is treated as never filed at all. Here is every way to verify, and which one to pick.
Section 245: When Your Refund Is Adjusted Against an Old Tax Demand
The refund you were expecting can be swallowed by a demand from a year you had forgotten about. You get one chance to object, and it expires quietly.