In this guide
Deductors filing Q1 TDS statements for Tax Year 2026-27 are encountering an unusual problem: a Justification Report may show a short-deduction demand of only a few paise, even where the practical TDS calculation appears substantially correct. One reported case showed a short deduction of just ₹0.57.
There are also cases where interest was already deposited through a challan but appears as unconsumed after processing.
Before paying such a demand again, the deductor should identify whether the problem is an actual short deduction, a challan-mapping issue, incorrect deductee data or a processing/correction issue.
Why Are Paise-Level TDS Demands Appearing?
TDS is calculated by applying the prescribed percentage to the amount paid or credited.
For example:
Payment: ₹17,171
TDS rate: 0.1%
Exact TDS: ₹17.171
If a filing utility or taxpayer reports only ₹17 instead of preserving the required precision, processing can potentially identify a difference.
The transcript attributes the 2026 problem to CPC processing now considering paise at the individual deductee-row level instead of ignoring them during processing.
However, an important distinction is necessary: there is currently no public CBDT/TRACES notification confirming that every paise-level demand is a software error.
Therefore, do not automatically ignore a ₹0.17 or ₹0.57 demand simply because it is small.
Does the ₹10 Rounding Rule Eliminate the Demand?
Not necessarily.
Under the earlier Income-tax Act, Section 288B provided that the final amount payable or refund due under the Act is rounded to the nearest multiple of ₹10.
But this does not necessarily mean that every individual deductee transaction should first be rounded to the nearest ₹10 while calculating whether sufficient TDS was deducted.
That distinction is important.
| Stage | Practical approach |
|---|---|
| Calculate TDS on deductee payment | Apply exact prescribed rate |
| Prepare deductee row | Preserve utility-required precision |
| Deposit TDS | Match challan with statement |
| CPC processing | Verify computation in Justification Report |
| Final demand/payment | Apply statutory/system rounding as applicable |
For transactions from 1 April 2026, deductors must also use the relevant TDS table item under Section 393 of the Income Tax Act, 2025, rather than blindly continuing old section codes such as 194C or 194J. The Income Tax Department warns that old codes can result in system-level validation errors.
Read more about TDS and TCS filing.
First Step: Download the Justification Report
Do not start by paying the amount shown on the dashboard.
TRACES says the Justification Report contains details of defaults and errors identified while processing a TDS/TCS statement and provides the calculation that needs to be examined before correction.
Check:
- Deductee PAN;
- Amount paid or credited;
- Applicable TDS rate;
- TDS deductible;
- TDS actually reported;
- Challan against which the row was mapped;
- Short-deduction amount;
- Late-deduction or late-payment interest; and
- Available/unconsumed challan balance.
This tells you whether the demand is mathematical or merely a mapping/processing issue.
What if the Short Deduction Is Genuine?
TRACES’ official procedure says that where a genuine short-deduction default exists, the deductor should deposit the shortfall and applicable interest through Challan ITNS 281 using Minor Head 400, then file a correction and map the additional challan appropriately.
TRACES also permits a single challan to be bifurcated across multiple entries, provided the credit claimed does not exceed the available challan amount.
Therefore, a genuine shortfall should be corrected rather than simply left outstanding because the amount is only a few paise.
What if Interest Was Already Paid but CPC Shows It as Unconsumed?
Do not immediately pay the same interest twice.
First compare:
- Original challan;
- Filed TDS statement;
- Conso file;
- Justification Report; and
- Challan-consumption status.
TRACES provides an online correction mechanism for adding a challan to a statement and for closing late-payment, late-deduction, interest and levy defaults.
Where an apparently valid payment has not been consumed because of incorrect mapping, correcting or tagging the challan may solve the issue.
Where the demand itself appears technically incorrect, TRACES also provides a Request for Resolution mechanism for specified processing disputes instead of forcing the deductor to blindly accept every demand.
See TaxClear’s income-tax notice guidance.
Can You File Q1 2026-27 TDS Correction Right Now?
This is currently the biggest practical problem.
As of 16 August 2026, the Income Tax e-Filing portal itself displays the message:
“Filing of TDS/TCS Correction Statements pertaining to Tax Year 2026-27 will be enabled shortly.”
Therefore, if your Q1 Tax Year 2026-27 correction upload option is unavailable, it may not be a problem with your login or utility.
The correction functionality is still being enabled for the new tax-year framework.
Prepare the correction data and supporting working now, but do not invent a workaround merely to close the demand before the prescribed correction channel becomes operational.
Practical Correction Checklist
Before taking action:
- Download the latest Justification Report.
- Download the Conso file where available.
- Recalculate TDS deductee-wise without casually dropping paise.
- Verify the correct Section 393 table item.
- Check whether the challan is actually unconsumed.
- Do not pay interest twice.
- Pay genuine short deduction through the correct demand challan.
- Prepare the correction statement.
- File it when Tax Year 2026-27 correction functionality is enabled.
- Recheck the statement after CPC processing.
TRACES confirms that online correction can cover challan correction, addition of challans, payment-related defaults, PAN corrections and deductee-detail modifications.
Explore TaxClear accounting and compliance services.
Frequently Asked Questions
Can a TDS demand really be raised for 57 paise?
A processing system can identify a deductee-level mathematical shortfall even when the amount is extremely small. The underlying Justification Report should be checked before deciding whether the demand is valid.
Should I round every deductee’s TDS to the nearest ₹10?
No. Do not apply final statutory rounding mechanically to each individual deductee calculation. Compute the applicable TDS accurately and follow the current statement utility requirements.
I already paid interest. Should I pay the new demand again?
Not until you confirm that the original challan was properly consumed and mapped. An unconsumed challan may require correction rather than duplicate payment.
Is Q1 Tax Year 2026-27 correction filing enabled?
As of 16 August 2026, the Income Tax portal says TDS/TCS correction statements for Tax Year 2026-27 will be enabled shortly.
Where should I start when a short-deduction notice arrives?
Start with the Justification Report, not the demand amount. It shows how CPC calculated the default and helps determine whether payment, correction, challan mapping or resolution is actually required.
