Multi-Entity Consolidation: How to Automate a 12-Entity Close

Consolidating financial statements across multiple entities is one of the most complex processes in corporate finance. When those entities operate in different currencies, under different regulatory regimes, and with active intercompany relationships, the complexity multiplies.

Most finance teams manage this with spreadsheets and prayers. There is a better way.

Why multi-entity consolidation is so hard

A 12-entity organization faces several interlocking challenges that make consolidation painful.

Intercompany transactions. When Entity A sells to Entity B, both record revenue and expense. At the consolidated level, these transactions must be eliminated. For 12 entities, that means tracking and eliminating IC activity across 66 possible entity pairs. Miss one, and your consolidated revenue is overstated.

Currency translation. Entities reporting in different functional currencies must be translated to the parent's reporting currency under ASC 830. Balance sheet items use the closing rate. Income statement items use the average rate. Equity uses historical rates. Each rate type requires different treatment, and getting it wrong flows through to CTA (cumulative translation adjustment).

Minority interests. Partially owned subsidiaries require calculating non-controlling interest at every level of the ownership hierarchy. Cascading ownership - where Entity A owns 80% of Entity B, which owns 60% of Entity C - makes the math non-trivial.

Timing. All entities must close before consolidation can begin. One late entity holds up the entire process.

The spreadsheet trap

Most mid-market companies consolidate in Excel. The controller maintains a consolidation workbook with tabs for each entity, elimination entries, currency translation, and the consolidated output. The workbook works. Until it does not.

Common failure modes include formula errors that go undetected for quarters, hardcoded elimination entries that should have been updated, translation rates applied to the wrong period, and broken links between entity-level workbooks and the consolidation file.

These are not hypothetical risks. They are the reason restatements happen.

Automating intercompany elimination

The first step in automating consolidation is handling intercompany elimination systematically.

Arvexi tracks intercompany transactions at the entity pair level. When Entity A records an IC receivable from Entity B, and Entity B records the corresponding IC payable, Arvexi matches them automatically. At consolidation, elimination journal entries are generated without manual intervention.

When IC balances do not match - and they often do not, due to timing differences or FX rate discrepancies - Arvexi flags the variance and provides the reconciliation detail. The accountant resolves the exception, not the routine.

Automating currency translation

Currency translation under ASC 830 requires three exchange rate types applied to different account categories. Getting this right manually across 12 entities and multiple periods is where errors compound.

Arvexi maintains an exchange rate repository with closing rates, average rates, and historical rates for each period. During consolidation, the platform automatically applies the correct rate type to each account based on its financial statement classification.

Balance sheet accounts are translated at the period-end closing rate. Income statement accounts use the weighted average rate for the period. Equity accounts use the historical rate from the date of investment. The cumulative translation adjustment is calculated automatically and posted to other comprehensive income.

When exchange rates change significantly between periods, Arvexi surfaces the translation impact so your team can explain the variance in management reporting.

Automating the consolidation workflow

Beyond IC elimination and currency translation, a full consolidation involves several additional steps that benefit from automation.

Ownership and hierarchy management. Arvexi maintains the legal entity hierarchy, ownership percentages, and consolidation method (full, proportional, equity method) for each entity. Changes to the structure - acquisitions, dispositions, reorganizations - are reflected in the consolidation logic automatically.

Non-controlling interest. For partially owned subsidiaries, Arvexi calculates the NCI share of net income and equity at each level of the hierarchy. Cascading ownership math is handled by the system, not by the controller.

Consolidation journal entries. Beyond IC eliminations, consolidation often requires goodwill adjustments, fair value step-ups, and other acquisition-related entries. Arvexi tracks these as recurring consolidation adjustments that post automatically each period.

Consolidated trial balance and financial statements. The output is a consolidated trial balance and financial statements that roll up all entity data, reflect all eliminations and translations, and calculate all derived amounts.

A practical timeline

Here is what consolidation looks like for a 12-entity organization running Arvexi:

Pre-close. IC matching runs continuously. By the time the period ends, most IC differences are already identified and resolved. Exchange rates are loaded automatically from the rate feed.

Day 1-2 of close. Entities close their books and certify. Arvexi tracks certification status across all 12 entities in the close manager, with visibility into which entities are complete and which are still in progress.

Day 3. Once all entities are certified, consolidation runs. IC eliminations, currency translations, NCI calculations, and consolidation adjustments are applied automatically. The consolidated trial balance is available within minutes, not days.

Day 4. The consolidation team reviews the output, validates key balances, and signs off on the consolidated financial statements.

Four days from period-end to consolidated financials. For organizations that previously took two weeks, this is transformational.

Consolidation is not optional

Every multi-entity organization must consolidate. The question is whether you do it in a system designed for the task or in a spreadsheet held together with duct tape and institutional memory.

Arvexi handles the mechanical complexity - the IC matching, the rate lookups, the ownership math - so your team can focus on the judgment calls that actually require their expertise.

See Arvexi's consolidation in action.