Skip to main content
Independent EPFO consultancy · Not affiliated with EPFO · Reply within 24 hrs +91 98397 17791 5.0 on Google
NidhiSetu
WhatsApp me
26 real cases · Anonymised

Real EPFO cases, including the ones that didn't work.

Twenty-six anonymised cases from my own work: the reported problem, what I investigated, what I did, and the honest outcome. No names, UANs, Member IDs, employers or other identifying details. Where a case was still being worked through official channels rather than concluded, I say so plainly.

26 anonymised cases8 resolved18 not concluded, shown anywayOfficial EPFO routes only
Problem
Outcome

26 cases

UAN · A1Resolved

Unfamiliar employer discovered in service history

Problem
Several members came to me after finding an employment entry in their UAN/service history for an organization they stated they never worked for — raising concerns about service history, UAN records, and future BGV or transfers.
What I did
Reviewed the complete UAN service history; identified the unfamiliar Member ID and employment record; compared the EPFO record against the member's actual employment history; assessed whether the entry appeared genuinely incorrect or unauthorized; guided the member on the appropriate employer/EPFO correction and delinking process; helped prepare supporting documentation establishing the employment did not belong to them.
Outcome
Where the entry was confirmed to be genuinely incorrect or unauthorized, members were able to pursue correction or delinking through the appropriate EPFO process — restoring a more accurate service history. Lesson: An unfamiliar employer in your UAN shouldn't be ignored. First verify the Member ID, DOJ, DOE and employment details to determine whether the entry is genuinely yours.
Read the full case Similar problem? WhatsApp me
UAN · A2Resolved

Unknown PF Member ID linked to UAN

Problem
A member checked their EPFO service history and found a PF Member ID belonging to an employer they didn't recognize, concerned it could affect future BGV and PF transactions.
What I did
Reviewed the available UAN/service-history information and helped the member understand which establishment was associated with the Member ID, the recorded DOJ/DOE, whether contributions were appearing, and whether the employment matched their actual work history.
Outcome
Where the record was determined to be genuinely unauthorized or incorrectly associated, the member was able to pursue correction of the unauthorized/incorrect PF employment entry through the appropriate EPFO/employer-assisted route — instead of leaving the discrepancy unresolved.
Similar problem? WhatsApp me
UAN · A3Not concluded

Unauthorized employment record flagged during BGV

Problem
A candidate's BGV raised a question about an employer appearing in their EPFO service history that they stated they had never worked for — creating a potential mismatch between declared employment, EPFO history, Member ID, and BGV records.
What I did
Helped the candidate investigate the record and determine the appropriate correction route. The focus was on establishing whether the EPFO record accurately reflected genuine employment history — not simply on removing an inconvenient entry.
Outcome and lesson
The priority in this case was accurately establishing whether the record was genuinely unauthorized before pursuing any correction route. Lesson: An unknown employer in your UAN can become a serious issue during BGV. Verify the record before assuming it's a normal PF entry.
Similar problem? WhatsApp me
UAN · A4Not concluded

Wrong employer appearing in service history — again

Problem
A member found an employer/Member ID in their UAN service history that they stated they had never worked for — the same pattern as the other cases in this category, raising the same PF transfer, withdrawal, and employment-verification concerns.
What I did
Reviewed the employment record and identified the appropriate correction or delinking route based on the specific circumstances, rather than defaulting to a generic response.
Outcome and lesson
The member was guided toward the appropriate EPFO correction process instead of attempting to create another UAN. Lesson: Don't create another UAN simply because an incorrect employment record appears. First determine whether the existing entry can be corrected or delinked.
Similar problem? WhatsApp me
BGV · B1Resolved

PF overlap triggered a red BGV after joining a new employer

