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.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Payroll Relationship Groups in Payroll Processing
Summary:
Is it possible to make payroll relationship group and consolidation group a required field when triggering payroll flows?
Content (required):
At one of our clients, we have multiple legal employers that are all tied to one payroll definition. Some of the employers would like to manage payroll processing by themselves while others would be centrally managed.
We are exploring the feasibility of creating multiple payroll relationship/consolidation groups for each of the employers that would like to manage payroll processing independently. We would try to restrict the groups in the payroll flow based on roles . However, payroll relationship group and consolidation group are not required(*) fields in payroll flows.
Tagged:
0