If your filed ITR contains deductions or exemptions you do not recognise, download the filed return and computation before doing anything else. Compare each claim with Form 16, AIS/TIS, Form 26AS and your actual supporting documents. Do not assume the return is correct because it was processed or produced a refund. The correction route depends on the year, processing status and whether revised, updated or rectification provisions are legally available.
What this means for you
Every material deduction should have a legal basis and evidence matching your facts.
Who this applies to
Individuals and business owners who outsourced ITR filing and cannot explain deductions, losses or refund computation.
Why this problem happens
Wrong regime, copied prior-year data, aggressive claims, data-entry error or misunderstanding can create unsupported claims.
What should be checked immediately
Use an indexed checklist rather than scattered messages. The exact documents vary by issue, but the records below should be under business control before any filing, correction or response.
| Source | Compare to return | Red flag |
|---|---|---|
| Form 16 | Salary/TDS/regime | Salary differs without explanation |
| AIS/TIS | Interest/securities/property | Income omitted |
| 26AS | TDS/TCS | Credit claimed without matching data |
| Proof | Deduction evidence | No support |
| Computation | Tax/refund | Unexpected large refund |
What to do now
Build a line-by-line review: schedule → claim → provision → amount → proof → correct/incorrect/uncertain. Then choose the legally available correction route.
Practical hypothetical example
A taxpayer sees a ₹2 lakh deduction but has no supporting eligible expense/investment. The next step is to identify the schedule and provision before filing anything else.
What happens if this is ignored
Unsupported claims can create demand, scrutiny or updated-return consequences. A processed refund is not permanent validation.
What TargoLegal checks before filing or responding
TargoLegal recreates the tax computation independently and labels each unsupported or unclear claim before recommending correction.
What the customer should approve and receive
Before filing or response
Receive the issue summary, pending-document list, proposed figures/treatment, deadline and payment impact. Material assumptions should be visible.
After submission
Receive the filed return/form or response, government acknowledgement, payment proof and a short open-items list.
Do not make the handover or correction harder
Statutory deadlines continue.
Keep portal access under business control.
Rebuild from source records and prior filings.
Every completed filing should leave an official trail.
What to send for a first review
Not sure what was claimed? Send the ITR acknowledgement and computation for a second-file review.
Related questions
How do I know the filing or response is actually complete?
Look for the official acknowledgement/status on the relevant government portal and retain the filed copy. A payment receipt or provider message is not enough.
Should I share my portal password with a new provider?
Prefer official authorisation, secure reset and business-controlled access. Do not send passwords or OTPs through uncontrolled chats.
Can I blame the previous adviser in the government response?
A statutory response should focus on facts, law and evidence. Private responsibility with a provider is a separate issue unless legally relevant.
What should I approve before filing?
You should receive a concise summary of figures, differences, payment/correction proposed and unresolved risks before submission.
What should I keep afterwards?
Keep the filed form/return, acknowledgement, payment proof, reconciliation and any response/order in a business-controlled archive.
Official sources used
Legal and portal claims were anchored to the official references below. Forums and customer complaints were used only to understand real-world confusion, never as legal authority.
TargoLegal Research and Editorial Desk · Last legally reviewed: 18 August 2026. Recheck live forms, notifications, portal workflows and response dates immediately before acting.
