EPFO Employer Portal Not Working: Login, ECR and DSC Errors (2026)

The exact errors behind "epfo employer portal not working today"

• "No record found" at Establishment Sign In — the Establishment ID is wrong, not the portal. The ID is structured as a 3-character Regional/Sub-Regional Office code, a 7-digit establishment registration code, and a 3-character extension (three zeros, or 00A/00B/00C if none) — a wrong code, extension or selected EPFO office throws this.
• "Invalid username or password" — a mismatched Establishment ID/User ID/password combination on the employer login.
• "Failed to send OTP" / "Failed to send SMS to user" — the registered mobile number on file is wrong, inactive, or the SMS gateway is temporarily failing for that number.
• "Digital signature fetching local certificate error" / certificate not found — a client-side DSC token driver, Java setting or certificate-registration problem, covered in the DSC section below.
• "Select Certificate" button does nothing, or the certificate dropdown is empty — the signer utility (historically a Java applet, emSigner on newer flows) isn't running or isn't running as Administrator.
• "EPFO EmSigner not working" — the same local signing-service family used on GST and MCA portals, with the same fix pattern.
• "No route to host" / "unable to get connection" and "no designation mapped" — neither is documented in any official EPFO source found for this guide. The first reads as a raw network exception, commonly from a firewall, proxy or VPN blocking the portal's backend calls, or a transient server-side issue; the second is consistent with a sub-user account that hasn't been assigned a role, but this specific mechanism is unconfirmed. Treat both as unverified rather than assuming a fix.

Login and password: what actually fixes it

The employer portal at unifiedportal-emp.epfindia.gov.in uses "Establishment Sign In" with an Establishment ID, User ID/password and a captcha — this is a different login from the member/UAN sign-in most "epfo login not working" searches are actually about.

• Wrong or invalid Establishment ID: re-check the 3-character region code, the 7-digit establishment code and the 3-character extension, and confirm the correct EPFO office is selected in the search screen — EPFO's own establishment-search guidance says to verify these three things before anything else. If it still fails, escalate to the concerned Regional/Sub-Regional Office rather than retrying blindly.
• Forgotten password (registered mobile/email still valid): use Forgot Password on the employer login page, enter the Establishment ID/User ID plus the registered mobile number or email and captcha, and an OTP is sent to that contact to set a new password.
• Forgotten password with a dead registered mobile/email: the online Forgot Password route fails outright here — there is no OTP-less self-service reset. The only path is offline: a signed request letter from the Authorised Signatory, on company letterhead with the company seal, submitted to the jurisdictional EPFO Regional/Sub-Regional Office.
• Changing the authorised signatory's registered mobile number: this is the same offline route — a signed, sealed letter to the Regional/Sub-Regional Office. There is no employer-portal self-service screen for this change.

DSC and e-Sign: where most employer-portal failures actually live

DSC registration happens under Establishment >> DSC/e-Sign >> Digital Signature Registration, where the authorised signatory's details are entered against the certificate. Only Class 2 or Class 3 DSCs from a licensed Certifying Authority can be registered. Registering the DSC is not the same as being able to use it — every registered DSC or e-Sign needs a one-time approval from the concerned EPFO Regional Office before the authorised signatory can actually sign with it.

EPFO has said openly that DSC forces multiple client-side dependencies that regularly break — Java installation and version, browser settings, and a local signer utility. That is the documented reason it added Aadhaar-based e-Sign as an alternative: once active, the authorised signatory "signs" by entering their Aadhaar number and validating an OTP sent to the mobile linked to that Aadhaar — no token, applet or Java involved. An establishment whose DSC is already registered can activate e-Sign directly with Aadhaar + OTP inside the Unified Portal; one with no DSC on file has to register e-Sign, print a request letter, sign it, submit it to the local EPFO field office, and wait for field-office approval. DSC and e-Sign both cover establishment registration, KYC approval, PMRPY registration and, on the revamped system, ECR/return approval.

