SAP S/4HANA: 5 Lessons Learned During the Implementation Phase


By: Ysabel Rojas, Business Services & Outsourcing Manager

 

I have had the opportunity to observe how decisions made during the early stages of SAP S/4HANA implementation projects can significantly influence the successful outcome of a project.

Beyond technology, many of the issues that lead to delays, reprocessing, or limitations in the use of information are often related to processes, organizational structures, the definition of responsibilities, and team readiness.

Every organization has its own unique circumstances, and there is no one-size-fits-all formula for implementing SAP S/4HANA. However, there are several lessons that I believe are worth sharing from a finance and management perspective, particularly for those involved in defining the functional aspects of the solution.

The following reflections are not intended to be absolute rules, but rather considerations that I have identified and believe are important to evaluate before starting a project of this nature.
 

1. Review, document, and share processes before configuring the system

SAP S/4HANA should not be used to automate processes that have never been reviewed, documented, or standardized. During functional workshops, it is common to find procedures known only to certain individuals, policies scattered across emails or individual documents, and no official version of the processes. Before beginning system configuration, the organization should have clearly defined processes, procedures, and policies available on a digital platform accessible to all employees involved.

Technology can automate processes, but the organization must first ensure that those processes are clearly defined and shared.
 

2. Design financial reporting and controls with business management in mind, not just accounting

One of the most critical decisions during an implementation process is defining the financial reporting and control model. Implementing SAP S/4HANA for a services company is not the same as implementing it for a commercial or industrial company with inventory. Each business model requires different structures for analyzing profitability, productivity, costs, and performance.

The most important question is not, “How are we going to account for this?” The more important question is, “What information will management need to make decisions in the coming years?
 

3. Properly integrate Finance, Controlling, and Logistics from the functional design stage

One particularly important lesson is the need to integrate Finance (FI) and Controlling (CO) decisions from the outset.

For example, an expense account may be correctly created within the chart of accounts, and a purchase may be recorded without any issues. However, if the cost center structure was not designed in coordination with the Procurement and Controlling processes, the financial information loses analytical value.
 

4. Consider local regulatory requirements and take advantage of automation opportunities

Requirements related to electronic invoicing, electronic books and records, “detraccion”, “retention” and “perception” regimes, and SUNAT requests should be incorporated into the functional design from the outset.

Likewise, many organizations continue to manually enter large volumes of purchase and sales vouchers, even though the information contained in structured XML files can be used for automated data entry.
 

5. Assign one team to day-to-day operations and another to manage the project

A functional implementation requires training, validation, testing, data migration, and continuous decision-making. It is essential to plan for two workstreams: one team focused on ensuring business continuity and another dedicated to project management, staff training, and functional validation. The project schedule should also be continuously monitored, with activities, responsibilities, risks, and dependencies actively managed.
 

Final Thoughts

An ERP implementation should be aimed at improving how the business is managed, how its operations are controlled, and how decisions are made. Therefore, before discussing system configuration, interfaces, or developments, it is worth asking one fundamental question:

Are we implementing SAP S/4HANA simply to replace our current system, or to transform the way we manage our organization?

 

Contact Us