Conso File Password 2026: TRACES Password for TDS Files
Last reviewed: 27 August 2026.
Answer first: TRACES does not use one universal password. For common deductor downloads, Form 16, Form 16A, Form 27D and Transaction Based Reports use the deductor TAN in CAPITAL LETTERS; a Conso File uses TAN_Request Number; and a Justification Report uses JR_TAN_FormType_Quarter_FY. Always identify the exact TRACES file before entering a password.
Quick TRACES password reference
| TRACES file / communication | Password format | Example |
|---|---|---|
| Form 16 download | TAN in CAPITAL LETTERS | ABCD12345E |
| Form 16A download | TAN in CAPITAL LETTERS | ABCD12345E |
| Form 27D download | TAN in CAPITAL LETTERS | ABCD12345E |
| Transaction Based Report | TAN in CAPITAL LETTERS | ABCD12345E |
| Conso File | TAN_Request Number | ABCD12345E_67890 |
| Justification Report | JR_TAN_FormType_Quarter_FY | JR_AAAAA1235A_24Q_Q3_2010-11 |
Important: A PDF later emailed by an employer, bank or other deductor may use that issuer's own password convention. That is different from the password for the original TRACES download.
1. Form 16 and Form 16A password
For Form 16 and Form 16A files downloaded by the deductor from TRACES, the official TRACES guidance specifies the deductor's TAN in capital letters as the password.
| TAN | Password to try for original TRACES download |
|---|---|
| abcd12345e | ABCD12345E |
If an employee receives a separately password-protected PDF from an employer and TAN does not work, check the employer's email or payroll instructions. The employer may have applied another password after generating/distributing the certificate.
2. Conso File password
The Conso or Consolidated File is commonly used as the base file for TDS/TCS correction work. The TRACES password format is:
TAN_Request Number
Example: TAN ABCD12345E and request number 67890 produces ABCD12345E_67890.
Conso password checklist
- Use the complete TAN.
- Keep TAN letters in uppercase.
- Use the request number of that specific Conso request.
- Insert exactly one underscore between TAN and request number.
- Do not add spaces before or after the password.
3. Justification Report password
A Justification Report explains defaults identified during processing of a TDS/TCS statement. The standard TRACES password structure shown in its guidance is:
JR_TAN_FormType_Quarter_FY
| Component | Meaning |
|---|---|
| JR | Fixed prefix |
| TAN | Deductor/collector TAN |
| FormType | For example 24Q, 26Q, 27Q or 27EQ |
| Quarter | Q1, Q2, Q3 or Q4 |
| FY | Financial year in the required format |
Example: JR_AAAAA1235A_24Q_Q3_2010-11.
If the report does not open, do not randomly change the financial year. Re-check the statement form type, quarter and FY attached to the exact TRACES request.
4. Form 27D and Transaction Based Report
TRACES guidance uses the deductor/collector TAN in CAPITAL LETTERS for the relevant Form 27D and Transaction Based Report downloads.
Original TRACES download vs distributed PDF
| File you are opening | Who created/protected it? | What to do |
|---|---|---|
| TRACES ZIP/text/download package | TRACES | Use the official TRACES password format for that document type. |
| Form 16 PDF emailed by employer | Employer/payroll system may have applied its own PDF password | Check employer email/payroll instructions if TAN does not work. |
| Form 16A PDF sent by bank/company | Issuer may have created a separate protected PDF | Do not assume the original TRACES ZIP password applies. |
How to identify the correct password in 30 seconds
- Check the file name and download request.
- Ask: is this an original TRACES download or a PDF later received from another person/system?
- If it is Form 16/16A/27D/TBR from TRACES, try uppercase TAN.
- If it is Conso, use TAN_Request Number.
- If it is a Justification Report, build the JR password from TAN, form, quarter and FY.
- If it is an issuer-created PDF, use that issuer's instructions.
Troubleshooting matrix
| Problem | Likely cause | Check |
|---|---|---|
| Form 16/16A does not open | Lowercase TAN, spaces, or not the original TRACES package | Uppercase TAN and file source |
| Conso fails | Wrong request number or missing underscore | TAN_Request Number for that exact request |
| Justification Report fails | Wrong form/quarter/FY | Statement details used in the request |
| Password looks right but extraction fails | Corrupt/incomplete download | Download again from TRACES |
| Copied password still fails | Invisible leading/trailing spaces | Paste into plain-text editor first |
Finance-team control checklist
- Record TRACES request number against each download request.
- Store TAN in standard uppercase form in the TDS master.
- Save form type, quarter and FY with Justification Report requests.
- Do not email passwords in the same unsecured message as sensitive files where internal policy prohibits it.
- Keep original downloads separate from PDFs subsequently generated for employees/deductees.
- Use a controlled folder naming convention such as FY_Q_Form_RequestNo.
Related TDS and filing guides
After opening the TRACES file, these related Tax Queries guides cover the next compliance steps:
- TDS Return Filing FY 2026-27: forms, due dates, filing and late fees
- Form 144 (old Form 27Q): non-resident TDS return filing
- Form 128: lower or nil TDS certificate under section 395
- AIS vs Form 26AS vs TIS: tax-credit reconciliation before ITR filing
- 44AD/44AB Tax Audit Guide: old-vs-new law transition
Internal-link route: Use this page for TRACES password/download problems; use the TDS Return guide for quarterly statement compliance; Form 144 for non-resident withholding statements; Form 128 for lower/nil withholding certificates; and AIS/26AS/TIS for taxpayer-side credit reconciliation.
Common mistakes
- Using PAN instead of TAN for a TRACES deductor download.
- Typing TAN in lowercase.
- Using the latest Conso request number instead of the number belonging to the downloaded file.
- Omitting the underscore in the Conso password.
- Using 26Q in a Justification Report password when the request was for 24Q.
- Confusing an employer-distributed PDF password with the original TRACES download password.
Official references
Operational formats can be updated by TRACES. If the portal displays a document-specific instruction that differs from an older guide, follow the live official instruction.
Frequently Asked Questions
What should I know about 1. Form 16 and Form 16A password?
For Form 16 and Form 16A files downloaded by the deductor from TRACES, the official TRACES guidance specifies the deductor's TAN in capital letters as the password. TAN Password to try for original TRACES download abcd12345e ABCD12345E If an employee receives a separately password-protected PDF from an employer and TAN does not work, check the employer's email or payroll instructions. The employer may have applied an
What should I know about 2. Conso File password?
The Conso or Consolidated File is commonly used as the base file for TDS/TCS correction work. The TRACES password format is: TAN_Request Number Example: TAN ABCD12345E and request number 67890 produces ABCD12345E_67890 .
What should I know about Conso password checklist?
Use the complete TAN. Keep TAN letters in uppercase. Use the request number of that specific Conso request. Insert exactly one underscore between TAN and request number. Do not add spaces before or after the password.
What should I know about 3. Justification Report password?
A Justification Report explains defaults identified during processing of a TDS/TCS statement. The standard TRACES password structure shown in its guidance is: JR_TAN_FormType_Quarter_FY Component Meaning JR Fixed prefix TAN Deductor/collector TAN FormType For example 24Q, 26Q, 27Q or 27EQ Quarter Q1, Q2, Q3 or Q4 FY Financial year in the required format Example: JR_AAAAA1235A_24Q_Q3_2010-11 . If the report does not o
What should I know about 4. Form 27D and Transaction Based Report?
TRACES guidance uses the deductor/collector TAN in CAPITAL LETTERS for the relevant Form 27D and Transaction Based Report downloads.
What should I know about Original TRACES download vs distributed PDF?
File you are opening Who created/protected it? What to do TRACES ZIP/text/download package TRACES Use the official TRACES password format for that document type. Form 16 PDF emailed by employer Employer/payroll system may have applied its own PDF password Check employer email/payroll instructions if TAN does not work. Form 16A PDF sent by bank/company Issuer may have created a separate protected PDF Do not assume the
What should I know about How to identify the correct password in 30 seconds?
Check the file name and download request. Ask: is this an original TRACES download or a PDF later received from another person/system? If it is Form 16/16A/27D/TBR from TRACES, try uppercase TAN. If it is Conso, use TAN_Request Number. If it is a Justification Report, build the JR password from TAN, form, quarter and FY. If it is an issuer-created PDF, use that issuer's instructions.
What should I know about Troubleshooting matrix?
Problem Likely cause Check Form 16/16A does not open Lowercase TAN, spaces, or not the original TRACES package Uppercase TAN and file source Conso fails Wrong request number or missing underscore TAN_Request Number for that exact request Justification Report fails Wrong form/quarter/FY Statement details used in the request Password looks right but extraction fails Corrupt/incomplete download Download again from TRACE
What should I know about Finance-team control checklist?
Record TRACES request number against each download request. Store TAN in standard uppercase form in the TDS master. Save form type, quarter and FY with Justification Report requests. Do not email passwords in the same unsecured message as sensitive files where internal policy prohibits it. Keep original downloads separate from PDFs subsequently generated for employees/deductees. Use a controlled folder naming convent
What should I know about Common mistakes?
Using PAN instead of TAN for a TRACES deductor download. Typing TAN in lowercase. Using the latest Conso request number instead of the number belonging to the downloaded file. Omitting the underscore in the Conso password. Using 26Q in a Justification Report password when the request was for 24Q. Confusing an employer-distributed PDF password with the original TRACES download password.
Join the conversation