• "Digital signature fetching local certificate error" / certificate not found: reinstall the token vendor's latest driver (ProxKey, ePass, Gemalto, HYP2003, WatchData, Mtoken, Safenet), replug the token into a rear USB port, confirm the certificate shows in the Windows Certificate Store, and if it was already registered, try de-registering and re-registering it against the correct PAN.
• "Select Certificate" does nothing / empty dropdown: launch the signer utility or emSigner as Administrator and confirm its tray icon is active before clicking Select Certificate on the EPFO page; reinstall the token driver if the list stays empty.
• "EPFO EmSigner not working": install or reinstall emSigner, run it as Administrator, and confirm the tray icon is active before attempting to sign — the same fix pattern as emSigner failures on GST or MCA.
• DSC has historically relied on a local Java-based signer, working most reliably on Internet Explorer 11 (or Edge in IE mode) with 32-bit Java, with the EPFO portal URL added to the Java exception site list — Chrome and Firefox need workarounds such as an IE Tab extension. Where that class of setup is unavoidable, match it exactly rather than guessing at a modern-browser fix.
• "No registered active DSC details found" / unexpected error while signing: this usually means the DSC completed registration but not the one-time Regional Office approval, so the portal doesn't yet treat it as active. Check DSC/e-Sign status on the employer portal for "approved" vs "pending approval" — re-registering the same certificate will not fix a pending approval; only the Regional Office can clear it.
• DSC signing over a remote-desktop session (RDP/AnyDesk/TeamViewer) is reported to fail because the signing utility often can't reliably see a USB token passed through a remote session — this specific EPFO behaviour is not strongly sourced, but the safer default is to sign on the local machine the token is physically plugged into.

Never share a DSC PIN, portal password or OTP with anyone, including a consultant helping you — the authorised signatory enters their own credentials.

ECR upload and rejection errors under the revamped system

EPFO states there is no change to the ECR text file's own format under the revamp — the plain-text file, using the '#~#' delimiter between fields (member/UAN, gross wages, EPF/EPS/EDLI wages, contributions, NCP days and so on), is unchanged. What changed is the portal workflow around it: filing and payment are no longer one pass. The employer submits the return and it has to be approved first; only then does the system allow generating a challan/TRRN and paying. The exact field-by-field order and total field count of the ECR file could not be independently re-confirmed here — EPFO's own file-structure PDF now 404s after the domain migration — so if a rejection looks like a pure formatting mismatch, regenerate the file from your payroll source rather than hand-editing an old template.

• "ECR upload rejected" on a field-count or delimiter error: a row has more or fewer fields than expected, a missing or extra '#~#' delimiter, stray spaces around a delimiter, or a trailing blank row. Regenerate the file from source data and confirm every row uses the exact delimiter with no surrounding spaces and no blank trailing row.
• "EPS wages exceed EPF wages" / EPS ineligible for this member: the revamped system's upfront validation blocks a return where a member's EPS wage line is higher than their EPF wage line, where EPS is claimed for someone who joined after 1 September 2014 above the wage ceiling, or where EPS continues past age 58 without a deferred-pension flag. Fix the wage figures and check date-of-joining/age against EPS eligibility before resubmitting.
• "UAN not found" / UAN mismatch: the UAN in the file doesn't match EPFO's record for that member, or it isn't Aadhaar-seeded/active. Verify the UAN against the member's EPFO profile, not just your payroll record, and confirm KYC/Aadhaar-seeding is complete before including them.
• "DOE not updated" / contribution after exit date: EPFO's system already has a date-of-exit on file for the member, but the return still carries contribution rows past that date. Reconcile your exit records against EPFO's member profile and remove or correct those rows before resubmitting.
• Challan generated but payment not completed / TRRN expired: a TRRN has a limited validity window in practice (commonly reported as up to the mid-month due date, though this could not be confirmed against a primary circular for the revamped system specifically). The established pattern is to cancel the lapsed challan and regenerate a fresh one from the already-approved return rather than trying to resurrect the old TRRN.
• Bank has debited the account but the TRRN status doesn't confirm payment: this is commonly reported, unconfirmed against a primary EPFO source for the revamped system specifically — the safer default is to keep the bank reference number and wait for reconciliation rather than immediately re-attempting payment, which risks a double debit, and to cancel a challan still shown as "in-process" (generated but unpaid) and regenerate rather than resubmit the same failed attempt.

The ECR and payment deadline — and what a delay actually costs

