PF Withdrawal & Transfer: UAN Guide for HR Teams

PF Withdrawal, Transfer, and UAN Consolidation: A Process Guide for HR Teams

Every time an employee resigns, retires, or joins your company from a previous employer, your HR and payroll team ends up in the middle of a question that has nothing to do with your own payroll cycle and everything to do with the Employees' Provident Fund Organisation (EPFO): "What happens to my PF now?" Understanding the PF withdrawal process, the PF transfer UAN workflow, and how to consolidate multiple Universal Account Numbers is one of those unglamorous but high-stakes parts of the HR job. Get it wrong, and an employee's claim sits rejected for weeks, their retirement savings sit scattered across three different UANs, or they call you every other day asking why their money hasn't arrived. Get it right, and it becomes one of the smoothest parts of your offboarding and onboarding experience.

This guide is written specifically for HR and payroll managers at Indian small and mid-sized businesses who are handling PF transfer and withdrawal requests as an ongoing, recurring part of the job — not a one-time registration task. We are not covering new PF/UAN registration for first-time joiners (see our separate guide on that), international workers' PF rules, EPS higher pension applications, or the wage ceiling debate — those are distinct topics we've covered elsewhere on the CozyHR blog. Here, the focus is squarely on what HR does after an employee already has a UAN: helping them transfer balances when they change jobs, helping them withdraw funds when they exit or need money for a life event, and helping them merge duplicate UANs into one clean account.

A quick but important note before we dive in: EPFO rules, portal workflows, form names, and processing timelines change from time to time, and the department periodically updates its online systems. Treat everything below as a structural, process-level guide to how things generally work — always verify the current step-by-step process, applicable forms, and timelines on the official EPFO website (www.epfindia.gov.in) or the EPFO member portal before advising employees or processing any claim.

---

Why Employees End Up With Multiple UANs

In theory, a Universal Account Number is meant to do exactly what its name promises — stay with an employee for life, across every employer they ever work for, linking together all their PF member IDs under one umbrella. In practice, a surprising number of employees in India end up with two, three, or even more UANs by the time they've had four or five jobs. As an HR professional, understanding why this happens is the first step to helping employees fix it.

Common reasons for duplicate UANs

