An intercompany transaction is any financial transaction between two or more entities that are members of the same corporate group — under common ownership or control. Intercompany transactions include the sale of goods between subsidiaries, the provision of management services from a parent to its subsidiaries, intragroup loans and interest payments, shared service recharges, rental of assets, dividend payments, and royalties for use of intellectual property. These transactions are legitimate business activities within the group — but they must be identified, matched, agreed between the transacting entities, and eliminated during the consolidation process, because they do not represent transactions with parties external to the group.
The practitioner distinction: intercompany transactions create matching obligations at period end. For every intercompany receivable in Entity A’s balance sheet, there must be an exactly equal intercompany payable in Entity B’s balance sheet. When they do not match — because of timing differences, currency differences, or accounting errors — the consolidation elimination is incomplete, and the group financial statements carry a reconciliation difference that must be investigated and resolved before the close is finalised.
In the Context of the GCC
In GCC conglomerate structures, intercompany transaction volumes are frequently very high relative to external revenue — particularly where a holding company provides shared services (finance, HR, IT, legal) to all operating subsidiaries, where the group treasury function manages cash centrally and on-lends to subsidiaries, or where properties are owned by one entity and leased to others. In these structures, the intercompany ledger can represent the majority of total transaction volume, and the discipline of the intercompany accounting process is as important as the external transaction process. Groups where intercompany accounting is informal — where management fees are agreed verbally and posted quarterly in round numbers — have consolidation problems that are structural, not incidental.
How This Connects to EPM and Systems
Intercompany transaction management in an EPM consolidation environment requires two things: clean intercompany flags at the GL account level (so the system knows which balances are intercompany), and a structured intercompany confirmation process before each consolidation run. Oracle FCCS provides intercompany matching as a standard module — each entity confirms its intercompany balances, the system matches them against the counterparty’s submission, and mismatches are surfaced before the consolidation runs rather than discovered during it. This pre-consolidation confirmation process is the single most effective control for preventing intercompany reconciliation breaks from delaying the close.
What Goes Wrong
The failure that causes consolidation discrepancies every close cycle is intercompany transactions posted in one entity’s books without notification to the counterparty entity. Entity A charges Entity B a management fee in December. Entity A posts the receivable in December. Entity B learns about the charge in January, when the invoice arrives. At December consolidation, Entity A’s intercompany receivable has no matching payable in Entity B — producing an elimination difference equal to the management fee. This is a process failure — the intercompany charge was not agreed and communicated in advance — that no amount of EPM configuration can fix without a corresponding process change.
How Loop Wise Solutions Encounters This
Intercompany process design — agreeing the timeline, communication method, and posting discipline for intercompany transactions between group entities — is a process deliverable in every consolidation implementation we undertake. The technical FCCS configuration for intercompany matching is straightforward. The organisational challenge of getting five or ten subsidiary finance teams to post intercompany entries to a common deadline, with agreed amounts, is the real implementation challenge. We address it through governance design: a written intercompany accounting policy, a close calendar that includes intercompany confirmation deadlines, and an escalation process for entities that do not confirm on time.
