Can Employers Discover a New Hire's Previous UAN Using PAN or Aadhar Details?

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 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.

Keep the UAN and previous employment ID number blank. Then fill in the details such as name, date of birth, Aadhar card number, PAN, and submit. It will display the data.

Thank you. I didn't know that.

KYC Section Issue with Aadhar

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?

UAN Issue with New Employee

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?

Aadhaar Data Matching Requirements for UAN Generation

Since last June, the department issued a notice requiring members to be added exactly as per Aadhaar data. The name, relation name, and date of birth must all match the Aadhaar data. I hope everyone has noticed this change.

The department asked employers to seed their Aadhaar data by December 15, 2016, and verify it digitally. In such cases, minor variations in name, date, etc., would be approved, but they are under scrutiny. Some entries may get rejected, requiring rectification with correct Aadhaar details.

Currently, everything must match the UAN data, including the name, relation name, and date of birth, as per the UAN portal and Aadhaar data port. Both must reconcile with each other; otherwise, it will be rejected.

Now, merely providing the year of birth is not sufficient to seed or generate a UAN. A letter-by-letter match is required; otherwise, it will be rejected.