VISHWAS 2026 lets an employer settle disputed or pending section 14B damages demands for pre-14-June-2024 defaults at reduced terms, but it does not waive section 7Q interest — full interest is a precondition — and it excludes fraud, misappropriation or falsified-records cases. This is separate from the Employees' Enrolment Campaign 2026 (1 July–31 October 2026), which lets an employer voluntarily enrol previously unenrolled employees for a flat ₹100 damages per company with no back-interest and no section 14B charge on those employees — the two 2026 schemes cover different situations and should not be conflated.

Member-level problems the employer, not the employee, has to clear

• "KYC approval pending at employer": the employee has already uploaded or linked KYC documents (Aadhaar/PAN/bank), but the establishment's authorised signatory hasn't yet digitally approved them via DSC/e-Sign. Downstream actions — claims, transfers — stay blocked until this approval happens on the employer portal.
• "Pending at employer" on a transfer or claim status: the current or previous employer's authorised signatory hasn't yet reviewed and digitally approved the request. The bottleneck is the company's own HR/payroll workflow, not EPFO — check the employer portal's pending-approvals queue.
• "Pending at field office" is a different, employer-uncontrollable bottleneck: the employer stage is already cleared and the claim is sitting in EPFO's own internal processing (service-history validation, UAN checks, workload backlog). No employer-side action moves it faster.
• PF transfer (formally Form 13, Revised) is processed almost entirely online today: once the member's UAN is active and KYC verified, the employer attests/approves the transfer digitally via DSC or e-Sign on the Unified Portal rather than physically signing and stamping a paper form.
• Name/DOB/Aadhaar (or father's-name) mismatches between EPFO's member record and Aadhaar, or between two employers' records at a transfer, are typically resolved through a joint declaration signed by both the employee and the employer, not a unilateral correction by either side.
• These are employer-side approval actions only. The employee's own withdrawal application, claim tracking or member-portal password is a separate, member-side process — this guide does not cover it.

Looks like a portal bug but isn't

• A stale epfindia.gov.in bookmark or PDF link that now 404s reads like a broken portal, but it is usually the effect of the ongoing migration to the new epfo.gov.in domain — try the current domain directly before assuming an outage.
• A "Digital signature fetching local certificate error" almost always traces to the client machine — a missing token driver, an inactive signer utility, or an unregistered certificate — not to an EPFO server fault, even though the wording sounds like a portal problem.
• A DSC or e-Sign that was just registered but still won't sign is very often stuck waiting on the one-time Regional Office approval, not a broken registration — re-registering the same certificate repeatedly will not fix a pending approval.
• An ECR that gets "rejected" on submission is frequently a genuine system validation catching a real data problem (EPS-over-EPF wages, an already-exited member, an unseeded UAN) rather than a portal glitch — read the specific rejection reason before assuming the file itself is malformed.
• A transfer or claim sitting for weeks might be stuck at the employer's own unapproved queue, not with EPFO at all — check "pending at employer" vs "pending at field office" before escalating to EPFO for something your own HR team hasn't actioned yet.

How to escalate an employer-side EPFO problem

• EPFiGMS (epfigms.gov.in) is EPFO's own grievance portal and explicitly accepts complaints from employers, not just members or pensioners — lodge here first and keep the grievance number.
• If EPFiGMS closes a grievance as "Disposed" without real resolution, escalate directly to the jurisdictional EPFO Regional/Sub-Regional Provident Fund Commissioner's office. This is also the only route for offline actions such as a password reset with a dead registered mobile, or changing the authorised signatory's registered mobile number — there is no portal self-service screen for either.
• If that stalls, file on CPGRAMS (pgportal.gov.in), citing every prior EPFiGMS grievance number as evidence of the earlier attempts.
• Quote the exact error string, the Establishment ID, and any TRRN/SRN reference in every escalation — a specific message routes faster than "the portal is not working."

Primary sources

The dates and fees on this page are read off the statute and the statutes and official portals cited, not copied from other guides. You can check every one of them:

• EPFO — new official domain (epfo.gov.in), "New Version" vs epfindia.gov.in "Old Version"
• EPFO — Revamped ECR overview page
• EPFO — DSC/e-Sign employer registration press note (06 May 2020)
• EPFiGMS grievance portal (employer grievances confirmed)
• PIB — ECR filing date extended to 22 October 2025
• SCC Online — EPFO VISHWAS 2026 damages settlement scheme