What is financial consolidation in simple terms?

Financial consolidation is the process of combining the financial statements of a parent company and the subsidiaries it controls into one set of statements that presents the group as a single economic entity. Practically, it means adding up the ledgers, removing any transactions between group members, translating subsidiaries that report in other currencies, and carving out the share of any subsidiary the parent does not fully own. The result is consolidated statements that show only the group's dealings with the outside world. Lightbridge ERP helps finance teams choose where this consolidation should run and configure it so it ties out automatically.

What are the main financial consolidation models?

There are two ways to frame consolidation models. The first is structural: a hub-and-spoke model, where subsidiaries report into a central entity that performs eliminations and translation, versus more distributed approaches. The second, and usually more decisive, is architectural: where the consolidation actually happens. The three common venues are inside the ERP, such as NetSuite OneWorld, in an FP&A or EPM planning platform, or in a dedicated close-and-consolidation platform. Most consolidation decisions come down to that venue question, because it determines single source of truth, statutory depth, currency handling, and how much flexibility the team has for management views.

Should we consolidate inside the ERP or in a separate platform?

It depends on the depth of statutory reporting you need and how much you value a single source of truth. Consolidating inside the ERP keeps consolidation on the same transactional ledger, so the audit trail runs unbroken from journal entry to consolidated statement and intercompany and currency are handled natively. That suits many mid-market and growing groups. A dedicated close-and-consolidation platform earns its place when the group spans many entities, multiple GAAP or statutory frameworks, and complex ownership changes that the ERP alone cannot model cleanly. An FP&A or EPM platform is the right home for management consolidation and planning, but it is generally not the statutory book of record. Lightbridge ERP selects the architecture that fits the group rather than a preset answer.

How does financial consolidation handle foreign currency?

When subsidiaries keep their books in different functional currencies, consolidation translates each one into the group's presentation currency before combining. Under ASC 830 and its international counterpart IAS 21, the assets and liabilities of a foreign operation are generally translated at the closing rate and income statement items at rates approximating those at the transaction dates, with the difference recorded as a cumulative translation adjustment within equity rather than in net income. Getting the functional-currency determination, rate types, periods, and the cumulative translation account right is one of the harder parts of a multi-currency consolidation, and it is a common source of audit questions. The consolidation venue you choose should automate this translation rather than leave it to spreadsheets.

How are intercompany transactions handled during consolidation?

Because consolidated statements present the group as one entity, any transaction between group members has to be eliminated, otherwise the group would appear to do business with itself. That includes intercompany sales and purchases, intercompany loans and interest, and intercompany receivables and payables, along with unrealized profit sitting in inventory that has not yet been sold outside the group. Eliminations are where many consolidations stall, because the two sides of an intercompany transaction must match exactly across entities, currencies, and periods. A consolidation architecture that matches and eliminates intercompany activity automatically removes most of that friction.

What is the difference between management consolidation and statutory consolidation?

Statutory consolidation produces the legal, audited financial statements the group files, following a defined framework such as US GAAP or IFRS, with full eliminations, currency translation, and non-controlling interest. Management consolidation produces internal reporting tailored to how leaders run the business: alternative hierarchies, segments, allocations, and rolling forecasts, often on a faster cycle. The same group frequently needs both. FP&A and EPM platforms shine at management consolidation, while statutory consolidation tends to live in the ERP or a dedicated close-and-consolidation system. Confusing the two leads groups to either over-engineer planning tools or stretch the statutory book of record into reporting it was not built for.

How does Lightbridge ERP help select a consolidation model?

Lightbridge ERP is an independent, vendor-neutral ERP advisory firm with deep in-house finance expertise across consolidation, multi-book accounting, intercompany, and currency translation. It maps your entity structure, ownership percentages, GAAP and statutory requirements, and close timeline, then recommends where consolidation should run: inside the ERP, in an FP&A or EPM platform, in a dedicated close system, or a combination. Because Lightbridge accepts no vendor kickbacks, no reseller quotas, and no partner-tier incentives, the architecture recommendation is driven by fit rather than commission. This guide is general information, not accounting, tax, or legal advice; confirm treatment with your auditor or accountant.

JH Written by Jully Hayasaka with Robert LabardeeNetSuite Advanced Accounting Lead and Founder and CEO

Last updated June 2026.

How do financial consolidation models compare?

Lightbridge ERP defines financial consolidation as combining the financial statements of a parent and its subsidiaries into one set, eliminating intercompany activity. Consolidation models differ mainly in where the work happens: inside the ERP, in an FP&A or EPM planning platform, or in a dedicated close-and-consolidation system. Each choice trades single source of truth against statutory depth and flexibility.

Multi-entity accounting Talk to a finance advisor

Financial consolidation combines a parent and its subsidiaries into one set of statements.

Financial consolidation is the process of combining the financial statements of a parent company and the subsidiaries it controls into a single set of statements, presenting the group as one economic entity. It brings in the full ledger of each controlled subsidiary, eliminates transactions between group members, translates foreign-currency subsidiaries to the presentation currency, and attributes the share of partly owned subsidiaries to outside owners. The standards behind it are ASC 810 and IFRS 10.

