Fix filed ITR payments: Guide

Fix filed ITR payments: Guide

When a payment error surfaces in a filed ITR — a challan tagged to the wrong assessment year, a TDS credit that failed to appear, or a refund bouncing back from a closed account — you have four distinct remedies under Indian income-tax law: challan correction, a revised return under Section 139(5), a rectification request under Section 154, and a refund re-issue request. The right fix depends on whether your return has already been processed and exactly what went wrong. This guide maps each scenario to the correct tool, with step-by-step procedures and worked Rs. numbers.

The Four Remedies at a Glance

Before diving into each fix, understand the decision framework. Choosing the wrong remedy wastes weeks.

The sections below unpack each remedy, step by step.

Challan Correction: Fixing the Wrong Assessment Year

The single most common pre-filing payment error is selecting AY 2025-26 when you meant AY 2026-27 on Challan ITNS-280. If you spot this before filing your ITR, you have two windows.

Bank-level correction (within 7 days of payment)

Most scheduled banks permit minor challan corrections — including the assessment year — within seven days of payment through net-banking or the branch counter. The sequence:

1. Log in to the bank's internet banking portal and locate the recent tax payment.
2. Navigate to the challan correction or tax payment section and raise a correction request specifying the wrong field (Assessment Year) and the correct value.
3. The bank forwards the instruction to TIN-NSDL/OLTAS. Allow 3–5 working days for OLTAS to reflect the change.
4. Verify the update on the OLTAS portal (tin.tin.nsdl.com) using your BSR code, challan serial number, and date of deposit.
5. Download the corrected challan PDF and save it with your tax records.

Seven days is a tight window. If you miss it, the AO route is your next option.

AO-level correction (after the bank window closes)

Submit a written application to your jurisdictional Assessing Officer (AO) requesting an OLTAS challan correction. Attach:

• A copy of the challan (with payment confirmation or bank statement entry)
• A brief explanation of the error
• The correct assessment year and tax-head details
• Your PAN card copy

There is no statutory time limit for AO correction, but most straightforward corrections are processed within 30–45 days. Once OLTAS is updated, the corrected challan reflects automatically in your AIS and Form 26AS.

> Critical follow-up: After the challan is corrected in OLTAS, it does not auto-link to a filed ITR. If you have already filed, you will need to either file a revised return or raise a Section 154 rectification to claim the credit for the correct AY.

Revised Return Under Section 139(5): Including a Missed Challan

If you filed your ITR and then discovered a valid challan was left out of the Advance Tax or Self-Assessment Tax schedule, file a revised return under Section 139(5) of the Income-tax Act 1961. A revised return entirely supersedes the original — it is not a patch; it is a complete refiling.

Eligibility and deadline

• You can file a revised return only if the original was filed under Section 139(1) (on-time) or Section 139(4) (belated).
• Deadline: before the end of the relevant assessment year or before completion of assessment, whichever is earlier.
• For AY 2026-27, the assessment year closes on 31 March 2027. As of May 2026, the revised return window for AY 2026-27 is still open — provided the return has not already been taken up for scrutiny assessment under Section 143(3).
• For AY 2027-28 (income earned in FY 2026-27), the window remains open until 31 March 2028.

Step-by-step: filing a revised return on the e-filing portal

1. Log in to incometax.gov.in with your PAN credentials.
2. Go to e-File → Income Tax Returns → File Income Tax Return.
3. Select the relevant AY, the correct ITR form, and choose Revised Return as the filing type. Enter the original ITR acknowledgement number and the original filing date when prompted.
4. The portal pre-fills data from the original return. Navigate to the Taxes Paid schedule (Schedule IT for advance tax, Schedule TDS for TDS credits).
5. Add the missed challan: BSR code (7 digits), challan serial number (5 digits), date of deposit, and amount. The system cross-checks against OLTAS in real time — ensure the challan is already updated in OLTAS before entering it.
6. Recalculate tax payable. If the missed challan eliminates the demand entirely, the return should show NIL or a refund.
7. E-verify within 30 days of submission — via Aadhaar OTP, net-banking EVC, or DSC. An unverified return is treated as if it was never filed.

> Trap to avoid: Entering a BSR code with even one transposed digit. The portal accepts the return without complaint, but the OLTAS match fails during processing, recreating the identical demand. Always copy challan details directly from the OLTAS portal or the challan PDF. Never type from memory.

Rectification Under Section 154: After Your Return Is Processed

If the return has already been processed and you hold an intimation under Section 143(1) showing an incorrect tax-paid figure — a challan omitted from credit, a TDS entry missing — you need a rectification request under Section 154.

Section 154 is not a fresh return. It corrects a "mistake apparent from the record" — a legal standard that covers arithmetic errors, tax-credit mismatches visible in OLTAS or AIS, and data discrepancies in the intimation. It does not cover substantive changes to income or deductions, which require a revised return (if still in time) or formal assessment proceedings.

