Techniques response: Allocate UAN if AADHAAR gets confirmed.

Techniques response: Allocate UAN if AADHAAR gets confirmed.

Techniques response: Allocate UAN if AADHAAR gets confirmed.

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.

Techniques response: Verify AADHAAR given by user contrary to the given information obtainable in system, If verification outcomes in success initiate UAN connecting. nonetheless try not to start Auto Claim, seed the AADHAAR up against the UAN in UAN repository. If verification fails, however initiate UAN Linking don’t seed AADHAAR being given by boss and don’t start Auto Claim. System will show the true name, Date of Birth , Gender and AADHAAR as obtainable in Unified Portal and continue with enabling the company to fill the other joining details regarding the member.

3. If any among DOB, title or AADHAAR doesn’t match because of the one present from the supplied UAN in UAN repository or user KYC table within the system.

Techniques response: System will show the title, Date of Birth, Gender and AADHAAR as available in Unified Portal along side a suitable mistake message, stating that Name/DOB/AADHAAR will not bodybuilder dating apps match with information obtainable in system, and it’ll perhaps perhaps not enable proceeding.

Note: For UAN connecting System should check always for no less than UAN, Name and DOB match with all the information obtainable in system, but also for car claim besides the above it will look for AADHAAR match offered the AADHAAR verification status contrary to the current UAN is confirmed.

1. Eligibility requirements for Auto-Transfer Request (checked in the period of UAN linking):

1.1. The member with the UAN, system checks the AADHAAR is present against the provided UAN in UAN repository or Member KYC and its status is verified in re verification in point no. 1 of Linking Process, where employer declares that member has a VAN and registers.

1.2. All employment that is previous of connected UAN have actually Date of Joining available.

1.3. Present and/or past establishment are un-exempted.

a. If above requirements just isn’t pleased during connecting:

The situations is likely to be invalid for auto-transfer claim and exhibited in Employer Interface for information.

b. If above criteria is pleased:

Auto-Transfer Request is created for Linked M1Ds against UAN and you will be considered qualified to receive initiating Auto-Transfer Claim. A SMS and e-mail should be delivered to the user on his/her UAN registered Mobile Number and Email-Id on next time of connecting.

Notification for Initiated Auto-Transfer Request:

A automobile transfer claim for moving your EPF accumulations from to was considered against UAN >. If this transfer will not are part of you, it could be stopped claim within 10 times of date of connecting( )by login to or speak to your company /concerned EPFO industry workplace.

Content of Email:

Subject:-AUTO TRANSFER CLAIM

2. Eligibility requirements for Auto-Transfer Claim:

The machine will always check qualified Auto-Transfer demands after 10days from date of UAN linking for the conditions that are followingthrough day-to-day scheduler operating at 10 P.M.)

Conditions (examined only one time)

2.1. Previous DOJ (EPF) & DOE (EPF) is not as much as or corresponding to present Date.

2.2. Previous DOJ (EPF) is more than or corresponding to 01-JAN-1952.

2.3. Previous DOJ (EPF) is higher than DOB.

2.4. Previous DOJ (EPF) is lower than or corresponding to DOE that is previous(.

2.5. Previous DOE (EPF) is significantly less than or add up to Present DOJ (EPF).

a. If above conditions aren’t pleased:

The Auto-Transfer Request will undoubtedly be considered displayed and invalid in company Interface for information.

b. If above criteria is pleased:

The machine will look for the further conditions as below:

Conditions (examined daily upto 60days from the linking date)

2.6. UAN is triggered.

2.7. ECR is reconciled from Present Establishment.

2.8. Date of exit for past work can be obtained.

2.9. Explanation of exit for past work can be acquired.

a. If the conditions that are above maybe maybe perhaps not pleased for 60days:

Then Auto-Transfer Request is supposed to be considered expired and displayed in company Interface for information.

b. If above criteria is satisfied:

The machine checks for the following conditions:

Conditions (examined as soon as after all of the conditions that are above pleased)

2.10. Present Member Id is checked in IN FO PDB.

2.11. Claim is certainly not in procedure for the Member that is previous id Unified Portal.

2.12. Claim just isn’t in procedure for the Member that is previous id OUT FO PDB.

a. If the above conditions are not pleased for 60 times:

Then Auto-Transfer Request would be considered invalid and shown in company Interface for information.

b. If above criteria is pleased:

The machine shall create an Auto-Transfer Claim in Unified Portal. It’s going to be pressed towards the OUT that is respective FO through day-to-day scheduler running at 1 A.M.

3. Stopping the Automobile Claim:

After generation of Auto-Transfer Request, user can stop initiation of Auto-Transfer Claim within 10 times through the date of connecting by after means:

3.2. Contact his/her present boss

3.3. Contact concerned current EPFO industry workplace.

Notification for Stopping Initiation of Auto-Transfer Claim:

The automobile transfer demand claim against UAN > happens to be stopped because of the

Share this post

Leave a Reply

Your email address will not be published. Required fields are marked *