Income-tax Reassessment Notice on the Portal: Service, Response Evidence and Deadline Controls
Finin2min 2-Minute Summary
- A reassessment file should begin with the exact notice PDF, portal event date, tax year and legal provision - not with an email subject line.
- Electronic service questions are evidence questions: preserve portal downloads, communication history, email/SMS alerts and response acknowledgements.
- Never calculate the response period from memory; use the date and wording appearing on the operative communication and the law applicable to that proceeding.
- If jurisdiction, limitation or service is disputed, raise the point without sacrificing a timely factual response where possible.
Current position
Reassessment is an area where procedure and evidence can be as important as the underlying tax issue. Taxpayers now receive and respond to many communications electronically through the Income Tax e-Filing system. The correct starting point is the operative notice or order available in the account: identify the tax year, statutory provision, issuing authority, document identification details, date of issue, date appearing in the portal record and the response period stated. Because reassessment law has changed over time, the applicable provision must be tied to the relevant tax year and procedural event rather than assumed from a current article or an old template.
How to analyse the issue
Service disputes are fact-sensitive. A taxpayer who says that a notice was never seen should still collect objective system evidence: portal communication history, registered email and mobile details, downloaded notice metadata, alerts, login records where available, and subsequent orders referring to the notice. If the notice is visible, preserve it immediately rather than relying on a screenshot alone. If the taxpayer plans to challenge jurisdiction, limitation or the manner of service, the response should avoid unnecessary admissions while still protecting the factual record. Silence can allow the proceeding to move ahead on available information, which may make the later dispute harder.
Worked India-specific example
Suppose a taxpayer discovers an old reassessment communication while checking the portal after receiving a demand alert. The first task is not to draft a merits reply. Download the notice, the later communication, any order and the communication history; verify the tax year and statutory path; identify whether a response window remains; then reconcile the issue with the original return, AIS, bank records and books. If the taxpayer disputes service because the registered email was obsolete, that fact should be documented, but the portal record must still be examined. The file should distinguish the procedural objection from the explanation of the underlying income item.
Documents and evidence to preserve
Preserve the original notice PDF, portal communication screen exported or printed to PDF, email/SMS alerts, profile contact details, response submission PDF, attachment list, acknowledgement number, original ITR and computation, AIS/TIS/26AS used for reconciliation, tax-payment challans and any subsequent order or demand. Where a professional representative is involved, keep the authorisation and proof of what was filed on each date. An indexed chronology is especially useful because reassessment cases can involve several communications with similar titles.
Common mistakes and control points
The most common operational mistake is answering only the substantive tax point while ignoring the notice's procedural framework. Others include relying on an email copy instead of the portal document, missing attachment acknowledgements, calculating a deadline from the date the taxpayer happened to open the notice, and using a reply prepared for a different reassessment regime. Do not assume that a defective service argument automatically cures a missed merits response; manage both tracks carefully.
Professional close-out file
A reassessment response file benefits from a communication register. Record the notice identifier, provision, notice date, portal appearance date, email or SMS alert, response due date, submission ARN and every attachment uploaded. If service or jurisdiction is disputed, preserve that objection separately while still tracking the merits response. This avoids an evidentiary problem in which the taxpayer can prove a substantive explanation but cannot later establish which communication it answered or when the electronic submission was made.
FAQs
Should I rely on the email alert as the notice?
Use the operative notice or order from the official portal as the primary record; the email or SMS is supporting evidence.
How should the response deadline be calculated?
From the applicable law and the wording/date of the operative communication, not from a generic internet timeline.
Can service and merits both be disputed?
Yes. Keep the procedural objection distinct from the factual and legal explanation of the income issue.
What should be downloaded first?
The notice/order PDF, communication history and any existing response or acknowledgement.
Why keep an indexed chronology?
It prevents confusion where several notices, responses and orders have similar descriptions but different legal consequences.
Official Sources
- Income Tax Department: e-Proceedings service - OFFICIAL_PORTAL
https://www.incometax.gov.in/iec/foportal/
Portal for notices, responses and electronic proceeding records. - Income Tax Department: e-Filing portal - pending actions and proceedings - OFFICIAL_PORTAL
https://www.incometax.gov.in/
Current electronic communication and response environment. - India Code: Income-tax legislation repository - LEGISLATION
https://www.indiacode.nic.in/
Verify the applicable reassessment provision for the relevant tax year and proceeding.