Pensions Team do not get sufficiently notified of the reasons for "end dates" and an end date within payroll.
For example, a change of site within a MAT, may not be a change to contract, just working site. This results in an end date on EveryHR for the employee and can trigger the pensions team to report a new job with the pension fund. This might not be the correct scenarios as a change of site, may not be a change to contract (e.g. a continuous job at different working site) and may not specifically mean an end date with the job on the pension scheme. This could lead to employees getting multiple pension pots when they shouldn't and increase queries from the fund and employees. More information is needed to provide pensions team with accurate reasons for transfers. .
Progressing this will improve customer experience, reduce employee and employer queries, mitigate multiple pension pensions when not required, mitigate amalgamation requests
