How Does Consolidation Software Automate Intercompany Elimination Entries?

Consolidation software automates intercompany elimination entries by matching intercompany transactions across entities, applying elimination rules set up in advance, and posting the offsetting journal entries at the consolidation layer instead of requiring an accountant to build them by hand every month. When one entity sells inventory to another entity in the same group, both sides record the transaction on their own books. Left alone, the group's consolidated financials would double count that revenue and expense. Consolidation software identifies the matching intercompany accounts, calculates the elimination amount, and posts the entry without touching either entity's general ledger.

For a controller managing several subsidiaries, that difference shows up directly in how many days the close takes and how confident the numbers are once it's done.

What Are Intercompany Elimination Entries?

Intercompany elimination entries are the journal entries that remove transactions and balances between related entities from a consolidated financial statement, so the group's financials reflect only activity with outside parties. Under U.S. GAAP, ASC 810 requires that intra-entity balances and transactions, including intercompany sales, loans, interest, and dividends, be eliminated in full when preparing consolidated statements. IFRS 10 sets an equivalent requirement for groups reporting under International Financial Reporting Standards. Neither standard prescribes exactly how the elimination should be calculated or posted. Both simply require that the consolidated result be free of intercompany activity.

That gap between “must be eliminated” and “how to eliminate it” is where most of the manual work in a close tends to live.

The categories of intercompany activity that most often require elimination include:

• Intercompany sales and purchases (revenue and cost of goods sold)
• Intercompany loans and the related interest income or expense
• Intercompany dividends
• Investment in a subsidiary, offset against that subsidiary's equity
• Unrealized profit still sitting in inventory at period end

Why Manual Elimination Entries Slow Down the Close

Multi-entity organizations tend to run into the same three problems every month:

• Each subsidiary may run on a different ERP with its own chart of accounts, so intercompany accounts don't map to each other automatically.
• Matching intercompany balances by hand in spreadsheets is slow and leaves room for error, particularly when volume is high or subsidiaries close on different schedules.
• Cross-currency intercompany balances have to be translated before they can be eliminated, and IAS 21 requires that monetary intercompany items be translated at the closing rate, which adds a step most spreadsheet processes handle inconsistently.

According to APQC's benchmarking research across more than 2,000 organizations, the median company takes roughly six business days to close its books each month. Multi-entity groups with meaningful intercompany activity routinely land above that median, because reconciliation and elimination work has to be finished before the rest of the close can proceed.

Intercompany Elimination Entries Example: A Step-by-Step Walkthrough

The mechanics are easier to see in a worked example than in the standard's language alone. The three examples below cover the transaction types a controller is most likely to encounter.

Example 1: Eliminating an Intercompany Sale

Company A (the parent) sells $50,000 of finished goods to Company B (a wholly owned subsidiary) at a cost of $38,000. At period end, Company B has not yet resold that inventory outside the group.

Entity-level books before elimination.

At consolidation, the elimination entry removes the intercompany revenue and cost of goods sold, then removes the $12,000 of profit still embedded in Company B's inventory, since the group hasn't sold anything to an outside customer yet:

• Debit Intercompany Revenue: $50,000
• Credit Intercompany COGS: $38,000
• Credit Inventory (unrealized profit): $12,000

This is consistent with the elimination principle in ASC 810-10-45-1 and the equivalent guidance under IFRS 10: any profit on a transaction within the group has to come out until it's realized through a sale to someone outside the group.

Example 2: Eliminating an Intercompany Investment

Company A holds a $200,000 investment in Company B, which matches Company B's $200,000 in paid-in capital. Left on the books, the group's consolidated equity would show that $200,000 twice: once as Company A's investment and once as Company B's capital.

• Debit Subsidiary Paid-In Capital: $200,000
• Credit Investment in Subsidiary: $200,000

This keeps the consolidated balance sheet from double counting capital that only exists on paper between two entities in the same group.

Example 3: Eliminating an Intercompany Loan Across Currencies

Company A lends Company B funds in a different functional currency. Before the loan balance can be eliminated, both sides need to be translated to the group's reporting currency under IAS 21. If the elimination doesn't fully net to zero after translation, the gap is usually a timing difference between when each entity revalued the balance, not an accounting error. Isolating that difference by hand, across dozens of intercompany pairs, is where manual close processes tend to lose the most time.

How Consolidation Software Automates the Elimination Process

The examples above involve two entities each. Multiply that by a dozen subsidiaries, several ERPs, and multiple currencies, and manual elimination stops being realistic on a monthly cadence. Consolidation software addresses this in three ways.

Automated Elimination Rules Instead of Manual Journal Entries

Rather than rebuilding elimination entries by hand each month, a controller sets up matching logic once. Solver's Automated Elimination Rules identify intercompany pairs by account, entity, and transaction type, then generate the elimination entry automatically at close. The underlying general ledgers stay untouched; only the consolidation layer reflects the elimination, which keeps individual entity books intact for local statutory reporting.

Multi-Entity, Multi-Currency Consolidation

QuickStart integrations connect directly to ERPs including Microsoft Dynamics 365 Business Central, Sage Intacct, and Acumatica, so each subsidiary's chart of accounts can be mapped to a common corporate structure without an IT project. Automatic currency translation applies the correct rate to each intercompany balance before elimination, and the platform supports multiple fiscal calendars for subsidiaries that don't close on the same schedule. You can see how these connectors work on the integrations page.

A Documented Audit Trail for Every Elimination

Every automated elimination is logged, so an auditor or controller can see which rule fired, which accounts it touched, and when. That audit trail replaces the version-control guesswork that comes with spreadsheet-based eliminations, where it's often unclear which tab reflects the final adjustment. Data feeding the consolidation comes from a single data warehouse connecting each subsidiary's source system, so the elimination rules are working from one consistent version of the data rather than reconciled exports.

Solver Copilot in Action

Consolidation questions tend to surface in the middle of close, when there's no time to wait on a support ticket. Solver Copilot is built for that moment.

The Help Agent answers application questions on the spot, walking a controller through where to check an elimination rule, how a chart of accounts mapping is configured, or why a particular subsidiary isn't picking up a currency translation, without leaving the application.

The Analysis Agent works on the data itself. It scans consolidated balances for anomalies, such as an intercompany balance that grew unexpectedly or an elimination that didn't fully clear, and surfaces the exception before it turns into a line item nobody can explain during the close review.

What Faster Eliminations Mean for Your Close

Automating elimination entries doesn't just save time on one task. It removes a dependency that other close activities are often waiting on: intercompany balances usually have to be settled before consolidated reporting, variance analysis, or board reporting can start. Pre-built, industry-specific consolidation templates in the Template Marketplace give finance teams a starting structure for elimination rules and chart of accounts mapping, rather than building the framework from a blank page.

None of this replaces a controller's judgment. Goodwill calculations, non-controlling interest attribution, and the percentage of unrealized profit to eliminate still require review. What automation removes is the manual journal-building work underneath those decisions, so the controller's time goes toward the calls that actually require it.