What Are the Key Considerations Behind the Use of the Employee Central Payroll Global Template?

  • by Stephane Routhier, Solution Architect, EPI-USE America
  • November 6, 2017
Review these considerations for using a global template for implementing Employee Central Payroll. Various decisions may positively or negatively affect your payroll implementation.
Learning Objectives

Reading this article, you will learn:

  • Pre-work activities that should be completed before you design a global template
  • The criticality of considering all aspects inherent to legal entities and the Employee Central payroll offering
  • The importance of involving the right resources during the overall Employee Central Payroll project and even more during the design of your global template
Key Concept

Because the business environment is leading corporations to perform mergers and acquisitions, many global corporations are performing global Employee Central Payroll implementations. Adopting a global template can help an SAP SuccessFactors Employee Central Payroll implementation at various levels: costs, efficiency, and global operability. Global entities have multiple local entities with different business realities. A global temple must provide what they need to operate and to manage changes with their employees. They need to be consulted and feel included as part of an implementation process. Payroll is country specific and it is critical to reflect those requirements for correct use of a global template.

You work for a company with business units distributed among different locations. Your corporation plans to standardize the way you are conducting business processes across those various entities and wants to take advantage of the Employee Central Payroll implementation to harmonize processes across your organization.

This is the moment when the term global template starts to be mentioned in your preparation meetings. A global template implies the adoption of a common shared model, covering not only the system itself but also the business processes, design standards, common master data definitions, the supporting (and reusable) testing and training material, the governance processes, the roll-out methodology, and more. The template should be the complete package, not just the system.

Stephane Routhier

Stephane is contributing to EPI-USE America market development and acting as a Solution Architect in the North American HCM Practice focused on the selection, planning, design, and delivery of HR solutions across multiple industries. He has more than 20 years of SAP application experience and knowledge of enterprise HCM and payroll processes, trends, issues, and organization design. He acts as an SAP Expert in the payroll area. He has been involved with large full-scale SAP ERP HCM and Payroll implementations using the breadth and depth of SAP modules. Stephane has contributed to the HCM community as a speaker and writer.


See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.