What is multi-entity accounting?

Multi-entity accounting is the practice of keeping separate accounting records for each legal entity in a corporate group, then combining those records into one consolidated set of financial statements for the parent. Each subsidiary, division, or holding company posts to its own ledger, and the group rolls them up after standardizing the chart of accounts, translating foreign currencies, and removing transactions between the entities. It applies to multi-subsidiary companies, holding-company structures, and organizations with foreign operations. This guide is general information, not accounting, tax, or legal advice.

What are the steps in financial consolidation?

Financial consolidation generally runs in four steps. First, standardize or map each entity chart of accounts so balances aggregate consistently. Second, translate any entity whose functional currency differs from the parent reporting currency into that reporting currency under ASC 830. Third, eliminate intercompany transactions and balances so the group does not count revenue or assets it owes to itself. Fourth, roll the standardized, translated, eliminated balances up into one consolidated financial statement under ASC 810. Lightbridge ERP configures these steps inside the ERP so consolidation runs in the system rather than in spreadsheets.

What is the difference between functional currency and reporting currency?

The functional currency is the currency of the primary economic environment in which an individual entity operates, typically the currency in which it earns and spends most of its cash. The reporting currency is the currency in which the parent presents its consolidated financial statements. When an entity functional currency differs from the reporting currency, ASC 830 requires translation: assets and liabilities at the current period-end rate, income statement items at the average rate, and equity at historical rates. The balancing figure is the cumulative translation adjustment.

What is the cumulative translation adjustment (CTA)?

The cumulative translation adjustment is the balancing amount that arises when an entity financial statements are translated from its functional currency into the parent reporting currency under ASC 830. Because assets and liabilities translate at the current rate while equity translates at historical rates, the two sides do not match, and the difference is the CTA. It is reported in other comprehensive income within equity, not in net income, which keeps currency-translation movement out of reported earnings. This differs from remeasurement gains and losses, which do flow through net income.

What are intercompany eliminations?

Intercompany eliminations are consolidation entries that remove transactions and balances between entities in the same group. Common examples include intercompany sales and the matching purchases, intercompany loans and the matching receivables and payables, and unrealized profit in inventory still held within the group. Eliminations prevent the consolidated statement from double-counting revenue or showing assets and liabilities the group effectively owes to itself. Only third-party activity should survive into the consolidated financials. Our intercompany accounting guide covers the elimination mechanics in detail.

When does a business need multi-entity accounting?

A business needs multi-entity accounting once it operates more than one legal entity that must report separately: multiple subsidiaries, a holding-company structure, foreign operations with their own functional currency, or entities created for tax, regulatory, or acquisition reasons. If a company runs a single legal entity, it can often track segments with classes, departments, locations, or dimensions inside one ledger instead. The dividing line is legal separateness. Separate legal entities generally require separate books and a consolidation process; internal business units usually do not.

How does ERP handle multi-entity accounting compared to spreadsheets?

An ERP system holds every entity in one database with a shared or mapped chart of accounts, applies currency translation with current rate tables, runs intercompany eliminations as repeatable consolidation rules, and produces consolidated statements on demand with an audit trail. Spreadsheets require manual rekeying, manual rate updates, and manual elimination entries every period, which is slow and error-prone as entity count grows. The ERP approach makes consolidation faster to close and far easier to audit. Our what-is-ERP guide explains the broader system, and NetSuite OneWorld is one platform that handles multi-subsidiary consolidation natively.

What is the difference between consolidation and a single ledger with classes or departments?

A single ledger with classes, departments, or locations tracks performance by internal segment inside one legal entity, with no separate financial statements per segment and no intercompany eliminations. Consolidation, by contrast, combines multiple separate legal entities, each with its own complete books, into one parent-level statement, and it requires currency translation and intercompany elimination along the way. Segments answer how parts of one company perform; consolidation answers how a group of distinct legal entities looks as a whole. Many groups use both at once.

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

Last updated June 2026.

Multi-Entity Accounting: Consolidation Explained

