Dear seniors,
I have a query regarding the new unified EPFO system. In the new EPFO system, can the present employer know the previous UAN number of a new employee using PAN or Aadhar details if the employee doesn't disclose the same in the form 11?
I understand that if the employee provides incorrect information and requests the employer to generate a new UAN as if they hadn't had a UAN earlier, the new employer will proceed. However, during the generation of the new UAN, when the PAN or Aadhar details of the employee are entered, an error message will appear stating "previous employment exists." My question is, can the employer know the member ID or UAN number of the previous employment using the PAN or Aadhar details, or do they have to ask the employee to provide that information?
Thank you.
From India, Kolkata
Acknowledge(0)
Amend(0)
14I have a query regarding the new unified EPFO system. In the new EPFO system, can the present employer know the previous UAN number of a new employee using PAN or Aadhar details if the employee doesn't disclose the same in the form 11?
I understand that if the employee provides incorrect information and requests the employer to generate a new UAN as if they hadn't had a UAN earlier, the new employer will proceed. However, during the generation of the new UAN, when the PAN or Aadhar details of the employee are entered, an error message will appear stating "previous employment exists." My question is, can the employer know the member ID or UAN number of the previous employment using the PAN or Aadhar details, or do they have to ask the employee to provide that information?
Thank you.
From India, Kolkata
Acknowledge(0)Amend(0)
keep blank the UAN and previous employment ID no then fill the details, name, DOB, aadhar pan and submit it will display the data
Acknowledge(0)Amend(0)
Acknowledge(0)Amend(0)
Thank you. I didn't know that.
For new member registration in the KYC section, Aadhar is not working properly. Aadhar updation as new KYC gives some kind of error. Is this happening with everyone or are we the only ones facing this problem?
Since you are a veteran in this field, I would like to know one more thing from you. One employee in Indore joined and confirmed that he didn't have a UAN in Form 11. Now, we have found out that he had a UAN earlier. Should we go ahead with Form 11 and generate a new UAN for him, or link it with his previous UAN that we have found in his payslips? Should we adhere to Form 11, or should we go by what we have found out on the UAN website and in his payslips?
From India, Kolkata
Acknowledge(0)Amend(0)
For new member registration in the KYC section, Aadhar is not working properly. Aadhar updation as new KYC gives some kind of error. Is this happening with everyone or are we the only ones facing this problem?
Since you are a veteran in this field, I would like to know one more thing from you. One employee in Indore joined and confirmed that he didn't have a UAN in Form 11. Now, we have found out that he had a UAN earlier. Should we go ahead with Form 11 and generate a new UAN for him, or link it with his previous UAN that we have found in his payslips? Should we adhere to Form 11, or should we go by what we have found out on the UAN website and in his payslips?
From India, Kolkata
Acknowledge(0)Amend(0)
To be specific to the query, since last June, the department flashed a notice to add members exactly as per Aadhaar data. Name, relation name, and date of birth all must match the Aadhaar data. I hope everyone has noticed the same.
The department had asked the employers to seed their Aadhaar data latest by December 15, 2016, and verify the same digitally. In that case, minor variations under name, date, etc., would be approved, and it is under scrutiny. Some of them would get rejected, and they would have to reload it with rectified Aadhaar details.
But at present, everything MUST match the UAN data, i.e., name, relation name, date of birth, as per the UAN portal and Aadhaar data port. Both must reconcile with each other; otherwise, it would be rejected.
Mere year of birth is not enough now to seed or generate UAN. It will now ask for a letter-by-letter match; otherwise, it will be rejected.
Acknowledge(0)Amend(0)
The department had asked the employers to seed their Aadhaar data latest by December 15, 2016, and verify the same digitally. In that case, minor variations under name, date, etc., would be approved, and it is under scrutiny. Some of them would get rejected, and they would have to reload it with rectified Aadhaar details.
But at present, everything MUST match the UAN data, i.e., name, relation name, date of birth, as per the UAN portal and Aadhaar data port. Both must reconcile with each other; otherwise, it would be rejected.
Mere year of birth is not enough now to seed or generate UAN. It will now ask for a letter-by-letter match; otherwise, it will be rejected.
Acknowledge(0)Amend(0)Join Our Community and get connected with the right people who can help. Our AI-powered platform provides real-time fact-checking, peer-reviewed insights, and a vast historical knowledge base to support your search.
ESIC HANDICAPED EMPLOYEE REGISTRATION-23 0311PhyHEmp.pdf
UAN Registration steps.zip