Intercompany Eliminations: The Consolidation Audit Procedure Juniors Get Wrong

The junior spent three hours ticking and bashing the IC recon before anyone asked whether she'd translated the USD payable at the closing rate. She hadn't. The €3.2 million difference she'd flagged as a "reconciliation item" on the parent's receivable from the German sub was half FX, and nobody on the engagement caught it until the second review round. I've seen this exact sequence on four group audits in the last two years, and every time the root cause is the same: IC eliminations get treated as a tick box exercise rather than an accounting procedure with real judgment in it.

IC eliminations under IFRS 10 .B86 require the group to eliminate in full all intragroup assets, liabilities, equity, income, expenses, and cash flows. ISA 600 .A44-A48 set out the group engagement team's responsibilities for evaluating whether IC transactions and balances have been properly identified, reconciled, eliminated, and presented in the consolidation.

What IFRS 10 .B86 requires for intercompany eliminations

IFRS 10 .B86 is direct. A parent shall eliminate in full intragroup assets and liabilities, equity, income, expenses, and cash flows relating to transactions between entities of the group. The words "in full" leave no room for partial elimination or netting.

The requirement applies to every transaction between entities within the consolidation scope. Sales from the parent to a subsidiary, management fees from a subsidiary to the parent, loans between group entities, dividends paid within the group, transfers of inventory between components. Each of these must be identified and removed from the consolidated FS so that the group presents as a single economic entity.

IFRS 10 .B86(c) addresses unrealised profits and losses. When one group entity sells inventory to another and the purchasing entity has not yet sold it to a third party by year end, the profit recognised by the selling entity on the IC sale must be eliminated. The consolidated FS should carry that inventory at the original cost to the group, not at the IC transfer price.

The same principle applies to fixed assets transferred within the group. If a parent sells a building to a subsidiary at a gain, that gain is unrealised from the group's perspective. It remains in the consolidated balance sheet as an inflated asset carrying amount and must be eliminated. The subsequent depreciation on the inflated amount must also be adjusted each period until the asset is disposed of to a third party.

IFRS 10 .B86(a) addresses intragroup balances. At year end, the parent's receivable from a subsidiary should equal the subsidiary's payable to the parent. In practice these balances rarely agree without intervention. Timing differences, FX rate differences, unrecorded transactions, and rounding in ERP systems create mismatches that must be reconciled before elimination.

Uniform accounting policies under IAS 27.19 -20

IAS 27.19 (for separate FS) and IFRS 10 .B87 (for consolidated FS) require that consolidated FS be prepared using uniform accounting policies. If a component uses different accounting policies from the parent for like transactions and events, adjustments must be made to the component's financial information before consolidation.

This matters for IC eliminations because a policy difference can create a false IC mismatch. If the parent recognises revenue on delivery and the subsidiary recognises revenue on dispatch, an IC sale near year end may be recorded as revenue by the subsidiary but not as a purchase by the parent (because the goods are still in transit). The elimination will not balance. The fix is not to force the elimination to balance by adjusting the elimination entry. The fix is to first align the accounting policies, then perform the elimination.

IAS 27.20 states that the FS of the parent and its subsidiaries used in preparing the consolidated FS shall be prepared as of the same reporting date. Where reporting dates differ (a subsidiary with a March year end consolidated into a December parent), IAS 27.20 requires additional financial information to be prepared as of the parent's reporting date, or adjustments for significant transactions between the dates. IC balances that arose between the component's reporting date and the parent's reporting date will not appear in the component's FS unless this additional information is prepared.

The group engagement team's role under ISA 600

ISA 600 (Revised) assigns specific responsibilities to the group engagement team (GET) regarding the consolidation process, including IC eliminations.

ISA 600 .A44-A48 address the GET's evaluation of the consolidation process. The GET evaluates whether intragroup transactions, unrealised profits, intragroup balances, and related tax effects have been eliminated appropriately. This is not delegated to component auditors. The GET performs or directs the audit of the consolidation adjustments, including eliminations.

ISA 600.30 -31 require the GET to understand the group's consolidation process: how IC transactions and balances are identified, how reconciliation differences are resolved, how elimination entries are prepared, and how those entries are reviewed. The understanding extends to the IT systems used for consolidation. A group that consolidates in Excel has different risks than a group using a dedicated consolidation tool like SAP BPC or OneStream.

