What to do if your EPF claim is rejected

Log in to the EPFO member portal with your UAN and password and go to Online Services, then Track Claim Status. Every claim you have ever filed is listed there with a claim reference number, the field office that handled it, a status, and — for anything rejected — a remarks field carrying the reason in the office's own phrasing. The SMS you received says the claim was rejected and nothing more. The remark says why. Until you have read it you are guessing, and guessing is what produces the second rejection.

Copy the remark out verbatim, with the claim reference number, the date, and the name of the office. Take a screenshot as well. The exact wording matters later: a grievance that quotes the office's own remark back to it is answered on the merits, and one that says the claim was rejected without explanation invites a reply telling you to check the portal. Remark wording is not fully standardised across field offices, so two people with the same defect can see it described in different words.

Establish who rejected the claim. A claim can be declined by the employer before it reaches EPFO at all, where the employer's digital signatory refuses or ignores the attestation, or by the field office after it arrives. Where your KYC is Aadhaar-verified, an online claim bypasses employer attestation entirely, so most rejections now originate in the field office and are about the record rather than the employer's willingness. If the claim never left the employer's dashboard, the fix is at the employer, not at EPFO.

Open your passbook in the same sitting. The EPFO passbook portal shows contributions month by month against each member ID, and it is where a second problem usually becomes visible — a gap where an employer stopped remitting, a member ID you had forgotten, or an employer-share column that does not match the employee-share column. If you cannot log in, the passbook portal publishes a missed-call number, 9966044425, and an SMS route, EPFOHO UAN sent to 7738299899, that return the balance without a login.

Note what the member portal itself tells you before you file again. It lists UAN activation, Know Your UAN and Track Application Status as separate pre-login services, states that direct UAN allotment through the portal has been discontinued, and points members towards the UMANG app for Aadhaar-based face authentication. It also carries a standing notice that services are running in a phased manner following a database upgrade, which is worth reading before you conclude that a stalled claim is a rejection.

Do not re-file straight away. A duplicate claim carrying the identical defect will be rejected identically, and you will have spent the office's processing cycle to learn nothing. Fix the record first, confirm on the portal that the correction has actually been applied — not merely submitted — and only then file the new claim.

Most remarks fall into a small number of families, and each family has one correct fix. Identity mismatches are the largest: the name, date of birth, father's or spouse's name held by EPFO does not match Aadhaar. Tata AIA's summary of rejection causes lists differences in name, date of birth, father's name and gender as a leading trigger, and ClearTax describes the same category as discrepancies between the EPFO database and the documents submitted with the claim. These are record defects, and no amount of re-filing clears them.

The second family is bank and KYC failure. An incorrect account number or IFSC, an account that has been closed, a joint account, or a bank account not digitally approved by the employer will all stop a settlement, because EPFO credits only an account seeded and verified against the UAN. Tata AIA specifically names incorrect account numbers, IFSC codes and inactive accounts. So does an unlinked Aadhaar: without Aadhaar seeded and verified against the UAN, an online claim cannot be processed at all.

The third family is service and eligibility. Kustodian's account of EPS-linked rejections notes that Form 10C is valid only where total service is more than six months and less than ten years, that submitting it outside that band triggers an automatic rejection, and that beyond ten years a scheme certificate replaces a cash withdrawal. ClearTax adds claims where the ground of withdrawal falls outside the categories the scheme allows — most often an advance claimed for a purpose the member does not yet qualify for on service or balance.

The fourth family is the record of employment itself: a missing or wrong date of exit, a service period that disagrees with what the employer reported, contributions that stop mid-year in the passbook, or two member IDs that were never linked. Kustodian describes an absent or incorrect exit date as an error that freezes both EPF and EPS processing. This family is the one most likely to need the employer or the field office rather than a self-service correction.

A fifth, smaller family is procedural: an illegible cheque leaf or passbook image, a signature that does not match the record, an attestation that was never completed, or a temporary portal failure during submission. ClearTax lists improper attestation and technical errors during submission among its rejection causes. These are worth re-filing against, once, with a cleaner upload — they are the only family where re-filing without a record change is a sensible first move.

The table below maps the wordings you are most likely to see onto the fix each one needs. Treat it as a decoder rather than a quotation: field offices phrase remarks differently, and your own remark may combine two of these.

