Key takeaways
- Each identifier answers a different question. Collecting all four by default is a design shortcut, not a compliance requirement.
- Applicability varies by employee — coverage thresholds, prior employment and role all affect which identifiers are relevant.
- Verification results belong on the record with an audit trail. Never silently overwrite what the candidate entered.
- A failed or inconclusive check is an exception for human review, not proof of invalid identity or ineligibility.
What each identifier supports
These four identifiers are frequently grouped together on onboarding forms, which obscures how differently they behave. PAN relates to tax and payroll records. UAN supports provident-fund records for eligible employees. ESIC identifiers relate to employees covered by that scheme. Aadhaar-based processes must follow the permitted method and purpose for the employer's specific use case.
| Identifier | Primarily supports | Applicability |
|---|---|---|
| PAN | Tax and payroll records | Generally relevant across employees |
| UAN | Provident fund records | Eligible employees; may already exist from prior employment |
| ESIC | Employees' state insurance records | Employees covered by the scheme |
| Aadhaar | Identity processes, where permitted | Depends on the permitted method and purpose |
Recommended control flow
The order matters. Explaining the purpose before collection is not merely courteous — it is what makes the collection justifiable, and it measurably reduces the rate at which candidates enter placeholder values to get past a field they do not understand.
- 01
Explain the purpose
State plainly why the identifier is being requested and what it will be used for, at the point of collection rather than buried in a policy document.
- 02
Collect through a secure form
Identifiers are sensitive. They belong in an authenticated form with restricted access, not in an email body or a spreadsheet attachment.
- 03
Validate formatting first
A format check catches typing errors immediately and avoids sending malformed values to a verification service.
- 04
Use authorised verification methods
Where verification applies, use the permitted method for your use case. Do not construct workarounds that access data through unintended routes.
- 05
Route mismatches to HR
A mismatch is a case to review. It should reach a named person with the context needed to resolve it, not sit as a red flag on a dashboard.
- 06
Retain the result with an audit trail
Store what was checked, when, by what method and with what outcome. Never silently overwrite candidate-entered data with a value returned by a check.
Handling exceptions properly
A failed or inconclusive digital check is an exception to review, not automatic proof of invalid identity or employment eligibility. Name mismatches from a recent marriage, an address that has not been updated, a legitimately dormant identifier, or a transient service outage all produce the same failure signal as a genuine problem.
The consequence of treating those as equivalent falls on the individual, which is why this step warrants a person rather than a rule. Document the review, the basis for the decision, and who made it.
- Distinguish a service failure from a data mismatch before acting on either
- Give the candidate a route to correct or explain, with a stated timeline
- Record who reviewed the exception and what they decided
- Never let an automated check alone determine an employment outcome
Frequently asked questions
Is Aadhaar mandatory for employee onboarding?
Aadhaar-based processes are subject to specific rules on permitted purpose and method, which depend on the employer's use case. Rather than assuming it is required, confirm what your organisation is permitted to do and design the form around that.
What if a new joiner does not have a UAN?
A first-time employee may not have one, while an experienced hire usually does from prior employment. Both are normal. The onboarding workflow should handle the absent case without blocking the form, and route it for the appropriate follow-up.
Should verification results overwrite what the candidate entered?
No. Keep both values and record the difference. Overwriting destroys the evidence of what the candidate actually submitted, which is precisely the record you need when an exception is later reviewed or disputed.
Primary references
This resource provides general HR operations information and is not legal, tax or regulatory advice. Requirements vary by organisation and employee circumstances.