Does your group CFO still spend close nights extracting Excel files to manually aggregate accounts across 20 subsidiaries? If so, the problem is not the ERP — it is the absence of a consolidation tool suited to the group’s scale. Conversely, a mid-market company with 8 subsidiaries all on uniform local accounting standards does not necessarily need a CPM tool costing £80–100K per year: a native ERP module may be perfectly sufficient.
The financial close and consolidation software market was valued at USD 6.7 billion in 2024, with projections reaching USD 15.3 billion by 2033 (Expert Market Research, 2024). This growth reflects a ground-level reality: groups that rely on Excel or basic ERP modules are effectively outsourcing their close risk to their finance teams. This guide maps the boundary between the two worlds.
Management Consolidation vs. Statutory Consolidation: Two Different Worlds
Management Consolidation: What Your ERP Handles
Management consolidation (or management reporting) aggregates operational metrics from multiple entities to provide a group-wide view: cumulative revenue, margins by business unit, budget tracking. It follows no mandatory legal framework — the group sets its own rules. Most mid-market ERPs handle this correctly, sometimes simply through a shared analytical chart of accounts across entities.
This is what SAP S/4HANA, Odoo Multi-Company, Sage X3, and Microsoft Dynamics 365 Finance do natively: consolidate balances from multiple instances or legal entities into shared reporting.
Statutory Consolidation: Why It Is More Demanding
Statutory consolidation produces legally required consolidated financial statements — balance sheet, income statement, notes — published under an accounting framework (IFRS, UK GAAP, US GAAP) and subject to external audit. It requires:
- Elimination of intercompany transactions: intra-group sales, loans, dividends, and margins on internally sold inventory must be eliminated to avoid artificially inflating group accounts.
- Non-controlling interests (minority interests, IFRS 10): the minority shareholders’ share in subsidiaries held at less than 100% must be calculated, presented, and broken out separately in equity and profit or loss.
- Accounting standard restatements: a group applying IFRS for its consolidated accounts must restate each subsidiary’s local-standard accounts before integrating them.
- Audit trail: every consolidation entry must be documented, traceable, and justifiable to statutory auditors.
This is where native ERP modules reach their true limits.
What Native ERP Modules Do — and Their Real Limits
SAP: Three Generations of Consolidation Solutions
SAP has several overlapping tools, which creates confusion for CFOs:
- SAP SEM-BCS (Strategic Enterprise Management – Business Consolidation): the legacy SEM module, now integrated into S/4HANA Group Reporting.
- SAP Financial Consolidation (formerly Cartesis): acquired in 2007 through BusinessObjects. Mainstream maintenance guaranteed through end-2030 (Prophix, 2024). SAP is migrating it to SAP Group Reporting on S/4HANA.
- SAP BPC 10.1 (Business Planning and Consolidation): the Microsoft platform version reached end-of-maintenance in June 2026; the NetWeaver version is supported through end-2027 (Prophix, 2024).
- SAP S/4HANA Group Reporting: the current solution, native within S/4HANA, combinable with SAP Analytics Cloud. Handles statutory consolidation with direct integration into the S/4HANA general ledger.
The migration from SAP FC (ex-Cartesis) and SAP BPC to SAP Group Reporting is the project currently occupying SAP group CIOs across Europe.
Oracle FCCS (Financial Consolidation and Close Service)
Oracle FCCS is Oracle EPM’s dedicated cloud module for financial close and consolidation. It manages intercompany eliminations, non-controlling interests, IFRS restatements, and foreign currency reconciliation. Its integration with Oracle ERP Cloud is native; with SAP or Dynamics, it works through connectors. A robust solution positioned for large enterprises and complex mid-market groups.
Microsoft Dynamics 365 Finance
Dynamics 365 Finance includes a financial consolidation module that aggregates multiple legal entities. It handles multi-currency and basic eliminations, but advanced IFRS 10 restatements — particularly the automated calculation of non-controlling interests with acquisition history — often require customisation or complementary tools (LucaNet, Tagetik) for mid-market groups.
Sage UK, Access Group, and Comparable Mid-Market ERPs
Sage UK and Access Group offer consolidation modules in their respective suites, oriented towards SMEs and mid-market. They cover standard local accounting (UK GAAP). For groups simultaneously applying IFRS or multi-standard reporting (IFRS + UK GAAP + US GAAP), these tools show limits in restatements and automation of complex eliminations.
The Shared Limit: IFRS 10, Minority Interests, Complex Restatements
The common limit shared by most native ERP modules is not simple consolidation (aggregating accounts in a single currency across ten homogeneous entities). It appears when the group combines:
- Partially held subsidiaries (IFRS 10 non-controlling interests)
- Different accounting standards across entities (IFRS vs. local GAAP)
- Leases to restate under IFRS 16
- High-volume, asynchronous intercompany transactions
- A target for consolidated close in under 5 business days
At this inflection point, dedicated CPM tools become necessary.
Dedicated CPM Consolidation Tools
CCH Tagetik (Wolters Kluwer) — Strengths in IFRS 16, 17, Multi-Standard
Acquired by Wolters Kluwer, CCH Tagetik is recognised as a Leader in the 2026 Gartner Magic Quadrant for Financial Close and Consolidation Solutions (Wolters Kluwer, 2026). This is the third consecutive year in that position.
Key strengths for mid-market and large enterprise groups:
- Simultaneous multi-standard reporting: a group can produce IFRS, UK GAAP, and US GAAP statements in parallel from the same platform, without double entry.
- IFRS 16 and IFRS 17: Tagetik has dedicated engines for lease contracts (IFRS 16) and insurance contracts (IFRS 17) — two standards that most native ERP modules do not handle natively.
- Elimination automation: intercompany flows are reconciled automatically, with entity-level dispute management.
- CSRD / IFRS S1-S2: the platform now integrates ESG non-financial reporting, addressing the growing CSRD requirement for groups subject to sustainability reporting obligations.
Pricing is by quotation. Implementation projects typically start from €60–100K depending on size and modules selected.
LucaNet — Mid-Market Solution, Strong in DACH and European Mid-Caps
LucaNet is a German mid-market solution with strong roots in the DACH region (Germany, Austria, Switzerland) and a growing presence among European mid-market groups with 15 to 50 entities. It positions itself as more accessible than Tagetik in terms of deployment and integration.
Its advantages:
- ERP-agnostic integration: native connectors for SAP, Microsoft Dynamics, Sage X3, and most mid-market ERPs.
- Moderate learning curve: finance teams regain ownership more quickly than with an enterprise platform like Tagetik or Oracle FCCS.
- Consolidation and planning in one: LucaNet combines statutory consolidation, management reporting, and budgetary planning in a single platform, limiting tool sprawl.
Pricing is by annual quotation, with no public pricing.
Workiva — 2026 Overview
Workiva is not a consolidation engine per se: it is a connected financial reporting platform that industrialises the production of financial documents (annual report, Form 10-K, CSRD report) by linking figures to their data sources. Its revenue for FY 2024 reached approximately USD 780 million, with 2025 guidance of USD 920 million (public sources, 2025). It is used as a complement to a consolidation engine (SAP, Oracle, Tagetik) rather than a substitute.
What They Concretely Deliver
Practitioner feedback consistently converges on three measurable benefits after adopting a dedicated CPM tool:
- Shorter consolidated close cycle: based on benchmarks shared at CFO conferences, groups typically move from 12–15 business days to 5–7 days after deploying a specialist tool.
- Complete audit trail: each consolidation entry is documented, time-stamped, and justifiable — a key criterion for statutory auditors.
- Scale without additional headcount: a group moving from 20 to 40 subsidiaries does not need to double its consolidation team if the tool automates eliminations and restatements.
The Five-Question Decision Matrix
Q1 — How Many Subsidiaries with Intercompany Transactions?
Below 10 subsidiaries with limited intercompany flows (simple recharges, no intra-group inventory sales), a well-configured native ERP module can suffice. Beyond 20 active subsidiaries with cross-entity flows, the volume of manual eliminations becomes an operational risk.
Q2 — What Is Your Reference Accounting Standard?
- Local GAAP only (e.g. UK GAAP, German HGB): native modules from local-market ERPs often cover this case.
- IFRS: IFRS 10 restatements (minorities), IFRS 16 (leasing), IFRS 9 (financial instruments), and IFRS 15 (revenue recognition) exceed native module capabilities for most mid-market groups.
- Simultaneous multi-standard (IFRS + UK GAAP + US GAAP): a dedicated CPM tool becomes near-mandatory.
Q3 — What Is Your Target Close Timeline?
- D+10 or more: a semi-manual process with a native ERP module is manageable.
- D+5: requires serious automation of eliminations and ERP-to-consolidation interfaces.
- D+3 or D+2: reserved for large enterprises with an enterprise CPM tool (Tagetik, Oracle FCCS, SAP Group Reporting on S/4HANA).
Q4 — What Is the Technical Debt on Your Current ERP Module?
Groups using SAP Financial Consolidation (ex-Cartesis) or SAP BPC face a decision imposed by SAP’s end-of-support calendar. Maintaining an end-of-life solution for consolidation is an audit and operational continuity risk.
Q5 — CSRD, IFRS S1/S2: What Non-Financial Obligations Are Being Added?
Groups subject to CSRD (mandatory for large enterprises since 2025, listed mid-caps from 2026) must produce audited sustainability reporting. Native ERP modules do not handle this workflow. Tagetik and LucaNet have integrated ESG modules. This is an increasingly decisive selection criterion.
2026 Solution Comparison Table
| Solution | Interco Eliminations | IFRS 10 Minorities | Multi-Standard | Source ERP Integration | Typical Target |
|---|---|---|---|---|---|
| Native ERP module (Sage, Dynamics) | Basic | Manual | Local GAAP only | Native | Groups <10 entities, local standards |
| SAP S/4HANA Group Reporting | Automated | Yes | IFRS + local | Native S/4HANA | Existing SAP clients |
| CCH Tagetik (Wolters Kluwer) | Automated + workflow | Yes, advanced | IFRS + local + US GAAP | Agnostic | Mid-to-large, 30–500 entities |
| LucaNet | Automated | Yes | IFRS + local | Agnostic | Mid-market, 15–50 entities |
| Oracle FCCS | Automated | Yes | IFRS + US GAAP | Native Oracle, API others | Oracle or mixed-ERP groups |
| Workiva | Reporting/document | No (downstream) | All (downstream) | Agnostic (connectors) | Complement to a consolidation engine |
Pricing: all by quotation. No vendor publishes a public pricing grid.
Three Mid-Market Profiles, Three Answers
Group of 15 Subsidiaries, Local GAAP, D+10 Close — Native ERP Module Sufficient
A manufacturing mid-cap with 15 subsidiaries all on local accounting standards, moderate intercompany flows (management fees, shared services recharges), and a 10-business-day close can manage with the native consolidation module of its ERP — provided that module is correctly configured, charts of accounts are harmonised across entities, and interfaces are automated. The configuration and optimisation project costs less than a dedicated CPM tool.
Group of 35 Subsidiaries Including 10 International, IFRS, D+5 Close — LucaNet or Tagetik
A mid-cap with European subsidiaries (Germany, Benelux, UK, Spain), applying IFRS for consolidated accounts, with leases to restate under IFRS 16 and a D+5 close target, exceeds what native ERP modules handle comfortably. LucaNet is often the first choice at this stage: accessible, well-integrated with common European ERPs (SAP, Dynamics), deployable in 4–6 months. Tagetik becomes relevant if the group anticipates growth toward 50–80 entities.
Group of 80+ Subsidiaries, IFRS 16 and CSRD, D+3 Close — Tagetik or Oracle FCCS
A large group with 80 or more subsidiaries, subject to IFRS, CSRD, and an accelerated close requirement, needs an enterprise platform. Tagetik (recognised 2026 Gartner Leader) or Oracle FCCS (for groups in the Oracle ecosystem) are the two mature options. SAP Group Reporting on S/4HANA is equally relevant for groups running 100% on SAP.
Related Articles
For a deeper look at multi-entity and intercompany architecture, read ERP Multi-Site and Multi-Entity: Consolidation, Intercompany and Multi-Currency — it covers ERP architectures for European groups, multi-currency management, and intercompany flows.
On the operational close cycle, the ERP Year-End Close Checklist for CFOs details the sequence from D-90 to D+3.
If your thinking covers the full EPM chain (FP&A, budgeting, forecasting in addition to consolidation), see our ERP vs. EPM Integration: SAP, Oracle, Anaplan, OneStream Compared.
