An income tax notice is not a conclusion that tax has been evaded. It is an official communication from the Income Tax Department asking for one of several things: a correction, an explanation, supporting information, payment against a demand, or a fresh return in a reassessment context. The important point is procedural: identify exactly what the notice asks, the assessment year involved, the due date, and the response channel before doing anything else.
Change-sensitive portal features and timelines mentioned below are based on Income Tax Department pages reviewed on August 16, 2026, including the Department’s guidance on authenticating a notice or order, e-Proceedings, response to outstanding demand, and the Department’s assessment explainer at incometaxindia.gov.in.
What an income tax notice usually means
Most notices fall into one of these buckets:
- Return correction: the return filed has a defect or mismatch that needs to be cured.
- Processing adjustment: CPC proposes or finalises a tax computation adjustment while processing the return.
- Scrutiny or enquiry: the Department wants books, documents, explanations, or specific information.
- Demand or refund adjustment: an existing tax demand is being raised, confirmed, or adjusted against a refund.
- Rectification or reassessment: the Department is correcting an apparent mistake or reopening a case under the law applicable to escaped income proceedings.
That distinction matters because the correct response is different in each case. Uploading a revised computation to answer a scrutiny query is not the same task as curing a defective return or disputing an outstanding demand.
First checks before you respond
- Authenticate the notice. The Income Tax Department provides a pre-login facility to verify whether a notice, order, summons, letter, or other communication is genuine. The Department states that communications issued on or after October 1, 2019 should carry a DIN.
- Read the section and the exact request. The section number tells you the legal route, but the operative part is the action asked for: file a return, explain a mismatch, upload documents, pay demand, or object.
- Match the PAN, assessment year, and date. Many response errors happen because a taxpayer answers for the wrong year or uses records from the wrong entity.
- Check the response path. Some items are handled through e-Proceedings, some through Response to Outstanding Demand, and some through the pre-login Comply to Notice path for limited cases.
- Preserve evidence before submitting. Download the notice PDF, prepare working papers, and keep challans, ledgers, AIS/TIS extracts, bank statements, and reconciliation files ready.
Common notice types and what they usually indicate
| Notice or communication | What it generally means | Typical first response |
|---|---|---|
| Section 139(9) defective return | The return has a defect that must be cured. The e-Proceedings manual shows an agree/disagree response flow and, where applicable, upload of the correct JSON for the return. | Read the defect description carefully, identify whether the issue is form selection, missing schedules, invalid claims, or data mismatch, and prepare the corrected return data before replying. |
| Section 143(1)(a) prima facie adjustment | CPC proposes an adjustment during return processing. The Department’s assessment explainer states that the assessee is given 30 days to respond electronically before finalisation. | Compare the proposed adjustment with the filed return, Form 26AS, AIS/TIS, and supporting schedules. Accept only if the Department’s computation is actually correct. |
| Section 143(2) scrutiny notice | The return has been selected for detailed examination. The Department’s assessment explainer describes scrutiny as a detailed review of reported income, deductions, and tax liability. | Frame the issue list, collect source documents, and answer point-by-point. Treat this as a documentation exercise, not a one-line explanation exercise. |
| Section 142(1) enquiry before assessment | The Assessing Officer may require a return, books, documents, or information. The Department’s assessment explainer lists separate uses for filing a return, producing accounts/documents, and furnishing information. | Map each query to a document set and submit a structured reply. If books are requested, reconcile them to the return and financial statements. |
| Section 154 suo motu rectification | The Department may be correcting an apparent mistake. The e-Proceedings service specifically lists suo motu rectification as a notice type that can be responded to online. | Check whether the issue is a clear apparent error or whether the Department is effectively disputing a substantive claim. |
| Section 245 adjustment against demand / outstanding demand | A demand may be adjusted against refund, or an old demand may require response. The portal provides a dedicated outstanding demand workflow and access to section 245 notices. | Verify whether the demand exists, whether it is already paid, and whether the year and challan tagging are correct before agreeing to it. |
| Section 148 or section 148A-related proceedings | The Department’s assessment explainer treats this as income-escaping assessment territory. These are materially more serious than routine processing communications. | Read the reasons and procedural papers carefully, map prior filings and disclosures, and prepare the response year-wise with full evidentiary support. |
How the response process works on the portal
The Department’s e-Proceedings service is the main response channel for many notices, intimations, and letters. The portal states that a registered user, or an authorised representative, can view and submit responses there. The currently listed categories include defective notice under section 139(9), prima facie adjustment under section 143(1)(a), suo motu rectification under section 154, notices issued by the Assessing Officer, and seek-for-clarification communications.
The same guidance states that responses submitted through e-Proceedings do not require separate e-verification, and that the taxpayer can view submitted responses later. The user manual also notes that a successful submission generates a transaction ID, which should be preserved.
For outstanding tax demand matters, the Department provides a separate Response to Outstanding Demand workflow. The portal allows the taxpayer to state that the demand is correct, that it is correct but already paid, or that the taxpayer disagrees in full or in part. The Department also states that if no response is submitted, the demand may be confirmed and adjusted against refund if any.
A workable first-response method
- Build a notice file. Save the PDF, note DIN, section, assessment year, issue date, response due date, and portal path.
- Prepare a one-page issue summary. State what the Department says, what the records show, and what exact action you will take.
- Reconcile before drafting. Match the return with computation, books, Form 26AS, AIS/TIS, tax payment challans, and financial statements.
- Respond to the exact defect or query. Do not send a generic explanation when the notice asks for specific schedules, documentary proof, or a corrected filing.
- Upload organised support. Use labelled attachments that can be understood without oral explanation, such as ledger extracts, bank proofs, challans, invoice lists, or working notes.
- Keep the submission trail. Save the acknowledgement, transaction ID, and final response set.
Examples with explicit assumptions
Example 1: Defective return under section 139(9)
Assumptions: A resident individual filed a return for AY 2026-27. The Department issues a defective return notice because the income schedule and tax computation do not align with the form data.
Response approach: Download the notice, identify the exact defect code or description, rebuild the computation from source records, and prepare the corrected return data. If the defect stems from choosing the wrong return form, the return framework itself may need correction. A separate guide on how the main ITR forms differ is useful when the problem starts with form selection rather than arithmetic.
Example 2: Prima facie adjustment under section 143(1)(a)
Assumptions: A proprietor claimed an expense or deduction in the return, but CPC proposes an adjustment because the claim is inconsistent with the available data set or the return schedules.
Response approach: Compare the filed return with the supporting computation and the Department-visible data. If the claim is supportable, respond with a focused explanation and backing documents where the workflow permits. If the return itself contains the error, correct the filing position instead of arguing a weak claim.
Example 3: Section 245 demand adjustment
Assumptions: A company receives intimation that refund for one year may be adjusted against a prior-year demand. Internal records show tax for the earlier year was already paid, but the challan was not properly matched.
Response approach: Use the outstanding demand workflow, check the demand reference and year, pull the challan details, and respond that the demand is already paid with supporting particulars. Do not agree to the demand merely because the amount is small; agreement may close off the dispute path on the portal workflow.
Situations that materially change the answer
- Scrutiny or reassessment notices are not routine mismatch notices. The record set and legal framing are much more important.
- A notice may be correct even when the tax outcome is not. For example, the communication is genuine, but the underlying demand may still be disputed.
- Portal workflow matters. The response path for e-Proceedings is different from the response path for outstanding demand.
- Old demands need documentary tracing. Many disputes turn on challan mapping, rectification history, appeal effect, or earlier payments rather than on the current year return.
- Business taxpayers need books-backed replies. Ledger-level support is often more persuasive than narrative explanation.
Practical checklist for accountants and finance teams
- Confirm authenticity through the Department’s authentication facility.
- Capture section, DIN, PAN, assessment year, issue date, and due date.
- Download the notice PDF and preserve the submission trail.
- Reconcile the return with books, AIS/TIS, Form 26AS, challans, and financial statements.
- Classify the notice correctly: defect, adjustment, scrutiny, enquiry, rectification, demand, or reassessment.
- Prepare a response that addresses the specific issue raised, not a general tax position.
- Where a demand is involved, decide separately whether it is correct, already paid, or disputed.
- Retain transaction ID, acknowledgement, and the exact attachment set submitted.
Why this matters in professional work
Income tax notice handling is less about drafting style and more about classification, reconciliation, and procedural accuracy. A short notice can still affect refunds, create demand, trigger best-judgment consequences for non-compliance, or move the case into a deeper assessment track. Professionals who respond well usually do three things consistently: they identify the notice category correctly, they reconcile records before replying, and they preserve the response trail completely.
