A large ITR refund is not automatically wrong, but it should be explainable. Recalculate the return from Form 16, AIS/TIS, 26AS, capital-gain statements and actual deduction evidence; confirm the tax regime and all TDS/self-assessment tax credits. If the refund depends on a deduction, loss or tax credit you cannot substantiate, review the filed ITR before relying on the result.
What this means for you
A refund should be a result you can reproduce, not a promised number.
Who this applies to
Individuals receiving a materially higher refund than expected after outsourced filing.
Why this problem happens
Wrong regime, omitted income, unsupported deductions, duplicated TDS, capital-gain errors or challan mistakes can distort the refund.
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.
| Check | Source | Question |
|---|---|---|
| Salary | Form 16 | Does gross salary match? |
| Regime | ITR/computation | Was intended regime used? |
| AIS | AIS/TIS | Any omitted income? |
| TDS | 26AS | Any duplicate/missing credit? |
| Capital gains | Broker/MF statements | Correct gain/loss? |
| Deductions | Actual proof | Can every claim be supported? |
What to do now
Recalculate from source documents and compare the independent computation to the filed return schedule-by-schedule.
Practical hypothetical example
A taxpayer expected ₹20,000 but the filed return shows ₹2.4 lakh refund. Review finds TDS entered twice and a capital-loss figure copied incorrectly. The high refund was a data problem, not proof of fraud.
What happens if this is ignored
A wrong refund can later produce demand, interest and other consequences depending on the facts.
What TargoLegal checks before filing or responding
TargoLegal produces a difference list covering income, deductions, tax credits and refund impact before any revised/updated filing.
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
Unsure about a refund computation? Ask for a second-file review before treating the refund as settled.
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.
