Exploring Cloud-Native General Ledger Systems Supporting Consolidated Reporting: Open API and Integrated Solutions
A US-based enterprise is evaluating cloud general ledger (GL) systems that require open APIs and the ability to handle consolidation and elimination entries for up to 30 entities. They prefer GL and consolidation functions to be completed within the same system, rather than relying on additional modules or product suites. Sage Intacct suggests pairing with Adaptive, but the user prefers an integrated solution. This article outlines their core requirements and the current industry landscape.
Selection Background: Consolidation Needs and Open APIs Are Key
A U.S. enterprise is seeking a cloud-native general ledger (GL) system that offers open APIs and can handle consolidated reporting and elimination entries. The company has multiple parent entities and, based on partial ownership, needs to consolidate up to 30 subsidiaries, all located within the United States. All subsidiaries and parent companies plan to use the same GL system, but the team has found that few cloud systems on the market can meet this need without significant customization.
According to the enterprise, they have spoken with Sage Intacct, which suggested combining Sage Intacct with Adaptive. However, the company wants to keep general ledger and consolidation functions within the same system to avoid introducing a multi-product suite. The team stated, "We are tired of feeling that our data is being 'held hostage,' and this is a core reason driving the system replacement." They want to learn how other companies handle this in an open API environment.
Core Pain Point: Integrated vs. Modular
Currently, most GL/ERP systems still rely on additional software or modules for consolidation, leading to data fragmentation and integration complexity. The company has clearly stated that they do not prefer purchasing a product portfolio, but rather seek to complete general ledger and consolidation processes within a single system. Open APIs are seen as a key requirement to ensure data portability and system flexibility.
"We no longer want to be locked into a product suite; we want data to flow freely." — Selection lead at the enterprise
Industry Status: Consolidation Capability Gap in Cloud GL Systems
Based on industry observations, cloud GL systems are relatively mature in basic bookkeeping functions, but advanced consolidation features (such as partial ownership, automatic eliminations, and multi-level consolidation) are often still offered as add-on modules or require integration with specialized consolidation tools (such as Adaptive, OneStream, etc.). Sage Intacct's recommendation reflects this trend, but user demand for integrated solutions is also increasingly evident.
The company emphasizes that all entities are located in the U.S. and the ownership structure is complex (partial holdings), requiring the system to flexibly handle consolidation ratios for non-wholly-owned subsidiaries. Additionally, open APIs are a necessary condition to ensure future data migration and system integration.
Potential Directions: Native Consolidation Capabilities and API Ecosystem
Some emerging cloud GL vendors (such as Workday Financial Management, Oracle Fusion Cloud ERP) claim to have built-in consolidation features, but actual deployment still requires configuration. Additionally, some pure cloud GL systems (such as QuickBooks Online Advanced) offer multi-entity consolidation but may not handle complex ownership. The company suggests that peers, during selection, focus on verifying whether the system supports "partial ownership consolidation" and "automatic elimination entries," and check the completeness of API documentation and rate limits.
Currently, the company has not publicly disclosed the final selection result, but has indicated it will prioritize vendors that offer "integrated consolidation" and have open APIs. They call on other companies to share successful cases in open API environments to promote more transparent solutions in the industry.
(This article is based on the user's original inquiry and does not add additional facts.)