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.

Solution needed for backdated pension contributions

Summary:


Content (required):

We have various pension elements in place for employees who pay additional contributions e.g. Added Pension, Effective Pension Age (all set up as per UK Pensions with the provider MyCSP). None of the elements were set up as retro enabled and unfortunately we have now been informed of increases to contribution rates dating back to April. These elements are also not user enter-able so we can't manually calculate the backdated contributions and enter it directly on the element entry .

I'm looking for advice on the best course of action to take here, if the backdated contributions won't be picked up by retro and can't be entered directly on the element. I'm hoping to avoid creating brand new versions of these elements from scratch. There aren't a large number of employees affected so a manual solution would be fine, but we're not sure how best to go about this, if we can't use the actual pension elements themselves.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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