Intercompany Accounting and Group Reporting: The ERP Integration Checklist for Conglomerates

Every month-end close at a multi-entity group carries the same quiet risk. Subsidiaries run different ERP systems, finance teams reconcile intercompany balances by hand, and group controllers wait for one entity in Singapore to confirm a number that another entity in Frankfurt has already booked, differently. If that sounds familiar, the problem is rarely the ERPs themselves. It is how they are connected.

Key Takeaways

• ▸Intercompany accounting means recording, matching and eliminating transactions between entities in the same group, so consolidated accounts do not double-count revenue, costs or balances.
• ▸Most groups do not need one ERP everywhere. They need a reliable integration layer that feeds clean, mapped data into one consolidation engine.
• ▸The checklist that matters: elimination rules, transfer pricing evidence, multi-currency revaluation, automated data feeds, audit trails and an exception workflow.
• ▸2026 raises the bar on data: Pillar Two safe harbours draw on consolidated data, and IFRS 18 changes how group statements are presented from 2027.
• ▸Start with your highest-volume intercompany flows, usually loans and management charges, and automate those first.

Why Intercompany Accounting and Group Reporting Break Down at Scale

Groups don't start complex. They become complex. An acquisition adds a subsidiary running SAP. Another deal brings in a company on Oracle. The original business runs Microsoft Dynamics. Suddenly group finance is managing systems that don't naturally talk to each other, and every intercompany transaction between those entities becomes a reconciliation task.

Intercompany accounting sits at the heart of this. When Entity A in Germany sells services to Entity B in Malaysia, both entities record the transaction. When the group consolidates, that transaction must disappear from the combined picture, because from the group's perspective it never happened. Under IFRS 10, intragroup balances, transactions, income and expenses are eliminated in full on consolidation.

That elimination sounds simple. In practice, three things make it hard:

• ▸Transfer pricing. Prices for goods and services traded between related entities must follow the arm's length principle, and the evidence has to hold up in every jurisdiction involved.
• ▸Currency. Intercompany balances in a foreign currency must be revalued at period end, and differences between entities' functional currencies create mismatches.
• ▸Timing. If one entity books an invoice on the 30th and its counterpart books it on the 2nd, the balances won't match at month-end, even though both are correct.

Auditors and regulators expect every intercompany balance to be traceable. For US-listed groups, SOX Section 404 requires effective internal control over financial reporting, and intercompany eliminations are a classic area of audit focus. "We reconciled it eventually" is not evidence. A timestamped, system-generated trail of how each balance was matched and eliminated is.

For growing groups, the question isn't whether to invest in ERP integration. It's which integration pattern fits the current structure without forcing a costly rip-and-replace of systems the subsidiaries already rely on. If you're still deciding whether to move subsidiaries onto one platform, our guide to consolidating subsidiaries onto one ERP tenant covers that decision in detail.

The ERP Integration Patterns Multi-Entity Groups Actually Use

Not every group has the budget or the appetite to standardise on a single ERP, and for many it isn't the right answer anyway. Business units often have genuinely different operational needs. What matters is how you connect those systems to a reliable consolidation layer.

Native options have also improved. Microsoft Dynamics 365 Business Central supports intercompany transactions and financial consolidation across separate Business Central environments, which arrived in the 2023 release wave 2. Dynamics 365 Finance offers its own consolidation, elimination and currency translation tools. For mid-market groups already on Microsoft, that can remove the need for a separate hub entirely.

One counter-intuitive point: sophisticated groups sometimes over-engineer their intercompany hub, building bespoke matching logic that duplicates what a proven consolidation platform such as SAP Group Reporting, Oracle Financial Consolidation and Close or BlackLine already does. Configuring a proven engine well usually beats building something proprietary, because proprietary always costs more to maintain.

What Is Changing in 2026 and Why Finance Leaders Should Care

Three developments make clean intercompany data more valuable this year:

• ▸Pillar Two global minimum tax. In January 2026 the OECD released its side-by-side package, including a permanent simplified effective tax rate safe harbour that generally draws on consolidated financial statement data. Groups in scope need entity-level figures they can trust and trace.
• ▸IFRS 18. The new presentation standard IFRS 18 replaces IAS 1 for annual periods beginning on or after 1 January 2027. IFRS reporters will need to restructure how group income statements are categorised and disclosed, and that work starts with consistent account mapping across entities.
• ▸AI in the close. ERP and consolidation vendors are adding AI-assisted matching and anomaly detection. These tools only help when intercompany data is mapped consistently. Messy data simply produces faster wrong answers.

The common thread is data lineage: being able to trace any consolidated figure back to its source transaction, with timestamps and system identifiers.

The Practical Checklist: What Your Integration Must Cover

Whether your group has three entities or thirty, the same requirements apply.

Elimination rules configuration. Every intercompany flow, whether sales, loans, dividends or management charges, needs a defined elimination rule. When Entity A shows a receivable from Entity B and Entity B shows a matching payable, both are eliminated from the consolidated balance sheet. Rules should be entity-specific, account-specific and reviewed whenever the group structure changes.

Transfer pricing evidence. The documentation that justifies intercompany prices should be linked to the transactions themselves, so it can be retrieved per transaction during a tax audit rather than hunted for in a shared drive.

Multi-currency revaluation. Foreign-currency intercompany balances must be revalued at the correct closing rate. The integration layer should apply the same rate source and logic across every entity, regardless of which ERP it runs.

No manual re-keying. The consolidation layer should pull trial balances and intercompany detail directly from each subsidiary ERP via API or scheduled extract, validate them against mapping rules and flag exceptions automatically. Finance staff should approve exceptions, not type figures.

Audit trail automation. Every match, elimination entry and revaluation adjustment should carry a timestamp, a user or system identifier and a link back to the source transaction.

• ▸Real-time visibility: the group controller should see intercompany positions at any point in the month, not only at period end, ideally through a Power BI dashboard on top of the consolidated data.
• ▸Exception workflow: unmatched balances should trigger notifications to the relevant subsidiary teams, with an escalation path if they aren't resolved in time.

Practical tip: even small teams can implement this incrementally. Start with your highest-volume intercompany flows, typically loans and management fees, and automate those first. A handful of transaction types usually accounts for most of the reconciliation effort.

How PapaSiddhi Can Help

PapaSiddhi Technologies designs and builds the integration layer behind group reporting. Our ERP for business groups and ERP integration services cover architecture assessment, data mapping, build, testing and ongoing support.

For groups on Microsoft, our Business Central and Dynamics 365 team can set up intercompany partners, consolidation business units and eliminations. For mixed ERP landscapes, our developers build API-based feeds into the consolidation platform you choose. Where it adds value, our AI and ML development team can add matching suggestions and anomaly flags on top of clean data.

You don't need a large internal IT team to get started. If you need extra capacity, you can hire Business Central developers or a dedicated team, and we aim to share suitable developer profiles within 48 hours. Tell us how your intercompany process works today and we'll tell you honestly where the quickest wins are. Book a free consultation.

Related case studies: multi-entity Business Central with ZATCA e-invoicing for a Saudi business group and multi-branch finance consolidation on Business Central (Denmark).

Conclusion

Intercompany complexity isn't going away. Acquisitions, new jurisdictions and new reporting rules make it more demanding each year. But the tools to solve it are mature and within reach of mid-market groups.

The groups pulling ahead aren't the ones with the biggest ERP licences. They're the ones with clean integration, consistent account mapping and an automated reconciliation process that frees their finance team from month-end firefighting. Start with your highest-pain flows, build incrementally, and the faster close follows.