If your UAN shows a company you never worked for, an extra Member ID, or an overlap that doesn't belong to you, it's fixable — but EPFO validates contributions, claims, and transfer activity before allowing removal. Filing the wrong reason resets the clock.
If your UAN shows a company you never worked for, an extra Member ID, or an overlap that does not belong to you, it can feel frightening. The first step is to identify the record and check whether EPFO's delink route applies.
A company name appears in service history even though you never worked there.
You accepted or discussed an offer, but never joined, yet a PF Member ID exists.
A Member ID that belongs to another employee or wrong establishment is linked to your UAN.
Two jobs appear for the same period, creating confusion in claims, transfers, or BGV.
A new employer flags the wrong PF entry and asks for clarification before joining.
You suspect your identity or UAN details were used to create an unauthorized record.
Two Member IDs create duplicate or confusing service history under one UAN.
The establishment name, Member ID, or service period does not match your actual job history.
EPFO's Delink facility is meant for wrong or unauthorized Member IDs. It is not a shortcut to erase genuine employment history.
The Member ID does not belong to your actual employment history.
You did not join the establishment, but it appears in your UAN service history.
You suspect the PF entry was created without your knowledge or consent.
The wrong establishment / member account is mapped to your UAN.
A PF Member ID was created even though the employment never actually started.
An incorrect Member ID is causing an overlap with your real employment.
You need a clean, process-backed explanation for a wrong PF record.
You want to understand risk before sharing documents or making a portal request.
These restrictions matter because a wrong delink request can waste time or create confusion. Check them before taking action.
If a claim is settled or pending against the Member ID, EPFO may block portal-based delinking.
If a transfer claim exists, is settled, or is pending, the system may prevent the Member ID from being removed.
Member IDs with Date of Joining before the cutoff can be rejected by system validation.
As per public 2026 guidance, Member IDs with contributions received more than six times are not eligible for this portal route.
Financial records are strictly validated because EPFO must protect fund and service integrity.
Delink is for incorrect or unauthorized entries, not for hiding real employment history from BGV.
Date of Joining before 31-Dec-2016 can block delinking through the portal.
Settled or pending claim found against the Member ID.
Transfer claim activity found against the Member ID.
Important restriction: if contribution, claim, or transfer activity exists, do not assume the entry can be removed instantly. Your safest move is to check the exact system status before filing anything.
This is the employee-facing journey. The exact result depends on EPFO system validations and employer / field-office review.
Use your own UAN and password. Do not share OTP or password with any consultant.
Check all Member IDs, establishment names, DOJ, DOE, and service overlap details visible in your UAN.
Select the incorrect Member ID. If the button or validation is not available, note the error code or screenshot it with sensitive details masked.
Choose the correct reason — such as “never worked in this establishment” or “wrong Member ID linked without knowledge”.
EPFO uses Aadhaar OTP verification through your registered mobile. Keep control of your own OTP.
The request is forwarded to the employer. If contributions are low and the employer accepts, it may be handled at employer level.
If the employer rejects, does not act, or contribution count requires it, eligible cases can move to EPFO office review.
If approved, the incorrect Member ID is removed from the UAN service history according to EPFO's process.
Safety note: NidhiSetu uses official EPFO routes only. Do not share your UAN password, Aadhaar OTP, bank OTP, ATM PIN, or net-banking login with any consultant. You can mask sensitive details before sending screenshots for review.
These rules decide whether your case is straightforward, blocked, or needs escalation.
Delink is meant for wrong or fraudulent entries, not genuine jobs.
Settled, processed, or pending claims can prevent removal.
Transfer activity may trigger system restrictions and error messages.
DOJ before 31-Dec-2016 can lead to ERR_UNE008.
The request needs Aadhaar e-KYC consent and OTP verification.
Employer action is part of the process, but rejection does not always end the case.
Eligible requests may move to Regional Office review if employer rejects or does not act.
Contribution count is a key eligibility check in 2026 guidance.
EPFO checks funds, claims, transfers, and service history before allowing removal.
Using delink to conceal genuine employment can create bigger BGV and legal risk.
Offer letters, non-joining proof, HR emails, and BGV notices can help explain the case.
The right reason and sequence matter. Random grievances can delay resolution.
Bottom line: Delink is simple only when the record is clean. EPFO checks the history behind that Member ID. A clean wrong-entry case is different from a case with contributions, claims, transfers, or old DOJ.
Wrong PF records affect money, jobs, credibility, and family security — that's why they feel so frightening at first.
BGV teams may pause onboarding until PF history is explained.
Wrong company names can make your employment history look inconsistent.
Wrong service records can create claim rejection or transfer confusion.
Incorrect service periods can affect future EPS understanding.
Two jobs in the same period can look like a serious employment mismatch.
Employees worry that their Aadhaar, PAN, or UAN was misused.
Reassurance: Most genuine incorrect-entry cases can be handled properly when the right EPFO route, reason, and evidence are used.
UAN delink cases need careful reading of service history, claim status, contribution count, and employer-response risk. NidhiSetu helps employees understand the safest route before they submit anything.
Deep EPFO process understanding — we map your issue to the correct official route instead of guessing.
Real drafting experience — if your case needs escalation, the wording and evidence sequence matter.
You can start with a masked screenshot and issue summary. PAN-India support.
You get the likely path, risk, and paid scope before committing.
Send the issue type and a masked service-history screenshot. Do not share OTP, password, Aadhaar number, PAN number, or full UAN in the first message.
Straight answers for employees facing wrong company, fake PF entry, overlap, and BGV stress.