PAN format structure
A Permanent Account Number is a 10-character alphanumeric identifier issued by the Income Tax Department of India. Each position carries meaning:
| Position | Character type | Meaning |
|---|---|---|
| 1–3 | Three letters | Alphabetical series (AAA–ZZZ), assigned sequentially |
| 4 | One letter | Entity type: P = Individual, C = Company, H = HUF, A = AOP, B = BOI, G = Government, J = AJP, L = Local Authority, F = Firm/LLP, T = Trust |
| 5 | One letter | First letter of the surname (for individuals) or entity name (for others) |
| 6–9 | Four digits | Sequential number (0001–9999) |
| 10 | One letter | Check letter (computed from the first 9 characters) |
Example: ABCPD1234E — series ABC, entity type P (Individual), surname initial D, sequence 1234, check letter E.
The 4th character: entity type codes
The 4th letter of a PAN tells you what kind of entity holds it. This is useful for validation beyond just format checking — if your vendor master says 'Company' but the PAN's 4th letter is P (Individual), something is wrong.
| Code | Entity type |
|---|---|
| P | Individual (Person) |
| C | Company |
| H | Hindu Undivided Family |
| A | Association of Persons |
| B | Body of Individuals |
| G | Government Agency |
| J | Artificial Juridical Person |
| L | Local Authority |
| F | Firm / Limited Liability Partnership |
| T | Trust |
Any other letter in the 4th position means the PAN is invalid.
Common PAN data problems
- Truncated values — copy-paste errors that lose the last character, leaving 9 characters instead of 10.
- Letter/digit confusion — O typed as 0, I as 1, or vice versa. Position-aware validation catches these because letters can't appear in positions 6–9 and digits can't appear in positions 1–5 or 10.
- Lowercase input — PAN is always uppercase. The validator normalises case before checking but flags the original as needing correction.
- Spaces and hyphens — 'ABC PD 1234 E' or 'ABCPD-1234-E' pass visual review but fail system validation.
- Dummy values — 'AAAAA0000A' or similar repetitive patterns are technically valid format but likely placeholder data.
Why PAN validation matters for business data
PAN is required on invoices above Rs 50,000, on TDS certificates (Form 16/16A), and for vendor onboarding under Section 206AB (higher TDS for non-filers). An incorrect PAN means TDS is deducted at a higher rate, GST input credit may be disallowed (since PAN is embedded in GSTIN), and your TDS return filing will show mismatches.
Validating PAN format before submitting to TRACES or your accounting system catches the errors that would otherwise come back as challan mismatches or PAN-name mismatch notices.