How Do You Correct a Wrong PAN in a TDS Return?

The deductor is the business or employer that reported the deduction. The payee, also called the deductee, is the person whose income suffered TDS. The Income Tax Department's tax-credit mismatch guidance directs the payee to the deductor for correction of the TDS return.

If you are the business owner, assign one person to coordinate the evidence, filing and follow-up with your chartered accountant. The related guide to TDS compliance for startups and MSMEs can help you review the wider deduction and reporting routine.

Start with the party that actually earned the income. Ask the payee to confirm their legal name and PAN through an agreed secure channel. Compare that confirmation with the agreement, invoice or payroll record and your party master. Resolve any difference before preparing the correction.

TRACES provides a PAN verification facility for deductors that displays validity and the PAN holder's name against the department's database. Use this alongside the transaction evidence: a valid PAN result alone does not establish that the PAN belongs to the intended recipient of your payment.

Keep a correction folder that explains the original entry, the proposed change and the evidence behind it. The checklist below is a recommended control record, not a claim that every document must be uploaded with every correction.

• ✓The payee's PAN evidence and written confirmation of the correct legal name.
• ✓The invoice, agreement or payroll record identifying the income recipient.
• ✓The relevant ledger entry, payment evidence and TDS working.
• ✓The deductor's TAN, financial year, quarter, form type and statement acknowledgement.
• ✓The affected deductee row, PAN originally reported and replacement PAN.
• ✓Previous correction references and any relevant processing or default report.
• ✓The reviewer's approval and the final submission acknowledgement.

Restrict access to these records. Keep full PAN details out of routine email subject lines and shared task lists. Tell the payee what evidence is needed, who will review it and how to send it securely.

Identify the affected statement by financial year, quarter and form type. Then match each reported row to the underlying transaction. Do not select a row solely because its amount resembles the payment: check the party, payment or credit date and deduction details together.

As a practical safeguard, search your party master and other filed statements for the same wrong PAN. Prepare a separate list of affected statements so that a correction to one return does not leave another unresolved. Correct the source record as well, after verification, to prevent reuse.

Use the current official instructions rather than an old screenshot tutorial. Authentication requirements, correction history and statement eligibility need checking for your case. Ask your chartered accountant to confirm the available route and any applicable filing restrictions.

For online correction, TRACES guidance directs deductors to Request For Correction under Defaults. Select the relevant statement and follow the available PAN correction workflow. Check the proposed replacement against your verified evidence before completing the authorised submission.

For a file-based correction, download the consolidated file from TRACES and prepare the correction from it. Ask your chartered accountant or return-preparation provider to confirm the current preparation, validation and submission steps for the file.

• ✓Confirm the statement identifiers and affected rows.
• ✓Compare the old and replacement PAN character by character.
• ✓Review the name against the intended income recipient.
• ✓Confirm that any other changed field is supported and intentional.
• ✓Save the submission reference and assign responsibility for tracking it.

Track the request through TRACES and read the processing result. Its online correction guidance identifies Track Correction Request as the place to monitor requests and view rejection remarks. If rejected, address the stated reason before resubmitting.

Treat submission, processing and reconciliation as separate checks. After processing, compare the available corrected statement records with your approved working. Check the affected PAN, transaction details and any relevant default report. Keep unresolved differences open.

Ask the payee to check the corresponding TDS entry in Form 26AS. The department's mismatch guidance uses Form 26AS when comparing reported credit. Do not promise that a submission acknowledgement means the payee's credit is already visible or that every related issue has been resolved.

Explain which reporting period is affected, what you are verifying and who owns the correction. After submission, share a suitable acknowledgement or reference through the agreed channel. Avoid sending a complete statement containing other parties' information.

After processing, explain what you checked and request confirmation of the relevant credit entry. If the payee has already filed an income-tax return or received a mismatch communication, ask them to consult their chartered accountant about any separate action. The income-tax pre-filing document checklist is a useful related guide for assembling their records.

• Changing only the party master and assuming the filed statement has changed.
• Using an old working file without checking previous corrections.
• Replacing a PAN without verifying the recipient's legal identity.
• Changing payment or deduction amounts merely to clear a validation error.
• Treating a successful upload as proof of processing and credit reconciliation.
• Closing the issue while another affected statement remains unresolved.

This guide addresses a wrong deductee PAN in a TDS statement. A wrong challan detail, missing payment, incorrect deduction or error in the payee's own return needs separate diagnosis. Tell your chartered accountant about those differences rather than treating every missing-credit case as a PAN correction.