Lightbridge ERP defines multi-entity accounting as the practice of keeping separate books for each legal entity in a group and then combining them into one consolidated financial statement. It standardizes charts of accounts, translates foreign currencies, eliminates intercompany activity, and rolls each entity up to a single parent view.

Talk to an ERP advisor Intercompany accounting

This guide is general information, not accounting, tax, or legal advice. The authoritative text is the FASB Accounting Standards Codification at asc.fasb.org, including ASC 810 on consolidation and ASC 830 on foreign currency matters.

Multi-entity accounting keeps separate books per legal entity, then consolidates them.

Multi-entity accounting is what a company does when it runs more than one legal entity. Each subsidiary, holding company, or foreign operation maintains its own complete set of books. The group then combines those books into one consolidated financial statement for the parent. The separate ledgers satisfy the legal and tax reporting each entity owes on its own, and the consolidation shows the economic picture of the group as a whole.

The driver is legal separateness, not size. A single legal entity, however large, can track internal performance with classes, departments, or locations inside one ledger. The moment a second legal entity exists, separate books and a consolidation process generally follow. The codification governs the result: ASC 810 sets out the consolidation requirements, and ASC 830 governs how foreign-currency entities are brought into the parent reporting currency.

The work of multi-entity accounting is therefore less about recording day-to-day transactions and more about the rollup: aligning charts of accounts, translating currencies, removing intercompany activity, and combining the result. Each of those steps is a place where a manual process breaks and where an ERP system earns its keep.

Financial consolidation runs in four steps, in order.

Consolidation is a sequence, not a single posting. The four steps below take a set of separate entity ledgers and turn them into one parent-level statement. Each step depends on the one before it: you cannot translate currency cleanly without a standardized chart, and you cannot roll up without first eliminating what the entities owe each other.

Step 1

Standardize the chart of accounts

Each entity posts to a shared or mapped chart of accounts so like balances aggregate cleanly. Multi-entity accounting depends on this alignment: a rollup is only meaningful when every entity classifies revenue, expense, asset, and liability the same way.

Step 2

Translate currencies into the reporting currency

Entities with a foreign functional currency are translated into the parent reporting currency under ASC 830. Assets and liabilities use the current rate, income statement items use the average rate, and the difference accumulates as a separate equity item.

Step 3

Eliminate intercompany activity

Transactions between group entities (intercompany sales, loans, and balances) are removed so the consolidated statement reflects only third-party activity. Without elimination, multi-entity accounting double-counts revenue and inflates assets the group owes to itself.

Step 4

Roll up to the consolidated parent

The standardized, translated, eliminated entity balances combine into one set of consolidated financials under ASC 810. The rollup can stop at a regional subtotal or run to the ultimate parent, depending on how the legal structure is tiered.

These four steps are the spine of multi-entity accounting under ASC 810. Step three, intercompany elimination, is detailed in our intercompany accounting guide. Where the consolidation runs, inside the ERP versus an FP&A platform versus a dedicated close-and-consolidation platform, is compared in our guide to financial consolidation models, and a partly owned subsidiary brings in a non-controlling interest. On the platform side, NetSuite OneWorld is one ERP that runs multi-subsidiary consolidation, currency translation, and eliminations natively.

Currency translation under ASC 830 routes the CTA through equity, not earnings.

When entities in a group operate in different currencies, consolidation has to express them all in one reporting currency. ASC 830 governs how. The pivotal concept is the functional currency: the currency each entity primarily transacts in. The three cards below set out functional currency, the translation method that applies when it differs from the parent reporting currency, and where the resulting cumulative translation adjustment lands. For a deeper treatment of translation versus remeasurement and the cumulative translation adjustment, see the guide to foreign currency translation and the CTA.

Functional currency

Under ASC 830, the functional currency is the currency of the primary economic environment in which an entity operates, usually where it generates and spends cash. Each entity in a group can have its own functional currency. It is the starting point for every translation decision in multi-entity accounting.

Reporting currency and translation

When an entity functional currency differs from the parent reporting currency, the current-rate method applies: assets and liabilities at the period-end rate, income statement at the average rate, and equity at historical rates. The balancing difference is the cumulative translation adjustment.

