Reconcile Before You Eliminate: 7 Checks

Eliminations are often described as a technical part of consolidation. Yet when intercompany figures do not match, the main problem is rarely the elimination entry itself. The problem usually starts earlier in the workflow.

Before finance eliminates internal revenue, costs, receivables and payables, transactions must be identified, mapped, periodised and reconciled between companies. Otherwise, an elimination may hide a discrepancy instead of resolving it.

For CFOs and controllers in private multi-entity groups, the sequence matters: reconcile first, explain the difference, document the decision and eliminate last.

Short answer: What should be reconciled before elimination?

Before intercompany balances are eliminated, finance should check counterparty, amount, currency, period, account and dimension, documentation and discrepancy status. Both sides of a transaction should be connected and explainable. An elimination should remove a documented internal effect from group reporting, not conceal that subsidiaries report different versions of the same event.

Why reconciliation comes first

An internal invoice has at least two sides. The seller records revenue and a receivable. The buyer records a cost and a payable. These internal effects normally disappear at group level, but the entries do not always match automatically.

Common causes include:

• the invoice is posted in different periods
• the amount is translated at different exchange rates
• companies use different accounts or dimensions
• a credit note is recorded on only one side
• the counterparty is missing or incorrectly tagged
• one company accrues the cost while the other follows the invoice date
• the transaction is included in one reporting package but not the other

If a controller eliminates a total without understanding these differences, the group number may look right while the discrepancy rolls into the next period.

A CFO scenario: six companies and a NOK 430,000 difference

Consider a private group with six companies across multiple countries. Three use one accounting system, two use another, and a newly acquired company uses a third.

At month-end, the parent reports NOK 4.8 million in internal service revenue. The subsidiaries report NOK 4.37 million in corresponding costs. The difference is NOK 430,000.

It is tempting to post a manual elimination that makes the group report balance. Instead, the controller investigates and finds three explanations:

1. A NOK 210,000 invoice is posted in July by the seller and August by the buyer.
2. A NOK 140,000 credit note is missing in one company.
3. NOK 80,000 is posted to an external consultant account without a counterparty tag.

Finance can now handle each issue correctly. The timing difference can be documented and followed up next month. The credit note can be posted in the source system. The classification error can be corrected. Only then is the actual internal effect eliminated.

The distinction matters: the group has not merely produced a report that balances. It has created a control trail that explains why.

The 7 checks before elimination

1. Check the counterparty

Both sides must point to the correct group company. A description such as “management fee” or a familiar customer name is not always enough. Use counterparty fields, internal customer and supplier numbers, dimensions or other stable identifiers where systems support them.

If the counterparty exists only in one controller’s memory, the process is person-dependent.

2. Check amount and currency

Compare both local and group currency. A difference may come from the invoice amount, the exchange rate or the translation date.

Do not combine every currency difference into one unexplained residual. Separate expected translation effects from errors that require correction.

3. Check the period

A transaction may be correctly posted locally but appear in different reporting periods. This often happens around month-end, with accruals and when invoices are approved late.

Mark whether the difference is timing-related, who owns the follow-up and when it should reverse or match.

4. Check the account and group mapping

The seller may use “internal services” while the buyer uses “consulting costs”. Local charts of accounts need not be identical, but mapping to the group structure must make the relationship visible.

Incorrect mapping can leave total profit unchanged while distorting gross margin, cost allocation or segment reporting.

5. Check dimensions

Project, department, cost centre and country can mean different things across companies. Decide which dimensions should carry into group reporting and which are local only.

Dimensions should help controllers explain discrepancies, not introduce a new comparison error.

6. Check documentation

Controllers should be able to move from the reconciliation line to the underlying transaction, voucher and attachment where data is available. Manual adjustments need a visible reason, owner and approval.

Documentation makes the control repeatable next month and helps finance answer auditors, the board or management without reconstructing the entire process.

7. Check discrepancy status before posting

Not every difference must be zero before reporting, but every material difference should have a status. For example: explained timing, correction requested, posted, accepted residual or escalated.

The CFO can then distinguish a known difference with clear follow-up from an unknown amount pushed into an elimination.

Reconciliation and elimination are different controls

Reconciliation asks: Have both companies recorded and classified the same internal event in a way we can connect?

Elimination asks: Which documented internal effect should be removed when the group is presented as one economic entity?

The two controls are connected, but they are not the same. Reconciliation finds and explains differences. Elimination treats the internal effect in group reporting.

This distinction is especially important when the group uses several ERP and accounting systems. Local reports may be correct individually while stopping at company and system boundaries. Read more about multi-ERP control and group reporting.

What should an intercompany reconciliation show?

A practical overview should include at least:

• company and counterparty
• account and group reporting line
• local and group currency
• period and voucher date
• amount on both sides
• difference
• explanation and status
• responsible owner
• transaction and voucher reference where available
• elimination or correction resulting from the control

The goal is not to make the overview large. It is to make discrepancies visible, traceable and manageable.

When Excel becomes a risk

Excel can be valuable for analysis and flexible controls. Risk appears when a workbook becomes the only home for counterparty logic, manual matches, status comments and elimination entries.

Month-end then depends on file versions and individuals. It becomes harder to see whether a difference is new, already explained or actually corrected in the next period.

A shared control layer can bring reconciliation together across companies and source systems while finance continues using Excel where it adds value. See also financial control across companies.

A stronger month-end workflow

A practical sequence is:

1. Collect and structure transactions from each company.
2. Identify intercompany counterparties.
3. Match amount, currency, period, account and dimension.
4. Explain discrepancies and assign owners.
5. Correct source data where appropriate.
6. Approve documented residual differences.
7. Post and verify eliminations.
8. Preserve the control trail in the report and next period.

This makes elimination the endpoint of a control, not a shortcut around it.

Sumledger’s role

Sumledger is a financial control layer for private groups that have outgrown Excel but do not need a heavy enterprise EPM system.

Sumledger connects to ERP and accounting systems and supports group reporting, consolidation, eliminations, analysis and Excel workflows. Where data is available, CFOs and controllers can work from group figures down to accounts, dimensions, transactions, vouchers and attachments.

The goal is not only to make the elimination entry balance. It is to help finance see what has matched, what differs, who follows up and how the number can be explained.

Summary

Reconciliation comes before elimination. Check counterparty, amount and currency, period, account and mapping, dimensions, documentation and discrepancy status before removing the internal effect.

The elimination then becomes a documented treatment of intercompany items, not an entry that hides unknown differences.

Want to see how Sumledger gives finance one control layer for reconciliation, eliminations and group reporting? Book a short demo.