Intercompany eliminations are technically straightforward — every debit and credit between group entities is reversed so that the consolidated statements reflect only external activity. The accounting rules are clear. What makes eliminations genuinely difficult in practice is not the accounting but the operating model: coordinating data from multiple teams, in multiple time zones, on different accounting systems, working to the same close deadline every month.
This post covers the governance, process, and policy decisions that determine whether a group’s intercompany elimination program runs cleanly or becomes the bottleneck that extends every close.
Strategy 1: Treat Eliminations as a Program, Not a Series of Monthly Events
The most significant mindset shift for finance teams struggling with eliminations is to stop treating them as something that happens at close and start treating them as a continuous program with monthly execution.
A program approach means the policies are designed once and reviewed periodically. The technology configuration — which accounts are tagged as intercompany, which elimination rules are stored, which tolerances apply — is set up once and applied automatically each period. The monthly close doesn’t involve rebuilding anything; it involves running a defined process and managing exceptions.
By contrast, a “monthly event” approach means that every close involves rediscovering what the intercompany positions are, manually matching them, and posting elimination entries that were not stored from last month. Each month is a fresh start. Each close is as hard as the last.
The practical difference: a group that runs intercompany eliminations as a program can close in three days what a comparable group running the monthly event model closes in eight.
Strategy 2: Define the Governance Model Before the Close Starts
Eliminations require input from multiple entities and coordination by a central function. Without clear ownership at each step, the work falls into gaps — each entity assumes someone else is handling the reconciliation, and the group finance team discovers the mismatches on day one of close.
A functional governance model assigns specific responsibilities:
| Role | Responsibility |
|---|---|
| Group finance / consolidation team | Publishes intercompany policy and rate tables; confirms the elimination rules in the system; approves the consolidated result; owns the escalation process |
| Entity finance team | Maintains intercompany accounts using agreed account codes and counterparty references; submits the intercompany schedule alongside the trial balance; confirms balances with counterparties before the close submission |
| Named intercompany contact in each entity | First point of contact for mismatch investigation; responsible for confirming or disputing balances within the agreed response time; escalates unresolvable differences before the close deadline |
Without named ownership at the entity level, mismatch investigation queries go unanswered during close — the group finance team is left chasing multiple contacts who each believe someone else is responsible.
Strategy 3: Structure the Close Calendar Around Intercompany Dependencies
Eliminations cannot proceed until intercompany balances are confirmed. Close calendars that treat intercompany reconciliation as an activity that happens in parallel with entity close are structurally flawed — the reconciliation requires both sides of each balance to be finalised before it can begin.
The correct sequencing:
Intercompany-aware close calendar — 10-entity group Day −3 (pre-close): Group finance publishes exchange rate table and confirms intercompany policy reminder to all entity contacts.
Day 1 (close opens): Entities finalise their own books and submit trial balance AND intercompany schedule to group. Any new accounts must be flagged for mapping review.
Day 2: Group finance runs intercompany matching. Matched pairs confirmed automatically. Exception list (unmatched balances) distributed to entity contacts by 10am.
Day 2–3: Entity contacts investigate and resolve exceptions. Confirmed matches returned to group by end of Day 3.
Day 3: Elimination entries posted against confirmed matched balances. Consolidation run executed.
Day 4–5: Group finance reviews consolidated output, writes management commentary, approves for distribution.
This calendar reserves the first three days for data submission and reconciliation — so that elimination entries on Day 3 are posted against confirmed positions, not best guesses. The consolidation runs once, against clean data, rather than multiple times as corrections arrive.
Strategy 4: Write the Intercompany Policy and Enforce It
Most intercompany problems trace back to one of a small number of policy gaps. A complete intercompany policy covers:
- Transaction cut-off: Which date governs recognition — invoice date, shipment date, service delivery date — and who adjusts if an entity has recorded a different date
- Exchange rates: Which rate applies to intercompany transactions, which source publishes it, and the deadline by which it must be applied
- Account codes: Which accounts are used for each transaction type, and the counterparty reference format that must appear on every intercompany entry
- Transfer pricing: The applicable markup rates for each transaction type between entity pairs, and the process for updating them when a transfer pricing study is refreshed
- Dispute resolution: The escalation path when a balance cannot be confirmed in time — who makes the final judgment call, and how the difference is treated in the current period
The policy doesn’t need to be long. It needs to be specific, current, and distributed to entity finance contacts at the start of each reporting year — not filed somewhere and referenced only when something goes wrong.
Strategy 5: Design Escalation Protocols for When Mismatches Don’t Resolve
Some intercompany mismatches will not be resolved before the close deadline, regardless of how well the process is designed. A governance protocol that has no answer for unresolvable mismatches produces improvised solutions at close — ad hoc adjustments, plug entries, and workarounds that accumulate across periods.
The escalation protocol should define:
- Materiality threshold: Differences below a defined amount (e.g., 0.5% of the transaction value or a fixed dollar threshold) are waived with a documented note; differences above the threshold require resolution or escalation
- The CFO call: When entity contacts cannot agree within the close window, the group CFO (or designated authority) makes the determination — which entity adjusts, by how much, and in which period the adjustment is recognised
- Carry-forward documentation: Any balance carried forward as unresolved must be documented in the working papers with the reason, the entity responsible for investigation, and the expected resolution timeline
✅ The discipline that makes escalation work: Every escalation should be reviewed to determine whether it represents a transactional error (one-off) or a systemic problem (recurring). Transactional errors are corrected. Systemic problems are fixed in the policy or process — so the same escalation doesn’t recur every month.
BrizoConsol supports the intercompany elimination program with automated matching before the close runs, elimination rules stored and applied consistently each period, and exception lists surfaced for investigation — so eliminations are posted against confirmed balances, not unconfirmed estimates. Learn more or see it in action →