PwC and Oracle Alliance

Future proofing finance transformation with Oracle Cloud: Navigating a complex architecture with smart solutions

  • Publication
  • October 21, 2024

Oracle Fusion Cloud Enterprise Resource Planning (ERP) transformation and downstream applications

Global Chart of Accounts (“COA”) and ERP Implementation with the existing downstream applications helps in creating efficiencies in business insight processes and the ability to access data in a common language while also helping to reduce downstream impacts.

Industry-leading financial services clients often recognize Oracle Cloud ERP implementations as one of the crucial drivers of innovation and a strategic pathway to help attain competitive advantage. Fundamental to substantial ERP-led transformation initiatives is typically the establishment of a new enterprise structure including ledgers, business units, and a redesign of global chart of accounts (COA). The redesign of the COA can present many clients with a valuable opportunity to modernize outdated business processes and help enhance analytics capabilities.

Clients undergoing finance redesign initiatives encounter substantial changes not only in the applications being replaced but also in the upstream (feeders) and downstream applications (consumers). The downstream remediation scope is typically evaluated separately from the upstream changes which can lead to a potential time lag that may result in significant disruptions to business processes, potentially jeopardizing the success of the transformation initiative in delivering value within the expected timeframe.

Addressing downstream system retrofitting can be time-consuming and, in some instances, may not be entirely feasible. To help mitigate the risk to the transformation program and, depending on the downstream application landscape, a solution such as a reverse map or an approach from the new chart back to the legacy chart enables downstream applications to operate with fewer disruptions. Having remediation plan upfront, allows for a phased and more manageable implementation of the transformation, helping to reduce the likelihood of business process disruptions.

Considerations for Oracle Cloud ERP transformation and downstream

It is important to have a clear objective and strategy for addressing downstream applications needs during a Global ERP implementation. PwC can provide the industry-leading capabilities needed for Oracle Cloud ERP implementations in addition to helping determine banking industry specific requirements and provide the structured approach to address them. When preparing for a finance transformation, be sure to evaluate downstream applications on the following parameters:

  • Is master data source centralized in Oracle Data Relationship Management or from Oracle Cloud ERP?
  • Does the downstream consume the extract from Oracle Cloud ERP or are there multiple processing hops in between?
  • Is there a requirement for data at the journals, balances or average daily balances (ADB) level?
  • Is downstream supporting internal, external/regulatory reporting or both?
  • Is there additional processing logic built into the consumption, processing and reporting of data?
  • Are downstream applications cloud-based or on-prem?
  • In house or third party?
  • Does the change in COA constitute a data conversion in the downstream application?
  • What is the residual life of the application i.e. is there a plan to retire the application or are they part of strategic roadmap?
  • What is the current volume and processing times of data sent downstream?
  • How often is data sent downstream?
  • Is data full load or incremental?

Potential solutions for Oracle Cloud ERP transformation and downstream applications

As one of the leading Oracle Cloud ERP implementors, PwC has evaluated several solutions to help mitigate the impact on the downstream applications. Below are some key solution options to consider during global implementations, including Chart of Accounts (COA) redesign, aimed at minimizing the disruption to the downstream applications and processes. These strategies can be reinforced through a downstream impact analysis, evaluating the nature, extent, and feasibility of downstream remediations in alignment with implementation timelines.

1. Rule-based mapping engine

Establish a comprehensive reverse mapping for data, guided by account management governance through a consistent rule-based mapping approach. This ensures data integrity, data lineage and facilitates smooth transitions between new and legacy COAs.

2. Ledger construct

Utilize the scalable Oracle General Ledger construct to help establish an enterprise structure supported by a rule engine. This helps direct transactions with mappings for both new and legacy COAs, thereby reducing the complexity of reverse mapping rules.

3. Retrofitting downstream applications

Mandate downstream applications transition to the new COA, providing a consistent solution across various applications. This approach ensures uniformity, data lineage and reduces discrepancies within the financial data across the enterprise.

  • Rule-based mapping engine and ledger construct (Options 1 and 2) are both automated solutions that can leverage delivered - ERP functionality whereby new chart-to-old-chart ‘reverse mapped’ rules can be housed within the Oracle ecosystem leveraging PaaS application, Oracle Financial Services Analytical Applications (OFSAA) or Enterprise Data Management Cloud Service (EDMCS) and/or Accounting Hub Cloud Service (AHCS). These options provide a streamlined and efficient approach to managing the transition and the need for extensive manual interventions.

While retrofitting downstream applications to the new COA offers a consistent solution, maintain operational efficiency, it is a complex, costly, and time-intensive process. It often requires external vendor support and/or beyond project team to manage and implement the changes effectively within the downstream applications. Due to these challenges, Options 1 and 2 are often the preferred choices for banks and financial services clients. These options will be covered in greater detail in the subsequent sections.

Solution 1 Rule-based reverse mapping engine

Approach overview

This reverse mapping approach involves the establishment and ongoing maintenance of rule-based mappings until each downstream application successfully adopts the new Chart of Accounts (COA) for input, processing, and reporting. In this approach, clients can use any of the Oracle products like OFSAA, EDMCS, PaaS application, and/or Accounting Hub to house and maintain mapping rules. This strategy allows organizations to transition smoothly to the new COA while ensuring continuity and accuracy in downstream applications.

Unified conformed reverse mapping:

  • Implement a unified reverse mapping approach to ensure information undergoes reverse mapping when leaving the new systems.

  • This process guarantees that data remains consistent and accurate as it transitions between the new COA and legacy systems.

