Struggling with EPF Transfer Rejections: How Can We Resolve This Communication Gap?

My husband changed his job from a company in Gurgaon to a company in Mumbai during the year 2016. Afterwards, he applied for a PF transfer (Form 13) manually. The application got rejected, stating, "Claim-Form-13 (Transfer Out)(Transfer (Unexempted to Unexempted in other region or to Exempted Establishments)) Claim id-xxx, Member id-xxx, has been rejected due to: DATE OF JOINING -xxx DIFFERS WITH OFFICE RECORD, CLARIFICATION REQUIRED (DOE xxx) OK."

He applied for transfer again in the year 2018, only to face another rejection with the reason stated as, "Claim-Form-13 (Transfer In/Same Office) (Transfer (Unexempted to Unexempted in other region or to Exempted Establishments)) Claim id-xxx, Member id-xxx has been rejected due to: SUBMIT WITH PRESENT RPFC FORWARDING LETTER/OK."

We did not understand the proper reason for rejection the second time. He raised a grievance and received an email instructing him to contact the Gurgaon office, along with some contact numbers. However, upon trying to reach out via those numbers, nobody answered the phone; they were either busy or unavailable. I also attempted to contact the toll-free helpline number [Phone Number Removed For Privacy-Reasons], but it was consistently busy. What should we do next? Please help me.

Understanding DOJ Differences in PF Transfers

DOJ (Date of Joining) differences usually occur when a member frequently changes jobs. Before the payout of contributions from one establishment, the member may join another establishment and apply immediately for a transfer. If the previous employer does not process your exit and you join another company, the transfer claim could be in jeopardy. In such a situation, the UAN with the previous establishment will show "not employed with your establishment," and you will not be able to make an exit. Therefore, a physical mode of the claim form must be submitted with the signature of the present employer, stating the reason for missing or mismatched data.