Issue in form 16 TDS credit
This query is : Resolved
16 September 2025
We filed the revised TDS return (Form 24Q of Q4 ) for F.Y. 2024-25, wherein we added the challan to the statement in traces and reported the deduction details against it using WinMan TDS software. While the tax payable and gift card perquisite value are reflecting correctly in Part B of Form 16, the TDS credit is not appearing in Part A, resulting in a higher tax liability for employees. On checking in TRACES, we noticed that the challan is appearing under our statement, but the “challan claimed amount” is showing as zero. We downloaded a new conso file and checked that there are no deduction details available against that particular challan , even though we entered deduction details. Could experts advise why this situation arises and what corrective steps should be taken?
16 September 2025
The core issue is that the challan you have added in your revised Form 24Q (Q4) statement is visible in TRACES, but the challan claimed amount is zero, and deduction details are not mapped to that challan, leading to no TDS credit appearing in Part A of Form 16 for affected employees, even though those details were entered in your TDS software. This is a common reconciliation problem during TDS return revisions.
Issue Analysis
A challan will reflect in your statement on TRACES only if it’s successfully added to the TDS return.
The “challan claimed amount” becomes non-zero only when deduction records are tagged/mapped to it in the TDS statement.
If, after revision, no deduction records (employee/transaction-wise data) are mapped to the new challan, TRACES treats it as unused, hence the zero claimed amount.
Part A of Form 16 draws TDS credit based on mapped deduction records. If nothing is mapped, TDS credit becomes zero, even though Part B (salary/other perquisites) may reflect correct values (as these are from the employer inputs, not the TDS credit details themselves).
Issue Analysis
A challan will reflect in your statement on TRACES only if it’s successfully added to the TDS return.
The “challan claimed amount” becomes non-zero only when deduction records are tagged/mapped to it in the TDS statement.
If, after revision, no deduction records (employee/transaction-wise data) are mapped to the new challan, TRACES treats it as unused, hence the zero claimed amount.
Part A of Form 16 draws TDS credit based on mapped deduction records. If nothing is mapped, TDS credit becomes zero, even though Part B (salary/other perquisites) may reflect correct values (as these are from the employer inputs, not the TDS credit details themselves).
16 September 2025
Common Reasons for This Error
Deduction details not linked: During the revised return filing, deduction entries (Annexure I/employee records) may not have been properly linked to the new challan in the return file prior to upload.
Mistakes in TDS software: Sometimes, TDS software (like WinMan) may not map the deduction rows to the new challan, especially in revised files, or export errors can cause mapping failures.
Incorrect conso file usage: When preparing the revised return, if deduction details are not correctly extracted from the latest conso file or the mapping is not updated, such issues result.
Deduction details not linked: During the revised return filing, deduction entries (Annexure I/employee records) may not have been properly linked to the new challan in the return file prior to upload.
Mistakes in TDS software: Sometimes, TDS software (like WinMan) may not map the deduction rows to the new challan, especially in revised files, or export errors can cause mapping failures.
Incorrect conso file usage: When preparing the revised return, if deduction details are not correctly extracted from the latest conso file or the mapping is not updated, such issues result.
16 September 2025
Corrective Steps
Download the latest conso file from TRACES before making any revisions.
Re-import the conso file into WinMan TDS software. This ensures all prior deduction–challan mappings are current.
Add the new challan, ensuring you enter correct CIN details.
Map deduction details for affected employees specifically to the correct (new) challan within the software. This step is crucial—ensure every relevant deduction gets linked to the correct challan.
Re-generate the revised TDS return file and validate with the File Validation Utility (FVU).
Re-upload the corrected return to the TIN-FC/NSDL portal.
Wait for TRACES processing, then verify both the challan claimed amount and relevant deduction details are visible for the challan.
Only after successful mapping will the TDS credit appear in Part A of Form 16 for relevant employees.
Download the latest conso file from TRACES before making any revisions.
Re-import the conso file into WinMan TDS software. This ensures all prior deduction–challan mappings are current.
Add the new challan, ensuring you enter correct CIN details.
Map deduction details for affected employees specifically to the correct (new) challan within the software. This step is crucial—ensure every relevant deduction gets linked to the correct challan.
Re-generate the revised TDS return file and validate with the File Validation Utility (FVU).
Re-upload the corrected return to the TIN-FC/NSDL portal.
Wait for TRACES processing, then verify both the challan claimed amount and relevant deduction details are visible for the challan.
Only after successful mapping will the TDS credit appear in Part A of Form 16 for relevant employees.
16 September 2025
Cross-check “Deductee details” in the validated FVU file—each row should show the correct challan serial.
If using software, verify in the “Deductee entry” or “Deductee mapping” screens that new deductions go against the correct challan. If confusion persists, try contacting the software vendor’s helpdesk for step-by-step mapping checks.
Filing a revised TDS return is mandatory when deductions were omitted/misreported, but mapping omissions can only be rectified by revising the return again with proper mapping.
If using software, verify in the “Deductee entry” or “Deductee mapping” screens that new deductions go against the correct challan. If confusion persists, try contacting the software vendor’s helpdesk for step-by-step mapping checks.
Filing a revised TDS return is mandatory when deductions were omitted/misreported, but mapping omissions can only be rectified by revising the return again with proper mapping.
19 September 2025
Good Luck...
You need to be the querist or approved CAclub expert to take part in this query .
Click here to login now
Click here to login now
Similar Resolved Queries
Unanswered Queries
- Applicability of TDS on CFS, CHA fees, and shipping line charges
- Notice from IT DEPTT IF FD AMOUNT EXCEEDS 10 LACS
- Limited Liability Partnership Firm
- Unable to generate and save json file for updated return
- GST payable under RCM
- Applicablity on tds
- Section 194I not showing in TDS RPU for Compnay Assessee for TDS on rent
- LTCG offset against property buy
- PRODUCT AND SERVICE CATEGORY CODE
- Tax audit & Switching from Presumptive taxation
- Regarding TDS not deducted on rent
- REGARDING CLAIM OF LAST YEAR TDS
- Regarding income tax return of company and LLP
- Import purchase entry
- Under which tax head RCM on Commission on Sale is to be paid.
- Rule 54(1A) for Distributing ITC
- EXCESS CREDIT REALTED GST REVERSAL
- Export invoice not reported
- CA Articleship Extension Matter
- GST OFFICER WRONG NOTICE
Trending Online Classes
-
LIVE Course on GSTR-9 & GSTR-9C (Technical | Practical | Concept - Based)
Sachin Jain03 November 2025
CAclubindia