Where teams disagree is not what consolidation does, but where it should happen. A consolidation can run inside the ERP on the transactional ledger, inside an FP&A or EPM planning platform, or inside a dedicated close-and-consolidation system. Each model trades a single source of truth and audit trail against statutory and multi-GAAP depth, currency handling, flexibility, and scale. For the structural foundation underneath all of this, see the Lightbridge ERP guide to multi-entity accounting.

This guide is general information for finance and operations leaders, not accounting, tax, or legal advice. Confirm specific treatment with your auditor or accountant.

Every financial consolidation performs the same four steps.

Whatever model a group adopts, the underlying consolidation work is consistent: combine the parent and subsidiaries, eliminate intercompany activity, translate foreign currency, and attribute non-controlling interest. These four steps are what any consolidation architecture has to automate, and the chosen venue is mostly a question of where they run and how deeply they are supported.

Combine parent and subsidiaries

Consolidation aggregates the assets, liabilities, revenues, and expenses of the parent and every controlled subsidiary into one set of statements, as if the group were a single economic entity under ASC 810 and IFRS 10.

Eliminate intercompany activity

Sales, loans, and balances between group members are removed so the consolidated statements show only transactions with outside parties. Unresolved intercompany differences are a leading cause of slow consolidations.

Translate foreign currency

Subsidiaries reporting in other currencies are translated to the presentation currency under ASC 830 and IAS 21, with the resulting adjustment carried in the cumulative translation account inside equity.

Attribute non-controlling interest

When the parent owns less than 100 percent of a subsidiary, consolidation still brings in the whole subsidiary, then carves out the outside owners' share as non-controlling interest within equity and net income.

Consolidation models differ most by where the consolidation runs.

The decisive comparison is architectural: where does the consolidation actually happen. The three common venues, plus the structural hub-and-spoke pattern, each carry a distinct trade-off between single source of truth, statutory depth, flexibility, and scale. For groups that include partly owned subsidiaries, read this alongside the Lightbridge ERP guide to non-controlling interest, since the venue you pick must attribute that interest correctly.

Inside the ERP (for example NetSuite OneWorld)

Consolidation runs directly on the transactional ledger, so a single source of truth and a continuous audit trail extend from journal entry to consolidated statement. This fits groups that want close-of-books consolidation without exporting data, and it handles multi-currency and intercompany natively. Statutory and multi-GAAP depth varies by platform.

In an FP&A or EPM planning platform

A planning platform consolidates management figures alongside budgets and forecasts, which suits flexible reporting hierarchies, what-if views, and rapid restructuring of the org. It typically reads balances from one or more source ledgers, so it is strong for management consolidation but is not the statutory book of record.

In a dedicated close-and-consolidation platform

A purpose-built consolidation system handles complex multi-GAAP, statutory reporting, ownership-change accounting, and rigorous intercompany matching at scale. It is the strongest fit for large, multi-entity, multi-standard groups, at the cost of another system to integrate and reconcile against the ERP.

Hub-and-spoke into a central ledger

In the hub-and-spoke model, subsidiaries report into a central entity or chart of accounts that performs the eliminations and translation. This concentrates control and standardizes the close, but depends on disciplined, timely reporting from each spoke and clean mapping into the central structure.

A worked example shows how a consolidation model is chosen.

Suppose a group has a US parent and four subsidiaries: two domestic, one in the eurozone, and one held at 80 percent. The parent sells inventory to the eurozone subsidiary during the year, and leadership wants both audited statutory statements and a segment-level management view. Consolidation here must eliminate the intercompany sale, translate the euro subsidiary under ASC 830 and IAS 21, and attribute 20 percent of the partly owned subsidiary to non-controlling interest.

For a group this size, consolidating inside the ERP often fits: the eliminations and currency translation run on the same ledger that recorded the underlying transactions, so the statutory close stays on one audit trail. The segment-level management view can then be built in an FP&A or EPM platform that reads consolidated balances. A dedicated close-and-consolidation platform would be the call instead if the group spanned many more entities and multiple statutory frameworks. The intercompany sale in this example is exactly the kind of transaction covered in the Lightbridge ERP guide to intercompany accounting.

ASC 810 and IFRS 10 govern consolidation regardless of the model.

ASC 810, Consolidation, is the US GAAP standard governing when one entity consolidates another and how non-controlling interests are presented. Its international counterpart is IFRS 10, Consolidated Financial Statements. Currency translation follows ASC 830 and IAS 21. These standards apply no matter where the consolidation physically runs, so the model you choose is a question of tooling and architecture, not of which rules apply. The authoritative US text lives at asc.fasb.org.

The practical trade-offs follow from that. Consolidating inside the ERP maximizes single source of truth and audit trail. A dedicated close-and-consolidation platform maximizes statutory and multi-GAAP depth and scale. An FP&A or EPM platform maximizes management flexibility but is not the statutory book of record. For the product-level mechanics of consolidating a multi-subsidiary group inside one platform, the Lightbridge ERP guide to NetSuite OneWorld shows how ERP-native consolidation works.

Lightbridge ERP selects the right consolidation architecture, vendor-neutral.

