HCM upgrade methodology for parallel
For the last 20 years all Peoplesoft/Oracle HRMS upgrades at JMU have included a ‘parallel’ of payroll to make sure totals balance. This meant keying all data that affects the payroll into both the existing production database and an upgraded parallel database. This required much effort and double entry.
Since our last upgrade to 9.1, we have implemented electronic PAR forms with workflow routings and approvals. As we consider the upgrade to HCM 9.2, it is not practical or feasible to perform a parallel as we have in the past.
We are curious to know how other customers who use electronic PAR’s do payroll ‘parallel’ testing during an HCM upgrade. If you don’t parallel, what methodology do you use to verify payroll balancing prior to going live?