Which action should you take to implement a change from a semi-monthly payroll to a monthly payroll for all workers?

• A. Create a new monthly payroll definition and date the workers employment records associated with the semi-monthly payroll
• B. Create a new monthly payroll definition and transfer the workers from the semi-monthly payroll to the monthly payroll
• C. Update the Date Paid field on the semi-monthly payroll's time periods to reflect the new monthly payment dates
• D. Update the Start and End Dates on the semi-monthly payroll time periods to reflect the new monthly payroll period dates

Answer: (B)

In Oracle Payroll Cloud, the way to switch all workers from one payroll frequency to another is to create a new payroll definition that reflects the monthly processing and then transfer the workers from the semi-monthly payroll into that new monthly payroll. A payroll definition sets the calendar, periods, and rules for a payout run, so having a separate monthly definition ensures the monthly periods and associated processing logic are cleanly applied. Migrating workers via a transfer keeps the historical data intact on the old semi-monthly payroll while moving future processing to the new monthly calendar, which is the correct way to implement the change across everyone.

Updating dates or employment records on the existing semi-monthly payroll would not actually switch the processing to monthly; it would simply alter the current semi-monthly setup or the dates of its periods, leaving the workers tied to the old monthly rhythm. Creating a new monthly definition and adjusting the existing semi-monthly setup without transferring would also fail to reassign processing for all workers consistently. The transfer approach ensures a complete, auditable changeover to monthly for all workers.