From decade-old stuck claims to remote NRI withdrawals — every case below started with the same thing: a claim that seemed impossible until the actual blocker was found.
Rejections, silence, and years of follow-up usually come down to one identifiable issue — not an unrecoverable claim.
54 case studies
EPFO rejected this claim four times citing unclear technical reasons, leaving the client unsure what was actually wrong.
Root cause traced to a DOJ/DOE mismatch — corrected, and the claim was approved.
Based in the US with no way to visit an EPFO office, this client needed the full withdrawal handled remotely across time zones.
Full amount credited with zero in-person visits required.
A second UAN generated by a later employer was silently blocking this client's original claim, and neither portal flagged the conflict.
UANs merged into one active account; withdrawal proceeded without further issue.
Spanning three employers and over ten years of service history, this case had been considered unrecoverable after repeated failed attempts.
Full & final settlement released — the money had been recoverable all along.
A high-value claim sat untouched because the former employer had stopped responding to EPFO's verification requests entirely.
Resolved directly with EPFO without requiring the employer's cooperation.
Repeated rejections cited "previous EPS service not received" — service that had never been transferred from an earlier employer's exempted trust.
Missing service record traced and filed; full pension claim approved.
A name spelling difference between Aadhaar and EPFO records had stalled this claim for over a year with no clear path forward.
Joint Declaration filed and approved; withdrawal followed within days.
Months-long postings at sea meant this client could never visit an EPFO office to correct an employer's data error.
Employer data corrected remotely; completed without a single office visit.
An elderly parent's family pension application had stalled for ten years across multiple failed follow-ups with no clear owner.
Claim reactivated and approved; monthly pension now active.
The claim kept bouncing back over a signature mismatch, but EPFO's rejection note never specified which document was at fault.
Correct specimen signature identified and resubmitted; claim cleared on first refiling.
Two rejections in a row gave only a generic remark, leaving the client repeating the same mistake without knowing it.
Diagnosed a mismatched exit date between employer records and the claim form.
A medical advance claim was rejected on a technicality the client didn't know applied to their case.
Refiled under the correct eligibility clause; advance approved in full.
Working full-time in London, this client had no bandwidth for EPFO's business-hours phone verification process.
Entire process handled over email and WhatsApp, working around the time difference.
The employer had shut its India office years ago, leaving no one to verify service details for this Gulf-based worker's claim.
Alternate verification route used through EPFO records instead of employer confirmation.
After immigrating years ago, this client had lost track of which UAN and employer their PF sat under.
Old UAN traced through PAN and Aadhaar cross-check; funds released to an NRE account.
Three separate jobs in three cities had generated three UANs, and the client had no idea which one held their latest balance.
All three consolidated into a single UAN before filing the final withdrawal.
A staffing agency had issued a fresh UAN without linking it to the client's existing one, breaking the transfer chain.
Duplicate UAN flagged and merged with EPFO directly; transfer completed.
A forgotten UAN from a short internship years earlier was still active and conflicting with the client's current account.
Inactive UAN closed and balance merged into the active account.
After three failed attempts over twelve years, the client had stopped expecting any resolution at all.
A fresh diagnostic pass found the actual blocker within the first review.
Funds sat in an old exempted-trust account from before 2014, a category most consultants had no experience untangling.
Trust records reconciled with EPFO; full balance transferred and withdrawn.
The former employer disputed the client's recorded service period, stalling the claim on a factual disagreement.
Payslips and Form 16 used as independent proof; EPFO accepted the claim without employer sign-off.
The employer entered liquidation mid-process, leaving the client's PF transfer request with no one to approve it.
Claim routed through EPFO's liquidation-case process instead of waiting on employer action.
Every time the client followed up, a different HR contact restarted the verification from scratch.
Escalated directly to the EPFO regional office, bypassing the employer bottleneck.
Unsure whether they qualified for a pension or a withdrawal benefit, this client had left the case untouched for years.
Eligibility confirmed for withdrawal benefit, not a certificate — and paid out accordingly.
A system error had undercounted this client's pensionable service by nearly four years.
Service record corrected after formal representation; revised pension approved.
A missing nomination form on file meant the deceased member's spouse couldn't access the pension despite being the rightful claimant.
Legal heirship established through alternate documentation; pension released.
One employer's records omitted the client's middle name entirely, creating a mismatch that blocked the merge of two accounts.
Joint Declaration filed with both employers to standardise the name across records.
A name originally in a regional script had been transliterated two different ways across two employer records.
Standardised spelling confirmed via gazette and Aadhaar; claim proceeded without delay.
Working on an offshore rig with limited connectivity, this client could only respond to requests during narrow shore-leave windows.
KYC completed in batched remote sessions timed around the client's shore leave.
Years at sea meant this merchant navy officer never had a continuous stretch on Indian soil to sort out the claim in person.
Entire filing handled via digital signatures and courier, no port stop required.
After the member's death, the surviving minor children's pension was stuck pending guardian verification.
Guardianship documentation completed; monthly pension now credited to the guardian account.
Conflicting nominee records from before and after a second marriage left EPFO unable to determine the rightful recipient.
Legal succession established through court-recognised documentation; pension released.
A family medical emergency needed funds released fast, but the client's KYC had a pending Aadhaar-seeding gap.
KYC gap closed same week; advance credited in time for the procedure.
An advance for a home purchase was rejected because the employer's address on file hadn't been updated in years.
Employer records updated and advance refiled under the correct address.
An education advance was stuck over a mismatch between the dependent's school records and the claim form.
Supporting documents realigned; advance approved before the admission deadline.
The client's Aadhaar-linked mobile number no longer matched what was on file with UIDAI, blocking e-KYC entirely.
Mobile number updated at the source before re-attempting Aadhaar seeding.
The client kept submitting details for a bank account that had quietly been closed years earlier.
New account seeded and verified; KYC approved on first resubmission.
Neither the registered email nor mobile number was reachable anymore, locking the client out of their own UAN portal.
Contact details updated through employer attestation; portal access restored.
Three different employers had recorded three slightly different dates of birth, none matching the Aadhaar record.
Joint Declaration filed with all three employers to standardise the DOB.
One employer's records had no father's name field filled in at all, causing a mismatch flag on every claim attempt.
Missing field added via Joint Declaration; claim proceeded without further hold.
Moving from a company-run trust to an EPFO-managed account triggered a transfer type the client's HR hadn't handled before.
Trust-to-EPFO transfer processed under the correct scheme code.
EPFO's auto-transfer feature had failed silently, leaving the client's old balance orphaned for years without anyone noticing.
Manual transfer initiated and orphaned balance merged into the current account.
The death claim stalled because one specific annexure to the death certificate had never been submitted.
Correct annexure obtained and filed; nominee claim settled in full.
No nominee had ever been registered, so the family had to establish legal heirship from scratch after the member's death.
Succession certificate secured; claim settled to legal heirs.
The client had completely forgotten about a PF account from their very first job over fifteen years earlier.
Account traced via old UAN records; balance withdrawn with accumulated interest.
Years without KYC completion had marked the account inoperative, freezing any withdrawal attempt.
KYC completed and account reactivated before final withdrawal.
As a foreign national on an Indian payroll, this client's claim needed handling under a specific bilateral social security agreement.
Claim filed under the correct Social Security Agreement provisions; full withdrawal approved.
A mismatch between the client's Certificate of Coverage and EPFO's International Worker records blocked withdrawal.
Certificate re-verified with the issuing authority; claim cleared.
With the account holder deceased and the nominee a minor, the claim needed a legally appointed guardian before EPFO would proceed.
Guardian appointed through proper process; funds released to a minor's guardian account.
A bank merger changed the client's IFSC code, and EPFO's records still pointed to the old, defunct code.
Bank details re-verified with the new IFSC; withdrawal processed without further delay.
EPFO repeatedly rejected a joint bank account for the payout, without ever stating that individual accounts are required.
Individual account seeded and verified; payout released immediately after.
A routine PF review surfaced an ESIC registration gap for several employees that the client's HR team hadn't caught.
Backdated registration filed correctly; compliance gap closed before the next audit.
A change in the client's payroll vendor caused two consecutive months of PF filings to be missed entirely.
Missed filings submitted with applicable interest; compliance brought current.
A growing company needed its PF and UAN generation process set up correctly from day one to avoid downstream claim issues.
Process set up correctly the first time, avoiding the errors seen in other cases on this page.
Old, rejected, or stuck for years — most claims come down to one identifiable blocker. Book a free consultation and we'll tell you what's actually holding yours up.