Problem
A candidate's BGV was flagged because EPFO service history showed an overlap between one employer's DOJ and another's DOE/DOL. The candidate maintained the actual employment timelines didn't overlap.
What I did
Reviewed the candidate's EPFO service history, DOJ/DOE records, employment documents, and actual joining/relieving timeline. The discrepancy was identified as an EPFO date-record issue. With the employer's cooperation, the relevant records were reviewed and the incorrect DOJ/DOE information was corrected through the applicable process.
Outcome
After the service dates were brought into alignment with the supporting employment records, the candidate had a clearer and more consistent employment history for BGV purposes. Lesson: A PF overlap doesn't automatically mean dual employment. An incorrect DOJ/DOE entry can create a serious BGV discrepancy on its own.
Read the full case Similar problem? WhatsApp me
BGV · B2Resolved

A short employment stint created an unexpected PF overlap

Problem
A candidate had a very short employment period at one organization before joining another. The previous employer's PF record stayed active for a period that overlapped with the next employer's DOJ, and the candidate was concerned it would read as dual employment.
What I did
Examined the complete employment timeline against the EPFO service history. The issue was traced to the recorded exit date rather than assumed simultaneous employment. I coordinated on the documentation needed from the previous employer and guided the employer-assisted correction of the relevant EPFO date.
Outcome
The PF service history was aligned with the actual employment documentation, reducing the discrepancy that had triggered the BGV concern. Lesson: Even a short employment stint can create a long-lasting EPFO service-history discrepancy if the exit information isn't correctly recorded.
Read the full case Similar problem? WhatsApp me
BGV · B3Resolved

Previous employer's exit date overlapped with a new job

Problem
A candidate had already left an organization and joined another company, but the previous employer's EPFO record showed a later exit date than the candidate's actual last working day — creating an overlap with the new employer's DOJ.
What I did
Reviewed the EPFO service history, compared recorded dates with employment/relieving documents, identified the discrepancy in the previous employer's exit information, and guided the candidate on approaching that employer for correction through the appropriate EPFO route — with employer involvement and supporting documentation, not a false employment history.
Outcome
The discrepancy was addressed by correcting the inaccurate employment-date information. Lesson: Your BGV result can be affected by what EPFO records show — not only by what actually happened during your employment.
Similar problem? WhatsApp me
BGV · B4Resolved

DOJ overlap created a dual-employment red flag

Problem
A candidate's new employer recorded a DOJ that appeared to overlap with the previous employer's PF service period — the candidate maintained the previous employment had already ended.
What I did
Reconstructed the employment timeline using available documentation and EPFO records. The discrepancy was traced to the recorded employment dates. The candidate was guided to obtain employer confirmation and pursue correction of the inaccurate DOJ/DOE information through the proper employer/EPFO process.
Outcome
The candidate was able to address the discrepancy with documentary support and corrected service information. Lesson: Before assuming a BGV rejection means dual employment, first compare your actual employment timeline with your EPFO DOJ/DOE records.
Similar problem? WhatsApp me
BGV · B5Resolved

Multiple Member IDs created a complex BGV discrepancy

Problem
A candidate had multiple PF Member IDs under the same UAN. During BGV, different Member IDs showed different DOJ/DOE information, creating an apparently inconsistent employment history.
What I did
Mapped the candidate's complete service history across all three employers, then compared UAN service history, Member IDs, DOJ, DOE, employment documents, and actual joining/leaving dates to identify the inconsistent entries. Where employer records were incorrect, the candidate was guided to approach the relevant employer for correction and follow the appropriate EPFO process.
Outcome
The candidate obtained a clearer and more consistent employment record. Lesson: Multiple Member IDs under one UAN can make BGV complicated when DOJ/DOE information is inconsistent across them.
Read the full case Similar problem? WhatsApp me
BGV · B6Not concluded

PF transfer stuck because of a service overlap

