You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

TUPE Transfer in (UK specific)

edited Dec 7, 2020 10:19AM in Payroll and Global Payroll Interface (GPI) 9 comments

Summary

How to handle historic data requirements when there is a TUPE transfer into the company

Content

Scenario - a few thousand people are TUPE transferring into the company. For statutory purposes they are treated as a new employee and reported to HMRC as a new hire on the TUPE transfer date.

But TUPE requires that you handle payments effectively as if the employment was continuous from their previous employer. For example, for SSP/SMP/SPP etc you need NIable pay from before the transfer date in order to determine whether they have sufficient average earnings. Sickness history is needed for company sick pay calculations. Payroll period balances for the last 12 months may be needed for anything from bonus calculations to average holiday pay schemes. But HCM doesn't support payroll balances or absence entries before the hire date.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!