CTA in other comprehensive income

The cumulative translation adjustment (CTA) is recorded in other comprehensive income within equity, not in net income. Routing it through OCI keeps exchange-rate movement on currency translation out of reported earnings, a distinction ASC 830 draws between translation and remeasurement.

ASC 830 draws a sharp line between translation and remeasurement. Translation applies when an entity keeps its books in its functional currency and that currency differs from the reporting currency: the adjustment goes to the CTA in other comprehensive income. Remeasurement applies when an entity books are not kept in its functional currency: those gains and losses flow through net income. Getting the two apart is one of the most common errors in multi-entity accounting.

Intercompany eliminations remove activity the group owes to itself.

A consolidated statement should reflect only the group dealings with the outside world. When one entity sells to another, lends to another, or holds a receivable from another, that activity is real on each entity own books but is internal to the group as a whole. Intercompany eliminations strip it out so the consolidated financials are not overstated. Without elimination, intercompany sales would double-count revenue, and intercompany loans would inflate both assets and liabilities the group owes to itself.

The common eliminations are intercompany revenue against the matching purchase, intercompany receivables against the matching payables, intercompany loans against the matching debt, and unrealized profit on inventory still held inside the group. Each is a consolidation-only entry: it never touches the individual entity ledgers, which must stand on their own for statutory and tax reporting. Our intercompany accounting guide works through these elimination entries in full.

A business needs multi-entity accounting when it runs separate legal entities.

The decision is structural, not a matter of preference. If an organization operates one legal entity, it can usually track internal performance with classes, departments, locations, or dimensions inside a single general ledger. There are no separate statutory statements per segment and no intercompany activity to eliminate. Reporting by business unit is a slicing of one set of books.

Multi-entity accounting becomes necessary the moment a second legal entity exists: a new subsidiary, a holding company over operating companies, a foreign operation with its own functional currency, or an entity created for tax, regulatory, or acquisition reasons. Each legal entity must file and report on its own, so each keeps complete books, and the group consolidates them. Mistaking a multi-entity structure for a single-ledger one (or the reverse) is a frequent source of misstated consolidations and painful audits.

ERP handles multi-entity consolidation in one system; spreadsheets handle it by hand.

In a spreadsheet, every consolidation step is manual. Someone rekeys each entity trial balance, looks up and applies exchange rates, posts elimination entries by hand, and rebuilds the rollup every period. As entity count rises, the work compounds and so does the error surface: a stale rate, a missed elimination, a broken formula. The close gets slower precisely when the group is getting more complex.

An ERP system holds every entity in one database with a shared or mapped chart of accounts, maintains currency rate tables and applies translation under ASC 830 automatically, runs intercompany eliminations as repeatable rules, and produces consolidated statements on demand with a full audit trail. The result is a faster financial close and a consolidation that an auditor can trace. NetSuite OneWorld is one platform built around native multi-subsidiary consolidation; it is not the only one, and the right fit depends on the group structure.

Lightbridge ERP turns multi-entity accounting into a working consolidation process.

Understanding consolidation is one thing. Configuring an ERP so it standardizes charts, translates currencies under ASC 830, eliminates intercompany activity, and rolls every entity up correctly each period is another. Lightbridge ERP is an independent, vendor-neutral advisory firm whose senior finance professionals (CPAs, controllers, and former CFOs) design multi-entity structures that map legal-entity reality to the system that runs the books.

Because Lightbridge accepts no vendor kickbacks, no reseller quotas, and no partner-tier incentives, the platform recommendation follows fit, not commission. For organizations already on NetSuite, the practice delivers multi-subsidiary consolidation in-house. For other platforms, Lightbridge provides program governance and technical leadership while vetted partners execute. Either way, the outcome is the same: an auditable, repeatable consolidation that closes faster than a spreadsheet ever could. This page is general information, not accounting, tax, or legal advice.

Multi-entity accounting: frequently asked questions