For the GET, the practical question is whether we can trace every material IC balance and transaction from the component's records through the IC reconciliation to the elimination entry in the consolidation workbook. If the answer is no at any point in the chain, the elimination has not been adequately audited. The file should tell a story from component GL through reconciliation to elimination journal, and if that story has gaps, you have an audit problem.

Component auditors contribute by confirming IC balances and transactions at the component level ( ISA 600 .A47). The GET issues instructions to component auditors specifying what IC information must be reported. Outstanding balances at year end, transactions during the period, unrealised profit amounts, currency of denomination. Without these instructions, component auditors may not report the information the GET needs to perform elimination procedures.

Five errors juniors make on intercompany eliminations

These are the errors that show up repeatedly on group audit review files. Each one causes either a misstatement in the consolidated FS or a documentation gap that inspectors flag.

Translating foreign currency after elimination instead of before. When a parent entity in euros has a subsidiary in US dollars, the IC balance exists in two currencies. The subsidiary records a payable of $1.1 million and the parent records a receivable of €1 million. At year end the USD has weakened and the parent's receivable translates to €950,000. The difference (€50,000) is a foreign exchange effect, not a reconciliation difference. If the junior eliminates the USD amount against the EUR amount without first translating both to the group's presentation currency at the closing rate, the elimination entry is wrong and a fictitious reconciliation difference appears. Translate first, then eliminate. The FX difference runs through OCI ( IAS 21.39 ), not through the elimination.

Recording one-sided elimination entries is the second error I see. An elimination entry must debit one account and credit another for the same amount. A junior who eliminates the IC receivable on the parent side but forgets to eliminate the corresponding payable on the subsidiary side produces a one-sided entry. The consolidated balance sheet will show a liability that does not exist from the group's perspective. This error doubles in frequency when the consolidation workbook does not have a dedicated elimination column and instead adjusts component trial balances directly.

Ignoring timing differences between components is the third. The parent records a €500,000 cash transfer to a subsidiary on 30 December. The subsidiary's bank does not credit the amount until 3 January. At year end the parent has derecognised the cash and recognised a receivable. The subsidiary has no corresponding payable because it has not received the cash. The IC accounts do not reconcile. The junior marks it as a "timing difference" and moves on. The right procedure is to identify whether this creates a misstatement in either component's individual FS (it likely does, because the subsidiary may need to accrue the amount) and to ensure the elimination addresses both the balance sheet and the cash flow statement impact.

Fourth, failing to identify all IC balances. The formal IC reconciliation covers receivables and payables. But IC transactions also flow through accrued expenses, prepayments, deferred revenue, loans, and equity accounts. A subsidiary that receives a management fee invoice dated in December but records it in January has an IC accrual that will not appear on the standard IC reconciliation schedule. If the junior only reconciles designated IC accounts, these balances are missed.

Step-by-step elimination audit procedure

This procedure applies to any group engagement where material IC transactions and balances exist.

What the GET checks

The GET's review of IC eliminations goes beyond verifying arithmetic. ISA 600 .A48 requires evaluation of whether the eliminations are appropriate in the context of the consolidated FS. The agree-to-agree round always seems to happen late on a Thursday, and in my experience the difference between a clean file and a mess is whether the team insisted on the four checks below during planning rather than during review.

The team checks that the consolidation workbook's elimination column is self-balancing. The sum of all elimination entries should net to zero across all accounts (within rounding). An unbalanced elimination column indicates a missing entry.

The team checks that the PY elimination entries have been properly reversed (where applicable) and re-posted at current-year amounts. A common error in manual consolidations is to carry forward the PY unrealised profit elimination without updating it for current-year inventory levels.

The team checks that IC eliminations are consistent with the group's accounting policy manual. If the policy states that management fees between entities are charged at cost, the elimination should reflect cost-based transactions. If the team discovers markup in IC management fees, this is a policy issue that may require unrealised profit consideration.

The team checks the tax impact. IC profit eliminations change the group's consolidated profit. In some jurisdictions the elimination of unrealised profit from inventory transfers creates a deferred tax asset. The tax was paid on the profit at the component level, but the profit is eliminated in the consolidated FS. IAS 12.39 addresses this. If the junior eliminated the profit but not the corresponding deferred tax, the consolidated FS understate the deferred tax asset.

Worked example: Van der Berg Holding N.V.