Problem
A member's PF transfer wasn't progressing because their service history showed overlapping employment periods — traced to a previous employer's date of exit not correctly aligning with the next employment period.
What I did
Compared DOJ/DOE across the member's Member IDs, identified the overlapping period, determined which employer's record required correction, and guided the member on the appropriate correction/grievance route.
Outcome and lesson
The case was moved toward correction of the underlying service-history problem rather than repeatedly submitting transfer requests. Lesson: When a PF transfer is stuck because of overlap, fixing the underlying service-history problem usually matters more than repeatedly filing the transfer request.
Similar problem? WhatsApp me
Service history / EPS · C1Not concluded

PF transferred but EPS/service history not updated

Problem
A member's PF amount was successfully transferred to their latest PF account, but the previous employment's DOJ/DOE and EPS/service-history information didn't properly appear in the current service history.
What I did
Reviewed the member's service history, compared previous and current Member IDs, checked PF transfer records and available statements, and identified the mismatch between the transferred PF amount and the service/EPS history. Guided the member on filing an EPFiGMS grievance with supporting documents — UAN details, PF statements, and Form 13/transfer documentation where applicable.
Outcome and lesson
This case needed direct EPFO intervention to correctly reflect the employment/service information — it was not something a portal-side correction alone could resolve.
Similar problem? WhatsApp me
Service history / EPS · C2Not concluded

PF transferred across four employers, but pension service stayed behind

Problem
A member had worked for four employers. Their PF amounts were transferred to the latest PF account, but EPS/pension service information remained associated with the earlier Member IDs instead of consolidating.
What I did
Reviewed all four employment records, compared PF transfer information against EPS/service records, and identified that pension/service information hadn't followed the PF balance. Guided the member that this needed EPS/service correction specifically — not just a PF balance-transfer fix.
Outcome and lesson
The case needed dedicated attention to EPS/service consolidation in addition to the already-completed PF transfer. Lesson: A completed PF transfer is not proof that your pension service history transferred with it — check both separately, especially across multiple employers.
Read the full case Similar problem? WhatsApp me
Service history / EPS · C3Not concluded

EPS/pension service missing from service history

Problem
A member's EPF records existed and looked correct, but pension (EPS) service wasn't correctly reflected or transferred alongside it.
What I did
Compared the previous and current Member IDs, EPS service, transfer records, and Annexure K/service information where applicable.
Outcome and lesson
The member was guided toward correcting/adding the missing pension-service information before proceeding with a pension-related claim. Lesson: A PF balance can look correct while EPS service history remains incomplete — the two should be checked separately.
Similar problem? WhatsApp me
Service history / EPS · D1Not concluded

Employer created a PF Member ID after only 3 days of employment

Problem
A member worked for an employer for only 3 days. Roughly 1.5 years later, the employer had created/maintained a PF Member ID showing a zero balance, which the member wanted removed or corrected.
What I did
Reviewed the employment timeline and the PF Member ID/balance, identified this as a service-history/Member-ID correction matter rather than a normal withdrawal issue, and guided the member on approaching EPFO for correction given the short employment period and zero balance.
Outcome and lesson
The objective was correction/clarification of the erroneous or unwanted service-history entry through the appropriate EPFO route.
Similar problem? WhatsApp me
Service history / EPS · D2Not concluded

3-day employment, then a new employer — worried about overlap

Problem
A member joined a company, worked roughly 3 days, submitted PF-related documents, resigned, and then joined another company — concerned about UAN impact, the short-service PF entry, possible overlapping dates, and future BGV problems.
What I did
Reviewed the employment sequence, checked the implications of the short-service PF entry, examined the potential date overlap, and explained the importance of correctly maintained DOJ/DOE — advising correction through the appropriate EPFO/employer process where needed.
Outcome and lesson
Not concluded in the information available — the case is included here because it illustrates something worth knowing upfront, stated in the lesson below. Lesson: Even a very short employment period can become significant when it appears in EPFO service history or background verification — don't assume a few days won't register.
Read the full case Similar problem? WhatsApp me
UAN · E1Resolved

UAN frozen, unable to use online services

