A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::open($save_path, $name) should either be compatible with SessionHandlerInterface::open(string $path, string $name): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 6

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::close() should either be compatible with SessionHandlerInterface::close(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 7

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::read($session_id) should either be compatible with SessionHandlerInterface::read(string $id): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 8

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::write($session_id, $session_data) should either be compatible with SessionHandlerInterface::write(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 9

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::destroy($session_id) should either be compatible with SessionHandlerInterface::destroy(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 10

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::gc($maxlifetime) should either be compatible with SessionHandlerInterface::gc(int $max_lifetime): int|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 11

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 284

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_set_cookie_params(): Session cookie parameters cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 291

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 306

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 316

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 317

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 318

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 319

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 377

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_set_save_handler(): Session save handler cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 110

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_start(): Session cannot be started after headers have already been sent

Filename: Session/Session.php

Line Number: 143

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

NRIPage | Articles | How to Merge Multiple UANs and Consolidate Your EPF Accounts Easily | Get Latest International News & Updates. Your Source for World Events and Updates - NRI Page
Edit

How to Merge Multiple UANs and Consolidate Your EPF Accounts Easily

How to Merge Multiple UANs and Consolidate Your EPF Accounts Easily

If you've switched jobs multiple times, there's a chance you may have more than one Universal Account Number (UAN) from the Employees’ Provident Fund Organisation (EPFO). Managing multiple UANs can be confusing and may result in losing track of your provident fund savings. To avoid this, it's important to consolidate all your previous UANs into a single active account.
 

Why Do Employees End Up with Multiple UANs?

There are a few common reasons why employees end up with multiple UANs:

  1. Failure to Provide Existing UAN: Employees sometimes do not inform their new employer about their previous UAN while joining a new organization. As a result, the employer registers a new UAN.
  2. Exit Date Not Updated: If the previous employer fails to update the date of exit in the EPFO system, the new employer may generate a fresh UAN unknowingly.
  3. Automatic UAN Generation by EPFO: If the system does not recognize the existing UAN details due to incorrect or missing information, a new UAN is assigned.


If you have multiple UANs, it's essential to merge them with your latest one to prevent financial mismanagement.How to Merge Multiple UANs and Consolidate Your EPF Accounts. The good news is that EPFO allows employees to merge their UANs so they can manage all their provident fund contributions under one account. Here’s how you can do it:
 

Method 1: Merging UANs Online via EPFO Portal

 
  1. Visit the EPFO Member Sewa Portal

    • Log in to the EPFO Member Portal using your UAN and password.
  2. Select ‘One Member - One EPF Account (Transfer Request)’

    • Under the ‘Online Services’ tab, click on ‘One Member - One EPF Account (Transfer Request)’.
  3. Verify Your Details

    • Your personal details and current EPF account will be displayed. Ensure all information is correct.
  4. Select Previous Employer for Attestation

    • Choose either your previous employer or current employer to attest the old UAN details. Opting for the current employer usually speeds up the process.
  5. Enter Old UAN or PF Account Number

    • Submit your old UAN or PF number and click ‘Get Details’ to fetch previous account records.
  6. Generate OTP and Submit Request

    • Once the details are verified, generate an OTP (One-Time Password) and submit the request.
  7. Approval and Processing

    • Your current employer needs to approve the request. After approval, EPFO will process the request and merge the previous EPF accounts with your current UAN.
  8. Track Merger Status

    • Keep checking the EPFO portal to monitor the status of your request.


Note: Ensure that your old EPF accounts are KYC-compliant (linked with Aadhaar, PAN, and bank details). If you have multiple accounts, you’ll need to merge them one by one.


Method 2: Request UAN Merging via Email

If you prefer an alternative method, you can also email EPFO to consolidate your UANs:

  1. Compose an email to uanepf@epfindia.gov.in.
  2. Provide the following details:
    • Your Full Name
    • Your Old UAN(s) and Latest UAN
    • Your Registered Mobile Number
    • Supporting Documents (Aadhaar, PAN, and Employment Details)
  3. EPFO Verification:
    • EPFO will verify the details and deactivate the extra UANs.
  4. Transfer EPF Balance:
    • Once the older UANs are deactivated, claim the EPF balance and transfer it to your active UAN account.


Important Points to Remember

  • Always provide your existing UAN to new employers to avoid duplication.
  • KYC compliance is mandatory for seamless transfers.
  • It’s better to opt for the current employer’s attestation to speed up the process.
  • Regularly check the EPFO portal to ensure all accounts are consolidated properly.


Final Takeaway

Managing multiple UANs can be cumbersome, but merging them ensures better tracking of your provident fund savings. If you have more than one UAN, follow the steps above to consolidate your EPF accounts and secure your retirement funds.For further assistance, you can contact EPFO Customer Service or visit the nearest EPFO office.

What is your response?

joyful Joyful 0%
cool Cool 0%
thrilled Thrilled 0%
upset Upset 0%
unhappy Unhappy 0%
AD
AD