Group consolidation in the mid-market — what ERP and tooling actually have to deliver.

Group consolidation is often elevated to an ERP topic too late in the mid-market. As long as financial statements are produced per entity, everything looks fine. Once external pressure starts — financing, investors, banking ratings, regulatory reporting, acquisitions — it becomes visible that consolidation is more than adding up single-entity statements. This profile shows what a consolidation-capable ERP architecture has to deliver, where a separate consolidation tool still makes sense and which systems consolidate reliably in the mid-market.

The audience: mid-market companies with two or more legal entities for which a group statement is currently or imminently relevant — whether by legal obligation, external expectation or internal steering need.

1. When consolidation really becomes mandatory in the mid-market

Obligation to consolidate emerges in the German mid-market on several levels — not all at once:

• Legal obligation (§ 290 HGB). Parent companies must produce a group statement once the group exceeds defined size criteria (balance sheet total, revenue, headcount).
• Contractual obligation. Banks, insurers or investors require consolidated figures for financing, reporting, covenants — often years before the legal obligation kicks in.
• Internal steering need. Management wants group-wide KPIs, uniform margins, a uniform sales view — even without external obligation.
• Acquisitions. A takeover changes the consolidation logic abruptly: a new subsidiary, possibly a different accounting standard, new intercompany relationships.

Anyone seeing consolidation only as a compliance task overlooks the steering value. Anyone seeing it only as steering overlooks the formal requirements. In practice, decide early in which order to address both.

2. From single-entity statement to group statement

A single-entity statement ends at the entity. A group statement portrays the group as if it were a single company. Between the two lie four consolidation steps that any consolidation-capable setup has to master:

Capital consolidation

The parent's investments in subsidiaries are netted against the subsidiaries' equity. Otherwise the same value would appear twice in the group balance sheet — once as investment, once as subsidiary equity.

Debt consolidation

Receivables and payables between group entities are eliminated. Subsidiary A has 100 k EUR receivable from subsidiary B – in the group statement neither position appears.

Income / expense consolidation

Intercompany sales are eliminated: when A delivers to B, that is no third-party sale from a group perspective. Otherwise, group revenue would be artificially inflated.

Interim profit elimination

If inventories from intercompany deliveries remain on the balance sheet date, embedded intercompany profits must be eliminated. This step is often run manually in the mid-market — with corresponding error risk.

If an ERP cannot handle these four steps in the standard, consolidation runs downstream in Excel or a specialist tool. That works, but has consequences for speed, data quality and audit reliability.

3. Requirements for a consolidation-capable ERP

An ERP that should consolidate reliably in the mid-market has to deliver at least these functions:

• Multi-entity data model. Entity as a data dimension on posting level, not just tenant separation.
• Group chart of accounts. Mapping between local charts of accounts (SKR03/04, local standards) and a uniform group account plan.
• Intercompany flagging. Postings between group entities are automatically flagged as intercompany and are eliminable.
• Multi-currency with consolidation currency. Local postings in local currency, group reporting in a consolidation currency with defined valuation rates.
• Parallel ledgers. Local GAAP, IFRS, US GAAP – every posting can be assigned to multiple standards without duplicate capture.
• Period-end logic. Consolidation runs at defined dates with downstream adjustment postings; reporting periods must be group-wide closeable.
• Audit trail at group level. Every consolidation entry must be traceable – who, when, why.

These functions distinguish a "consolidation-capable" ERP from an ERP that "has multiple tenants". The gap is significant.

4. ERP-internal consolidation vs. separate consolidation tool

Two realistic architecture patterns exist in the mid-market, each with clear pros and cons:

Consolidation in the ERP

Advantages: one data model, real-time view, fewer interfaces, shorter period closes, lower licence and maintenance costs for secondary software. Prerequisite: the ERP has to deliver the necessary depth.

Suitable for mid-market companies with manageable consolidation logic (3–10 entities, one to two standards, defined intercompany relationships). NetSuite OneWorld and D365 Finance & Operations address this case directly in the standard.

Consolidation via separate tool (LucaNet, IDL Konsis, SAP BPC, Tagetik)

Advantages: specialist functionality, depth in multi-GAAP, mature reporting and disclosure logic, adaptability to complex group structures. Prerequisite: clean interfaces from the ERP, maintained mappings, dedicated consolidation resources.

