I have a situation where one of our payrolls is being outsourced and will no longer be run on Oracle. My question is, how do we close off the payroll so that it can no longer be used or do we just leave it in limbo. The third party is using the same tax reference so we won't be terminating records.
If I recall correctly you could end date the payroll calendar so that it can't run processes in pay periods beyond that date. The concern in my mind would be if you needed to do any retropay stuff beyond that last normal pay period? How will they handle that?
Fortunately we don't run retropay on this particular payroll.You can't actually end date the payroll calendar as it is generated from the number of years entered on the Payroll Description. My first thought was to end date the payroll itself but you can't do that either when it is assigned to records. I think its going to be a case of leaving it in limbo, as is.
Can you not change the number of years for which the payroll calendar is generated, eg reduce it from 30 years to 15?
I think also you should be able to set the status of individual pay periods to 'closed', or you may even be able to delete (purge) those future calendar entries if you go to the payroll calendar periods screen?
As a minimum protection, end date the payment method usages for the payroll so at least no one gets 'accidentally' paid from it.
Thanks CT. You can only increase the number of years once the calendar has been generated. Your idea of setting the pay periods to 'closed' sounds a good option. Thinks I'll explore that one and see where it leads.