Mobile Number Not Linked to UAN
No OTP access because your registered mobile number is outdated? Here's how to update it even without an active login.
Since nearly every self-service action on the EPFO portal, from password resets to KYC verification, depends on OTP delivery to your registered mobile number, an outdated number doesn't just cause one specific problem, it quietly blocks a whole range of actions until it's corrected. And because updating your registered number itself often requires access you don't have without a current OTP, this specific issue can feel like it has no clear starting point.
This guide focuses specifically on how to break that circular problem, updating your mobile number when the standard self-service path isn't available to you.
Why This Matters
An outdated registered mobile number is a foundational problem that cascades into every other EPFO interaction that depends on OTP verification, which is most of them. Fixing this specific issue first, before trying to resolve whatever secondary problem brought you to the portal in the first place, usually clears the path for everything else you actually needed to do. It's easy to spend time troubleshooting a symptom, like a failed claim, without realising the outdated number is the actual root cause underneath it.
Understanding the Problem
Your registered mobile number is typically tied to either your Aadhaar or your original EPFO enrollment details, and changing your phone number in daily life doesn't automatically update this record. Since most self-service update paths themselves require OTP verification to confirm identity, an outdated number creates a genuine circular blocker: you need OTP access to update your number, but you can't get OTP access because your number is outdated.
Step-by-Step Solution
Step 1: Confirm the mobile number currently registered against your UAN
Check with your employer or use available portal lookup tools to confirm exactly which number is currently on record, since this establishes the starting point for resolving the issue.
Step 2: Check whether your Aadhaar-registered number is current instead
If your Aadhaar has a different, current mobile number linked to it, this can sometimes offer an alternate path forward, particularly for Aadhaar-based verification processes, so it's worth checking this separately.
Step 3: Update your mobile number with UIDAI if it's outdated there too
If your Aadhaar-linked number is also outdated, updating it directly with UIDAI is a necessary parallel step, since Aadhaar-based verification depends on that number being current as well.
Step 4: Coordinate with your current employer to update your EPFO record
Since your employer has access to submit or facilitate updates to your EPFO KYC details, including your mobile number, reaching out to HR is typically the most direct path when self-service isn't available.
Step 5: Provide identity verification documents if requested
Your employer or EPFO may request identity verification, like Aadhaar or PAN, to confirm the update request is legitimate before processing the mobile number change.
Step 6: Verify the update by testing OTP delivery
Once the update is processed, test that OTP delivery works correctly to your new number before relying on it for a time-sensitive action like a claim or password reset.
Common Mistakes to Avoid
- Repeatedly attempting self-service actions that depend on OTP delivery to an outdated number, when this circular problem needs to be broken through employer coordination instead.
- Not checking whether the issue is specifically with your EPFO-registered number, your Aadhaar-registered number, or both, since the fix differs depending on which is actually outdated.
- Assuming a former employer can update this detail, when it's your current employer who typically has the active access needed to facilitate the change.
- Not providing clear identity verification documents when requested, which can delay an otherwise straightforward update.
- Forgetting to test OTP delivery after the update is processed, and discovering it still doesn't work at a genuinely time-sensitive moment.
- Letting a mobile number go outdated for an extended period without addressing it, allowing the problem to compound as more portal actions become inaccessible.
- Not informing family members who might need to assist with EPFO matters on your behalf that the registered number has changed, causing confusion if they try to help later.
- Assuming a temporary SIM issue, like travel roaming, is the same as a genuinely outdated registered number, when the troubleshooting for each is quite different.
Quick Recap
An outdated registered mobile number creates a circular blocker across nearly every EPFO self-service action, and resolving it requires either an alternate verified access path or direct coordination with your current employer. Fixing this foundational issue first typically clears the way for whatever other action originally brought you to the portal.