An accountant needs to correct a processed TDS return and does not know where to start or what the conso file is.
The conso file is the department's copy of the processed return. Corrections are prepared by importing it into the return preparation utility, changing only the faulty rows, validating and uploading.
TRACES deductor login, token number of the original return, challan and deductee details for the KYC check, and the return preparation and file validation utilities.
A correction statement built on the department's data, with the faulty rows fixed and the rest unchanged.
A TDS conso file (short for consolidated file) is the download from TRACES of your processed TDS return, with the challan and deductee details exactly as the department holds them. You need it as the starting point for any correction statement. A correction built on it lines up with the department’s records.
TRACES is the TDS portal run by the Centralised Processing Cell. A correction statement is a revised return that fixes errors in one already filed.
How do I request it, and how long is it available?
- Log in to TRACES as the deductor.
- Request the consolidated file for the TAN, tax year, quarter and form (for example 26Q, or Form 140 from tax year 2026-27).
- Pass the check: TRACES asks for the token number of the original return and some details from it, such as a challan and deductee rows.
- Wait while the file is generated. It typically appears in your downloads area within a few hours to a day.
- Download it. The file is usually a compressed, password-protected file; the password format is shown on TRACES.
Download it within the period shown on screen. If it expires, request it again.
Conso file, justification report or Form 26AS?
| Document | What it shows | When to use it |
|---|---|---|
| Conso file | Your whole processed return: challans and every deductee row | Preparing a correction statement |
| Justification report | Why each default arose: short payment, short deduction, interest, late fee | Understanding a demand |
| Form 26AS (Form 168 from tax year 2026-27) | TDS credit for one PAN, from all deductors | A payee checking their credit |
A typical correction uses two of them: the justification report to find what is wrong, and the conso file to fix it.
Why can I not file a correction without it?
Your own copy of the return may not match what the department holds. A challan may have been corrected, or an earlier correction may have changed rows. If you edit your old file and upload it, the correction may be rejected or create new defaults.
The conso file also carries row identifiers the department uses to match changes. The return preparation utility uses these to know which rows you changed.
Corrections matter for money. A wrong PAN can mean a default at the 20 percent higher rate under Section 206AA. Interest at 1.5 percent per month under Section 201(1A) keeps running on any genuine short payment.
A worked example: one wrong PAN in a ₹2,400 row
Your Q2 return reported ₹2,400 of TDS on a ₹24,000 payment (10 percent) to a consultant, but one character of the PAN was wrong. The consultant cannot see the credit.
- Request the conso file for Q2 on TRACES, using the original token number.
- Import it into the return preparation utility.
- Open only that deductee row and correct the PAN. Leave the ₹2,400 and the other rows unchanged.
- Run the file validation utility (FVU) and upload the correction.
- After processing, the consultant sees ₹2,400 of credit against the right PAN.
Check: ₹24,000 times 10 percent equals ₹2,400. Had the PAN been treated as invalid, 20 percent would apply, so ₹4,800, and a short deduction of ₹2,400 could be raised against you.
What to read next
- The TDS correction return process: the full correction, step by step.
- TRACES portal reconciliation
- TDS reconciliation software: TransactIG reconciles TDS across books, challans and credit statements, so PAN and amount errors reach an exception queue before you file.