• Employer didn't check for an existing UAN at onboarding. When a new joiner doesn't proactively share their previous UAN (or doesn't remember it), some employers' payroll or HR desks generate a fresh UAN instead of asking EPFO to link the new employment to the existing one. This is probably the single biggest cause of duplication.
• Employee provided incorrect or inconsistent KYC details. If the name, date of birth, or Aadhaar details furnished to the new employer don't closely match what's on file with the old UAN, the EPFO system may not automatically flag it as the same person, leading to a new UAN being issued.
• Gaps in employment or informal work stints. An employee who worked briefly at a small, unorganised establishment, or through a contractor/staffing agency, may have had a UAN generated for that engagement that they were never even told about, only to have another one created later at a "real" job.
• Manual data entry errors at the employer or EPFO field office level — a transposed Aadhaar digit, a misspelled surname, a different last name after marriage — can all cause the matching logic to fail.
• Employee simply forgot they had a UAN from a short internship, apprenticeship, or first job, and never carried the number forward.

Why this matters for HR

Multiple UANs aren't just an inconvenience — they create real downstream problems:

• The employee's retirement corpus is fragmented, and they may not even realise a portion of their money is sitting untouched (and untracked) in a dormant account.
• Interest continues to accrue on funds parked in an inoperative or dormant PF account, but the employee loses visibility of it.
• When it comes time to withdraw or transfer, EPFO will typically require the duplicate UAN issue to be resolved first, which slows down an otherwise routine claim.
• It complicates HR's own record-keeping and statutory reporting, since employer contributions may be getting reported against the wrong account for a given employee.

The fix — UAN consolidation, essentially merging the old member ID(s) into the active UAN — is something EPFO provides a defined online process for, and HR support at this stage can save an employee months of frustration. Most employees don't realise consolidation is even something they need to actively initiate; they assume UANs "merge automatically" when in fact this generally needs to be flagged and processed.

---

The Online PF Transfer Process When an Employee Joins a New Company

Let's walk through what generally happens, step by step, when an employee with an existing UAN joins your organisation and needs their previous PF balance transferred into their new (or newly linked) member ID under your establishment.

Step 1: Confirm whether the employee already has a UAN

This should be a standard part of your new-joiner documentation checklist, distinct from fresh registration. Ask directly: "Do you have a UAN from a previous employer?" Many employees don't know their UAN number offhand but will have it on an old payslip, Form 16, or PF passbook screenshot. If they genuinely don't know it, EPFO's member portal generally allows a UAN lookup using registered mobile number or Aadhaar/PAN details.

Step 2: Ensure the UAN is activated and KYC is seeded

An employee's UAN needs to be activated on the EPFO member portal (typically using the mobile number registered with the previous employer) before most self-service transfer requests can be filed online. Once activated, the employee should check that their KYC details are seeded and, where applicable, digitally verified against the UAN — this usually includes:

• Aadhaar
• PAN
• Bank account number and IFSC code

If any of these are missing, mismatched, or unverified, the transfer or withdrawal claim is very likely to get stuck later. This is the single most common point of friction, so it's worth having employees confirm their KYC status on the portal early rather than waiting until they try to file a claim.

Step 3: File the online transfer claim (Form 13 type request)

Once the new employment is reflected against the UAN (which typically happens once your organisation has processed the employee's first PF contribution/ECR filing under that UAN), the employee can generally log into the EPFO member portal and raise an online request to transfer their previous PF account balance into the current one. This is commonly referred to informally as a "Form 13" transfer request, though the exact online workflow and terminology should always be checked on the current EPFO portal.

Key things HR should tell employees at this stage:

• The transfer request needs to specify the previous member ID/UAN details accurately.
• The employee will typically choose whether the claim is to be attested/approved by the previous employer, the current (present) employer, or in some cases self-attested if certain digital KYC conditions are met — the portal will present the applicable options.
• Once submitted online, the request generates a tracking number that the employee (and often HR) can use to check status.

Step 4: Employer approval/attestation

This is where HR's role becomes active rather than advisory. Many transfer claims require approval from the employer's authorised signatory on the EPFO employer portal before the claim moves forward. Delays here are almost always internal — a request sitting in the employer login queue because nobody checked it — rather than an EPFO-side delay.

Practical recommendations for HR:

• Designate a specific person (or backup) responsible for logging into the employer portal at a fixed cadence (e.g., twice a week) to check for pending approvals.
• Don't wait for the employee to chase you — build a proactive check into your routine, especially during months with high joiner/leaver volume.
• Keep a simple log of pending approvals so nothing falls through the cracks when the responsible person is on leave.

Step 5: Track and confirm

Once approved on the employer side, the claim moves to EPFO's processing queue. HR should let employees know they can track status directly on the member portal, and should keep a note of typical turnaround expectations (these vary and should be checked against current EPFO service standards) so employees know when it's reasonable to follow up versus when to wait.

---

The Online PF Withdrawal Process: Eligibility Scenarios

Withdrawal is a different workflow from transfer, and it's important that HR clearly distinguishes the two for employees — a surprising number of employees say "I want to withdraw my PF" when what they actually need, and what is often in their long-term interest, is a transfer.

Broadly, withdrawal situations fall into a few categories. Below is a general overview — always confirm current eligibility conditions, waiting periods, and withdrawal percentage limits on the official EPFO website, since these are the kinds of parameters that get revised from time to time.

1. Withdrawal after resignation (unemployment-based withdrawal)

When an employee resigns and does not join another EPF-covered establishment, they generally become eligible to withdraw a portion of their PF balance after a defined waiting period of continuous unemployment, with eligibility for withdrawing the balance in full typically tied to a longer waiting period. HR should be careful here:

• Advise employees that withdrawing on resignation is a choice, not a requirement — transferring to a new employer (or simply leaving the account dormant while earning interest) is usually the better long-term outcome for retirement savings.
• Make sure the employee understands that if they take up new EPF-covered employment during the waiting period, the withdrawal-on-unemployment route is generally no longer the applicable option, and transfer becomes the right path instead.

2. Withdrawal on retirement

Employees who reach the retirement age defined under EPF rules are generally eligible for full withdrawal of both the PF corpus and the EPS (pension scheme) component, subject to the applicable EPS rules (which we've covered separately in our EPS higher pension article — this guide does not go into EPS mechanics).

3. Partial withdrawals / advances for specific life events

EPFO allows partial withdrawals (often called "advances") for a defined set of purposes, without full separation from employment, subject to conditions like minimum service period and caps on the amount depending on the purpose. In general terms, common categories include:

• Medical treatment — for the employee or certain dependents, generally without a minimum service requirement in genuine medical emergencies.
• Housing — purchase or construction of a house/flat, or repayment of a home loan, subject to years of service and other conditions.
• Education — for the employee's own further education or their children's education, subject to minimum service and number-of-times restrictions.
• Marriage — of the employee, their children, or siblings, subject to minimum service.
• Home renovation/repair — subject to conditions on how old the property/service tenure is.
• Certain other special-circumstance advances (e.g., during specific national emergencies or crises) that EPFO has permitted from time to time as one-off provisions.

Every one of these categories has specific eligibility conditions, documentation requirements, and caps on withdrawable amounts that change periodically — HR should never quote specific percentages, amounts, or service-year thresholds to employees from memory. Instead, point employees to the current rules on the EPFO portal, or maintain an internal reference note that your team updates whenever EPFO revises these parameters.

4. General online withdrawal filing steps

Regardless of category, the general shape of the online process tends to look like this:

1. Employee logs into the EPFO member portal with their activated, KYC-verified UAN.
2. Employee selects the relevant claim type (full settlement, pension withdrawal, or the specific advance category).
3. The system may pre-check certain eligibility conditions (like service length) automatically based on records already with EPFO.
4. Bank account details linked to the UAN are used for direct credit — this is why KYC and bank seeding accuracy matters so much.
5. Depending on the claim type and whether Aadhaar-based e-KYC/digital signature conditions are met, the claim may be processed without needing employer attestation, or it may route through the employer for approval.
6. The employee receives a claim reference number and can track status online.

---

Tax Treatment Basics of PF Withdrawal

This is a topic where HR frequently gets asked questions but should be cautious about giving anything beyond general, well-established principles — tax rules and TDS thresholds are revised periodically, and specific advice should always point employees to current Income Tax and EPFO guidance, or a qualified tax advisor for their individual situation.

At a conceptual level, here's what HR teams generally need to know so they can explain the shape of the rule to employees, without quoting exact rates:

• Continuous service threshold: EPF withdrawals are generally treated as tax-exempt when the employee has completed a specified minimum period of continuous service (aggregating service across employers where the account was transferred, not withdrawn, in between). Withdrawals before completing that threshold are generally more likely to attract tax.
• TDS on premature withdrawal: When PF is withdrawn before completing the applicable continuous service threshold and the amount exceeds a specified limit, EPFO/the trust generally deducts tax at source (TDS) at the time of payout, with the applicable rate depending on whether the employee's PAN is linked and verified in the system.
• PAN linkage matters: An employee without a properly linked and verified PAN on their UAN may face TDS at a materially higher rate than one with PAN properly on record — this is a very practical reason for HR to double-check PAN-UAN linkage during exit formalities.
• Transfers are not taxable events: Moving a balance from a previous employer's PF account to a new one via the transfer process (rather than withdrawing it) is generally not treated as a withdrawal for tax purposes, which is one more reason HR should default to encouraging transfer over withdrawal wherever the employee is moving to another EPF-covered job.
• Certain advances/withdrawal categories may have different treatment — again, verify current provisions rather than assuming a blanket rule applies to every withdrawal type.

HR's practical takeaway: don't try to be the employee's tax consultant. Your job is to (a) make sure the employee's continuous service record, PAN linkage, and KYC are accurate and complete in EPFO's system so that whatever tax treatment applies is applied correctly, and (b) point them to the current EPFO/Income Tax Department guidance or their own tax advisor for specifics on their situation. Consider adding a standard line to your exit communication template that flags this rather than letting employees assume withdrawal is always tax-free.

---

Common Reasons PF Transfer and Withdrawal Claims Get Rejected or Delayed

If you've handled even a handful of PF claims, you've probably already run into most of these. Building awareness of these failure points into your onboarding, exit, and ongoing HR processes is the single highest-leverage thing you can do to reduce employee frustration and repeat claims.

KYC mismatches

By far the most common cause of rejection or delay. This includes:

• Name spelling differs between Aadhaar, PAN, bank records, and the UAN/EPFO record (including differences after marriage or legal name change that weren't updated everywhere).
• Date of birth mismatch between Aadhaar and EPFO records.
• Aadhaar or PAN not seeded, or seeded but not digitally verified/approved by the employer on the portal.

HR fix: Build a KYC self-check step into onboarding and make it a habit to re-confirm before any exit is processed — don't wait for a claim to bounce back before checking.

Bank account verification issues

• Bank account number or IFSC entered incorrectly.
• Bank account not linked to the UAN at all, or linked but not verified.
• Bank account closed or changed since it was last updated (very common with employees who change banks/branches over a multi-year tenure).

HR fix: As part of exit formalities, explicitly ask the employee to confirm their current active bank account is correctly reflected and verified on the EPFO portal before filing any claim.

Employer approval delays

• Transfer or withdrawal claims that require employer attestation sit unprocessed simply because nobody on the HR/payroll side logged into the employer portal.
• This is especially common at SMBs where PF compliance is handled by one person, or outsourced to a consultant who isn't checking the portal on a fixed cadence.

HR fix: Set an internal SLA (see next section) and assign clear ownership, with a backup person, for checking and clearing pending employer-side approvals.

Incomplete or inconsistent service/UAN linkage

• Previous employment isn't properly reflected against the UAN because the previous employer never filed the exit date, or filed it incorrectly.
• Multiple unresolved UANs exist for the same employee, and EPFO's system flags the mismatch before allowing the claim to proceed.

HR fix: Encourage UAN consolidation proactively (see next section) rather than letting it surface as a blocker only when an employee tries to withdraw or transfer.

Claim form/category errors

• Employee selects the wrong claim type (e.g., applies for full settlement when they've actually taken up new employment, or applies for an advance category they don't meet the service-length criteria for).
• Missing or improperly uploaded supporting documents for advance categories (medical, housing, education, etc.).

HR fix: Provide simple, plain-language guidance (like the checklist later in this article) so employees pick the right claim type the first time.

Employer-side compliance gaps

• Employer has not filed timely Electronic Challan cum Return (ECR) for the relevant periods, so contribution records for the employee are incomplete.
• Establishment-level compliance issues (delayed payments, mismatched employee master data) can hold up individual employee claims even when the employee has done everything right.

HR fix: This one is squarely on the employer side — timely, accurate ECR filing every month is foundational to your employees ever having smooth PF experiences. This is exactly the kind of statutory hygiene an HRMS with automated PF processing can help enforce.

---

HR and Payroll's Role: Documentation, Approvals, and SLAs

Think of HR's PF-support responsibilities in three buckets: documentation readiness, internal SLAs, and employee communication.

Documentation HR should keep ready

For every employee, ideally maintained from the day they join rather than assembled reactively at exit:

• UAN and, if applicable, previous member ID(s)/employment history
• KYC status snapshot (Aadhaar, PAN, bank — seeded and verified, yes/no)
• Copies of ID proof and bank proof collected at onboarding
• Record of any prior UAN consolidation requests raised and their outcome
• Exit-related documents: relieving letter, full and final settlement details, last working day, reason for separation (relevant for withdrawal eligibility category)

Suggested internal SLAs

Every organisation's context differs, but rough internal benchmarks help keep this from becoming a source of employee frustration:

These are internal targets, not EPFO-mandated timelines — set them at a level your team can realistically hit, and adjust based on your employee headcount and PF claim volume.

Employee communication templates

Having a couple of ready-made message templates saves HR time and ensures employees get consistent, accurate information. A few examples you can adapt:

Template 1: New joiner PF transfer nudge

Hi [Name], welcome aboard! As part of getting your PF account set up correctly, please share your UAN from your previous employer (if any) and confirm your KYC — Aadhaar, PAN, and bank details — are updated on the EPFO member portal. This helps us initiate your PF transfer smoothly once your first contribution is processed. Let us know if you need help locating your UAN.

Template 2: Exit-time PF guidance

Hi [Name], as you complete your exit formalities, here's what you need to know about your PF: if you're joining another organisation covered under EPF, we recommend transferring your balance rather than withdrawing it, to preserve your continuous service record and avoid tax implications. If you plan to withdraw, please ensure your KYC and bank details are verified on the EPFO portal beforehand to avoid delays. We're happy to answer any questions — see the attached checklist for step-by-step guidance.

Template 3: KYC mismatch follow-up

Hi [Name], we noticed a mismatch in your KYC details on the EPFO portal ([specific field, e.g., date of birth]) that may delay your PF claim. Could you please update this on the portal, or share the correct details so we can help you get it corrected? Resolving this now will help avoid delays later.

Template 4: Claim status check-in

Hi [Name], following up on your PF [transfer/withdrawal] claim filed on [date]. We've approved it on our end as of [date]. You can track live status using your claim reference number on the EPFO member portal. Let us know if you see it flagged for any additional action.

---

How an HRMS Can Streamline UAN Tracking and Claim Visibility

Manually tracking UAN status, KYC completeness, and claim approvals across dozens or hundreds of employees in spreadsheets is exactly the kind of repetitive, error-prone work that an HRMS is built to absorb. Here's where the right platform makes a tangible difference for both HR and employees:

• Centralised UAN and KYC status tracking: Instead of hunting through emails and portal logins to check whether an employee's Aadhaar/PAN/bank are seeded and verified, an HRMS can maintain this as structured, searchable data against each employee's profile — flagging incomplete KYC before it becomes a claim-blocking problem.
• Proactive alerts for pending approvals: Rather than relying on someone remembering to log into the EPFO employer portal, an HRMS can help HR build reminders and internal task tracking around pending transfer/withdrawal approvals, reducing the "nobody checked" delay category entirely.
• Employee self-service visibility: Giving employees a single place (rather than repeated HR queries) to see their own PF/UAN status, download relevant statements, and understand where their claim stands reduces the back-and-forth load on HR significantly.
• Digital document storage: Keeping KYC proofs, exit documents, and claim-related paperwork attached to the employee's digital record means HR isn't scrambling to find a scanned Aadhaar copy from three years ago when a claim gets flagged.
• Consistent statutory data hygiene: Since PF claim delays are so often rooted in upstream data quality issues (inconsistent employee master data, delayed contribution filings), an HRMS that automates and validates statutory data as part of the regular payroll cycle reduces the volume of claim problems before they ever start.
• Audit trail: When an employee disputes what HR did or didn't do around their PF claim, having a timestamped record of KYC checks, communications sent, and approvals processed protects both the employee and the employer.

None of this replaces EPFO's own systems — the transfer, withdrawal, and consolidation processes themselves still happen on the official EPFO portal — but a well-set-up HRMS meaningfully reduces the operational drag on HR teams supporting employees through the process, and gives employees a much better self-service experience than chasing HR by email.

---

Step-by-Step Checklist for HR to Hand Employees (Exit or Transfer)

This is designed to be copy-pasted, adapted to your branding, and handed to employees at the relevant moment — new joining or exit.

For a new joiner with a previous PF account

1. Locate your UAN from a previous payslip, Form 16, or PF passbook.
2. Log into the EPFO member portal and activate your UAN if not already active.
3. Verify your KYC — Aadhaar, PAN, and current bank account details — are seeded and marked as digitally verified.
4. Share your UAN and previous employment details with HR for our records.
5. Once your first PF contribution is processed under this employment, log in and raise an online transfer request for your previous PF balance.
6. Choose the correct attestation option as guided by the portal (previous employer, current employer, or self-attestation if eligible).
7. Note your transfer request reference number and track status periodically.
8. Reach out to HR if the claim shows any rejection, discrepancy, or has been pending significantly longer than usual.

For an exiting employee

1. Decide: are you joining another EPF-covered employer, or not currently taking up new employment? - If joining another employer: plan to transfer your balance once your new UAN/employment is active — do not withdraw. - If not currently employed: understand the applicable waiting period and eligibility conditions for withdrawal, and whether partial vs. full withdrawal applies to your situation. 2. Confirm your KYC (Aadhaar, PAN, bank account) is fully seeded and verified on the EPFO portal before filing any claim. 3. Confirm your PAN is linked and verified to avoid a higher TDS rate, if your withdrawal may be subject to tax. 4. If you have more than one UAN, raise a consolidation request rather than trying to claim from a single one — check with HR if you're unsure whether you have multiple UANs. 5. File your claim (transfer or withdrawal) on the EPFO member portal, selecting the correct claim category. 6. Note your claim reference number for tracking. 7. Follow up with HR if employer attestation is required and you don't see movement within the expected internal timeline. 8. Keep your contact and bank details updated even after leaving, in case of any correspondence needed on your claim.

---

Common Withdrawal Scenarios at a Glance

Always verify current eligibility conditions, waiting periods, caps, and required documentation for each scenario on the official EPFO website before advising employees, as these parameters are revised periodically.

---

Frequently Asked Questions

1. Can an employee have two active UANs at the same time? An employee is only supposed to have one UAN for their entire working life. If duplicates exist due to employer error or KYC mismatches, they should be consolidated via the EPFO process rather than left as-is, since operating with duplicate UANs can cause claim rejections and fragmented retirement savings.

2. Should HR encourage employees to withdraw or transfer their PF when they resign? As a general practice, transferring is usually better for the employee if they're joining another EPF-covered employer — it preserves continuous service (relevant for tax treatment and pension eligibility) and keeps retirement savings consolidated. Withdrawal makes more sense in situations like genuine long-term unemployment, retirement, or specific approved advance categories. HR should present this as guidance, not as a decision made on the employee's behalf — the final choice is theirs.

3. What's the most common reason a PF claim gets rejected? KYC mismatches — name, date of birth, or bank details not matching cleanly across Aadhaar, PAN, and EPFO records — are generally the single biggest cause of rejected or delayed claims. Encouraging employees to verify their KYC status well before filing any claim is the most effective preventive step HR can take.

4. How long does a PF transfer or withdrawal claim typically take to process? Processing timelines can vary based on claim type, whether employer attestation is required, and EPFO's current processing volumes. HR should avoid quoting a fixed number of days to employees and instead point them to their claim's live status on the EPFO member portal, while setting reasonable internal expectations based on recent experience with the local EPFO office.

5. Does an employee need employer approval for every PF claim? Not always — certain claims can be processed with reduced or no employer attestation if the employee's UAN has met specific digital KYC/verification conditions set by EPFO. Where attestation is required, timely employer action is one of the most controllable factors in how fast a claim moves, which is why HR should treat portal approval checks as a routine task rather than an occasional one.

6. Is PF withdrawal always taxable? No — broadly, withdrawals after completing a defined period of continuous service are generally treated as tax-exempt, while premature withdrawals above a certain amount may attract TDS, with the rate affected by whether PAN is properly linked. Since tax rules are revised periodically, HR should direct employees to current EPFO/Income Tax guidance or a tax advisor rather than giving a blanket answer.

7. What should HR do if an employee doesn't remember their old UAN? The EPFO member portal generally allows employees to retrieve their UAN using their registered mobile number, Aadhaar, or PAN. HR can guide employees through this lookup as part of onboarding documentation, since starting the transfer process depends on having the correct previous UAN/member ID on record.

8. How can a small HR team with limited bandwidth manage PF claims for a growing headcount? Building simple, repeatable processes — a fixed cadence for checking employer-portal approvals, a KYC verification step at onboarding and exit, standard communication templates, and a checklist handed to every joiner and leaver — goes a long way even without additional headcount. An HRMS that centralises UAN/KYC status tracking and automates statutory data hygiene can further reduce the manual load as the team scales.

---

Conclusion

PF transfer, withdrawal, and UAN consolidation will never be the most exciting part of an HR professional's job, but done well, it's one of the most quietly appreciated. Employees remember whether their retirement money moved smoothly when they changed jobs, and whether HR actually helped when they needed a housing or medical advance versus leaving them to figure out the EPFO portal alone. The core of doing this well isn't complicated: keep KYC data clean from day one, check employer-portal approvals on a fixed schedule rather than reactively, guide employees toward the right choice between transfer and withdrawal, and always point them to the official EPFO website for the current rules rather than relying on what "used to be true."

Where this becomes hard to sustain manually is scale — once you're supporting dozens of joiners and leavers a month, spreadsheet-based UAN tracking and ad hoc portal checks start to crack. This is exactly the kind of statutory workflow CozyHR is built to support: automated tracking of employee PF/UAN and KYC status, structured document storage for compliance records, and employee self-service visibility into their own statutory data — so your team spends less time chasing portal logins and more time actually helping employees through moments that matter to them. If PF administration has been eating more of your team's week than it should, it's worth seeing what a purpose-built HRMS can take off your plate — explore CozyHR to see how automated statutory tracking and self-service can fit into your existing process.

This article is intended as general guidance for HR and payroll teams and does not constitute legal, tax, or financial advice. PF rules, forms, and portal processes are set and periodically updated by EPFO — always refer to the official EPFO website for current, authoritative information before advising employees or processing claims.