Top 5 Reasons Your EPF Form 31 Claim Was Rejected (And How to Fix It)

Few things are more frustrating than applying for an emergency provident fund advance only to see your Form 31 claim status update to "Rejected." With the Employees' Provident Fund Organization (EPFO) shifting to automated, IT-driven processing in 2026, the margin for administrative error is practically zero.

The vast majority of Form 31 rejections are not because you are ineligible for the money, but because of a mismatch in your digital KYC profile or service history.

Here is a complete troubleshooting guide to the top 5 reasons your EPF Form 31 claim was rejected, and the exact steps you need to take to fix them before reapplying.

1. Bank IFSC Mismatch (The Bank Merger Problem)

The Issue: Over the last few years, several major Indian public sector banks underwent massive mergers (e.g., Syndicate Bank merged into Canara Bank, Allahabad Bank into Indian Bank). As a result, the old IFSC codes were permanently disabled by the RBI.

If your EPF account is still linked to your old branch's IFSC code, the EPFO portal will automatically reject your claim because the NEFT/RTGS transfer will bounce.

How to Fix It:

1. Log into the EPFO Unified Member Portal.
2. Navigate to the Manage tab and click KYC.
3. Select Bank and enter your updated account number and the new IFSC code provided by your merged bank.
4. Save the request. It will show as "Pending for Employer approval."
5. Contact your HR/Employer to approve the new bank KYC using their Digital Signature Certificate (DSC). Once verified, you can reapply for Form 31.

2. Aadhaar Name or Demographic Mismatch

The Issue: The 2026 auto-settlement system relies heavily on UIDAI e-KYC. If the name, date of birth, or gender on your Aadhaar card does not perfectly match the records in the EPFO database, the system cannot authenticate your identity and will reject the claim.

Even minor string mismatches (e.g., "Rahul K. Sharma" on Aadhaar vs. "Rahul Kumar Sharma" in EPFO) will trigger a rejection.

How to Fix It:

1. Log into the Member Portal and go to Manage > Basic Details.
2. Enter your details exactly as they appear on your current Aadhaar card.
3. Click Update. This generates an online Joint Declaration request.
4. Inform your employer to approve the modification request on their portal. Once the regional PF office approves the change, your demographics will sync, and you can reapply.

3. Name Missing on the Cancelled Cheque

The Issue: When you file a Form 31 claim, you must upload a scanned PDF of a cancelled cheque or bank passbook. A massive percentage of claims are rejected because the uploaded cheque is "non-personalized"—meaning your name is not printed on it by the bank.

The EPFO Dealing Assistant (or the automated optical character recognition system) must be able to visually verify that the name on the cheque matches the name on the PF account.

How to Fix It:

You have two options when you reapply:

• Option A: Upload a personalized cheque where your name is explicitly printed on the leaf by the bank.
• Option B: If you only have non-personalized cheques, do not use them. Instead, upload a clear scan of the front page of your bank passbook, ensuring the bank manager's stamp and signature are visible over your photograph.

4. Insufficient Service History (Non-Transfer of Previous PF)

The Issue: Many Form 31 advances (like Education, Marriage, and Housing) require a minimum number of years of continuous service (e.g., 5, 7, or 10 years). If you have switched jobs over your career but never transferred your old PF accounts to your current UAN, the system will only calculate the tenure of your current employment.

If you have worked for 8 years total, but only 2 years at your current company (without transferring the past 6), a marriage advance claim requiring 7 years of service will be rejected for "Insufficient Service."

How to Fix It:

1. Log into the portal and check your View > Service History.
2. If past employments are missing, go to Online Services > One Member - One EPF Account (Transfer Request).
3. Submit a Form 13 transfer request to pull the funds and service history from your previous Member IDs into your current, active Member ID.
4. Once the transfer is successfully credited, your cumulative service history will update, and you can reapply for the advance.

5. Illegible or Blurry Document Scans

The Issue: Under the 2026 paperless processing rules, the physical legibility of your uploaded PDF is critical. If you upload a blurry photo of a passbook taken in bad lighting, or if the IFSC code is unreadable due to low resolution, the claim will be manually rejected with the remark "Document Not Legible."

How to Fix It:

• Do not simply take a photo with your smartphone camera. Use a dedicated document scanning app to capture a high-contrast, flat image.
• Ensure the file is saved in PDF format.
• Verify the file size is within the portal's limits (usually between 100KB and 500KB) without losing readability.
• Open the PDF on your own computer before uploading it to ensure you can clearly read the account number, IFSC, and printed name.

Official Verification & Sources

• KYC Mandates: EPFO circulars regarding mandatory Aadhaar seeding and DSC-verified bank details for online claim settlement.
• Joint Declaration: EPFO Standard Operating Procedure (SOP) 2024/2026 for processing Joint Declarations to correct demographic mismatches.
• Service History Rules: Employees' Provident Funds Scheme, 1952 provisions regarding continuous service calculation for Para 68 advances.