Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
TDS PAN validation mismatch in India is one of the most common — and most costly — causes of short deduction exposure. Under Section 206AA, a single invalid or inoperative PAN forces TDS at 20%, regardless of the actual section rate, and the deductor bears the liability for the shortfall if the correct rate was applied instead.
What Section 206AA Covers
Section 206AA requires every deductee to furnish their PAN to the deductor. If the PAN is not provided, is invalid, or cannot be validated, the deductor must apply TDS at the highest of three options: the rate in the relevant section, the rate in force under the Finance Act, or 20%. Since 20% exceeds most section rates — 194C is 1-2%, 194J is 10%, 194H is 5% — the floor effectively governs most vendor payments where PAN validation fails.
From 1 July 2023, the Income Tax Department extended 206AA to cover inoperative PANs — those not linked to Aadhaar. An inoperative PAN is treated as an invalid PAN for TDS deduction purposes.
Where PAN Validation Breaks Down
Inoperative PAN After Aadhaar Linking Deadline
The Finance Act 2023 required all PANs to be linked with Aadhaar by 31 May 2024. PANs not linked by the extended deadline became inoperative. For finance teams, this created a category of vendors whose PAN appeared valid in the ERP vendor master but was flagged as inoperative on TRACES. Deductors who did not refresh their TRACES PAN validation before the Q1 FY 2024-25 return continued deducting at section rates, creating a short-deduction position under 206AA.
PAN Quoted Incorrectly on Invoice
A PAN has 10 characters in a fixed format: the fourth character identifies the type of taxpayer (P for individual, C for company, F for firm). A single transposed character — especially common when vendors type PAN manually on invoices — produces an invalid PAN that does not match any TRACES record. The deductor who accepts the invoice PAN without TRACES verification and files the return with the incorrect number is liable for the 206AA differential.
Stale Vendor Master After PAN Reissue
When a vendor changes their company structure — a proprietorship converting to a private limited company, for example — the Income Tax Department issues a new PAN. If the deductor’s ERP vendor master is not updated, TDS is quoted under the old PAN in the return. TRACES will either flag it as not found or show it belonging to a different entity, both of which expose the deductor.
Reconciliation Process: TRACES Bulk Validation
| Step | Action | Data Source | Timing |
|---|---|---|---|
| 1 | Extract vendor PAN list from ERP | AP/vendor master | Before each payment cycle |
| 2 | Upload PAN list to TRACES PAN Verification | TRACES portal | Before quarterly return |
| 3 | Review output: valid / inoperative / not found | TRACES verification result | Within 24 hours of upload |
| 4 | Flag vendors with invalid/inoperative PAN | Internal exception list | Before payment processing |
| 5 | Deduct at 20% and document TRACES output | TRACES report (PDF/CSV) | Per payment to flagged vendor |
PAN Validation — Deduction Rate Impact
| Scenario | Normal Rate | 206AA Rate | 206AB Rate (if non-filer) | Action |
|---|---|---|---|---|
| Valid PAN, ITR filed | 194J: 10% | N/A | N/A | Deduct at 10% |
| Inoperative PAN (Aadhaar not linked) | 194J: 10% | 20% | N/A | Deduct at 20%, document TRACES output |
| PAN not furnished at all | 194C: 2% | 20% | N/A | Deduct at 20% per 206AA |
| Valid PAN, non-filer (206AB) | 194J: 10% | N/A | 20% (twice rate or 5%, higher) | Deduct at 20%, verify on TRACES |
| Non-resident, no PAN (Rule 37BC applies) | Treaty rate | 20% under 206AA | N/A | Furnish Form 10F to avoid 206AA |
What Automated Reconciliation Changes
Manual PAN validation requires finance teams to extract vendor lists, upload them to TRACES manually each quarter, and reconcile the output against the ERP before filing. At 50 vendors this is a few hours of work. At 500 active vendors across multiple entities, the process breaks: teams either skip validation and accept the 206AA risk, or they validate only for new vendors and miss changes in existing vendor PAN status.
TDS reconciliation software India that integrates TRACES PAN validation data can run the check automatically before each payment cycle, flag vendors whose PAN status has changed since the last run, and tag the correct deduction rate in the transaction record. The audit trail is generated automatically — the TRACES output date, the PAN status at the time of deduction, and the rate applied are all captured without manual effort.
Reconciliation software India platforms that manage the deductor-side TDS ledger can also map 206AA flags to the variance code TAX_DEDUCTION, making it visible in exception reports rather than buried in individual payment records.
The Income Tax Department of India publishes updated PAN verification procedures and 206AA guidance through its portal, which is the authoritative source for current rates and compliance requirements.