.svg)
Elimination methods for SME CFOs: complete guide (2026)
Four elimination methods — full GLA, per IC relationship, per transaction and manual IC entry — and the hybrid approach most SME groups end up running. Plus how to map residual the right way.
.png)
Intercompany elimination strips out transactions and balances between group entities during consolidation, so the consolidated numbers show only external activity. Four methods — full GLA (fastest), per IC relationship (the default), per transaction (highest auto precision) and manual IC entries (safety net for edge cases) — usually combined into a hybrid approach. Finstack supports all four, configurable per IC ledger account, with native connections to Exact, AFAS, Twinfield, Yuki, Pennylane, eAccounting, Tripletex, Nmbrs, Xero, QuickBooks Online and Microsoft Dynamics 365 BC.
Elimination methods for SME CFOs: complete guide (2026)
What the four methods do, which one to pick for which IC category, and how to map your elimination ledger accounts.
TL;DR
Intercompany elimination removes transactions and balances between entities of a group from the consolidated numbers. Four methods exist, each with its own balance between precision and manual work and its own use cases: full GLA (all balances on one ledger account, fastest, works for 100% IC accounts), per IC relationship (per entity pair plus ledger account, the default), per transaction (automatic matching of individual postings, required for mixed IC/external accounts), and manual IC entry (a journal entry you post yourself, the safety net for edge cases the other three don't cover). In practice SME CFOs almost always run a hybrid approach: the best-fit auto method per IC category, plus manual entries for year-end corrections or restructuring eliminations. PE portcos tilt toward per transaction because elimination differences flow straight through to EBITDA. Make a conscious choice about what happens to residual after elimination: your tool maps it either to a generic "Other equity" line (which hides it) or to a dedicated "Elimination reserve" (which surfaces it). For transparent board and investor reporting: always pick Elimination reserve. Elimination runs as part of consolidation, and reconciliation then surfaces any elimination differences — IC balances that don't tie out between entities and that you need to resolve to keep your consolidated numbers credible.
What is intercompany elimination and how is it different from reconciliation?
Intercompany elimination is the process of stripping out transactions and balances between entities of a group during consolidation, so the consolidated numbers reflect only external activity. If production sells €800,000 to distribution, that shows up as IC revenue at production and IC cost at distribution. At group level it's an internal transfer, not an external transaction — elimination removes both sides so that group revenue reflects only what customers actually paid.
Without elimination you double-count intercompany activity. An SME group with a production and a distribution arm can easily report 20-30% of group revenue on paper that doesn't exist in reality — the same €800k from production to distribution counted again as the external sale. Investors who see your standalone numbers without elimination get a distorted picture of your real size and margin. Elimination is therefore more than an administrative step; it's what turns consolidated numbers from fiction into reality.
Elimination and reconciliation are two distinct steps that reinforce each other. Elimination = stripping out IC transactions and balances during consolidation — this runs automatically as part of the consolidation. Reconciliation = matching IC balances between entities (receivables = payables, revenue = cost) to find where elimination differences sit. Reconciliation is the diagnostic that tells you whether elimination lands cleanly or whether there are IC balances that don't tie out. Elimination differences that surface through reconciliation have to be resolved — and then you re-run the consolidation — to keep your consolidated reporting credible. For the full reconciliation cycle, see the guide on intercompany reconciliation for SME CFOs.
Inside an SME group, IC items typically come from five categories that each call for their own elimination approach: current accounts, loans and interest, intercompany revenue and cost, intercompany receivables and payables, and participations (only relevant at the holding level). For the broader context: pillar on consolidation for SME CFOs.
The four elimination methods: full GLA, per IC relationship, per transaction and manual
You can apply elimination in four ways. Three auto methods (full GLA, per IC relationship, per transaction) process items based on ERP data; the fourth method (manual IC entry) is a journal entry you post yourself for edge cases the auto methods don't cover. Each method has its own balance between precision and manual work and its own use cases — none is universally "better", the choice depends on the type of IC ledger account and the situation.
Eliminate every balance on a single ledger account
The simplest method: eliminate every balance on a specific ledger account across all entities. Quick to set up, low maintenance, but only works when the account is 100% intercompany. Classic example: a dedicated ledger account "IC receivables Dis BV" at production and "IC payables Pro BV" at distribution. These accounts hold only IC balances; elimination wipes them out completely.
The risk: if the account picks up an external posting by mistake, that posting gets eliminated by accident — and your external asset or revenue position is distorted. For the SME CFO an acceptable method on strictly IC ledger accounts, but not on mixed ones.
Per combination of entity pair plus ledger account
The medium-precision method: eliminate per IC relationship, where a relationship is defined as the combination of two specific entities plus the IC ledger account. ProdCo ↔ DistCo for IC revenue, ProdCo ↔ HoldCo for current accounts, and so on. Matching and offsetting happen per relationship; differences stay visible per relationship for the audit trail.
The default for SME groups. Gives you insight per IC relationship without forcing you to track every individual transaction. Workable in practice up to 10 entities; with 20+ entities the number of IC relationship pairs gets large (up to 190 pairs at 20 entities).
Offset individual postings
The highest-precision method: eliminate individual transactions between entities. Requires that your tool knows every IC posting as a separate line and can match it against the counter-posting at the other entity. The result: maximum audit trail, with exact visibility into which invoice flows into which group number or gets eliminated.
Indispensable for ledger accounts with mixed content — for example a receivables account that carries both external customer balances and IC receivables. Full GLA elimination would wipe out the external receivables here; per IC relationship is too coarse. Per transaction is then the only method that eliminates the IC items precisely and leaves the external ones standing. For PE portcos with covenant tracking, often the default because elimination differences flow straight through to group EBITDA.
Manual IC entry as a journal entry
The fourth method: a manual IC elimination entry the CFO or controller posts directly in the consolidation tool. No automatic matching against ERP transactions like per transaction, but an explicit journal entry where you decide yourself which items get offset and for what amounts. Unlike the other three methods, which always assume an existing posting in the source ledger.
Used for situations the auto methods don't cover: year-end corrections that fall outside the standard IC flow, one-off restructuring eliminations (legal reorganisation or acquisition integration), IC items not yet captured in the source system, or auditor-driven adjustments. Trade-off: maximum flexibility, but harder to trace back to source transactions through the audit trail. Requires explicit documentation of why the entry was made and what its effect is. For SME groups typically 1-5% of total elimination volume; for PE portcos with heavy restructuring activity that can climb to 10-15%. Finstack supports this through manual journal entries in the Entries menu, with the same audit-trail mechanics as the auto methods.
Four methods, four roles. The three auto methods process items coming out of your ERP data; the manual entry is your safety net for edge cases. The art isn't picking one method for everything but combining the right auto method per IC ledger account with manual entries for what the auto methods can't pick up. That's the hybrid approach almost every SME group ends up running in practice.
Which method for which IC category?
The five IC categories in an SME group each have their own characteristics and therefore their own preferred elimination method. The table below shows the default choice per category.
The rule of thumb for the auto methods: the more a ledger account is mixed with external transactions, the more you shift towards per-transaction elimination. The more an account is fully IC, the more often full GLA is enough. Per IC relationship sits in between and is the pragmatic default for most categories in most SME groups.
The manual IC entry isn't tied to a specific category — it gets used situationally. Typical moments: year-end (corrections on participations or profit appropriations that fall outside the standard flow), restructurings (legal reorganisation, mergers, acquisition integration), and adjustments at the auditor's request (corrections that can't be brought in through regular IC entries). In a normal SME yearly cycle, count on a handful of manual IC entries around the year-end close and sparing use across the monthly closes in between.
Participations add an extra dimension: at the holding level you eliminate the participation, at the subsidiary level you eliminate the mirror equity (share capital, share premium, retained result, reserves). Results for the current and prior year are generated automatically by Finstack; the other equity items have to be mapped explicitly per subsidiary. For the multi-entity context in detail: see multi-entity consolidation for SME groups.
When do you choose a hybrid approach?
The practical answer: almost every SME group with more than two entities runs a hybrid approach. Not as a luxury but out of necessity — one elimination method for everything means either too little precision (full GLA on mixed accounts produces false eliminations) or too much manual work (per transaction on accounts that are 100% IC). The manual entry sits on top for whatever the auto methods can't capture cleanly.
A concrete hybrid configuration for a typical 5-entity SME group with production, distribution and a holding:
- Full GLA for current-account ledgers and participations — these are 100% IC and rarely vary.
- Per IC relationship for IC loans plus interest and for IC revenue/cost on dedicated IC ledgers.
- Per transaction for receivables and payables where external customers sit mixed in with IC receivables.
- Manual IC entries for year-end corrections (participations, profit appropriations), restructuring eliminations and auditor-driven adjustments — used situationally, not embedded in the monthly cycle.
For PE portcos the pattern shifts further towards per transaction: elimination differences flow straight through to EBITDA reporting and covenant calculations. An elimination that's slightly too generous or too tight translates into an EBITDA swing visible to investors. Per-transaction elimination delivers the tight audit trail PE investors expect. Plus relatively more manual IC entries during heavy M&A activity or execution of a value creation plan.
Finstack supports this hybrid approach out of the box: per IC ledger account you configure which auto method runs on the Eliminations page, and manual IC entries go in as journal entries through the Entries menu. Four methods — three picked per IC ledger account, plus manual entries for edge cases — with a dashboard that shows per IC relationship what percentage of the account is IC-related, so you can quickly identify mixed accounts that need to be handled per transaction. For where transaction-level fits within consolidation: see transaction level vs trial balance consolidation.
Elimination ledger accounts: "Other equity" or "Elimination reserve"?
Every elimination triggers Finstack to generate an elimination ledger account automatically — needed to keep the group balance sheet balanced after IC items have been stripped out. Those accounts then have to be mapped to a line on your consolidated balance sheet. Two options, with different consequences for transparency.
Option 1: map to an "Other equity" line. The elimination accounts disappear into a catch-all line under Equity. Any residual (small differences that don't tie out to zero after elimination) vanishes into the "Other equity" line without showing up anywhere else in the annual accounts. Easier for private SME groups without external investors — no separate explanation needed to the board about what that line means.
Option 2: map to a dedicated "Elimination reserve" line. A dedicated line under Equity where every elimination effect lands visibly. Makes residual explicit on the balance sheet. Requires an explanatory note in the annual accounts, but gives stakeholders direct sight of how large the elimination impact is and whether any unexplained residual is sitting there. Recommended for PE portcos, VC portcos and other groups with external investors that want to be transparent about internal settlements.
The choice between the two is essentially a choice between easier reporting (Other equity) and a stronger information position with stakeholders (Elimination reserve). For SME CFOs with future financing rounds or exit scenarios on the horizon: always pick the Elimination reserve approach. Hiding feels easier, but over time it builds a weaker relationship with investors and banks. For a deeper explanation of the mapping mechanics, see the Finstack Help Center page on IC eliminations in practice.
Elimination for multi-entity and multicurrency groups
For groups with more than two entities, elimination complexity scales linearly with the number of IC relationship pairs. A 5-entity group has up to 10 IC relationship pairs; at 10 entities, up to 45 pairs. For each pair you pick the default method per IC ledger account. With well-designed tooling this is a one-off configuration — after that, the right method is applied automatically per relationship every month. For the multi-entity context in detail: see multi-entity consolidation for SME groups.
For multicurrency groups, FX translation comes before elimination. Each entity reports in its functional currency; the tool translates to the group's presentation currency at the relevant rate per period. Elimination then happens at the group-currency level, after translation. Important: matching IC items (reconciliation) happens in transaction currency — to separate real matching problems from FX translation effects. Elimination itself runs in group currency.
FX translation differences between booking and presentation rates are posted to a separate translation reserve under Equity, not as an elimination difference. This prevents you from confusing real elimination problems with currency fluctuations. Finstack handles this out of the box: each IC relationship is visible in both transaction currency and group currency, with the translation component shown separately. For multicurrency context: multicurrency consolidation for SME CFOs.
What should your tool be able to do for IC elimination?
A solid elimination workflow stands or falls on tools that support all four methods — three auto methods plus manual journal entries — while also pushing you to consciously decide which method fits each account. Six tool requirements make the difference for the SME CFO.
1. All four methods built in, configurable per IC ledger account. Full GLA, per IC relationship and per transaction all need to be available as auto methods in one environment, and manual IC entries need to be supported as journal entries for edge cases. Per ledger account you pick the right auto method — that's the hybrid configuration that's always needed in practice. Finstack delivers this through the Eliminations page inside the Entries menu, plus manual journal entries for whatever falls outside.
2. Automatic generation of elimination ledger accounts with a mapping choice. Every elimination creates a new ledger account; that account needs to be generated automatically and mapped to either "Other equity" (hides residual) or "Elimination reserve" (surfaces it). The choice has to be made deliberately, not buried in a hidden default.
3. Reconciliation built in as the diagnostic on elimination. Elimination runs automatically as part of consolidation, but without reconciliation you can't tell whether elimination differences exist. The tool should flag when material elimination differences indicate IC balances aren't tying out between entities and show exactly where the gap sits — per IC relationship, per ledger account — so you can resolve it deliberately before releasing the consolidated numbers.
4. Audit trail per elimination. Which posting was eliminated when, using which method, and with what effect on the group numbers. Indispensable for accountant and bank audits; for PE portcos often a mandatory part of investor reporting.
5. FX-aware elimination for multicurrency groups. Elimination in group currency, reconciliation in transaction currency, FX translation differences posted separately to a translation reserve. Essential for groups with international entities.
6. Native ERP connections for automatic data feed. Trial balances and transaction data have to refresh automatically from the bookkeeping systems. Finstack connects at the transaction level with Exact, AFAS, Twinfield, Yuki, Pennylane, eAccounting, Tripletex, Nmbrs, Xero, QuickBooks Online and Microsoft Dynamics 365 BC.
Start with your two largest IC relationships and configure the right method per IC ledger account for those. Test one consolidation cycle before scaling out to the other IC relationships. Start with the 14-day free Finstack trial to try the elimination functionality yourself.
Explore Finstack.
Free trial for 14 days.
Access to all features. No credit card required.
.png)
Three common mistakes in IC elimination
Applying one elimination method to everything
Full GLA on every IC ledger account gives you simple configuration but false eliminations on mixed accounts. Per transaction on every account gives you maximum precision but unmanageable manual work. Only manual entries for everything makes the cycle unsustainable at a monthly close cadence. What works: a hybrid approach, the right auto method per IC category plus manual entries for edge cases. Plan on a one-off configuration of one day for a 5-entity SME group.
Skipping reconciliation as the diagnostic after consolidation
Elimination runs automatically as part of consolidation. But without reconciliation as a follow-up step you can't tell whether there are elimination differences — IC balances that don't tie out between entities. The gap sits as residual on the balance sheet without you knowing where it came from. What works: reconciliation as a standing diagnostic step after every consolidation, resolving elimination differences until they fall within thresholds, then re-running the consolidation. Tooling that builds reconciliation in shows the gaps per IC relationship and per ledger account immediately. For the full reconciliation cycle, see the guide on IC reconciliation.
Not mapping elimination ledger accounts deliberately
The tool generates elimination accounts, you accept the default mapping without thinking — and residual disappears into an "Other equity" catch-all line without anyone realising that's what was chosen. What works: deliberately choose between "Other equity" (hidden, easy) and "Elimination reserve" (explicit, transparent). For groups with external investors: always go with Elimination reserve.
Frequently asked questions
Can't find your question? Let us know
What exactly is intercompany elimination?
Intercompany elimination is the process of stripping out transactions and balances between entities of a group during consolidation, so the consolidated numbers reflect only external activity. If production sells €800k to distribution, that shows up as IC revenue at production and IC cost at distribution. At group level it's an internal transfer, not an external transaction — elimination removes both sides so that group revenue reflects only customer revenue. Without elimination you double-count intercompany activity and overstate the real size of the group. Elimination always follows reconciliation: only with IC balances that tie out can you eliminate reliably.
What's the difference between IC reconciliation and IC elimination?
Elimination runs as part of consolidation, and reconciliation follows as the diagnostic. Elimination = stripping out IC transactions and balances during consolidation. Reconciliation = matching IC balances between entities (receivables = payables, revenue = cost) to find where elimination differences sit. Elimination differences — IC balances that don't tie out — surface through reconciliation and have to be resolved; then you re-run the consolidation so elimination lands cleanly. Elimination removes the net effect from the consolidated numbers; reconciliation makes sure you see the differences and act on them. For the reconciliation cycle, see the guide on intercompany reconciliation for SME CFOs.
Which four elimination methods exist and when do you use which?
Four methods, each with a different balance between precision and manual work. (1) Full GLA — eliminate every balance on a specific ledger account. Fastest method, only works when the account is 100% IC. (2) Per IC relationship — eliminate per combination of entity pair and IC ledger account. Medium precision, the default for SME groups because it gives an audit trail per IC relationship. (3) Per transaction — automatic matching of individual transactions between seller and buyer, highest precision and audit trail; required for IC ledger accounts with mixed content. (4) Manual IC entry — a journal entry the CFO or controller posts directly in the consolidation tool. Unlike per transaction: no automatic matching, you decide yourself which items get eliminated. Used for year-end corrections, one-off restructuring eliminations or IC items not yet captured in the source system. In practice most SME CFOs run a hybrid approach: different methods per IC category plus manual entries for edge cases.
What is a hybrid elimination approach and when do you need one?
A hybrid approach combines the four methods per IC category. For IC ledger accounts that are fully intercompany (current accounts between entities, IC loans): full GLA. For IC revenue/cost and receivables/payables where IC and external transactions can sit on the same account: per IC relationship or per transaction. For PE portcos with covenant tracking: more often per transaction because elimination differences flow straight through to EBITDA. Plus manual IC entries as a safety net for edge cases — year-end corrections, restructurings, auditor-driven adjustments. The hybrid approach is essentially required for SME groups — one method for everything either gives too little precision (full GLA on mixed accounts produces false eliminations) or too much manual work (per transaction on accounts that are 100% IC).
How do I map my elimination ledger accounts?
Finstack automatically generates elimination ledger accounts every time you apply an elimination. Those accounts have to be mapped so the balance sheet stays balanced. Two mapping options: (1) to a generic "Other equity" line — hides any residual from elimination differences in a catch-all line, easier for private SME groups without external investors; (2) to a dedicated "Elimination reserve" line under Equity — makes residual explicit on your balance sheet, recommended for PE portcos and groups reporting transparently to board and investors. Hiding feels easier, but builds a weak information position with stakeholders. For consolidation context: see the pillar on consolidation.
How does elimination work for multicurrency groups?
For multicurrency groups, FX translation comes before elimination. Each entity reports in its functional currency; the tool translates to the group's presentation currency at the relevant rate per period. Elimination happens at the group-currency level, after translation. FX translation differences between booking and presentation rates are posted to a translation reserve under Equity — not as an elimination difference. Important: matching IC items happens in transaction currency (to separate real mismatches from FX effects); elimination itself runs in group currency. Finstack handles this out of the box. For multicurrency context: see the guide on multicurrency consolidation for SME CFOs.
Which tool fits best for IC elimination for SME CFOs?
Finstack is the default choice for SME groups with 1-30 entities: all four elimination methods (full GLA, per IC relationship, per transaction and manual IC entries) built in, configurable per IC ledger account for the hybrid approach; automatic generation of elimination ledger accounts with a mapping choice between "Other equity" and "Elimination reserve"; FX-aware elimination for multicurrency groups; audit trail per elimination; native connections to Exact, AFAS, Twinfield, Yuki, Pennylane, eAccounting, Tripletex, Nmbrs, Xero, QuickBooks Online and Microsoft Dynamics 365 BC. From €29/month per entity, sign-up in 5 minutes, the whole SME group live in 1 day. Speedbooks and Visionplanner lack transaction-level elimination; BrightAnalytics and Lucanet have longer implementation timelines.
Related articles
CFO turned Founder - Finstack
Sources and provenance
- Finstack Help Center — Intercompany eliminations — Eliminations page, categorisation and method configuration
- Finstack Help Center — IC eliminations in practice — five IC categories, causes of incomplete elimination and mapping options
- Finstack Help Center — Intercompany reconciliation — reconciliation as the diagnostic on elimination
- finstack.io — Consolidation — elimination functionality and method configuration
- finstack.io — Integrations — native ERP connections at transaction level
- Raad voor de Jaarverslaggeving — Guideline 217 Consolidation (RJ-Annual edition 2025)
- finstack.io — Pricing — pricing plans and trial
Last reviewed: 5 June 2026 · Next review: September 2026
Consolidated reporting and forecasting.