Choosing the right rectification sub-type

The e-filing portal's rectification screen offers two primary paths:

• Tax Credit Mismatch Correction: Use this when the Section 143(1) intimation denied credit for a TDS or challan that clearly appears in Form 26AS or AIS. You input the correct figures and can upload supporting documents.
• Return Data Correction: Use this when the mismatch is in data you entered in the original return — for example, an incorrect challan amount or a wrong TAN for a deductor.

Step-by-step: raising a Section 154 rectification

1. Log in to incometax.gov.in.
2. Go to Services → Rectification → New Request.
3. Select the relevant AY and the order to be rectified (the 143(1) intimation; the order number appears in your portal inbox).
4. Select the rectification type.
5. Enter corrected TDS/challan details. For TDS: TAN of the deductor, the relevant quarter, and the amount. For challans: BSR code, challan serial number, date, and amount.
6. Upload a supporting document if prompted — challan copy, Form 16/16A extract, or AIS/26AS screenshot.
7. Submit and save the acknowledgement number.

The department must pass a rectification order within six months of the end of the month in which it receives the application. Track progress under Services → Rectification → Rectification Status.

> Time limit: Section 154 applications must be filed within four years from the end of the financial year in which the original order was passed. A Section 143(1) intimation issued in FY 2025-26 can be rectified up to 31 March 2030 — but do not rely on this; memories fade and the earlier you act, the cleaner the resolution.

Demand Notice Under Section 156: Respond Within 30 Days

An outstanding tax demand from a Section 143(1) intimation becomes a formal demand notice under Section 156 when it is served on you. From that date, you have 30 days to pay, dispute, or partly agree. Miss the window and Section 220(2) kicks in: simple interest at 1% per month (or part of a month) on the unpaid amount — with no upper cap.

Three response options

Option 1 — Agree and pay: If the demand is correct, pay the shortfall via Challan ITNS-280 (e-Pay Tax on the portal), selecting the correct AY and the Self-Assessment Tax head. Then go to Pending Actions → Response to Outstanding Demand, select the demand, click Agree, and enter the payment challan details. The demand is extinguished once payment is verified.

Option 2 — Partially agree: If part of the demand is valid and part is disputed, pay the undisputed portion immediately and raise a Section 154 rectification for the disputed balance. Record both actions in your response on the portal.

Option 3 — Disagree and contest: If the entire demand results from a computation error or an OLTAS credit mismatch, select Disagree, state the reason clearly (e.g., "Challan of Rs. X paid on [date] not credited; rectification filed"), and simultaneously submit a Section 154 rectification request. The AO reviews both and either rectifies or passes a fresh order.

> Never ignore a demand notice. Under Section 245, the department may adjust a confirmed demand against a future refund with only an intimation — you lose your refund without prior notice. And every month of inaction adds 1% interest to the outstanding figure.

Refund Re-issue: Fixing a Failed Bank Credit

If the department processed your return and granted a refund but the credit never arrived, log in to incometax.gov.in and check Refund/Demand Status. A Refund Failure status with a reason code (wrong account number, inactive account, IFSC mismatch) means the refund was returned to the department by SBI, the designated refund banker for income tax.

Step-by-step: pre-validate and request re-issue

1. Go to My Profile → Bank Accounts. If the problem account is listed, you can update the IFSC or remove it entirely and add the correct account.
2. Enter the new account's details (account number + IFSC) and submit for pre-validation. The system links the account to your PAN via the bank's API. Pre-validation typically completes in 1–2 working days; you will receive a status update in the portal.
3. Once the account shows Validated, go to Services → Refund Reissue.
4. Select the AY, confirm the refund sequence number (visible on the Refund/Demand Status screen), and select the validated bank account.
5. Submit. The portal issues an acknowledgement number. Track the credit under Refund/Demand Status — SBI typically processes re-issued refunds within 20–45 working days.

> Pre-validation failure: The most frequent cause is a name mismatch between the bank account holder name and the PAN database. Even "Suresh K. Mehta" versus "Suresh Kumar Mehta" will fail. Visit your bank branch to align the account name with your PAN record before attempting pre-validation again.

> One more step often missed: Pre-validation and nomination are separate actions. Pre-validation proves the account belongs to you; nomination tells the department to credit that specific account. Without nominating the validated account for refunds, your re-issue request may not route correctly.

Worked Example: A Wrong-AY Challan Produces a Rs. 49,440 Problem

Background. Priya is a senior manager based in Pune. For FY 2025-26 (AY 2026-27), her employer deducted TDS of Rs. 1,80,000. After computing her total liability at Rs. 2,28,000, she paid the Rs. 48,000 balance as self-assessment tax on 28 July 2025 via ITNS-280 — but accidentally selected AY 2025-26 instead of AY 2026-27 in the challan details.

