GP UK - Auto Enrolment - Current Inter-company Transfer Logic Results In Non-compliance
(Doc ID 2565272.1)
Last updated on MARCH 09, 2020
Applies to:PeopleSoft Enterprise HCM Global Payroll UK - Version 9.2 and later
Information in this document applies to any platform.
There is a situation where using particular effective dates for inter-company (pay entity) transfers results in non-compliance of sending out postponement notice, based on the current logic the system uses to decide when to postpone or assess employees after undergoing inter-company transfer.
The system currently bases the ICT assessment/enrolment on the End Date of the latest pension scheme row. Depending on calendar dates, this means some employees will not get postponed until the following pay period after they have transferred, which then means that the postponement is not produced until the end of the second pay period after transfer, which results in missing the 6 week compliance deadline.
Where a company is using postponement, this should happen immediately after an employee is transferred, it should not wait until the next pay period to process the event. Similarly if a company is not using postponement, the employee should be assessed and enrolled immediately in the period where they are processed in the new pay entity, it should not wait until the next pay period - otherwise there will be a gap in contributions.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document