EPFO has notified a system-driven auto-transfer mechanism for provident fund accumulations, under which a member's previous PF account balance will be automatically transferred to the new account opened by a subsequent employer, triggered upon the new employer's first Electronic Challan-cum-Return (ECR) filing against the employee's Aadhaar-seeded Universal Account Number.

This removes the requirement for employees to separately file Form 13 for transfer in the vast majority of cases, addressing a long-standing pain point where unclaimed or un-transferred PF balances accumulated across multiple UANs, particularly for employees who changed jobs without completing the transfer formality.

For the auto-transfer to trigger correctly, both the previous and current employer must have completed KYC seeding (Aadhaar, PAN, and bank account) against the UAN, and any mismatch in employee demographic details between the two employments will route the case to manual processing at the Regional Office instead of auto-transfer.

Employers are required to ensure that UAN allotment and KYC completion happen at the time of onboarding, ideally within the first wage month, since delayed KYC seeding is the most common reason for auto-transfer failure and resultant employee grievances routed through the EPFiGMS portal.

The circular also places an obligation on the exiting employer to correctly mark the 'date of exit' in the member's PF record at the time of separation — a field that is frequently left blank or delayed, and which blocks the auto-transfer trigger even where KYC is otherwise complete.

HR teams should build a standard offboarding checklist item to update the date of exit within the statutory window (currently expected within two months of the employee leaving service, though enforcement of this timeline has been inconsistent), and a corresponding onboarding checklist item to complete UAN KYC seeding within the first payroll cycle.

Given that auto-transfer reduces employee grievances and manual EPFO correspondence, employers should treat this as an opportunity to clean up legacy KYC data gaps across their active employee base, not only new joiners, to benefit from smoother future transfers.