Executives compare DIVA and SAP Group Reporting solutions during a focused business meeting.
Many Japanese companies have relied on DIVA for years as a core platform for consolidated accounting, financial consolidation, and group reporting.
However, as organizations migrate to SAP S/4HANA, consolidate ERP landscapes, and explore SAP Central Finance, CFOs and finance leaders are facing a new set of strategic questions:
Should we continue using DIVA in the future?
If we consolidate our accounting platform on SAP S/4HANA, should financial consolidation also move to SAP?
Does SAP Central Finance compete with DIVA, or can the two coexist?
These are not simply system selection questions.
They are fundamentally about how CFOs should design the future finance architecture and financial data platform required to manage the enterprise.
DIVA is a solution widely used in Japan to support consolidated accounting, financial consolidation, and disclosure processes.
It is provided by DIVA Corporation, a member of the AVANT Group.
One of its core solutions, DivaSystem LCA, supports a broad range of financial consolidation processes, including financial data collection from group companies, consolidation processing, preparation of consolidated financial statements, and reporting.
At a high level, the architecture can be represented as follows:
ERP / Accounting Systems of Group Companies
→ Financial Data Collection
→ DIVA
→ Financial Consolidation
→ Consolidated Financial Statements / Reporting / Disclosure
DIVA is therefore not an ERP system itself.
Its primary role is to collect financial information from multiple companies and systems and provide a platform for group-level financial consolidation and reporting.
Evaluating DIVA simply as a “financial consolidation system” is not enough.
From a CFO perspective, several broader questions need to be considered:
One of the most important considerations is to avoid treating financial consolidation and enterprise performance management as completely separate topics.
CFOs are no longer responsible only for producing accurate consolidated financial statements at month-end, quarter-end, or year-end.
They are increasingly expected to provide timely management insights across dimensions such as company, business unit, region, and product, using metrics including revenue, profit, cash flow, working capital, and ROIC.
The finance architecture must therefore support not only financial reporting but also faster and better management decision-making.
This leads to an important question: how should DIVA be positioned in an SAP S/4HANA landscape?
Traditionally, many Japanese corporate groups have operated heterogeneous system landscapes such as:
SAP ECC + SAP S/4HANA + Local Accounting Systems + Overseas ERP Systems
→ DIVA
→ Financial Consolidation
Even when individual group companies operate different ERP systems, DIVA can serve as a common financial consolidation platform by collecting financial information from those systems.
However, as organizations increasingly standardize their ERP landscape on SAP S/4HANA, another architectural option becomes possible:
SAP S/4HANA across Group Companies
→ SAP S/4HANA Finance for Group Reporting
For organizations that expect multiple ERP systems to remain in place for an extended period, SAP Central Finance can also serve as an intermediate financial integration platform:
ECC / S/4HANA / Other ERP Systems
→ SAP Central Finance
→ SAP S/4HANA Finance for Group Reporting
This architecture makes it possible to integrate financial data and financial consolidation within the broader SAP platform.
This is an area where confusion can easily arise.
DIVA and SAP Central Finance are fundamentally designed for different primary purposes.
The core role of DIVA is financial consolidation, consolidated accounting, and disclosure.
SAP Central Finance, by contrast, is designed to centralize financial data from multiple ERP and accounting systems into SAP S/4HANA and establish a centralized finance platform.
Therefore, an architecture such as the following is also possible:
Source ERP Systems
→ SAP Central Finance
→ DIVA
In other words, implementing SAP Central Finance does not automatically mean that DIVA must be replaced.
The more important question is:
What role should each platform play within the overall finance architecture?
CFOs should therefore avoid framing the decision simply as:
DIVA vs SAP Central Finance
A more meaningful comparison is between:
A DIVA-centered financial consolidation architecture
and
An integrated SAP finance architecture centered on SAP Central Finance and SAP S/4HANA Finance for Group Reporting.
Several architectural options can be considered.
The organization continues collecting financial data from existing ERP systems into DIVA and retains the current financial consolidation platform.
The main advantage is lower disruption to existing consolidation processes and potentially lower transition risk.
However, even after ERP consolidation progresses, the organization may need to maintain multiple finance platforms, interfaces, master data mappings, and operational processes.
This can create additional long-term complexity and cost.
The ERP landscape is progressively consolidated on SAP S/4HANA while DIVA remains the financial consolidation platform.
This approach allows the organization to transform the ERP landscape without significantly changing the existing consolidation process at the same time.
For many companies, this can represent a pragmatic Transition Architecture.
Financial information from multiple ERP systems is centralized in SAP Central Finance while DIVA continues to perform financial consolidation.
In this architecture:
SAP Central Finance = Group Financial Data Platform
DIVA = Financial Consolidation Platform
This separation of responsibilities can be useful during a multi-year ERP transformation.
Another option is to integrate financial data centralization and financial consolidation within the SAP platform.
This can become a potential Target Architecture for organizations that intend to position SAP as their strategic group finance platform over the long term.
A critical principle is that companies do not necessarily need to move directly from today’s architecture to the final target state.
For large corporate groups, ERP consolidation can take several years—and in some cases more than a decade.
It is therefore useful to think in terms of:
Current Architecture
→ Transition Architecture
→ Target Architecture
For example, the current environment might consist of:
ECC on RISE + S/4HANA On-Premise + Other ERP Systems + DIVA
while the long-term target might be:
One S/4HANA + SAP Group Reporting
Between those two states, the organization could establish a Transition Architecture such as:
Multiple ERP Systems
→ SAP Central Finance
→ DIVA
or:
Multiple ERP Systems
→ SAP Central Finance
→ SAP Group Reporting
The right answer depends on the company’s transformation timeline, business requirements, risk appetite, existing investments, and long-term ERP strategy.
System selection discussions often focus heavily on software licenses and implementation costs.
However, CFOs should evaluate the broader long-term TCO.
A more complete view includes:
**Software Licenses
For example, retaining DIVA may reduce near-term migration risk, but interfaces between SAP and DIVA may need to be maintained for many years.
Conversely, consolidating the finance architecture entirely on SAP may simplify the long-term application landscape but require higher initial investment and introduce greater transformation risk.
The architecture should therefore be evaluated over a five- to ten-year horizon, rather than solely on the basis of initial implementation cost.
There is another important dimension: the changing role of the CFO organization itself.
Traditional finance systems were primarily designed around:
Record → Consolidate → Report
The next generation of CFO platforms increasingly needs to support:
Record → Consolidate → Analyze → Predict → Decide
The objective is shifting from simply producing accurate financial results to using financial data to accelerate management decision-making.
From this perspective, the discussion should not stop at whether DIVA should remain or whether the organization should migrate to SAP Group Reporting.
The more fundamental question for the CFO is:
What finance architecture will provide the financial and management information our group needs over the next ten years?
Enterprise Architecture provides a useful framework for answering this question.
Instead of beginning with a comparison of individual software products, organizations can work through the following layers:
Business Strategy
→ Business Capabilities
→ Business Processes
→ Data
→ Applications
→ Technology
For example, suppose the organization’s strategic objectives include:
The first step should be to define the business capabilities required to achieve those objectives.
Only then should the organization determine the appropriate roles of DIVA, SAP S/4HANA, SAP Central Finance, and SAP Group Reporting.
In other words:
Do not begin the discussion with “Should we keep DIVA?”
Begin with:
“What group finance architecture do we need to support our future management model?”
That is the more important question for CFOs.
DIVA has played an important role in supporting financial consolidation at many Japanese companies.
However, as organizations migrate to SAP S/4HANA and consolidate their ERP landscapes, some companies are reaching the point where the role of their existing consolidation platform should be reconsidered.
They may choose to:
Continue using DIVA
Run DIVA alongside SAP S/4HANA
Combine DIVA with SAP Central Finance
or
Eventually consolidate financial data and group reporting within SAP
There is no single architecture that is right for every organization.
The key is to distinguish clearly between:
Current Architecture
→ Transition Architecture
→ Target Architecture
CFOs should not simply ask:
“Which financial consolidation product is better?”
The more strategic question is:
How should we build the finance and financial data architecture that will support our group management strategy over the next five to ten years?
Reframing the discussion in this way enables organizations to define the appropriate roles of DIVA, SAP S/4HANA, SAP Central Finance, and SAP Group Reporting—and build a finance architecture that supports not only financial consolidation, but the future of enterprise management.
Parts of this article were developed with reference to generative AI suggestions and were reviewed, refined, and supplemented based on the author’s professional expertise and judgment.
What does AI need to rate stakeholder power and interest as High, Middle, or Low…
How can AI streamline TOGAF stakeholder management? This guide outlines a practical six-step process, from…
Do Tier 1 and Tier 2 automotive suppliers really need MRP? Discover when SAP S/4HANA…
Which Treasury Management System is right for your enterprise? Compare SAP Treasury, Kyriba, FIS, ION,…
After a merger, how much financial integration can SAP Central Finance really deliver? Using a…
Which system performs each process step, in what order, and how do the systems integrate?…