Problem
A member's UAN was frozen, preventing normal online EPFO services and creating difficulty accessing or processing PF-related requests.
What I did
Checked UAN status and Aadhaar/UAN linkage; reviewed member profile details and service history; checked existing Member IDs and, where available, the reason for the freeze; assessed the case against EPFO's freeze/de-freeze process; prepared supporting documents and routed the request to the appropriate EPFO channel for verification.
Outcome
UAN de-freezing was pursued through the appropriate official process, and the member was able to resume eligible EPFO services. Lesson: A frozen UAN shouldn't automatically be treated as a "need a new UAN" problem. The first step is identifying why the UAN/Member ID was frozen and what verification EPFO actually requires. See my full UAN freeze guide for the complete process.
Read the full case Similar problem? WhatsApp me
UAN · E2Not concluded

Aadhaar seeding kept failing against the UAN

Problem
The member's employer attempted Aadhaar seeding against the UAN, but the process repeatedly failed due to portal/verification issues.
What I did
Checked name, date of birth, Aadhaar details, UAN profile, mobile number, and KYC status to isolate the mismatch or technical blocker, then guided the member toward the appropriate Aadhaar/KYC correction route.
Outcome and lesson
A structured correction path was established instead of the member repeatedly attempting the same failed action. Lesson: Before blaming the portal, compare Aadhaar data and UAN profile data field-by-field — the mismatch is usually there.
Similar problem? WhatsApp me
UAN · E3Not concluded

Multiple UANs from different employments

Problem
A member had more than one UAN, created during different periods of employment — creating confusion around service history, PF balance, transfer, KYC, and claim filing.
What I did
Mapped all UANs and Member IDs against each other and identified the active, appropriate UAN to consolidate around.
Outcome and lesson
The member received a consolidation/correction strategy instead of creating yet another UAN. Lesson: The goal is generally to resolve the existing UAN structure, not keep generating new UANs every time something looks wrong.
Similar problem? WhatsApp me
UAN · E4Not concluded

PF account linked to the wrong UAN

Problem
One employment's PF Member ID appeared to be associated with the wrong UAN entirely.
What I did
Reviewed the employment record, UAN details, and the Member ID relationship to determine the appropriate correction/transfer route.
Outcome and lesson
A structured correction path was established. Lesson: Wrong-UAN linking should be treated as a record-correction problem, not simply a password or login problem.
Similar problem? WhatsApp me
Claims · F1Not concluded

Wrong date of exit preventing PF withdrawal

Problem
The member had genuinely left their employment, but the date of exit recorded in EPFO didn't match reality or was incomplete — blocking the claim they wanted to file.
What I did
Checked the employment timeline against available employment documents and identified the appropriate DOE-correction route.
Outcome and lesson
The member received a documented action plan for correcting the DOE before proceeding with the claim. Lesson: A claim problem can sometimes actually be a service-history/DOE problem in disguise.
Similar problem? WhatsApp me
Claims · F2Not concluded

Claim rejected over a name mismatch

Problem
A member's PF claim was rejected because the name in EPFO's records didn't match the identity/KYC records submitted with the claim.
What I did
Compared Aadhaar and EPFO records to identify the exact mismatch, and determined whether the correction was needed in the member profile or the KYC record.
Outcome and lesson
The member received a clear correction-first action plan before submitting another claim. Lesson: Resubmitting the same rejected claim without fixing the underlying mismatch usually doesn't solve anything.
Similar problem? WhatsApp me
Transfers · F3Not concluded

Transfer not reflecting despite employer action

Problem
The employer had completed its part of a PF transfer, but the transfer still wasn't showing correctly in the member's records.
What I did
Checked transfer status, previous and current Member ID, passbook, service history, and claim/transfer records to isolate exactly where the process had stalled.
Outcome and lesson
The member was guided toward the appropriate EPFO follow-up/grievance route. Lesson: Always distinguish between employer approval, EPFO processing, and the transfer actually reflecting — they're three different steps, not one.
Similar problem? WhatsApp me
Claims · F4Not concluded

Rejected with "claim already settled"