Identity corrections go through a joint declaration, and it is now an online workflow rather than a paper form carried to an office. Log in to the member portal and go to Manage, then Joint Declaration. Select the member ID the correction applies to — this matters, because a correction applied to one member ID does not propagate to a member ID under a different establishment. Enter the corrected value exactly as it appears on Aadhaar, character for character, and upload the supporting documents as PDFs.

EPFO classifies each requested change as minor or major, and the classification decides both how much proof you need and how senior an officer signs it off. ClearTax's account of the form states that a minor change needs at least two documentary proofs and a major change at least three, and that acceptable self-attested documents include Aadhaar, PAN, passport, driving licence, voter ID, birth certificate and school leaving certificate. Aadhaar is mandatory for a name or gender correction. Kustodian's guide describes minor as a spelling fix of up to about three letters or the expansion of initials, and major as a longer name change or a date of birth shift of more than three years.

The request does not go straight to EPFO. It lands on your employer's dashboard on the employer portal, where the authorised signatory has to verify and digitally approve it, and only then does it reach the regional office for the record to be amended. Moneylife's summary of the EPFO circular sets out the same three-tier sequence — member submission with documents, employer validation, EPFO processing — and lists eleven profile parameters that can be corrected this way, including name, gender, date of birth, father's name, relationship, marital status, dates of joining and leaving, reason for leaving, nationality and Aadhaar number.

Two limits in that circular catch people out. Most parameters can be changed only once, with marital status allowed twice, so a correction submitted carelessly can consume the single change you were entitled to. And where a member requests more than five changes, Moneylife's summary records that additional scrutiny is applied to guard against fraud — which in practice means the file stops being a routine approval and starts being examined. Submit one accurate declaration rather than a series of partial ones.

Timelines are the part where expectation and practice diverge. The circular as summarised by Moneylife sets seven business days for a minor update and fifteen for a major one. ClearTax puts the real-world figure at around twenty to twenty-five days, and Kustodian breaks it down as one to two weeks for the employer to confirm and a further two to six weeks at the field office, longer where the record is old. Plan on weeks, not days, and do not file the corrected claim until the portal shows the new value.

Fix the source document first if the source document is the problem. If your Aadhaar itself carries the wrong spelling or date, correcting EPFO to match a wrong Aadhaar leaves you with two matching wrong records and a bank account that still disagrees. Update Aadhaar, wait for the updated record, and then run the joint declaration against it. Where the documentary proof you need is a board certificate or a PAN card, the issued copies held in DigiLocker are accepted as authenticated documents and save a trip.

A joint declaration stalls the moment the employer stops responding, and the employer has no direct incentive to act on an ex-employee's correction. Start with a written request to the HR or payroll contact naming the exact change, the member ID, and the fact that the request is already sitting on their EPFO employer dashboard awaiting digital approval. Keep it in email rather than on a phone call — an unanswered written request is the evidence a grievance is built on later, and a phone call is not.

The date of exit is the one employer dependency you can now break yourself. Where the employer has not marked the date on which you left, the system continues to treat you as in service and blocks a final settlement. Members can mark their own date of exit through the member portal once the qualifying period after leaving has passed, which removes the most common single point of failure in the whole process. Mark the true last working day, because a date that conflicts with the employer's remittance record creates the service-period mismatch you were trying to avoid.

A missing contribution is a different and more serious problem than a mismatch. If the passbook shows months where your share was deducted from salary but nothing was remitted, that is not a record error to be corrected by declaration — it is a default in payment. Contributions reach EPFO through the electronic challan-cum-return the employer files on the employer portal, so a gap means the return was not filed or not paid. Raise it in writing with the employer, and in parallel with the field office, with the salary slips showing the deduction attached.

Where the establishment has closed, been struck off, or has no traceable signatory, the online workflow has nowhere to go. Kustodian's guide describes the fallback as a physical joint declaration submitted to the field office with alternative verification, longer timelines, and escalation through the grievance system where the office does not act. Gather what a closed employer's record would have proved — appointment and relieving letters, salary slips, Form 16, the establishment code from your passbook — before you approach the office, because the office will ask for exactly that.

Attestation by an alternative authority exists for the paper route. Where an employer cannot attest, the scheme's forms allow attestation by specified officers — a bank manager where the account is held, a gazetted officer, or a local body head among them. This route is slower and more discretionary than the online one, and offices vary in how readily they accept it, so treat it as a fallback for a genuinely defunct employer rather than a shortcut around an inconvenient one.

