Expert PF ESI Consultant in Ahmedabad

Accurate PF ESIC Consultant in Ahmedabad

Top PF ESIC Consultant Solution in Ahmedabad India. There are instances, where the Aadhar data (name, day of birth, gender) inequality with the EPFO data source, therefore Aadhaar number could not be seeded till the employee gets his details corrected either with Aadhar or with EPFO data source. There are instances where Aadhar information needs to be updated, and the worker is called for to visit the nearby Aadhar facility, however as a result of Lockdown restrictions, there are few Aadhar exec(s) being in banks and in many cases, the Aadhar facilities are not operating as most of the locations are under lockdown limitations. The UANs that were earlier seeded with Aadhar numbers were consequently modified by the worker without notifying his employer and captured the employer on the wrong foot. In such situations the company is caught unaware of the information mismatch and the ECR is turned down by the EPFO with the reason "Error Aadhaar not validated versus UAN". The EPFO Dashboard under the 'Missing out on Information' tab does not have capability for the employers to determine cases where the employee has after seeding of Aadhar number with UAN has got their Aadhar details modified. 

Best PF ESIC Consultant Solution in Ahmedabad India. The EPFO must develop capability to identify situations where Aadhaar is not validated versus UAN. Subsequently, the company is blind-sided while uploading the ECR that blinks the above mistake message. In cases, where the worker has changed his Aadhar data, he has to visit the PF Office for accomplishing the corrections in EPFO Data source w.r.t. his name, day of birth, gender, and so on and the procedure of name correction and day of birth improvement is troublesome and the EPFO needs for at the very least 3 papers from the employee to support his claim. In many cases, it is discovered that in the lack of a 3rd record, the staff member's information is not remedied by the EPFO. There are extra strange instances of information inequality where the online ask for correction of name/DOB might not be submitted with EPFO, as it would at least require a valid mobile number connected to UAN or Aadhar number seeded KYC with UAN. In the absence of both, the online demand cannot be forwarded to EPFO. We have seen situations where the worker changed his mobile number (that was earlier related to UAN and Aadhar) and thus no OTP could be obtained and no adjustments could be filed online.