What is multi-entity accounting?: Multi-entity accounting is the practice of keeping separate accounting records for each legal entity in a corporate group, then combining those records into one consolidated set of financial statements for the parent. Each subsidiary, division, or holding company posts to its own ledger, and the group rolls them up after standardizing the chart of accounts, translating foreign currencies, and removing transactions between the entities. It applies to multi-subsidiary companies, holding-company structures, and organizations with foreign operations. This guide is general information, not accounting, tax, or legal advice.
What are the steps in financial consolidation?: Financial consolidation generally runs in four steps. First, standardize or map each entity chart of accounts so balances aggregate consistently. Second, translate any entity whose functional currency differs from the parent reporting currency into that reporting currency under ASC 830. Third, eliminate intercompany transactions and balances so the group does not count revenue or assets it owes to itself. Fourth, roll the standardized, translated, eliminated balances up into one consolidated financial statement under ASC 810. Lightbridge ERP configures these steps inside the ERP so consolidation runs in the system rather than in spreadsheets.
What is the difference between functional currency and reporting currency?: The functional currency is the currency of the primary economic environment in which an individual entity operates, typically the currency in which it earns and spends most of its cash. The reporting currency is the currency in which the parent presents its consolidated financial statements. When an entity functional currency differs from the reporting currency, ASC 830 requires translation: assets and liabilities at the current period-end rate, income statement items at the average rate, and equity at historical rates. The balancing figure is the cumulative translation adjustment.
What is the cumulative translation adjustment (CTA)?: The cumulative translation adjustment is the balancing amount that arises when an entity financial statements are translated from its functional currency into the parent reporting currency under ASC 830. Because assets and liabilities translate at the current rate while equity translates at historical rates, the two sides do not match, and the difference is the CTA. It is reported in other comprehensive income within equity, not in net income, which keeps currency-translation movement out of reported earnings. This differs from remeasurement gains and losses, which do flow through net income.
What are intercompany eliminations?: Intercompany eliminations are consolidation entries that remove transactions and balances between entities in the same group. Common examples include intercompany sales and the matching purchases, intercompany loans and the matching receivables and payables, and unrealized profit in inventory still held within the group. Eliminations prevent the consolidated statement from double-counting revenue or showing assets and liabilities the group effectively owes to itself. Only third-party activity should survive into the consolidated financials. Our intercompany accounting guide covers the elimination mechanics in detail.
When does a business need multi-entity accounting?: A business needs multi-entity accounting once it operates more than one legal entity that must report separately: multiple subsidiaries, a holding-company structure, foreign operations with their own functional currency, or entities created for tax, regulatory, or acquisition reasons. If a company runs a single legal entity, it can often track segments with classes, departments, locations, or dimensions inside one ledger instead. The dividing line is legal separateness. Separate legal entities generally require separate books and a consolidation process; internal business units usually do not.
How does ERP handle multi-entity accounting compared to spreadsheets?: An ERP system holds every entity in one database with a shared or mapped chart of accounts, applies currency translation with current rate tables, runs intercompany eliminations as repeatable consolidation rules, and produces consolidated statements on demand with an audit trail. Spreadsheets require manual rekeying, manual rate updates, and manual elimination entries every period, which is slow and error-prone as entity count grows. The ERP approach makes consolidation faster to close and far easier to audit. Our what-is-ERP guide explains the broader system, and NetSuite OneWorld is one platform that handles multi-subsidiary consolidation natively.
What is the difference between consolidation and a single ledger with classes or departments?: A single ledger with classes, departments, or locations tracks performance by internal segment inside one legal entity, with no separate financial statements per segment and no intercompany eliminations. Consolidation, by contrast, combines multiple separate legal entities, each with its own complete books, into one parent-level statement, and it requires currency translation and intercompany elimination along the way. Segments answer how parts of one company perform; consolidation answers how a group of distinct legal entities looks as a whole. Many groups use both at once.

From separate ledgers to a consolidation that runs itself.

When the group has to consolidate correctly every period, Lightbridge ERP configures multi-entity accounting into your ERP and keeps it audit-ready. Vendor-neutral, no kickbacks, senior finance talent.

Talk to an ERP advisor Read the intercompany guide