Utilization of reverse mapping engine:

  • Deploy the reverse mapping engine within the Oracle landscape to apply predefined rules for deriving the Legacy COA from the new COA.

  • The engine facilitates seamless mapping of data, ensuring compatibility with downstream applications.

Transmission of Legacy COA data:

  • Define and implement orchestration, timing, and frequency for transmitting Legacy COA data to downstream applications.

  • This ensures that downstream systems receive timely and accurate data, maintaining operational efficiency and accuracy.

  • Strategic interim solution for clients aiming for long-term downstream conformity to a consolidated COA. It provides a transitional path, reducing immediate disruption while working towards full integration.

  • Requires fewer changes and development work, offering flexibility to add accounts, update mappings based on evolving business needs. 

  • Aligns with clients' objectives of automation and industry-leading approach, as opposed to solutions necessitating the creation of additional applications, leveraging existing Oracle capabilities for reverse mapping.

  • Potential addition of a substantial number of accounts, may add overhead to support various aspects of operations such as compliance, reconciliation, audit, consolidation, etc.

  • Movement of balances between new and legacy COAs may impact trend analysis, necessitating careful consideration during implementation.

  • Ongoing maintenance of both new and legacy COAs, along with the mappings. This involves regular monitoring to ensure mapping remains accurate and effective as business needs evolve.

By implementing the reverse mapping solution, organizations can achieve a balance between adopting a new COA and maintaining the integrity and functionality of downstream applications. This approach minimizes disruption and provides a clear path toward long-term integration and automation.

Solution 2 Ledger construct

Approach overview

The ledger construct approach leverages Oracle General Ledger to establish an enterprise structure that maintains data in both the new and legacy Chart of Accounts (COA). This method involves extracting legacy COA data from the ledger and interfacing it with downstream applications, ensuring smooth operations during the transition period. AHCS ensures source feeds get recorded in both new and lecUser access is controlled to ensure all operations are conducted within a single general ledger, minimizing manual processes and AHCS ensures source feed.

  • Load upstream files containing the Legacy COA into Cloud GL and allow rules engine within AHCS to populate old and new chart in the appropriate ledgers.

  • Utilize extended attributes for manual journal entries (MJE) to capture legacy COA. This will allow AHCS to reverse map the MJEs to the legacy chart ledger and feed the downstream applications.

  • Build default reverse mapping logic for transactions originating in Cloud Subledgers like Accounts Payables, Assets, Accounts Receivable, etc. Or systemic transactions within Cloud GL like Revaluation and Intercompany lines.

  • Control user access by ledgers to facilitate the exclusion of manual processes within the old legacy ledger.

  • Technical solution that helps keep the downstream extracts and systems unaffected, with only limited reverse mapping.

  • Business users work on a single general ledger using the new chart, simplifying the operational processes and reducing complexities.

  • Seamless integration of both legacy and new COAs within the ledger construct ensures a smooth transition and accurate data management with reduced minimal manual intervention.

  • Require additional ledgers for transaction processing until each of the downstream applications adopts the new COA.

  • Reliance on the reverse mapping, especially for Manual Journal Entries (MJEs), revaluation and/or Oracle Subledger modules.

  • Require ongoing maintenance of new and legacy COAs, along with their mappings.

By implementing the ledger construct approach, organizations can achieve a balance between adopting a new COA and maintaining the integrity and functionality of downstream applications. This approach minimizes disruption and provides a clear path toward long-term integration and automation. It allows business users to operate efficiently on a single general ledger while ensuring that downstream systems continue to function correctly.

Navigating downstream impact mitigation: key success factors

Clear strategy

  • Define clear solution strategies to help mitigate downstream impacts

  • Determine downstream's alignment with new COA, necessitating an interim or permanent solution

  • Finalize the need for a secondary ledger and/or required level of reverse mapping and plan to maintain them

Well-defined solution rollout strategy

  • Integrate downstream solutions into the main capability rollout or subsequent phases

  • Align downstream solutions with the sequence of global rollouts based on capabilities (e.g., HR, Finance, SCM)

Stronger technology solution capabilities

  • Implement a scalable and extendable solution to help accommodate future growth, expansions, and regulatory changes

  • Incorporate analytical and reporting capabilities for data-driven decisions for both data in the new chart as well as in legacy chart

Engage in a deal skill mix: Oracle functional, Oracle Tech and Business SME

  • Involve Oracle Functional SMEs in the configuration of reverse mapping and/or secondary ledger

  • Leverage Tech SMEs with knowledge of data relationships of upstream/downstream systems

  • Engage business process SMEs to help address varying downstream reporting needs across groups/companies

Active collaboration with stakeholders

  • Integrate downstream impacts and solutions into the communication strategy

  • Collaborate with local stakeholders, Operations SMEs, business partners, customers, and suppliers

Effective governance

  • Establish industry-leading processes as the standard, with steering committee-approved exceptions for exception application needs

  • Establish a global and 'application-specific' Project Management Office (PMO) structure for governance and control

  • Conduct architectural reviews for overall and respective downstream application and technology solutions

Let PwC help you future proof your finance transformation with Oracle Cloud. Get in touch and explore services and solutions from PwC and Oracle Alliance.

Contact us

Avinash Mullick

Principal, PwC US

Shince Francis

Principal, Oracle Finance Consulting, PwC US

Abhishek Jaju

Director, Oracle Finance Consulting, PwC US

Follow us