What Is a Defective Return Notice Under Section 139(9)?
A Section 139(9) notice means the return has a defect that must be corrected within the allowed time. If not fixed, the return may be treated as invalid.
A practical guide to defective return notices, common causes, response timelines, correction steps, and when to get CA help.
At a glance
| Point | What it means for you |
|---|---|
| 1 | 139(9) needs timely correction. |
| 2 | Wrong form is a common cause. |
| 3 | Do not resubmit without fixing the defect. |
What this guide covers
Defective return notices are more common than most salaried taxpayers expect, and they are almost always caused by something that could have been caught before filing. This guide covers the practical rule for FY 2025-26 income filed in AY 2026-27, the documents to check, the key decision points, and the mistakes that most often lead to defective returns, refund delays, or incorrect tax demands.
The right approach is to treat the return as a reconciliation exercise rather than a form-filling task. Salary, interest, capital gains, freelance income, foreign assets, trading income, deductions, and tax paid should all trace back to a source document. If the return produces a refund, a demand, a loss claim, a foreign disclosure, or a regime change, the working papers should be able to explain every number before submission.
Why this notice catches people by surprise
Reddit threads on defective notices show a consistent pattern: wrong form chosen, a missing schedule, or figures that contradict each other. The underlying reasons usually fall into three categories.
First, timing confusion: filing utility availability, Form 16 issue dates, AIS updates, TDS return processing, due dates, revised-return windows, and updated-return windows do not all align. Taxpayers who start filing as soon as the portal opens often work with incomplete data.
Second, eligibility confusion: ITR-1, ITR-2, ITR-3, ITR-4, old regime, new regime, presumptive taxation, and foreign asset schedules each apply to different taxpayer profiles. Selecting a form because it looks familiar, rather than because it matches the income, is a reliable path to a 139(9) notice.
Third, evidence confusion: a bank credit, a broker statement, a Form 16, a Form 16A, an AIS entry, a Form 26AS credit, and a final return computation each prove different things. Treating them as interchangeable creates inconsistencies that the department's processing systems catch.
What the law and the department say
Under Section 139(9), the department can treat a return as defective where required information, schedules, or consistency checks fail. The taxpayer is given an opportunity to correct the return within the specified period.
For AY 2026-27, income earned during FY 2025-26 should be reported by selecting AY 2026-27. The Income Tax Department's transition guidance confirms that AY 2026-27 returns continue under the Income Tax Act, 1961 framework for that year. The return should therefore be built around the law, form instructions, and portal utilities applicable to AY 2026-27.
AIS and TIS help identify income that others have reported against your PAN. Form 26AS helps confirm tax credits and payments. Form 16 and Form 16A reconcile TDS. The key point: if official records are incomplete or wrong, do not blindly copy them. Review the underlying evidence, submit AIS feedback where appropriate, ask the deductor to correct TDS returns if needed, and document the treatment you have taken.
Documents to keep ready
| Document | Why it matters |
|---|---|
| Notice or intimation PDF | Defines the response route, deadline, and the specific issue the department has raised. |
| Response acknowledgement | Proof that rectification, grievance, notice reply, or other action was submitted. |
| AIS and TIS | Reported income and transaction data to compare against your own records. |
| Form 26AS | TDS, TCS, advance tax, self-assessment tax, refund, and demand details mapped to your PAN. |
| Computation working | The bridge between source documents, taxable income, tax paid, and refund or demand. |
| Final ITR acknowledgement | Confirmation that the return was submitted and e-verified. |
Prefilled portal data is a starting point, not a verified computation. Always check figures against source documents before filing or responding to a notice.
A practical illustration
Using the wrong ITR form, leaving business schedules incomplete, or filing figures that are inconsistent with a tax audit requirement — these are the most common triggers for a 139(9) notice.
When reviewing a case, work in three passes. First, identify the income period and assessment year. Second, confirm which form and which schedules legally apply to the income being reported. Third, compare tax deducted, tax paid, and tax payable. If all three passes are consistent, the return is ready for a final review. If one pass fails, stop. That is where the defect almost certainly is.
For salaried taxpayers, the evidence file typically includes Form 16, monthly payslips, AIS, Form 26AS, a bank interest certificate, rent proof where applicable, a housing loan certificate, and investment proof. For investors, add broker capital gains reports, mutual fund statements, dividend entries, STT details, and AIS securities data. For freelancers and business owners, add invoices, bank statements, Form 16A, GST returns, expense documentation, and books. Foreign asset cases need foreign bank statements, ₹U or ESPP statements, broker reports, foreign tax certificates, exchange-rate workings, and Form 67 evidence.
Response checklist
- Read the defect code in the notice carefully.
- Identify exactly what data is missing or inconsistent.
- Prepare a corrected return addressing the specific defect.
- Submit the response within the allowed time.
- Save the acknowledgement of the response.
Before submitting the corrected return, check the return preview. Verify name, PAN, assessment year, bank account, filing section, regime selection, ITR form, schedule count, taxable income, TDS, self-assessment tax, refund or demand, and e-verification mode. Most defects are visible in the preview if the taxpayer reviews it carefully.
Choosing the right next action
| Situation | Practical next action |
|---|---|
| Return not filed yet | Reconcile records first, then choose the correct AY 2026-27 ITR form and schedules. |
| Portal data and personal records differ | Check the source document, give AIS feedback where relevant, and keep a note before filing. |
| Return already filed with a mistake | Check whether revised return, rectification, ITR-U, grievance, or notice response is the correct route. |
| Refund, notice, capital gains, business income, or foreign assets involved | Use CA review before submitting a final position. |
Paying a demand, filing a revised return, using ITR-U, submitting AIS feedback, raising a grievance, and replying to a notice are not interchangeable. Each route solves a different problem. Match the action to the document and statutory window in front of you.
Errors that make things worse
- Ignoring the notice and hoping it resolves itself.
- Uploading the same defective data again in the corrected response.
- Selecting the same wrong form for the second time.
- Waiting until the last day to deal with it.
Filing ITR-1 when ITR-2 or ITR-3 is required is a reliable way to get a 139(9) notice. Trying to use ITR-U to reduce tax or increase a refund often fails because the updated return route has restrictions. Claiming TDS credit without reporting the related income can delay refunds. Ignoring Schedule FA because the foreign income seems small can create a disclosure problem that is far more serious than the tax amount. Selecting a tax regime without checking deduction eligibility, business income rules, or Form 10-IEA implications can generate a demand or forfeit a benefit.
Also, do not treat portal data as complete too early in the season. AIS, Form 26AS, and TIS continue to update as deductors, banks, brokers, and employers file or correct their statements. If the return depends on a large refund or a disputed entry, waiting for cleaner data — or documenting your evidence clearly — is usually better than rushing.
What to preserve after responding
Keep the full file: final computation, AIS download, Form 26AS, source statements, bank records, deduction proofs, challans, the final ITR acknowledgement, the notice PDF, your response, and the response acknowledgement. Name files clearly — for example, "AY-2026-27-AIS.pdf", "Form-16-employer-name.pdf", "Capital-gains-broker-report.xlsx", or "143-1-intimation-response.pdf". Clear file names save significant time if a CA needs to review the case or the department follows up later.
Deciding what to do next
If the return has not been filed, complete reconciliation first, then file the correct form. If the return has been filed and the revision window is open, a revised return may be appropriate. If the issue is an apparent processing mismatch, rectification may apply. If the window is closed and additional income must be disclosed, updated return is possible but only within its statutory restrictions. If a notice has arrived, read it fully before choosing any route.
Useful tools
When a CA review is worth it
Get professional input when the case involves capital gains, trading income, foreign assets, foreign tax credit, freelance or business income, a large refund, an AIS mismatch, a demand notice, a defective return notice, or any uncertainty about the correct ITR form.
The tax exposure in some of these situations is smaller than the compliance risk of getting it wrong. Foreign asset disclosures, form selection errors, missed business income, and invalid correction routes can create problems that outlast the filing season. A CA review should leave you with a clear explanation of the filing position, checked evidence, and a defensible computation.
Final takeaway
139(9) needs timely correction. Wrong form is a common cause. Do not resubmit without fixing the defect.
A defective return notice is not a catastrophe, but it needs prompt attention. Treat it as part of the broader AY 2026-27 filing review. A clean return is built from consistent treatment across income, supporting statements, tax credits, schedules, and declarations. Where facts are routine, the checklist above may be enough. Where facts are mixed, disputed, or high-value, get the position reviewed before responding.
CA technical notes
For refund and notice matters, the technical review should reconcile the filed return with Form 26AS, AIS, TIS, challans, the intimation, the defect code, the department's demand computation, bank validation, e-verification status, and the response deadline. Rectification, revision, updated return, grievance, and payment are separate routes and should not be used interchangeably.
For the defective return scenario, document the working position using the taxpayer's facts, the AY 2026-27 form selected, the records used for computation, and why each major figure appears in the return. The note should explicitly cover whether the issue affects form selection, income classification, deduction eligibility, tax credit matching, refund timing, notice response, or the completion of any disclosure schedule.
The minimum evidence file should include the source statement behind each position, the calculation sheet, portal screenshots or downloads, and proof for every adjustment. Where the position depends on timing — AIS updates, Form 16 issue date, revised-return deadline, ITR-U restrictions, e-verification, or a notice response window — record the date alongside the decision. Where it depends on classification — capital gains versus business income, resident versus non-resident, old versus new regime, or foreign income versus Indian receipts — record the reason for that classification before filing.