What happened next. Priya filed her ITR for AY 2026-27 on 31 July 2025, entering the Rs. 48,000 challan in the Self-Assessment Tax schedule. The portal accepted the filing. During CPC processing, however, OLTAS showed the challan under AY 2025-26 — not AY 2026-27. The credit was denied.

In November 2025, a Section 143(1) intimation arrived showing a demand of Rs. 48,000. Priya did not act within 30 days. By the time she contacted a CA in mid-February 2026, three full months had elapsed (December, January, February).

Interest calculation under Section 220(2): 1% per month × 3 months × Rs. 48,000 = Rs. 1,440

Total payable by February 2026: Rs. 48,000 + Rs. 1,440 = Rs. 49,440

How the fix was structured. Priya's CA submitted an AO application for OLTAS challan correction (AY changed from 2025-26 to 2026-27). The AO processed it in 32 days. Once Form 26AS for AY 2026-27 reflected the corrected challan, Priya filed a revised return under Section 139(5) — the revised-return window for AY 2026-27 was still open (closes 31 March 2027). She simultaneously responded to the outstanding demand on the portal, selecting Disagree and citing the AO correction in progress.

The revised return was processed and the demand extinguished. The Rs. 1,440 interest was confirmed (the delay was genuine), but no further interest accrued post-response.

The lesson. Responding to the Section 143(1) intimation within the 30-day window — even just flagging the dispute and initiating the AO correction — would have saved Rs. 1,440 and four months of follow-up.

Common Mistakes That Turn a Simple Fix Into a Long Problem

Raising a Section 154 rectification when a revised return is needed

Section 154 only corrects mistakes apparent from the record — things the CPC can verify in OLTAS or AIS without new information from you. Adding a challan that was never in OLTAS at the time of filing is not a mistake apparent from the record; it is new data. Use a revised return for that. Filing the wrong type of request leads to rejection and wastes six weeks waiting for the order.

Ignoring the 30-day demand notice window

At 1% per month under Section 220(2), a Rs. 1,00,000 demand costs Rs. 1,000 every month you delay — Rs. 12,000 in a year, Rs. 24,000 in two. File a response (even a Disagree response with a reason) the day the demand appears on the portal. It stops the clock.

Entering challan details from memory

BSR codes are 7 digits; challan serial numbers are 5 digits. A single transposition is invisible in the revised return or rectification form but fatal during OLTAS verification. Always copy from the challan PDF or the OLTAS portal, never from memory or a handwritten note.

Assuming the AIS is always correct

AIS (Annual Information Statement) aggregates data from multiple sources — employers, banks, mutual fund houses, registrars. Errors upstream (a TDS return filed with your PAN typoed by a deductor, or an interest certificate filed with the wrong amount) propagate into your AIS. Reconcile AIS and Form 26AS against your own records before filing. If a deductor's entry is wrong, have them revise their TDS return first; only then will your 26AS and AIS reflect the correct credit, making the Section 154 rectification clean.

Not e-verifying a revised return within 30 days

An unverified ITR is legally non-existent. If the 30-day e-verification window lapses, you must apply for a condonation of delay in verification — an added procedural hurdle that delays the entire fix.

Nominating the pre-validated account for refunds

As noted above, pre-validation and nomination are two separate portal actions. Completing pre-validation but skipping nomination means the refund re-issue request has no destination to route to. Always check that the correct account is nominated under My Profile → Bank Accounts → Primary Account for Refund.

Key Takeaways

• Match the remedy to the situation. Challan correction handles wrong-AY errors before they reach the ITR; revised return under Section 139(5) includes omitted challans before the AY closes; Section 154 rectification fixes processed-return mismatches; refund re-issue resolves failed bank credits. Using the wrong tool leads to rejection and delay.
• The revised return window for AY 2026-27 remains open until 31 March 2027 — or until your case is taken up under Section 143(3), whichever is earlier. If a challan is missing from your AY 2026-27 return, act now; the window is closing.
• Respond to every Section 156 demand notice within 30 days, even if only to flag a dispute. Section 220(2) interest at 1% per month adds up fast, and Section 245 allows the department to adjust confirmed demands against future refunds without your consent.
• Pre-validation plus nomination — both are required for a successful refund re-issue. Pre-validate the new bank account, then explicitly nominate it for refund credit. Skipping nomination is the leading cause of re-issue failure.
• Section 154 has a four-year limit from the end of the financial year in which the original order was passed. Do not defer rectification requests on the assumption that the window is long — complex cases take time, and starting early allows for re-submission if the first request is rejected.
• Fix TDS errors at the source first. If a demand or mismatch arises from a deductor's wrong TDS filing, the only durable solution is to have the deductor correct their TDS return (Form 24Q/26Q). A Section 154 rectification filed before the deductor's correction is made will be denied — OLTAS still shows the wrong figure.
• Reconcile AIS, Form 26AS, and your own records before every filing. The majority of post-filing payment errors are detectable at the pre-filing stage in five minutes of careful comparison. Building this habit into your annual tax routine eliminates most of the scenarios this guide covers.