Van der Berg Holding N.V. is a Dutch holding company with three wholly owned subsidiaries: Van der Berg Productie B.V. (Netherlands, €45 million revenue), Van der Berg Deutschland GmbH (Germany, €22 million revenue), and Van der Berg Logistics B.V. (Netherlands, €8 million revenue). Group revenue is €75 million, but €12 million is intercompany (€9 million from Productie to the German subsidiary for finished goods, €3 million from Logistics to Productie for transport services). Consolidated revenue after elimination: €63 million.

1. Obtain the intercompany schedule. The group finance team provides a schedule showing IC receivables/payables for each entity pair, IC sales/purchases, a €2.5 million IC loan from the holding company to the German subsidiary, and a €600,000 management fee charged by the holding company to all three subsidiaries.

   Documentation note: File the IC schedule. Confirm it includes all transaction types (trade, loans, management fees, and dividends). Note that the schedule does not include a line for IC dividends. Verify with management whether any dividends were declared during the period.

2. Reconcile balances. Productie records a receivable from Deutschland of €1.4 million. Deutschland records a payable to Productie of €1.38 million. The €20,000 difference is an FX effect (the receivable is denominated in euros at Productie, but Deutschland records it in euros translated from its functional currency euro reporting, with a minor FX rounding difference from the ERP system). After investigation, the difference is below the €25,000 reconciliation threshold (set at 5% of component PM of €500,000).

   Documentation note: Document the reconciliation for each entity pair, the nature of each difference, the currency of denomination, and confirmation that differences below threshold were considered for aggregation. Record that the FX rounding difference is an ERP system limitation, not an error.

3. Test unrealised profit on inventory transfers. Productie sold finished goods to Deutschland at a 20% markup on cost. At year end, Deutschland holds €1.8 million of inventory purchased from Productie. The unrealised profit is €1.8 million divided by 1.2, times 0.2 = €300,000. The group has eliminated €300,000 from consolidated inventory and consolidated gross profit. The PY elimination was €240,000 (based on €1.44 million of IC inventory then on hand). The current-year consolidation correctly reverses the €240,000 opening adjustment and posts the €300,000 current-year elimination.

   Documentation note: Document the markup percentage (verified to IC pricing policy and sample of invoices), the inventory on hand at year end (agreed to Deutschland's inventory listing), the calculation of unrealised profit, and the comparison to the PY elimination. Note the €60,000 net income statement impact (additional elimination of €300,000 less reversal of €240,000).

4. Eliminate the intercompany loan and management fees. The €2.5 million loan from the holding to Deutschland eliminates against the corresponding IC liability. The €600,000 management fee income at the holding eliminates against the management fee expenses at the three subsidiaries (€200,000 each). Verify the elimination entries are posted and the consolidated income statement shows zero IC management fee revenue and zero IC management fee expense.

   Documentation note: Trace the loan elimination to both the balance sheet (receivable/payable) and the cash flow statement (ensure the loan advance does not appear as an investing/financing activity in the consolidated cash flow). Trace the management fee elimination to both income and expense lines.

5. Review the elimination column. The total of all elimination debits equals the total of all elimination credits. The column is self-balancing. No unmatched entries exist.

   Documentation note: Record the self-balancing check on the elimination column. Sign off the IC elimination section of the consolidation workbook.

Practical checklist

Common mistakes

• The FRC has flagged group audit files where the IC reconciliation covered trade balances only, missing IC loans, management fees, accrued expenses, and deferred revenue. IFRS 10 .B86 requires elimination of all intragroup items, not just those in designated IC accounts.

• Unrealised profit on IC inventory transfers is calculated at year end but not reversed from the opening balance, resulting in a double-count. This is particularly common in manual consolidation workbooks where the PY elimination entry is hard-coded rather than formula-driven.

• The GET relies on component auditors to confirm IC balances but does not issue specific instructions on what to confirm. Without standardised instructions ( ISA 600 .A47), component auditors report incomplete information and the GET discovers gaps at the final review stage.

Related content

• Consolidation. Glossary entry covering the consolidation process under IFRS 10 , including the elimination of intragroup transactions.
• Materiality calculator. Useful for setting component materiality under ISA 600 , which determines the threshold for investigating IC reconciliation differences.
• Component materiality in group audits: ISA 600 allocation methods. Covers how component materiality is set, which directly affects the threshold for IC reconciliation differences the GET investigates.

Related tools