Do not let the employer dispute and the claim run as one file. If you are also owed salary or notice pay, keep that dispute in its own channel. Mixing a wage complaint into a PF grievance gives the office a reason to route the file somewhere else, and PF entitlement does not depend on the outcome of a wage claim.

Form 13 is the transfer of an old account into your current one, and it fails for reasons that have nothing to do with a withdrawal. The commonest is that the old service does not sit where you think it does: it is under a second UAN generated by a later employer who did not ask for your existing number, or under a member ID that was never linked to the UAN you use. Until those are joined, the old balance is invisible to the account you are transferring into, and the transfer request has nothing to act on.

Duplicate UANs have to be resolved before anything else works. The old UAN is deactivated and its member IDs are linked to the surviving one, after which the transfer can proceed. Establish first which UAN each period of service sits under by checking the passbook against each number you have ever been issued, and by using the Know Your UAN service on the member portal, which returns the UAN against your registered mobile and identity details.

Transfers also fail on the same identity mismatches that break withdrawals, but they fail in both directions. The name, date of birth and parentage have to reconcile across the previous employer's record, the present employer's record and Aadhaar. A joint declaration corrects one member ID at a time, so a mismatch present under both employers needs two declarations, and running only the first leaves the transfer failing for the same stated reason.

Attestation on a transfer sits with either the previous or the present employer, depending on where the record is complete, and a transfer sent to the wrong side stalls without being formally rejected. If the request has sat unattended for weeks, check on the portal which employer it was routed to and chase that one rather than the other. Where the previous establishment has closed, the transfer generally has to be handled by the field office holding that establishment's records.

The reason to persist with a transfer rather than give up and withdraw is continuity of service, and it is worth more than the balance. Continuous service determines whether a later withdrawal is taxable and whether you reach the pension qualification, and service counts as continuous only if the balance was transferred rather than taken out. Kustodian's account of EPS rejections makes the related point that split records across job changes are themselves a cause of pension-claim rejection, which a merge fixes and a withdrawal does not.

Where a transfer has been rejected and a final settlement is what you actually want, run them in the right order anyway. Transfer first, confirm the consolidated balance and service in the passbook, and claim afterwards. Claiming from two accounts separately produces two settlements, two service records, and a much harder argument later about how long you were continuously in service.

The bank account is the single most avoidable rejection. It must be a savings account in your own name, seeded against the UAN, digitally approved by the employer, and open. A joint account, an account closed when you moved cities, or an account whose name field carries an initial your Aadhaar spells out in full will all stop the credit. Tata AIA lists incorrect account numbers, IFSC codes and inactive accounts among its rejection causes, and adds joint and closed accounts to the same family.

Re-seeding a bank account is not instantaneous, because the employer has to approve the new KYC entry before it counts as verified. Add the account, ask the employer to approve it, and confirm on the portal that it shows as verified — not merely as pending — before you file. Upload a cheque leaf or passbook first page that shows the name, the account number and the IFSC in one legible image, because an unreadable upload is itself a stated ground for rejection.

PAN matters on a withdrawal that attracts tax. Withdrawal before five years of continuous service is taxable, and tax is deducted at source when the amount exceeds the threshold the Income Tax Department prescribes — at a materially higher rate where PAN is not available. In EPFO terms the practical effect is that a claim filed without PAN seeded, or with a PAN whose name does not match the EPFO record, is returned rather than settled. Seed PAN, reconcile the name across PAN, Aadhaar and EPFO, and file again.

A declaration that no tax should be deducted is filed alongside the claim where your total income for the year is below the taxable limit. It is a statement of fact about your income, not a switch that turns tax off, and filing one you are not entitled to is an incorrect declaration rather than a clever move. Where five years of continuous service have been completed — counting transferred service — the question does not arise, which is another argument for transferring rather than withdrawing between jobs.

Thresholds, rates and the forms themselves change, and the authority on them is the Income Tax Department rather than EPFO. The e-Filing portal is where the statutory forms are hosted and where TDS credit appears in your annual statement, and its helpdesk on 1800 103 0025 answers questions about a deduction you can see but do not understand. If tax was deducted on a settlement and you were below the taxable limit for the year, the remedy is a refund claimed in your return, not a grievance against EPFO.

Reconcile the settled amount when the money arrives. A settlement that is smaller than the passbook balance is usually tax deducted at source, occasionally an interest calculation that stops at the date the account became inoperative, and sometimes a partial settlement where one member ID was settled and another was not. Work out which before complaining, because the three have entirely different remedies.