Suitable for mid-market companies with high consolidation depth (multi-GAAP in parallel, several joint ventures, international complexity, frequent acquisitions) or those that have historically relied on a dedicated tool.

The question "ERP-internal or separate tool" should be answered before the ERP selection, not in parallel. Otherwise, architecture decisions emerge that are hard to correct later.

5. Multi-GAAP: local GAAP, IFRS, US GAAP in parallel

Anyone reporting in parallel under local GAAP and IFRS in the mid-market (often demanded by banks or investors) needs two ledgers per entity, runnable in the same system. Three technical approaches exist:

• Ledger model: One dedicated ledger per standard, every posting goes simultaneously into all active ledgers. Clean, transparent, resource-intensive.
• Adjustment postings: One main set of books plus correction postings for the other standard. Leaner, more error-prone.
• Mapping-based consolidation: Consolidation happens only at group level; local books only in one standard. Works for simple cases, fails with complex valuation differences.

Which variant fits depends on complexity, volume and the expected development of the group. Anyone considering a stock listing or PE participation in the medium term should seriously evaluate the ledger model.

6. Which ERP systems consolidate reliably in the mid-market

Profiling of relevant systems by their consolidation suitability in the mid-market:

In mid-market consolidation work, NetSuite OneWorld is particularly often shortlisted in practice. The reason is not marketing but architecture: consolidation entries, eliminations, multi-book logic and consolidated reporting are standard functions, without the need to set up a second tool. For mid-market companies that do not want to run their consolidation across two different system worlds in parallel, that is a clear advantage – which is why the solution appears above average in our advisory mandates around consolidation and multi-entity topics.

7. Typical pitfalls in consolidation projects

Three patterns repeat in mid-market consolidation projects:

Treating consolidation as an Excel task until it is too late

While the group is small, consolidation runs in Excel. Once the group grows, Excel slowly becomes a risk source: auditors want audit trails, banks want timeliness, management wants group-wide KPIs in days rather than weeks. The transition should be planned, not crisis-driven.

Mappings between local and group charts of accounts underestimated

Context-free consolidation does not fail at the software, it fails at the mapping. Every subsidiary has its own accounts, cost centres and posting patterns. Translating these into a uniform group plan is data work that has to be done early and cleanly.

Responsibilities between holding and subsidiaries unclear

Who maintains the group chart of accounts, who owns eliminations, who reviews consolidation entries? Without clear RACI logic, consolidation turns into an endless discussion between holding and subsidiary accounting.

8. Frequent questions on group consolidation

From which size does consolidation become mandatory in the mid-market?

The thresholds under § 290 ff. HGB are currently (exceeded on two consecutive reporting dates): balance sheet total > EUR 27 m (gross) / EUR 22.5 m (net), revenue > EUR 54 m (gross) / EUR 45 m (net), > 250 employees. Contractually, consolidation can be required much earlier.

Is ERP-internal consolidation enough for mid-market group structures?

In most cases yes – if the ERP delivers the necessary depth (NetSuite OneWorld, D365 F&O, S/4HANA). For very complex group structures with frequent acquisitions or multiple parallel standards, dedicated tools may remain the better choice.

What changes with an acquisition?

A takeover changes the obligation to consolidate (consolidation perimeter) and the complexity. Ideally, the new subsidiary is migrated to the group ERP promptly. Until then: defined data export pipelines, clear mapping logic, transitional workflow for the first close.

How can the group close be shortened?

Consolidation in the ERP rather than downstream saves days. Clean mappings save more days. Clear responsibilities and a documented closing schedule save the rest. Mid-market companies that consolidate in the ERP typically close the group statement in 5–10 working days instead of 4–6 weeks.

When is a separate consolidation tool really needed?

When the group structure is multi-layered (holding + sub-holdings + subsidiaries), when multi-GAAP in parallel is the standard case, when frequent acquisitions constantly change the consolidation setup, or when disclosure requirements (notes, management report, cash flow statement under DRS) are not mappable in the ERP. In a classic mid-market group, that is more the exception than the rule.

---

Note: This profile does not replace an individual project assessment. The patterns and recommendations presented here are experience values from selection projects in the German-speaking mid-market.

Author: Joerg H. Paul Schaefer · As of: May 2026 · erp-check.info is a vendor-neutral information platform.