Choosing a consolidation model is a high-stakes architecture decision, and the wrong venue shows up later as a slow close, manual currency translation, and intercompany differences that never tie out. Lightbridge ERP is an independent, vendor-neutral ERP advisory firm with deep in-house finance expertise across consolidation, multi-book accounting, intercompany, and currency translation. It maps your entity structure, ownership, GAAP and statutory requirements, and close timeline, then recommends where consolidation should run and configures it to tie out automatically and stay audit-ready.

Because Lightbridge accepts no vendor kickbacks, no reseller quotas, and no partner-tier incentives, its architecture advice is driven by fit rather than commission. A structured selection is the right starting point when the underlying system still needs to be chosen, and ERP consulting covers the design and configuration once the model is set.

Financial consolidation models: frequently asked questions

What is financial consolidation in simple terms?: Financial consolidation is the process of combining the financial statements of a parent company and the subsidiaries it controls into one set of statements that presents the group as a single economic entity. Practically, it means adding up the ledgers, removing any transactions between group members, translating subsidiaries that report in other currencies, and carving out the share of any subsidiary the parent does not fully own. The result is consolidated statements that show only the group's dealings with the outside world. Lightbridge ERP helps finance teams choose where this consolidation should run and configure it so it ties out automatically.
What are the main financial consolidation models?: There are two ways to frame consolidation models. The first is structural: a hub-and-spoke model, where subsidiaries report into a central entity that performs eliminations and translation, versus more distributed approaches. The second, and usually more decisive, is architectural: where the consolidation actually happens. The three common venues are inside the ERP, such as NetSuite OneWorld, in an FP&A or EPM planning platform, or in a dedicated close-and-consolidation platform. Most consolidation decisions come down to that venue question, because it determines single source of truth, statutory depth, currency handling, and how much flexibility the team has for management views.
Should we consolidate inside the ERP or in a separate platform?: It depends on the depth of statutory reporting you need and how much you value a single source of truth. Consolidating inside the ERP keeps consolidation on the same transactional ledger, so the audit trail runs unbroken from journal entry to consolidated statement and intercompany and currency are handled natively. That suits many mid-market and growing groups. A dedicated close-and-consolidation platform earns its place when the group spans many entities, multiple GAAP or statutory frameworks, and complex ownership changes that the ERP alone cannot model cleanly. An FP&A or EPM platform is the right home for management consolidation and planning, but it is generally not the statutory book of record. Lightbridge ERP selects the architecture that fits the group rather than a preset answer.
How does financial consolidation handle foreign currency?: When subsidiaries keep their books in different functional currencies, consolidation translates each one into the group's presentation currency before combining. Under ASC 830 and its international counterpart IAS 21, the assets and liabilities of a foreign operation are generally translated at the closing rate and income statement items at rates approximating those at the transaction dates, with the difference recorded as a cumulative translation adjustment within equity rather than in net income. Getting the functional-currency determination, rate types, periods, and the cumulative translation account right is one of the harder parts of a multi-currency consolidation, and it is a common source of audit questions. The consolidation venue you choose should automate this translation rather than leave it to spreadsheets.
How are intercompany transactions handled during consolidation?: Because consolidated statements present the group as one entity, any transaction between group members has to be eliminated, otherwise the group would appear to do business with itself. That includes intercompany sales and purchases, intercompany loans and interest, and intercompany receivables and payables, along with unrealized profit sitting in inventory that has not yet been sold outside the group. Eliminations are where many consolidations stall, because the two sides of an intercompany transaction must match exactly across entities, currencies, and periods. A consolidation architecture that matches and eliminates intercompany activity automatically removes most of that friction.
What is the difference between management consolidation and statutory consolidation?: Statutory consolidation produces the legal, audited financial statements the group files, following a defined framework such as US GAAP or IFRS, with full eliminations, currency translation, and non-controlling interest. Management consolidation produces internal reporting tailored to how leaders run the business: alternative hierarchies, segments, allocations, and rolling forecasts, often on a faster cycle. The same group frequently needs both. FP&A and EPM platforms shine at management consolidation, while statutory consolidation tends to live in the ERP or a dedicated close-and-consolidation system. Confusing the two leads groups to either over-engineer planning tools or stretch the statutory book of record into reporting it was not built for.
How does Lightbridge ERP help select a consolidation model?: Lightbridge ERP is an independent, vendor-neutral ERP advisory firm with deep in-house finance expertise across consolidation, multi-book accounting, intercompany, and currency translation. It maps your entity structure, ownership percentages, GAAP and statutory requirements, and close timeline, then recommends where consolidation should run: inside the ERP, in an FP&A or EPM platform, in a dedicated close system, or a combination. Because Lightbridge accepts no vendor kickbacks, no reseller quotas, and no partner-tier incentives, the architecture recommendation is driven by fit rather than commission. This guide is general information, not accounting, tax, or legal advice; confirm treatment with your auditor or accountant.

From comparing consolidation models to running the right one.

When the question shifts from which consolidation model fits to how your ERP should run it, Lightbridge ERP designs the architecture and configures the system, audit-ready and automated.

Talk to an ERP advisor Multi-entity accounting