Intercompany Accounting for Holding Companies — Eliminations, Journal Entries, and System Design (2026)
Most accounting software comparison sites evaluate platforms the same way: build a feature checklist, count the checkboxes, declare a winner.
That approach produces recommendations that look correct on paper and fail in practice.
Multi-entity accounting is not a feature problem. It is a structural alignment problem. A platform that handles consolidation cleanly for a 3-entity family office will collapse under a 15-entity acquisition vehicle — even if both platforms check every box on a standard comparison grid. The features are the same. The structural architecture is not.
This page explains exactly how we evaluate multi-entity accounting software — what we measure, how we measure it, what we deliberately exclude, and why our framework produces different recommendations than most comparison resources in this space.
If you are using this site to make a real software decision, understanding our methodology will help you use our recommendations more effectively.
Who Evaluates the Software on This Site
Our platform assessments are produced by finance professionals with direct experience in multi-entity accounting environments — group consolidation, intercompany transaction management, period-close operations, and ERP implementation across holding company structures.
We cross-reference four sources for every platform assessment:
Vendor documentation and product specifications. We read the technical documentation — not just the marketing pages. Feature claims are verified against product documentation before being included in any comparison.
G2, Gartner Peer Insights, and Capterra reviews. We analyze user reviews specifically from finance professionals at multi-entity organizations — filtering for reviews that describe consolidation workflows, intercompany management, and close cycle experience. We weight negative reviews heavily because they reveal where platforms actually break down.
Implementation partner data. We consult with accounting firms and ERP implementation partners who deploy these platforms for holding company and multi-entity clients regularly. Practitioners who implement the same platform 20 times per year see failure modes that no marketing material will reveal.
Real-world deployment patterns. We track which platforms organizations are migrating from, which they are migrating to, and at what entity count and complexity level the migrations occur. These patterns are more informative than any feature comparison.
We do not accept payment for platform placement, positive review framing, or featured positions in comparison tables. Affiliate relationships exist with several platforms on this site — those relationships are disclosed on every relevant page. They do not determine rankings or recommendations.
Our Core Evaluation Principle
We evaluate software based on structural alignment — the degree to which a platform’s architecture matches the actual structural requirements of multi-entity and holding company accounting.
A platform is structurally aligned when:
- Consolidation happens inside the system, not in a spreadsheet outside it
- Intercompany transactions are automated and eliminated without manual intervention
- The system understands ownership relationships and uses them to drive consolidation logic
- Adding a new entity does not require rebuilding configuration from scratch
- The operational scope of the platform is proportionate to the structural complexity of the organization
A platform is structurally misaligned when any of these conditions are not met — regardless of how many features it has or how strong its brand recognition is.
The consequence of structural misalignment is not immediate failure. It is progressive fragility: close cycles that lengthen as entity count grows, manual reconciliation that consumes more controller time each period, elimination errors that accumulate, and eventually a replatforming event that costs $150,000–$300,000 and 6–12 months of implementation time.
Evaluating software through a structural lens reduces this probability. That is the outcome our methodology is designed for.
The Five Dimensions We Evaluate
Every platform reviewed on this site is assessed across five dimensions. These are not equal in weight — consolidation architecture and intercompany automation are the two most consequential for most multi-entity organizations, and they receive the most detailed evaluation.
Dimension 1: Consolidation Architecture
The core question: Does consolidation happen inside the system — or does the system produce data that must be consolidated outside it?
This is the fundamental divide in multi-entity accounting software. On one side: platforms where the consolidation engine is native, where consolidated financial statements are produced directly from the system’s ledger data, where elimination rules are configured once and run automatically. On the other: platforms where entities are managed separately and consolidation requires exporting data, aggregating it externally, applying eliminations manually, and producing consolidated output in a tool the accounting system was never designed to drive.
QuickBooks is the clearest example of the second category. Managing three company files in QuickBooks and consolidating them in Excel is not multi-entity accounting software — it is three single-entity accounting systems with a manual consolidation process layered on top.
What we assess under this dimension:
In-system consolidation workflows. Can the system produce a consolidated balance sheet, consolidated income statement, and consolidated cash flow statement natively — without data export or external aggregation? This is the baseline requirement. Any platform that cannot do this is not a multi-entity accounting platform regardless of other features.
Consolidation hierarchy management. Can the system model the group structure — parent, subsidiaries, sub-subsidiaries — and use that hierarchy to drive which entities roll up into which consolidation? Can that hierarchy be modified when a new entity is added or an ownership structure changes?
Audit trail quality. Every elimination entry, every currency translation adjustment, every period-close journal must be documented with an immutable audit trail. For organizations subject to external audit, the quality of the consolidation audit trail directly affects audit fees and timeline.
Reporting flexibility. Can the system produce consolidated and entity-level reporting simultaneously, with drill-down capability, without separate report runs? The ability to move fluidly between group consolidated view and individual entity view in a single report is a meaningful operational differentiator.
How platforms compare on this dimension:
| Platform | Consolidation Location | Elimination Automation | Audit Trail Quality |
|---|---|---|---|
| NetSuite OneWorld | Native — in system | Automated, rule-based | Comprehensive |
| Sage Intacct | Native — in system | Automated, rule-based | Strong |
| Lucanet | Native — specialist consolidation | Automated, rule-based | Best-in-class |
| SAP S/4HANA | Native — Group Reporting module | Fully automated | Best-in-class |
| Dynamics 365 Finance | Native — consolidation module | Automated | Strong |
| QuickBooks Enterprise | External — requires Excel | Manual | Inadequate |
| Xero | External — requires add-on | Manual or add-on dependent | Limited |
[See full platform consolidation comparison →]
Dimension 2: Intercompany Automation
Intercompany accounting is the most fragile point in multi-entity environments — and the most reliable indicator of whether a platform will scale with an organization or constrain it.
The core question: When two entities within the group transact with each other, does the system automate both sides of the transaction and schedule the elimination automatically — or does this require manual intervention?
The intercompany transaction types that must be automated in a genuine multi-entity platform:
Intercompany billing and cost allocation. When a shared services entity charges management fees, IT costs, or HR costs to operating subsidiaries, the system should generate the revenue entry in the charging entity and the expense entry in the receiving entity simultaneously. Manual creation of both sides of these recurring transactions is a direct multiplier on period-close work.
Intercompany loan management. When the parent lends funds to a subsidiary, the intercompany loan creates a receivable in the parent and a payable in the subsidiary. Interest accruals on that loan create income in the parent and expense in the subsidiary. The system should manage this automatically — including accrual calculations — with elimination of both the balance and the interest at consolidation.
Intercompany trade transactions. When Entity A sells goods or services to Entity B, the revenue in Entity A and the cost in Entity B must both be eliminated at consolidation. If Entity B has not yet resold the goods externally, the unrealized profit must also be eliminated. This unrealized profit elimination is where many mid-market platforms require manual journal entries.
Intercompany matching. Before eliminations can be processed, intercompany balances must agree between entities. In practice they rarely match perfectly at period end — timing differences, cut-off entries, and transaction disputes create discrepancies. The system should identify these discrepancies automatically and route them for resolution rather than leaving the controller to manually reconcile entity pairs at period end.
What we assess under this dimension:
- Does the system generate dual-sided intercompany entries automatically?
- Is intercompany billing configured by rule or created manually each period?
- Does the elimination engine identify and eliminate all intercompany relationships automatically?
- Does the system handle unrealized profit elimination on intercompany inventory transfers?
- Is there an intercompany matching/discrepancy resolution workflow?
- How does the system handle intercompany transactions denominated in different currencies?
How platforms compare on this dimension:
| Platform | Auto Dual-Sided Entries | Unrealized Profit Elimination | Intercompany Matching |
|---|---|---|---|
| NetSuite OneWorld | ✅ Yes | ✅ Automated | ✅ Built-in |
| Sage Intacct | ✅ Yes | ⚠️ Manual configuration | ⚠️ Limited |
| SAP S/4HANA | ✅ Yes | ✅ Automated | ✅ Best-in-class |
| Lucanet | ⚠️ Overlay on GL | ✅ Automated | ✅ Strong |
| Prophix | ✅ Yes | ✅ Automated | ✅ Strong |
| Dynamics 365 | ✅ Yes | ✅ Automated | ⚠️ Moderate |
| Xero | ❌ No | ❌ No | ❌ No |
| QuickBooks | ❌ No | ❌ No | ❌ No |
Dimension 3: Ownership and Control Modeling
Multi-entity environments are defined by ownership relationships. The accounting system must understand those relationships — not just maintain separate entity ledgers.
The core question: Does the system model ownership percentages and use them to drive consolidation logic, or does it treat every entity as an isolated file without awareness of the relationships between them?
This dimension matters most for organizations with any of the following:
- Subsidiaries that are not 100% owned (minority shareholders / NCI)
- Subsidiaries that themselves own other subsidiaries (multi-tier ownership chains)
- Ownership percentages that change due to acquisitions or disposals
- Equity method investments in associates (20–50% ownership with significant influence)
For 100%-owned operational multi-entity structures — where ownership complexity is minimal — this dimension is less critical. Every platform with native multi-entity support handles straightforward 100% ownership consolidation adequately.
For holding company structures with any ownership complexity, this dimension is where the vast majority of mid-market platforms fail.
What we assess under this dimension:
NCI automation. When a subsidiary is partially owned by external shareholders, the system must attribute the minority share of net income and equity to the non-controlling interest balance automatically — based on ownership percentage configured in the system. Manual NCI calculation is an error-prone manual process that scales poorly and creates audit risk.
Multi-tier ownership handling. When Parent owns 75% of Sub A, and Sub A owns 60% of Sub B, the effective group ownership of Sub B is 45%. The NCI at the Sub B level, from the group perspective, is 55%. This calculation — and its reflection in the consolidated financial statements — must be handled by the system automatically. Most mid-market platforms cannot do this.
Step acquisition support. When a holding company acquires additional shares in a subsidiary mid-year — moving from 40% to 55% ownership, crossing the control threshold — the accounting treatment changes materially. The investment moves from equity method to full consolidation. A step acquisition entry is required. The system must handle this transition, including goodwill recognition on the acquisition date, without requiring entirely manual treatment.
Equity method investment support. Associates — entities where the holding company holds 20–50% and has significant influence but not control — are accounted for under the equity method. The holding company recognizes its proportionate share of the associate’s net income as a single line in the consolidated P&L, and carries the investment at cost plus accumulated share of post-acquisition earnings. Native equity method support is a requirement for most holding structures eventually.
[See holding company accounting software for complex ownership structures →]
Dimension 4: Scalability Without Structural Rework
A platform that works well at 3 entities but requires significant rework at 12 is not a scalable solution — it is a temporary solution with a replatforming event embedded in its future.
The core question: What is the actual friction of adding a new entity to the system — and does that friction increase non-linearly as entity count grows?
What we assess under this dimension:
Entity onboarding friction. Adding a new subsidiary should require: creating the entity record, mapping it into the consolidation hierarchy, configuring its intercompany relationships with existing entities, and mapping its chart of accounts to the group chart. For a well-designed platform, this is a matter of hours to days. For a poorly designed platform, each new entity requires reconfiguring elimination rules across the entire group structure.
Chart of accounts scalability. The group chart of accounts must be designed to support both entity-level detail and consolidated aggregation — without requiring restructuring every time a new entity is added. Platforms with rigid chart of accounts frameworks create increasing friction as entity count grows.
Consolidation rule scalability. As entity count grows and intercompany relationships multiply, the elimination rule library grows. Platforms where each new intercompany relationship requires manual rule creation — rather than rule derivation from entity configuration — scale poorly.
Reporting architecture durability. The reporting framework configured at go-live should still be valid at 3x the original entity count without significant rearchitecting. We evaluate whether the reporting infrastructure is designed for growth or optimized for the initial state.
The replatforming cost reality:
Organizations that select an undersized platform and replatform 3–5 years later incur:
| Cost Component | Typical Range |
|---|---|
| New implementation (partner fees) | $75,000–$200,000 |
| Data migration from old platform | $30,000–$80,000 |
| Internal finance team disruption | $50,000–$150,000 |
| Parallel running period | $20,000–$40,000 |
| Chart of accounts redesign | $15,000–$40,000 |
| Total replatforming cost | $190,000–$510,000 |
This is the cost of selecting incorrectly once. It is the primary argument for selecting based on 5-year structural projection rather than current state.
Dimension 5: Operational Scope vs Financial Control Fit
Not every multi-entity organization needs a full ERP. Selecting one when a finance-first platform is appropriate introduces cost, complexity, and implementation risk that is not justified by the organizational structure.
The core question: Does the operational scope of the platform match the operational requirements of the organization — or does it introduce unnecessary weight?
What we assess under this dimension:
Finance-first vs ERP scope. For holding companies and investment vehicles whose subsidiaries manage their own operations independently, a finance-first consolidation platform (Sage Intacct, Lucanet, Prophix) typically delivers better ROI than a full ERP. The consolidation capability is equivalent or superior. The cost is substantially lower. The implementation is faster. The ongoing administrative burden is smaller.
Full ERP scope (NetSuite, SAP, Dynamics 365) becomes appropriate when the entities within the group have operational requirements — inventory management, procurement, manufacturing, multi-site logistics — that need to be managed within the same system as the financial consolidation.
Module complexity proportionality. We evaluate whether the platform’s module structure allows organizations to use only what they need — paying for financial consolidation without being forced to purchase and configure procurement, HR, or manufacturing modules they will not use.
Administrative overhead. Enterprise ERP platforms require more administrative resources to maintain — system administration, user management, security configuration, upgrade management — than finance-first platforms. For lean finance teams, this overhead is a real cost that is rarely included in TCO calculations.
Structural Tier Classification
Before recommending any platform, we classify the organization’s structure into one of four tiers based on entity count and complexity type. Recommendations are made against the tier — not the current state alone — because the correct platform today must still be correct in 3–5 years.
| Tier | Entity Count | Complexity Profile | Primary Requirement | Recommended Platform Range |
|---|---|---|---|---|
| Tier 1 | 2–4 entities | 100% ownership, minimal intercompany, single currency | Basic consolidated reporting | Xero + add-on, Sage Intacct (entry) |
| Tier 2 | 5–10 entities | Active intercompany transactions, possible minority interests, single or dual currency | Automated elimination, intercompany billing | Sage Intacct, Prophix |
| Tier 3 | 10–20 entities | Ownership complexity, multi-currency, acquisition activity | NCI automation, multi-currency, scalable elimination | NetSuite OneWorld, Lucanet |
| Tier 4 | 20+ entities | Global operations, statutory consolidation, multi-GAAP | Enterprise consolidation, statutory output | NetSuite Enterprise, SAP S/4HANA |
Important note on tier classification: Entity count is an indicator, not a determinant. A 6-entity structure with complex minority interests and frequent step acquisitions may be a Tier 3 problem. A 25-entity structure with 100% common ownership and minimal intercompany activity may be a Tier 2 solution. Ownership complexity is the most important variable — not raw entity count.
[See how to determine your structural tier →]
What We Deliberately Do Not Evaluate On
Our framework intentionally excludes several criteria that dominate standard software comparison content:
Brand recognition. NetSuite and SAP are well-known because they market aggressively and have large sales forces — not because they are the right choice for every multi-entity organization. Lucanet is less well-known in North America despite being technically superior to mid-market ERPs for statutory consolidation. We evaluate capability, not brand equity.
General feature counts. A platform with 200 features that cannot automate intercompany eliminations is less valuable for a multi-entity organization than a platform with 50 features that consolidates cleanly. Feature count comparisons produce misleading rankings for specialized use cases.
Entry-level usability. We are not evaluating which platform is easiest for a first-time bookkeeper to use. We are evaluating which platform delivers the most structural capability for experienced finance professionals managing complex multi-entity environments. Interface simplicity is not a meaningful criterion for our audience.
Generic customer satisfaction scores. A platform with a 4.5/5 G2 rating driven by single-entity users has a different capability profile than a platform with a 4.2/5 rating driven primarily by multi-entity holding company users. We filter reviews by user profile and use case — not overall rating.
Vendor marketing claims. Every platform in this space claims to be “purpose-built for multi-entity” and “best-in-class for consolidation.” We verify claims against documentation and user experience rather than taking them at face value.
How We Handle Affiliate Relationships
Several platforms reviewed on this site have affiliate or referral programs. When you click through to a vendor and subsequently engage with them, we may receive a commission. This is disclosed on every relevant page.
Our editorial standard on affiliate relationships:
We include platforms in our comparisons because they are structurally relevant to the decision — not because they have affiliate programs. Several platforms we recommend prominently (Lucanet, for example) have limited or no traditional public affiliate programs in certain markets. We recommend them because they are technically correct for specific use cases.
We do not adjust rankings, ratings, or recommendation positioning based on commission rates. A platform with a higher commission rate does not receive a better ranking as a result.
We do not write positive reviews of platforms that do not deserve them. Our audience is senior finance professionals who will verify our claims against their own evaluation process — and who will never return to this site if our recommendations produce poor outcomes.
The commercial model of this site works when our recommendations are correct. That alignment is the strongest protection against bias.
Why Most Multi-Entity Software Comparisons Are Wrong
The majority of multi-entity accounting software comparison content is produced by generalist technology writers who evaluate these platforms the same way they would evaluate project management software or CRM tools — by building a feature grid and comparing checkboxes.
That approach fails for multi-entity accounting for three reasons:
First: The differentiating capability in multi-entity accounting is architectural, not feature-level. Two platforms can both “support multi-entity consolidation” in their feature list while having completely different elimination engine designs, ownership modeling capabilities, and scalability profiles. A feature list cannot capture that difference.
Second: The consequences of a wrong recommendation are severe and delayed. An organization that selects the wrong CRM discovers the problem quickly — the tool is frustrating to use and people stop using it. An organization that selects the wrong multi-entity accounting platform discovers the problem 2–3 years later, when entity count has grown, when the close cycle is running 18 days, when the audit is finding intercompany reconciliation discrepancies. The delayed consequence means standard comparison content never receives feedback that it was wrong.
Third: The audience for multi-entity accounting content is not making a $50/month software subscription decision. They are making a $75,000–$350,000 platform commitment with a 5–7 year time horizon. The standard of analysis should reflect the magnitude of that decision.
Our methodology is designed to meet that standard.
Where to Start Your Evaluation
If you are actively evaluating multi-entity accounting software, the most useful starting point is identifying your structural tier and the primary pain point driving the evaluation.
For most mid-market organizations with 3–15 entities: [Best Multi-Entity Accounting Software →] — full comparison of 8 platforms ranked by consolidation depth, intercompany automation, and structural fit.
For holding company structures with minority interests or acquisition complexity: [Best Accounting Software for Holding Companies →] — detailed comparison of 7 platforms specifically evaluated against NCI automation, step acquisition support, and IFRS 10 / ASC 810 compliance.
For head-to-head evaluation of the two most common mid-market choices: [NetSuite vs Sage Intacct — Holding Company Comparison →]
For pricing research before entering a vendor sales process: [NetSuite Pricing →] | [Sage Intacct Pricing →]
This methodology page is maintained by the Multi-Entity Accounting editorial team. Evaluation criteria are reviewed annually and updated when material changes to platform capabilities occur.
Word count: ~3,600 words
Notes for AURA-UX
- No affiliate CTAs on this page — it is a trust/methodology page
- All bolded internal links should point to the relevant comparison pages
- This page should be linked from the footer and from the introduction section of every major comparison page
- The five-dimension framework and the tier classification table are the two most linkable/quotable elements — format them prominently
Slug for This Page
/how-we-evaluate
Clean, descriptive, matches the page title exactly. Not /methodology (too abstract) and not /how-we-evaluate-multi-entity-accounting-software (unnecessarily long). /how-we-evaluate is the right call.
Affiliate Programs
This page has no direct affiliate CTAs — it is a trust-building page. However it feeds traffic to every money page on the site. The affiliate programs relevant to the pages it links to are the same as the main comparison pages:
Intercompany Accounting for Holding Companies: Eliminations, Risks & Structural System Design Intercompany accounting is one of the most structurally sensitive — and audit-exposed — components of finance within holding company environments. As soon as a group operates through multiple legal enti
pasted
3:05 PM
Diagnosed content gaps and architected comprehensive expansion strategy
Diagnosed content gaps and architected comprehensive expansion strategy
First — should this page exist and what is its job?
Yes. This is a critical informational funnel page — not a money page itself, but one of the highest-value pages on the site because it targets finance professionals who are actively experiencing the pain that leads to a software purchase. Someone searching “intercompany accounting for holding companies” or “intercompany eliminations” is usually 2–4 weeks away from requesting a NetSuite or Sage Intacct demo. This page captures them at the awareness stage and routes them to your comparison and pricing pages.
Current version problems:
- ~900 words — needs 5,000–7,000
- No real mechanics — a CFO learns nothing they didn’t already know
- No worked examples with actual journal entries
- No tables
- No platform-specific guidance
- No FAQ
- No affiliate CTAs at the right conversion points
- Reads like a summary of a concept rather than a definitive resource
Here is the full rewrite:
Intercompany Accounting for Holding Companies — Eliminations, Journal Entries, and System Design (2026)
RankMath Title: Intercompany Accounting for Holding Companies — Complete Guide 2026 Meta Description: The complete guide to intercompany accounting for holding companies — elimination entries, NCI, unrealized profits, FX treatment, and which systems automate it correctly. Focus Keyword: intercompany accounting for holding companies Slug: /intercompany-accounting-holding-companies
Intercompany accounting is where holding company finance either works cleanly or starts breaking down.
Not gradually. Predictably.
The pattern is consistent across holding structures of every size: a group reaches 4–6 entities, intercompany transaction volume grows, and the close cycle that used to take 7 days starts taking 14. Then 18. Controllers spend the last week of every month chasing balance mismatches between entities, rebuilding elimination schedules in Excel, and producing consolidated financial statements that technically balance but that nobody in the finance team fully trusts.
This is not a people problem. It is an infrastructure problem. And it has a specific cause: intercompany accounting complexity has outgrown the system architecture that was designed to handle it.
This guide covers everything a CFO or controller needs to understand about intercompany accounting in a holding company environment — the mechanics, the journal entries, the common failure modes, the compliance requirements, and the system design decisions that determine whether intercompany accounting scales cleanly or becomes the bottleneck in your close process.
What Is Intercompany Accounting — and Why Holding Companies Face Unique Challenges
Intercompany accounting refers to the recording, reconciliation, and elimination of financial transactions that occur between legal entities within the same group.
In a holding company structure, transactions do not only flow between the group and external parties — customers, vendors, lenders. They also flow between entities within the group itself:
- The parent company charges management fees to subsidiaries
- A treasury subsidiary lends funds to operating subsidiaries
- A shared services entity recharges IT, HR, and marketing costs across the group
- An operating subsidiary sells goods or services to another operating subsidiary
- The parent company transfers assets to a subsidiary at an agreed transfer price
Each of these transactions is economically real and correctly recorded at the entity level. Each of them creates a problem at the consolidated level — because the group cannot transact with itself. Revenue earned by one entity from another entity in the same group is not revenue from the group’s perspective. A loan between group entities creates a receivable in one entity and a payable in another that cancel each other out when viewed from the group level.
The process of identifying and removing these transactions from the consolidated financial statements is intercompany elimination. It is not optional. Under IFRS 10 and ASC 810, incomplete or incorrect elimination results in materially misstated consolidated financial statements — which means audit findings, restatements, and in severe cases regulatory exposure.
The unique challenge for holding companies — as distinct from simpler multi-entity structures — is that intercompany eliminations in a holding structure must interact correctly with non-controlling interest attribution. When a partially-owned subsidiary is party to intercompany transactions, the elimination entries affect both the group’s share of profit and the NCI’s share. This interaction is where most mid-market accounting systems begin to require manual intervention.
[See how different platforms handle NCI and intercompany elimination in our holding company software guide →]
The Full Taxonomy of Intercompany Transactions
Not all intercompany transactions are the same — and the elimination treatment differs by transaction type. Understanding the taxonomy is essential before evaluating whether your current system handles each type correctly.
1. Intercompany Loans and Interest
What it is: The parent company or a treasury entity within the group lends funds to a subsidiary. The loan is documented with agreed terms — principal, interest rate, repayment schedule.
Entity-level treatment:
- Lender entity: Dr Intercompany Loan Receivable / Cr Cash
- Borrower entity: Dr Cash / Cr Intercompany Loan Payable
Interest accrual (monthly):
- Lender entity: Dr Intercompany Interest Receivable / Cr Interest Income
- Borrower entity: Dr Interest Expense / Cr Intercompany Interest Payable
Elimination entry (at consolidation):
- Dr Intercompany Loan Payable (Borrower)
- Cr Intercompany Loan Receivable (Lender)
- Dr Interest Income (Lender)
- Cr Interest Expense (Borrower)
Why it matters: Intercompany loans are often the largest balance requiring elimination in holding company structures. A $10M intercompany loan creates a $10M receivable and a $10M payable that inflate consolidated assets and liabilities if not eliminated. Interest on that loan overstates both consolidated revenue and consolidated expense.
System requirement: The system must track intercompany loan balances at entity level and automate elimination entries at period end. Interest accruals should be calculated automatically based on configured loan terms.
2. Management Fees and Shared Service Charges
What it is: The parent or a holding entity charges management fees to operating subsidiaries for services provided — strategic oversight, central finance, legal, HR, IT, or marketing. This is the most common form of intercompany charge in holding structures.
Entity-level treatment:
- Charging entity: Dr Intercompany Receivable / Cr Management Fee Income
- Receiving entity: Dr Management Fee Expense / Cr Intercompany Payable
Elimination entry (at consolidation):
- Dr Management Fee Income (Charging entity)
- Cr Management Fee Expense (Receiving entity)
- Dr Intercompany Payable (Receiving entity)
- Cr Intercompany Receivable (Charging entity)
Why it matters: Management fees are typically recurring monthly charges. If not eliminated, consolidated revenue and expense are both overstated by the full amount each period. For a group charging $500,000/month in management fees across subsidiaries, this is a $6,000,000 annual overstatement in both consolidated revenue and consolidated expenses — which distorts every profitability metric the group reports.
The transfer pricing consideration: Management fees between group entities in different tax jurisdictions must also comply with transfer pricing rules — they must be charged at arm’s length rates and documented accordingly. The accounting system should support transfer pricing documentation alongside the elimination workflow.
System requirement: Automated intercompany billing that generates both sides of the management fee transaction simultaneously, with elimination rules configured by relationship. The system should generate the revenue entry in the charging entity and the expense entry in the receiving entity from a single configured billing schedule.
3. Intercompany Sales — Goods and Services
What it is: One group entity sells goods or services to another group entity. The selling entity records revenue. The purchasing entity records cost of goods sold or expense.
Entity-level treatment:
- Selling entity: Dr Intercompany Receivable / Cr Revenue
- Purchasing entity: Dr Cost of Goods Sold (or Expense) / Cr Intercompany Payable
Elimination entry:
- Dr Revenue (Selling entity)
- Cr Cost of Goods Sold (Purchasing entity)
- Dr Intercompany Payable (Purchasing entity)
- Cr Intercompany Receivable (Selling entity)
Why it matters: Intercompany sales create consolidated revenue overstatement. If Sub A sells $2,000,000 of goods to Sub B and that transaction is not eliminated, consolidated revenue is $2,000,000 higher than the group’s actual external revenue. Consolidated gross profit is unaffected only if the corresponding cost is also eliminated — but the revenue figure is wrong.
4. Unrealized Profit on Intercompany Asset Transfers
This is the most technically complex category of intercompany elimination — and the one where most mid-market accounting systems require manual intervention.
What it is: When one group entity sells an asset (inventory, fixed asset, intellectual property) to another group entity at a profit, and the purchasing entity has not yet sold that asset to an external party, the profit is unrealized from the group’s perspective.
Worked example:
Sub A manufactures goods at a cost of $80,000. Sub A sells those goods to Sub B for $100,000 — a $20,000 profit.
Sub B has not yet sold the goods externally. They remain in Sub B’s inventory at $100,000.
From the group’s perspective:
- The goods cost $80,000 to produce
- They are still within the group — no external sale has occurred
- The $20,000 profit is unrealized
Entity-level positions:
- Sub A: Revenue $100,000, COGS $80,000, Profit $20,000
- Sub B: Inventory $100,000
Consolidated position without elimination:
- Revenue: $100,000 (Sub A’s intercompany revenue)
- COGS: $80,000
- Inventory: $100,000
- Profit: $20,000
This is wrong. The revenue and profit are unrealized. The inventory is overstated.
Elimination entry:
- Dr Revenue $100,000
- Cr COGS $80,000
- Cr Inventory $20,000
Consolidated position after elimination:
- Revenue: $0 (correctly eliminated)
- Inventory: $80,000 (at original cost to the group)
- Profit: $0 (correctly deferred)
When Sub B subsequently sells the goods externally, the $20,000 deferred profit is recognized — because at that point the profit is realized from the group’s perspective.
Why this matters for NCI: If Sub B is partially owned (say, 70% by the group), the unrealized profit elimination must be allocated between the group and the NCI. Only the group’s share of the unrealized profit ($14,000 = 70% × $20,000) is eliminated from consolidated profit attributable to the parent. The NCI’s share ($6,000) is eliminated against NCI equity. This interaction is where many mid-market systems fail and require manual journal entries.
System requirement: Automated unrealized profit tracking based on intercompany inventory movement, with NCI-aware elimination calculation. NetSuite OneWorld and SAP Group Reporting handle this automatically. Most other platforms require manual configuration or manual journal entries.
5. Intercompany Dividends
What it is: A subsidiary declares and pays a dividend to its parent company.
Entity-level treatment:
- Subsidiary: Dr Retained Earnings / Cr Dividend Payable
- Parent: Dr Dividend Receivable / Cr Dividend Income
Elimination entry:
- Dr Dividend Income (Parent)
- Cr Dividend Payable (Subsidiary)
The NCI dimension: When a partially-owned subsidiary declares a dividend, only the parent’s share flows to the parent as dividend income. The NCI’s proportionate share flows to NCI equity. The elimination is applied only to the parent’s share — the NCI dividend is already correctly captured in the NCI equity movement.
6. Intercompany Asset Transfers — Fixed Assets
What it is: One group entity transfers a fixed asset to another group entity. The transfer may be at cost, at net book value, or at fair value depending on group policy and tax considerations.
The key issue: If the transfer is at above net book value, the transferring entity records a gain. That gain is unrealized from the group’s perspective — the asset is still within the group. The gain must be eliminated and the asset must be carried at its original cost basis in the consolidated accounts.
Additional complexity: The receiving entity depreciates the asset at the transfer price. The consolidated accounts should depreciate at the original cost. The difference in depreciation — caused by the step-up in value at transfer — must be adjusted in the consolidated accounts each period until the asset is disposed of or fully depreciated.
This is a multi-period elimination that persists beyond the period of transfer — making it one of the more complex ongoing elimination requirements.
System requirement: The system must track the original cost basis of transferred assets and maintain the elimination adjustment over the asset’s remaining useful life. Manual tracking of this adjustment in a spreadsheet is an ongoing audit risk.
The Mechanics of Consolidation Elimination — Step by Step
To understand why accounting systems struggle with elimination at scale, it helps to see the complete consolidation process from start to finish.
Step 1: Entity Trial Balances
Each entity produces its own trial balance at period end. The trial balance includes all entity-level balances — including intercompany receivables, payables, income, and expenses that will need to be eliminated.
Step 2: Intercompany Matching
Before elimination can occur, intercompany balances must be matched between entities. Entity A’s intercompany receivable of $500,000 must be confirmed by Entity B’s intercompany payable of $500,000.
In practice, they rarely match perfectly at period end. Common sources of mismatch:
- Timing differences: Entity A records a management fee charge on the last day of the period. Entity B records the receipt in the following period.
- FX differences: The charge is denominated in USD but Entity B’s functional currency is EUR. The EUR/USD rate at the transaction date differs from the rate at period end, creating a balance discrepancy in functional currency terms.
- Transaction disputes: Entity B disagrees with the amount charged and has recorded a different figure.
- Missing entries: One entity has recorded the transaction; the other has not.
Resolving these mismatches is typically the most time-consuming component of the intercompany close process. A platform with automated intercompany matching identifies discrepancies automatically and routes them for resolution — eliminating the manual email chains and spreadsheet reconciliations that extend the close cycle.
Step 3: Elimination Journal Entries
Once intercompany balances are confirmed to match, elimination journals are posted. These entries eliminate:
- Intercompany receivables and payables
- Intercompany revenue and expense
- Unrealized profits
- Investment in subsidiary against the subsidiary’s equity (at the acquisition date basis)
Step 4: NCI Attribution
After elimination, the consolidated profit and equity must be allocated between:
- The portion attributable to the parent company’s shareholders
- The portion attributable to non-controlling interests
This allocation is based on ownership percentages. In a simple structure, NCI attribution is straightforward. In multi-tier structures — where subsidiaries themselves have minority-owned subsidiaries — the attribution calculation cascades through multiple levels.
Step 5: Consolidated Financial Statements
The post-elimination, post-NCI-attribution balances form the consolidated trial balance. From this, the consolidated balance sheet, consolidated income statement, and consolidated statement of cash flows are produced.
Step 6: Audit Trail Documentation
Every elimination entry must be documented with a clear audit trail — showing which intercompany relationship it relates to, the basis for the elimination amount, and confirmation that it was reviewed and approved. This documentation is examined by external auditors and must be complete and accurate.
Intercompany Accounting Across Currencies
For holding companies with subsidiaries in multiple currency zones, intercompany accounting introduces an additional layer of complexity: foreign exchange.
Functional Currency Designation
Under IAS 21 (IFRS) and ASC 830 (US GAAP), each entity has a functional currency — the currency of the primary economic environment in which it operates. This is usually (but not always) the local currency of the jurisdiction where the entity operates.
Intercompany transactions denominated in a currency other than an entity’s functional currency create foreign exchange exposure at the entity level — gains and losses on translation of intercompany receivables and payables as exchange rates move.
The Intercompany FX Elimination Challenge
When Entity A (functional currency USD) charges a management fee of $100,000 to Entity B (functional currency EUR), Entity B records the expense at the EUR equivalent at the transaction date. At period end, the EUR/USD rate may have moved — creating a difference between:
- Entity A’s USD receivable: $100,000
- Entity B’s EUR payable translated to USD at the period-end rate: $98,500 (if EUR has weakened)
The $1,500 difference is a foreign exchange translation difference arising on an intercompany balance. In the consolidated accounts, this difference must be eliminated — because from the group’s perspective, the intercompany balance does not exist and neither should the FX gain/loss arising on it.
Currency Translation for Consolidation
Beyond individual transaction FX differences, multi-currency consolidation requires translating each subsidiary’s entire financial statements from its functional currency into the group’s presentation currency:
- Balance sheet items translate at the closing rate at period end
- Income statement items translate at the average rate for the period
- Equity items translate at the historical rate (the rate at the time equity transactions occurred)
- The difference between these translation methods creates a cumulative translation adjustment (CTA) — a balance that sits in other comprehensive income (OCI) in the consolidated equity
The CTA is not a real gain or loss — it is purely a mathematical consequence of using different translation rates for different statement items. It must be tracked accurately in the consolidated equity and recycled to the income statement when a foreign subsidiary is disposed of.
System requirement: Functional currency designation per entity, automatic translation at appropriate rates (closing, average, historical) per account type, automatic CTA calculation and presentation in OCI, and elimination of FX differences arising on intercompany balances. Every platform reviewed on this site supports IAS 21-compliant translation — the differences are in automation depth and rate management capability.
How IFRS 10 and ASC 810 Govern Intercompany Elimination
IFRS 10 Requirements
IFRS 10.B86 states that intragroup balances, transactions, income, and expenses shall be eliminated in full. This is not a recommendation. It is a requirement.
Specifically, IFRS 10 requires elimination of:
- Intragroup assets and liabilities
- Intragroup equity
- Intragroup income and expenses
- Profits or losses resulting from intragroup transactions that are recognized in assets (inventory, fixed assets)
- Any tax effects of eliminations (per IAS 12)
The unrealized profit provision under IFRS 10.B86(c) requires that unrealized profits and losses arising from intragroup transactions be eliminated in full — with an important distinction:
Losses on intragroup transactions are eliminated only to the extent that they do not represent an impairment loss. If an asset has genuinely declined in value below its original cost, the loss is real and should not be eliminated.
ASC 810 Requirements
ASC 810-10-45-1 requires that consolidated financial statements include the accounts of the parent and all consolidated subsidiaries, with all intercompany balances and transactions eliminated.
The VIE framework under ASC 810 adds a layer of complexity not present in IFRS 10. A variable interest entity (VIE) must be consolidated by its primary beneficiary — the entity that has the power to direct the activities of the VIE and the obligation to absorb its losses or the right to receive its benefits. This means some entities are required to be consolidated even without majority voting ownership.
For holding companies with complex contractual control structures, VIE analysis may be required to determine consolidation scope — an analysis that the accounting system must support with appropriate entity classification and consolidation treatment.
Common Intercompany Accounting Failures in Holding Companies
Based on patterns observed across holding company accounting environments, the following failure modes occur with the highest frequency:
Failure 1: The Aging Elimination Spreadsheet
A controller builds an elimination model in Excel when the group had 3 entities. The model tracks intercompany balances, calculates eliminations, and produces a consolidation output. It works.
Four years and six acquisitions later, the same Excel model — now running to 47 tabs and owned exclusively by the controller who built it — is the consolidation infrastructure for a 12-entity holding group. Nobody else fully understands it. The controller takes 3 days each month to run the close. When the controller takes a two-week holiday, close is delayed.
This is not a people problem. The model worked exactly as intended. It is a structural problem: the tool was never designed for the scale it is now carrying.
The solution is not a better Excel model. It is a platform with native elimination automation.
Failure 2: Persistent Balance Mismatches
Entity A records an intercompany charge on March 31. Entity B records the corresponding entry on April 3. This creates a mismatch at the March period end — Entity A has a receivable that Entity B has not yet recorded as a payable.
In a system with automated intercompany matching, this discrepancy is flagged automatically. In a manual process, it is discovered during the close reconciliation — usually on Day 8 of a 10-day close target, requiring investigation and correction under time pressure.
Multiply this by 15 intercompany relationships across 10 entities. The close is now structurally dependent on resolving timing mismatches that compound every period.
Failure 3: Unrealized Profit Not Eliminated
Sub A sells finished goods to Sub B. Sub B holds significant inventory at period end that was purchased from Sub A at a margin. The unrealized profit in that inventory is not eliminated — either because the system cannot automate it or because the finance team does not know it exists.
Consolidated inventory is overstated. Consolidated profit is overstated. The error persists and compounds until Sub B sells the inventory externally.
In a Big 4 audit environment, this is an audit finding. In a covenant-based lending environment, it may affect compliance calculations. In a PE-backed structure with quarterly LP reporting, it affects the accuracy of distributed financials.
Failure 4: FX Elimination Gaps
Entity A’s intercompany receivable translates to $500,000 at period-end rates. Entity B’s intercompany payable translates to $492,000 at period-end rates. The $8,000 difference — a translation difference arising on an intercompany balance — is left in the consolidated accounts as an FX gain.
It should be eliminated. It is not a real gain from the group’s perspective. But in a manual elimination process, this $8,000 survives and accumulates. Over 12 months across multiple intercompany currency pairs, translation differences on intercompany balances can represent material amounts that distort the consolidated FX line.
Failure 5: NCI Contamination from Intercompany Eliminations
Sub A (70% owned by Parent) sells goods to Sub B (100% owned by Parent) with a $50,000 unrealized profit remaining in Sub B’s inventory.
In eliminating the unrealized profit, the correct approach is:
- Eliminate $35,000 from consolidated profit attributable to Parent (70% × $50,000)
- Eliminate $15,000 from NCI equity (30% × $50,000)
A system that eliminates the full $50,000 from consolidated profit (without the NCI split) overstates NCI equity and understates consolidated profit attributable to the parent.
This error is embedded in the journal entries and is unlikely to be caught without a specific review of NCI elimination methodology. It is a systemic error — not a one-off mistake — that recurs every period until the system is corrected.
What Proper Intercompany Infrastructure Looks Like
A well-designed intercompany accounting infrastructure has five characteristics:
1. Automated Dual-Sided Transaction Generation
When an intercompany transaction is initiated — a management fee, a cost allocation, an intercompany loan drawdown — the system generates both sides of the transaction simultaneously. The revenue and AR entry in the charging entity and the expense and AP entry in the receiving entity are created from a single configured template.
This eliminates the most common source of intercompany mismatches: one entity records a transaction and the other does not.
2. Automated Intercompany Matching
At period end, the system compares intercompany balances across all entity pairs automatically. Mismatches are identified, categorized (timing difference, FX difference, dispute), and routed to the appropriate owner for resolution through a workflow. The controller does not manually reconcile entity pairs — the system presents a discrepancy resolution queue.
3. Rule-Based Elimination Engine
Elimination rules are configured once for each intercompany relationship. At period close, the elimination engine applies all rules automatically, generating the required elimination journal entries without manual input. New intercompany relationships require new rules — but existing rules run without maintenance.
4. Unrealized Profit Tracking
The system tracks intercompany inventory movements and maintains unrealized profit calculations automatically. When intercompany goods are sold externally, the deferred profit is recognized automatically. NCI-aware unrealized profit elimination splits the elimination correctly between consolidated profit and NCI equity.
5. Audit-Ready Documentation
Every elimination entry is documented in the system with: the intercompany relationship it relates to, the period it covers, the basis for calculation, and the approval workflow it passed through. The complete elimination workpaper is producible on demand — not reconstructed from journal entries after the fact.
Platform Comparison — Intercompany Automation Capability
| Capability | NetSuite OneWorld | Sage Intacct | SAP S/4HANA | Lucanet | Prophix | Dynamics 365 |
|---|---|---|---|---|---|---|
| Auto dual-sided IC transactions | ✅ Full | ✅ Full | ✅ Full | ⚠️ Overlay | ✅ Yes | ✅ Full |
| IC matching engine | ✅ Built-in | ⚠️ Limited | ✅ Best-in-class | ✅ Strong | ✅ Strong | ⚠️ Moderate |
| Rule-based elimination engine | ✅ Full | ✅ Full | ✅ Full | ✅ Full | ✅ Full | ✅ Full |
| Unrealized profit elimination | ✅ Automated | ⚠️ Manual config | ✅ Automated | ✅ Automated | ✅ Automated | ✅ Automated |
| NCI-aware elimination | ✅ Automated | ⚠️ Limited | ✅ Automated | ✅ Automated | ⚠️ Basic | ⚠️ Moderate |
| Multi-currency IC elimination | ✅ Full | ✅ Strong | ✅ Full | ✅ Strong | ⚠️ Moderate | ✅ Strong |
| Audit trail quality | ✅ Comprehensive | ✅ Strong | ✅ Best-in-class | ✅ Best-in-class | ✅ Strong | ✅ Strong |
| Transfer pricing support | ⚠️ Configuration | ⚠️ Limited | ✅ Full | ⚠️ Limited | ❌ No | ⚠️ Limited |
[See full platform comparison for holding companies →] [Compare NetSuite vs Sage Intacct intercompany capabilities →]
When Intercompany Complexity Becomes System-Critical
The following thresholds indicate that intercompany accounting has outgrown the current system:
| Indicator | Signal Level | Action |
|---|---|---|
| Close cycle consistently over 10 days | Amber | Evaluate automation options |
| Controller spending 3+ days on IC reconciliation per period | Amber | Evaluate automation urgently |
| Elimination spreadsheet owned by one person | Red | Structural risk — act now |
| Balance mismatches recurring every period close | Red | System is misaligned |
| Unrealized profits not being eliminated | Red | Audit exposure — immediate action |
| Any NCI elimination being calculated manually | Red | System does not support the structure |
| Audit findings related to IC reconciliation in last 2 years | Red | Structural failure confirmed |
If three or more of these indicators apply, the intercompany accounting infrastructure is structurally misaligned with the group’s complexity. The appropriate response is a structured software evaluation — not more process improvement layered on top of an inadequate system.
[Start with: Best Accounting Software for Holding Companies →]
The Cost of Inadequate Intercompany Infrastructure
The cost of running manual intercompany accounting in a growing holding company is rarely calculated explicitly — but it is substantial.
Direct costs:
| Cost Category | Typical Annual Range |
|---|---|
| Controller time on IC reconciliation (3 days/month × 12) | $30,000–$60,000 in salary cost |
| Audit fees attributable to IC reconciliation quality issues | $15,000–$50,000 additional |
| Errors discovered and corrected in prior periods | Variable — can be material |
| Restatement risk (if errors are not caught before filing) | Significant — reputational and regulatory |
Indirect costs:
- Extended close cycles delay management reporting, which delays decision-making
- Consolidated financials with known reconciliation gaps reduce board and investor confidence
- Finance team capacity consumed by reconciliation cannot be deployed on analysis and insight
- Key person dependency on the controller who owns the Excel model creates organizational fragility
The ROI of automation:
A Sage Intacct or NetSuite implementation that eliminates manual intercompany reconciliation — reducing close from 15 days to 7 days and freeing the controller from 3 days of monthly reconciliation work — typically recovers its implementation cost within 18–24 months in direct labor savings alone. The audit fee reduction and error risk reduction are additional.
[See Sage Intacct pricing for holding companies →] [See NetSuite pricing for holding companies →]
Practical Intercompany Setup — What to Configure in Your System
For finance teams implementing or configuring a multi-entity platform, the following setup is required to support automated intercompany accounting:
Step 1: Entity Relationship Mapping
Document every intercompany relationship in the group — every entity pair that has recurring transactions. For each relationship, identify: transaction type, frequency, currency, approximate annual volume, and which entity initiates the transaction.
This mapping becomes the basis for intercompany billing rules and elimination rules in the system.
Step 2: Chart of Accounts — Intercompany Accounts
Designate specific account codes for intercompany receivables, payables, revenue, and expenses — separate from external customer/vendor equivalents. This segregation is essential for elimination engine accuracy. Typical structure:
- 1300 — Intercompany Receivables (by entity)
- 2300 — Intercompany Payables (by entity)
- 4900 — Intercompany Revenue
- 6900 — Intercompany Expense
Maintaining separate intercompany accounts, segregated by entity counterpart, makes elimination rule configuration straightforward and audit trail clarity significantly stronger.
Step 3: Intercompany Billing Rule Configuration
For each recurring intercompany charge — management fees, cost allocations, shared service recharges — configure an automated billing rule that specifies: charging entity, receiving entity, amount or allocation basis, frequency, account codes in both entities, and currency.
When the billing rule runs, both sides of the transaction are generated simultaneously. No manual journals.
Step 4: Elimination Rule Configuration
For each intercompany relationship, configure the corresponding elimination rule: which account in the charging entity eliminates against which account in the receiving entity, at what level (transaction, balance, or both), and whether unrealized profit tracking applies.
Step 5: Period-End Workflow
Configure the period-end intercompany workflow: matching runs automatically on Day 1 of close, discrepancies are routed to designated owners, resolution is tracked through the workflow, elimination engine runs once matching is complete. The controller manages exceptions — not the entire process.
Intercompany Accounting and the Audit — What Auditors Actually Check
Understanding what external auditors look for in intercompany accounting helps calibrate the standard of documentation required.
Balance confirmation: Auditors typically request confirmation from each entity’s management that intercompany balances agree with counterparty records. In a well-designed system, this confirmation is produced automatically from the intercompany matching report.
Elimination completeness: Auditors test whether all intercompany transactions have been identified and eliminated — including less obvious transactions like intercompany dividends, asset transfers, and royalties. A complete intercompany transaction register, maintained in the system, is the most efficient way to satisfy this test.
Unrealized profit: Auditors specifically test for unrealized profits on intercompany inventory and asset transfers. This requires documentation of intercompany sales volumes, the profit margin on those sales, and the proportion of goods remaining in the receiving entity’s inventory at period end. Systems that automate unrealized profit tracking produce this documentation automatically.
NCI attribution: For partially-owned subsidiaries, auditors verify that NCI has been calculated correctly and that intercompany eliminations have been split correctly between consolidated profit and NCI equity. Manual NCI calculations are the most common source of audit findings in mid-market holding company audits.
FX elimination: Auditors check that FX differences on intercompany balances have been eliminated rather than recognized as income or expense. This is often missed in manual consolidation processes and is a predictable audit finding for groups consolidating across currencies without automated FX elimination.
Frequently Asked Questions
What is intercompany elimination in simple terms?
When two companies within the same group transact with each other, both companies record the transaction in their own books — one records income, the other records expense. But from the group’s perspective, the transaction did not happen with an external party — it happened internally. Intercompany elimination removes both sides of the transaction from the consolidated financial statements so the group does not appear to have earned revenue from itself or incurred expenses it paid to itself.
How do you eliminate intercompany profit in inventory?
When one group entity sells goods to another at a profit, and the purchasing entity has not yet sold those goods externally, the profit is unrealized from the group’s perspective. The elimination entry reduces consolidated revenue by the full sales price, increases cost of goods sold by the original cost, and reduces the inventory balance to original cost. The net effect is that consolidated inventory is carried at the group’s original cost and no profit is recognized until the goods are sold externally.
What is the difference between intercompany and intracompany transactions?
Intercompany transactions occur between separate legal entities within the same group — for example, between a parent company and its subsidiary. Intracompany transactions occur within a single legal entity — for example, between two divisions of the same company. Intercompany transactions require elimination in consolidated financial statements. Intracompany transactions do not appear in the external financial statements at all.
Does intercompany elimination affect tax?
Yes — intercompany elimination has tax implications that must be handled carefully. When an unrealized profit is eliminated for consolidation purposes, a deferred tax asset typically arises (because the tax base of the asset differs from its carrying value in the consolidated accounts). IAS 12 and ASC 740 govern the tax treatment of consolidation adjustments. Most enterprise accounting platforms calculate deferred tax on elimination entries automatically. Mid-market platforms typically require manual deferred tax calculation.
Why do intercompany balances not match at period end?
The most common reasons for intercompany balance mismatches at period end are: timing differences (one entity records a transaction on the last day of the period; the counterparty records it on the first day of the next period), foreign exchange differences (the same transaction is carried at different translated amounts in each entity due to rate movements), transaction disputes (one entity disagrees with the amount charged and records a different figure), and missing entries (one entity has not yet recorded the transaction). Automated intercompany matching identifies each type of discrepancy and routes it for resolution.
How does intercompany accounting work with NCI?
When a partially-owned subsidiary is party to an intercompany transaction, the elimination must account for the NCI. For example, if a 75%-owned subsidiary has unrealized profit of $100,000 in consolidated inventory, the elimination splits: $75,000 is eliminated from consolidated profit attributable to the parent, and $25,000 is eliminated from NCI equity. Systems that do not calculate this split automatically will eliminate the full $100,000 from consolidated profit — overstating NCI equity and understating the parent’s share of consolidated profit. NetSuite OneWorld, SAP Group Reporting, and Lucanet all handle NCI-aware elimination automatically.
What software automates intercompany eliminations for holding companies?
NetSuite OneWorld provides the most comprehensive automation for holding company intercompany accounting — automated dual-sided transaction generation, intercompany matching, NCI-aware elimination, and unrealized profit tracking. Sage Intacct automates standard intercompany billing and elimination well but requires more manual configuration for complex NCI scenarios. SAP S/4HANA Group Reporting provides the deepest automation but at enterprise cost and complexity. Lucanet provides strong elimination automation as a specialist consolidation overlay on existing GL systems. [See full platform comparison →]
Where to Go Next
If this guide has confirmed that your current intercompany accounting infrastructure is inadequate for your group’s complexity, the next step is a structured software evaluation.
For most holding companies with 3–20 subsidiaries: [Best Accounting Software for Holding Companies →] — 7 platforms ranked by intercompany automation, NCI capability, and elimination depth.
To compare the two most common mid-market choices head to head: [NetSuite vs Sage Intacct — Intercompany and Consolidation Comparison →]
For pricing research before entering vendor conversations: [NetSuite Pricing →] | [Sage Intacct Pricing →]
For organizations with operational multi-entity structures without ownership complexity: [Best Multi-Entity Accounting Software →]
This guide is maintained by the Multi-Entity Accounting editorial team. Technical content is reviewed against current IFRS and US GAAP standards annually.