When posting manual elimination entries in a consolidation, there are two ways to record them: at the group level — a single journal that lives in the consolidation without referencing which entities it relates to — or at the entity-pair level, where each elimination specifies the “from” entity generating the income and the “to” entity carrying the expense. Both produce the same net effect on the consolidated P&L and balance sheet. The difference is in audit trail, entity-level reporting accuracy, and how cleanly the eliminations interact with NCI calculations.
Choosing the right method — or the right method for each type of elimination — affects how much time is spent reconciling and how confident you can be in entity-level figures alongside the consolidated view.
Method 1 Group-Level Elimination
In this approach, the elimination entry is posted centrally at the group consolidation level. It adjusts the consolidated trial balance directly without attributing the debit and credit legs to specific entities.
Example The parent company charges a $30,000 annual management fee to three subsidiaries ($10,000 each). Rather than posting three entity-pair entries, the preparer posts one group-level elimination that removes $30,000 of management fee income and $30,000 of management fee expense from the consolidated P&L.
Group-level elimination entry
| Account | Debit | Credit |
|---|---|---|
| Management Fee Income (Group) | $30,000 | |
| Management Fee Expense (Group) | $30,000 |
What it doesn’t do: It doesn’t tell the system that $10,000 of this relates to Sub A, $10,000 to Sub B, and $10,000 to Sub C. In the entity contribution view — where each subsidiary’s standalone results are shown alongside the group — Sub A, Sub B, and Sub C will still show the $10,000 management fee expense in their entity-level figures. The elimination sits at group level, not within either entity’s contribution.
When this works well:
- Simple group structures where entity-level contribution reports aren’t produced or aren’t material to stakeholders
- High-volume routine charges (management fees, shared services, royalties) that follow a predictable pattern and don’t require entity-level attribution
- Groups where intercompany charges are clearly identifiable from account codes alone, making entity-pair tracking redundant
- Situations where speed at close is the priority and the audit trail is maintained externally in working papers
Method 2 Entity-Pair Elimination (From → To)
In this approach, each elimination entry specifies the originating entity (“from” — the one with income) and the receiving entity (“to” — the one with the expense). The system allocates the debit and credit to each entity’s contribution within the consolidation.
Same example The $10,000 management fee from the parent to Sub A is posted as a separate entity-pair entry: From = Parent, To = Sub A. The elimination removes $10,000 from Parent’s income contribution and $10,000 from Sub A’s expense contribution, so both entities’ standalone results in the consolidation are net of the intercompany charge.
Entity-pair elimination entry (one per subsidiary)
| Account | Entity | Debit | Credit |
|---|---|---|---|
| Management Fee Income | From: Parent | $10,000 | |
| Management Fee Expense | To: Sub A | $10,000 |
What it adds: Each entity’s contribution to the consolidated result is shown net of its intercompany activity. Sub A’s entity-level profit in the consolidation reflects the $10,000 expense already eliminated — the entity performance view is internally consistent with the group view.
When this is essential:
- Entity-level drill-down reporting: If stakeholders review each subsidiary’s contribution within the consolidated report, entity-pair eliminations ensure those contributions are accurate — not gross of intercompany charges that have been eliminated elsewhere
- Partially-owned subsidiaries (NCI): Where a subsidiary has minority shareholders, the NCI’s share of profit must be calculated from that entity’s net contribution. If intercompany eliminations aren’t allocated to the entity, the NCI calculation may be based on a gross figure that includes charges the entity didn’t actually bear
- Complex multi-entity structures: Groups with many intercompany relationships benefit from entity-pair attribution — it makes the audit trail navigable when tracing which entity generated which elimination
- Regulatory or lender reporting: Where entity-level schedules are submitted alongside the consolidated statements, entity-pair eliminations ensure the two sets of figures are internally consistent
The NCI Connection
The most important reason to use entity-pair eliminations over group-level ones — particularly for groups with partially-owned subsidiaries — is NCI accuracy.
NCI is calculated as the minority shareholders’ percentage of the subsidiary’s net assets and profit. If a subsidiary’s profit figure used in that calculation still includes management fee expenses that have been eliminated only at group level (not allocated back to the entity), the NCI is calculated on a gross figure. The minority shareholders are effectively being attributed a share of expenses they didn’t bear — or being denied a share of expenses they did.
Example Sub B is 70% owned by the parent (NCI: 30%). Sub B charges $20,000 management fee expense. Group-level elimination removes $20,000 from the consolidated P&L but leaves Sub B’s contribution showing $20,000 expense. NCI’s 30% share is calculated on Sub B’s gross profit — understating NCI by $6,000 (30% × $20,000).
Entity-pair elimination allocates the $20,000 removal to Sub B’s contribution, reducing its expense by $20,000 before the NCI calculation runs. NCI is calculated on the correct net figure.
Which Method to Use — and When to Use Both
| Scenario | Recommended method |
|---|---|
| Simple group, no NCI, entity-level reporting not required | Group-level — faster, sufficient audit trail |
| Entity contribution reports produced alongside consolidated view | Entity-pair — ensures entity figures are net of intercompany |
| Any partially-owned subsidiary (NCI present) | Entity-pair — NCI calculation accuracy depends on it |
| High-volume routine charges (management fees, royalties) | Group-level for speed; entity-pair if entity drill-down matters |
| Complex ownership structure, multiple intercompany relationships | Entity-pair — audit trail and traceability are essential |
| Audit or lender reporting with entity-level schedules | Entity-pair — internal consistency between group and entity figures |
In practice, many groups use both methods depending on the transaction type. Routine recurring charges with predictable amounts may be posted at group level for efficiency. Eliminations tied to entity performance measurement, NCI calculations, or external reporting schedules use entity-pair for accuracy. BrizoConsol supports both methods on a per-entity or per-elimination basis, so the approach can be set where it makes the most difference without forcing uniformity across every transaction type.
✅ Starting point recommendation: If your group has any partially-owned subsidiaries, default to entity-pair for all eliminations involving those entities. For wholly-owned entities where entity-level contribution reporting isn’t required, group-level is efficient and sufficient. Revisit the approach if entity drill-down reporting is added or if lender reporting introduces entity-level schedule requirements.
BrizoConsol supports both elimination methods — entity-pair for groups that need precise attribution and NCI accuracy, group-level for simpler structures that prioritise efficiency. The method can be configured per entity, so you’re not forced to choose one approach across the entire consolidation. Learn more or see it in action →