Claims made after a member's death fail overwhelmingly on nomination. Where a valid nomination exists, the nominee claims in their own right and the process is administrative. Where there is none, or where the nomination names a person who has since died or was recorded before a marriage, the office has to establish who is entitled, and that turns a claim into an evidentiary exercise involving a succession or legal heir certificate. The member portal carries a death claim filing route with separate paths for the provident fund and for pension, which reflects that these are two different entitlements with different qualifying conditions.

Three benefits arise on death and they are claimed separately: the accumulated provident fund balance, the pension payable to a surviving family member, and the insurance amount under the deposit-linked insurance scheme. A rejection can attach to one and not the others, so read the remark against each claim rather than assuming the whole file has failed. A pension claim in particular depends on the pension record — Kustodian's account of EPS rejections notes that a missing pension contribution against a period of service blocks the claim regardless of what the provident fund balance shows.

Identity documents on a death claim have to reconcile in the same way as a living member's, with the added difficulty that the member cannot correct their own record. A mismatch between the name on the death certificate, the name in the EPFO record and the name on the claimant's Aadhaar is a standard rejection, and correcting it after death runs through the field office rather than through the member portal's self-service workflow. Assemble the death certificate, the claimant's Aadhaar and bank details, and proof of relationship before filing rather than after a rejection.

Where the claimant is a minor, the claim is made by a guardian and the office will want the guardianship position documented. Where there are competing claimants — a first family and a second, or siblings against a spouse — the office is not the forum to decide the dispute and will generally hold the amount until the entitlement is established. That is the point at which a succession or legal heir certificate stops being paperwork and becomes the thing the money is waiting on.

Pension claims by living members fail on service arithmetic more than anything else. Form 10C is the withdrawal of the pension component and Kustodian records that it works only where total service exceeds six months and falls short of ten years. Cross that boundary and the correct application is for a scheme certificate, which preserves the service and converts it into a monthly pension at the eligible age. Filing the wrong one of those two produces a rejection that reads as if you were ineligible for anything, which is not what it means.

E-nomination is the single preventive step worth taking today. Recording a nominee online while the member is alive converts every one of the problems in this section from an evidentiary exercise into an administrative one, and it costs a few minutes on the member portal. It is the only item in this guide that is better done before there is a problem than after.

Re-file when the defect was in your application or your record and you have fixed it — a corrected bank account, a joint declaration that has been applied, a date of exit now marked, a legible upload, the right form for your length of service. Confirm on the portal that the correction is showing before you file, then file cleanly and track it. In this situation a fresh claim is the remedy, and a grievance would only ask the office to do what a new claim does anyway.

Complain when the defect is not yours. A joint declaration sitting unactioned for months, an employer who will not approve anything, a remittance gap where the employer deducted and did not deposit, a claim rejected for a reason that is factually wrong, or repeated rejections on the same ground after the record has been corrected — none of these is cured by re-filing. Filing again in those circumstances resets your own clock without touching the cause.

What a grievance contains determines what it gets back. Give the UAN, the member ID the claim relates to, the claim reference number, the date of filing and the date of rejection, the exact remark quoted word for word, and the establishment code and name of the employer. Then state, in one or two sentences, what you have already done — the joint declaration submitted on a date, the bank account re-seeded, the emails sent to the employer — and what specific action you are asking for. Attach the screenshots and the correspondence.

Ask for one thing. A grievance that asks the office to settle a specific claim, or to approve a specific pending declaration, can be closed by doing that. A grievance that recites a history and asks for help is easy to close with a generic reply, and closure is what the office is measured on. Track the registration number the system returns, and read the closure remark carefully — a reply that answers a different question from the one you asked is worth reopening or escalating rather than accepting.

Two general-purpose levers sit behind the EPFO-specific route. CPGRAMS takes grievances against any central government body, issues its own registration number, and allows an appeal after closure where the outcome is unsatisfactory — the portal notes that grievances sent by email are not entertained, so use the portal itself. A request under the Right to Information, filed online through the central RTI portal, is the other: asking for the file notings and the reason recorded for rejecting a named claim produces a documented answer within the statutory period and has an appeal built into it.

Keep the whole file in one place from the first rejection: the remark, the claim reference numbers, the joint declaration acknowledgement, the employer correspondence, the passbook downloads, and the grievance registration numbers. Cases that resolve quickly are almost always cases where the member could produce that file on request. Cases that drift are usually cases where the record has to be reconstructed from memory each time it changes hands.