Dear Anonymous (Mr. Sudhakar),
As brought out by Mr. S K Bandyopadhyay, this is a major problem being faced by many employees. If you look into the history & databases of each of these things, you will understand the problem.
a) First came PAN. In the PAN Database, they DO NOT accept initials; only full expansions are permitted. However, there is an option for PAN holders to get their name PRINTED on the card as per their choice. SO many people print the initials on the card and end up thinking that their name in the PAN database is as printed on the card. REMEMBER, the PAN DATABASE has your full name.
b) Then came AADHAAR. Now, AADHAAR accepts initials, special characters, etc., in its DATABASE. At this point in time, there was no thought of linking PAN & AADHAAR.
c) Then came PAN-AADHAAR Linking. The same issues of name mismatch happened here too. But based on customer complaints and feedback, Ministry of Finance & Income Tax Dept made a "work-around" to enable people to still link AADHAAR & PAN despite differences in their underlying Databases. This was a proactive step due to pressure from customers, the deadline to link PAN & AADHAAR, and SIMPLE acceptance of the FACT that fundamental differences exist in the way PAN & AADHAAR databases are created.
d) Then came UAN-AADHAAR Linking (Primary KYC for UAN). New members are inevitably enrolled as per the AADHAAR card presented by the employee. But for secondary KYC (PAN), the differences in name crop up. AND unfortunately, EPFO has not yet woken up to this massive GAP in the desired condition (UAN-AADHAAR-PAN KYCs) and the practical difficulties being faced by its customers due to the aforementioned reasons.
SOLUTIONS: Going forward, please ensure that in your personal lives and in case of people whom you can advise, NAMES MUST BE WRITTEN IN FULL EVERYWHERE; from school leaving certificate (when my son's school started using initials in his name in report cards, etc., I fought with my son's school management to ensure that my son's full name is mentioned in every school record), to AADHAAR, to PAN, PASSPORT, VOTER ID, RATION CARD, DRIVING LICENSE, etc. This is your right, not some favor being done by government departments / private organizations.
MY OPINION / SOLUTIONS ON THE UAN_AADHAAR_PAN KYC:
a) Changing PAN to match AADHAAR. This is not going to happen if the AADHAAR database has initials because PAN does not accept initials.
b) Changing AADHAAR to match the school leaving certificate. This can be done, but unlikely to help in UAN_AADHAAR_PAN Linking because, more often than not, school leaving certificates always have INITIALs. So, even if you correct your name in AADHAAR as per the School Leaving Certificate, the problem of PAN name mismatch still persists (remember no initials in PAN database).
c) Changing NAME in AADHAAR / PAN has other collateral implications. Just imagine how many RE-KYCs you will have to do... AADHAAR_PAN, BANK_AADHAAR_PAN, INSURANCE_AADHAAR, Investments_AADHAAR_PAN, name correction in PASSPORT, etc., etc. So, in my PERSONAL CONSIDERED OPINION, EPFO insisting on exact name matching in UAN (which was generated based on AADHAAR) with PAN (not going to match in millions of cases) is just not correct.
WAY AHEAD I feel, EPFO should do a "workaround" (just like IT Dept did in the case of AADHAAR_PAN Linking). It could be one or any of the following:-
a) FIRST & FOREMOST, STOP outright rejecting the PAN KYC based on name mismatch.
b) INITIATE alternative verification if there is a NAME MISMATCH:-
(i) OTP-based validation on the AADHAAR (or UAN) linked mobile.
(ii) In most cases, people have successfully linked AADHAAR_PAN. EPFO has access to both. EPFO can accept the PAN KYC based on verification of AADHAAR_PAN linking status.
(iii) Give the employer the feature to approve or reject the PAN KYC even if there is a name mismatch in UAN_PAN. Once the employer approves it, then EPFO can also approve it to complete the KYC requirements (just like the "BASIC DATA Correction" is being implemented now).
I have put forward these ideas to EPFO on their email id: employerfeedback@epfindia.gov.in. The problem is known to EPFO (I guess), and as well-meaning employers, we must give viable solutions to EPFO so that they can implement one of the suggestions (possibly already under consideration) to overcome the UAN_AADHAAR_PAN KYC issues.
Thanks and regards,
Arun