Problem
A member tried to file a PF claim and received a response stating the claim had already been settled.
What I did
Reviewed claim history and previous settlement information to determine whether the member had already been paid, whether another claim existed, whether the issue traced back to an old Member ID, or whether the rejection needed EPFO clarification.
Outcome and lesson
The member was advised to verify the historical claim before filing another one. Lesson: A "claim already settled" response should trigger claim-history verification first — not an immediate re-submission.
Similar problem? WhatsApp me
Employer · G1Not concluded

Employer closed down, no one left to approve KYC

Problem
The member's former employer had shut down operations entirely, leaving no accessible authorized representative to approve a pending KYC/correction request.
What I did
Reviewed the pending KYC request and available employment records, checked whether the issue could be escalated to EPFO directly, and prepared supporting documentation.
Outcome and lesson
The member was guided toward an EPFO-side resolution route rather than remaining dependent indefinitely on a closed employer. Lesson: An employer closing down doesn't necessarily mean the PF issue is impossible to resolve — the correct escalation route is what matters.
Read the full case Similar problem? WhatsApp me
Employer · G2Not concluded

Employer wouldn't cooperate with a needed correction

Problem
An employer refused or failed to cooperate with a required PF correction — DOJ or DOE correction, KYC approval, Joint Declaration, service-history correction, or transfer-related action — despite repeated requests from the member.
What I did
Documented the case with employer communication, employment proof, EPFO records, the exact correction required, and the member's previous attempts, then identified the appropriate EPFO grievance/escalation route.
Outcome and lesson
The member had an evidence-backed escalation strategy rather than relying indefinitely on the employer. Lesson: When employer cooperation fails, the case should move from "keep following up with HR" to a properly documented EPFO escalation.
Similar problem? WhatsApp me
Employer · G3Not concluded

EPFiGMS grievance closed without solving anything

Problem
The member had already raised an EPFiGMS grievance, but the response didn't actually resolve the underlying PF issue.
What I did
Instead of filing another generic complaint, the underlying issue was identified and the grievance was restructured around the exact problem, the relevant Member ID, a clear chronology, the previous grievance response, the specific relief being requested, and supporting evidence.
Outcome and lesson
The member obtained a more targeted escalation strategy. Lesson: A grievance should ask EPFO to resolve a specific record-level problem — not just say "please solve my PF issue."
Similar problem? WhatsApp me

How these cases were handled

Every case above was worked through official EPFO channels: employer-assisted corrections, EPFiGMS grievances and documented Joint Declarations. NidhiSetu is an independent consultancy, not an EPFO service. I never claim to guarantee an EPFO outcome or offer a way to conceal genuine employment.

I help identify incorrect DOJ/DOE records and guide employer-assisted correction where the EPFO record doesn't reflect genuine employment. I don't remove genuine service-period overlaps, and I don't alter DOJ/DOE records simply to help a candidate pass BGV. The objective is always an accurate record, not a convenient one.

See the overall numbers: resolved, partly resolved and refunded

See your situation in one of these?

Send me a masked view of your service history and I'll tell you honestly whether it's the same kind of issue, and what the realistic next step looks like.

Questions before you book? WhatsApp me Book a consultation — ₹499

I never ask for your OTP, UAN password or bank login.

Read the full guides

Service overlap

Two employers with overlapping dates blocking your claim.

Read the guide →

BGV PF mismatch

Job offer at risk due to a background-check PF discrepancy.

Read the guide →

UAN delink

A wrong or fraudulent Member ID linked to your UAN.

Read the guide →

Annexure K missing or wrong

Pension service history can go missing even after a clean PF transfer.

Read the guide →

Tell me what's wrong with your PF.

Ask me first. I reply to every message myself within 24 hours and tell you whether a consultation will help, before you book anything.

Questions before you book? WhatsApp me Book a consultation — ₹499
or call +91 98397 17791

I never ask for your OTP, UAN password or bank login.

Running a business? Book a 15-min call →