A TRACES Justification Report is the working paper a deductor should open when a TDS or TCS statement has been processed with defaults. It explains the errors or demands identified by CPC-TDS for a particular TAN, financial year, quarter and form type. The official TRACES Justification Report FAQ says the report provides detailed default calculations that may need to be resolved through a correction statement and, where applicable, payment of interest, fee or other dues.
The practical mistake is to start changing the TDS return before understanding the report. A default may arise from an unmatched or overbooked challan, incorrect PAN, late deduction, late payment, short deduction or another reporting mismatch. Each needs a different response. The safest workflow is: identify the default, reconcile it to source records, choose the correction route, submit the correction or payment, and verify that the statement has been processed again.
What the Justification Report actually tells you
TRACES states that a Justification Report is generated where defaults or errors have been identified. If a statement is processed without a default, the report is not available. It is therefore an exception report, not a routine return copy.
The TRACES Deductor Home lists the Justification Report and Conso File as separate services. In practice, the Justification Report tells you what went wrong, while the Conso File gives the latest consolidated statement data that may be needed for an offline correction.
A practical five-step method to resolve a TDS default
1. Download the latest Justification Report
TRACES instructs deductors to log in, open the Defaults area, request the report for the relevant statement and complete the required KYC validation. Once the request becomes available, it can be downloaded from Requested Downloads. TRACES also provides a utility to convert the text report into Excel format for easier review.
Use the latest report. If another correction has already been processed, an older copy may no longer reflect the current statement position.
2. Reconcile the default before changing the return
Do not assume the default amount is automatically correct or wrong. Reconcile it with the challan, bank payment evidence, deductee ledger, PAN, date of deduction, date of deposit, amount paid or credited, tax rate and accepted statement data.
For example, if TRACES shows an unmatched challan, compare the challan identification details and amount with the books and filed statement. If tax was correctly deposited but tagged incorrectly, the remedy may be a challan correction or retagging exercise. If tax was never deposited, changing statement data will not solve the payment default.
3. Match the error to the correct correction type
The official TRACES Online Correction FAQ lists functions including challan correction, adding a challan, PAN correction, personal-information correction and adding or modifying deductee details. It also covers specific options for overbooked or unmatched challans and certain salary-detail changes.
A correction should target the cause of the default. A wrong PAN should not be disguised as a challan problem, and a short deduction caused by an incorrect tax rate should not be treated as a mere master-data correction.
4. Decide whether online or offline correction is appropriate
TRACES provides online correction for several common errors, while its official Deductor e-Tutorial page also provides a separate offline-correction tutorial and specific tutorials for PAN, challan and deductee-row corrections. Where an offline correction is used, the latest Conso File matters because it reflects the consolidated statement after accepted corrections.
Confirm that the latest correction for the relevant statement has finished processing before starting another one. TRACES specifically says that online correction for older periods requires the latest correction for that statement to have been processed through TDS-CPC.
5. Track processing and recheck the default
Submission is not the end of the cycle. TRACES provides a Track Correction Request option in the Defaults menu. After processing, recheck the statement status and fresh default position. The objective is to confirm that the default has actually been resolved, not merely that a request was submitted.
Worked example: unmatched challan versus wrong PAN
Assume a company files a quarterly resident-payment TDS statement. After processing, TRACES shows two issues: one challan is unmatched and one deductee has an invalid PAN.
For the challan issue, compare the challan identification details, amount and payment evidence with the filed return. If tax was correctly deposited but the statement linked wrong challan particulars, use the applicable challan-correction route rather than paying the tax again.
For the PAN issue, verify the deductee's PAN from reliable records and use PAN correction. Guessing a PAN merely to clear a default can move tax credit to the wrong person and create a new compliance problem. The two errors belong in the same quarter but require different corrections.
Important transition point for old and new TDS formats
The Income Tax Department's current TDS Compliance FAQ states that return preparation utilities and TRACES support the old formats for periods up to March 2026 and the new formats for periods from April 2026 onward. It also states that corrections for periods governed by the Income-tax Act, 1961 continue to use the old Act's form numbers and formats even when filed after 1 April 2026.
So the correction route should be selected by the reporting period and governing law, not merely by the date on which the accountant is making the correction. Teams handling legacy periods and Tax Year 2026-27 together should keep their utility versions and checklists clearly separated.
Common mistakes that create repeated defaults
- Starting a correction from the default summary without reviewing the latest Justification Report.
- Paying tax again before checking whether the original challan was already deposited but only unmatched or wrongly tagged.
- Using an old Conso File after another correction has been processed.
- Correcting a PAN without documentary support.
- Changing multiple fields without preserving a maker-checker record of what changed and why.
- Assuming submission has resolved the issue without checking the processed statement.
- Mixing old-law and new-law statement formats during the post-April-2026 transition.
Practical file checklist
- Save the statement token or acknowledgement and latest processed status.
- Download the latest Justification Report for the exact TAN, year, quarter and form type.
- Map each default to supporting challans, ledgers, PAN records and deduction workings.
- Record the proposed correction type and reviewer approval before submission.
- Use the latest Conso File where an offline correction requires it.
- Preserve evidence for any interest, fee or shortfall payment.
- Track the correction request until processed and recheck the final default position.
Practical takeaway
Treat the TRACES Justification Report as a diagnostic document, not as an instruction to blindly edit a TDS return. Understand the default, reconcile the transaction, choose the correction function that matches the error, and verify the result after processing. That sequence reduces repeated corrections, duplicate payments and deductee-credit problems while leaving a cleaner tax file.
