Company declares that known user possesses UAN and registers the member with all the UAN:
The search that is initial he with regards to UAN in UAN repository. After the UAN is available then listed here scenarios arise.
1. DOB, AADHAAR and Name can be found within the operational system in a choice of UAN repository or user KYC table resistant to the supplied UAN and match using the title, DOB and AADHAAR being supplied by boss contrary to the same UAN
Case (a) The AADHAAR status up against the UAN just isn’t confirmed in UAN repository or Member KYC table from the supplied UAN:
Techniques response: Re verification of AADHAAR will occur because of the information for sale in UAN repository up against the UAN. If verified initiate UAN linking and initiate Auto Claim. If failed, start UAN linking, but, usually do not start Auto Transfer. System will display the title. Date of Birth. Gender and AADHAAR as for sale in Unified Portal and continue with enabling the company to fill the other joining details regarding the user.
Instance (b) The AADHAAR status up against the UAN is confirmed in UAN member or repository KYC table contrary to the supplied UAN.
Techniques response: Re verification of AADHAAR shall occur utilizing the information obtainable in UAN repository from the UAN. If verified initiate UAN linking and initiate Auto Claim. If failed, start UAN g that is linkin nonetheless, try not to start Auto Transfer. System will show the title, Date of Birth, Gender and A.ADHAAR as available in Unified Portal and allow proceed with ing the boss to fill the other joining details of this user.
2. Name and DOB matches nonetheless no AADHAAR exists contrary to the supplied UAN in UAN member or repository KYC table when you look at the system. (más…)