Payroll Implementation

• Cutover starts 4-6 weeks prior to go-live date

depending on pay period frequency
Prescriptive delivery model in Payroll Implementations
15% 18% 13% 12% 10% 10%

Oracle COE
checkpoints

Min % of
Employees
validated
5%
employees
25%
employees
60%
employees
80%
employees
90%
employees
95%
employees

Playback 1 Playback 2 Playback 3 Parallel 1 Parallel 2 Parallel 3

% of total
employees
converted 10% 50% 100% 100% 100% 100%

Build 25% 50% 100 100% 100% 100%

Integrations %

Build 10% 50% 100 100% 100% 100%

Reports %

Custom
solution++ 10% 40% 90% 100% 100% 100%

Focus Gross Earnings + Deductions + Taxes

Area or 60% of +General Ledger + Reconciliation of employee paycheck in cloud HCM with legacy paycheck
or 80% of
configuration + Bank ++ Custom Solution Development includes: (those impacting Net Pay)
configuration
+ External systems FF, UDTs, Reports, Local Taxes, Payroll Flows, Integrations to GL and Projects etc.
Enhance Quality of Delivery on Payroll engagements

Payroll projects adapt to the delivery model with following variations:

 Large Engagements – Ex: Kroger, Ford, IHG, BHE, ConEd

 Follow 3 or 4 Payroll Parallel
 E2E / SIT - before Parallel1
 Followed by consecutive Parallel 2 and Parallel3
 Addition of new Legal entities impacting existing configuration/ timelines

 Regulated (Public Sector and Healthcare) - Ex: HCD, TWU, RCSD

 Follow only 2 Payroll Parallel

 Mid-size - Ex: LLUH, Guidewell

 Sequential execution of Playback, followed by Parallel 1 and Parallel 2

Recommendations:
 Generally, OCS drives Playbacks till Payroll Parallel1; instead customer should own and run
payrolls starting Playback 2
 Complete all Inbound Integrations, GL Solutions and Costing Testing by PB3
 Payroll Balances should be initialized during PB3 and for all Parallel runs
 Plan for an extra POD for Balance Initialization
3 Copyright © 2024, Oracle and/or its affiliates | Confidential: Internal
Enhance Quality of Delivery on Payroll engagements
Payroll expertise Process adherence Leverage tools and Change Management
accelerators  Customers should own
 Payroll Lead to be  Clearly defined Entry/  Utilize Autoconfig and run payroll starting
preferably an employee Exit criteria between comparison for elements PB2
and should provide POV phases  Customer Business
 Leverage Payrec tool
to customer, manage CSPs team should own
 Client team should be during Parallel cycles
 Test scenarios to capture aware of all the Parallel testing
 Utilize Payrec dashboard
dependencies on other configurations  Customer team
modules and pillars for reconciliation –
 Obtain timely approvals Costing, State Tax reports availability for daily
 All the business scenarios of FDDs, Config. vs Summary reports calls during Playback
to be covered in FUT Decisions, Elements, when Employees working and Parallel testing
 Test all the Elements, Custom solutions, in two different states cycles
Costing setup, Costing Balance Mapping and  Provide appropriate  Bandwidth of customer
Processes Balance Initialization parameters like Tolerance team to be planned
 Payroll Run Book to be  Sign off on Conversion early on
 Deployment options and
ready before PB3 start extracts & Post pre-requisites of these  Major changes after
 Customer to have Payroll conversion reports tools to be discussed PB3 should be
and technical SMEs to validation during pre-sales cycle considered post go-live
support development  All development done  Vendor change should
done by customers/ by customer/ vendor to align with project
vendors be tested before PB3 timelines

4 Copyright © 2024, Oracle and/or its affiliates | Confidential: Internal