Skip to content
ERP Migration

ERP Migration: Handling Intercompany Transactions and Consolidations

A practical guide for CIOs and finance leaders on migrating intercompany transactions and consolidations. Covers data mapping, elimination rules, reconciliation, and risk mitigation strategies to ensure financial integrity during ERP upgrades.

4 min readSysGenPro Editorial
ERP Migration: Handling Intercompany Transactions and Consolidations

Direct Approach to Migrating Intercompany Transactions and Consolidations

Handling intercompany transactions and consolidations during an ERP migration requires a rigorous, finance-led approach that prioritizes data integrity and reconciliation accuracy. The recommended approach involves a complete mapping of entity structures, chart of accounts, and intercompany matching rules before any data is loaded. This phase is critical because intercompany balances must net to zero in consolidated views, and any discrepancy in the source data or mapping logic will result in material financial reporting errors. The primary risks to control include mismatched entity codes, incorrect currency conversion rates, broken elimination rules, and loss of audit trails. By treating intercompany data as a distinct, high-risk data domain, organizations can ensure that the new ERP system supports accurate group reporting from day one. This process is not merely a technical data transfer but a financial control exercise that demands close collaboration between IT, finance, and external auditors.

Preparation: Entity Structure and Chart of Accounts Mapping

The foundation of a successful intercompany migration is the accurate definition of the legal entity structure in the target ERP. Each legal entity in the legacy system must be mapped to a corresponding entity in the new system, ensuring that tax jurisdictions, reporting currencies, and fiscal calendars are correctly configured. This step requires a detailed review of the organizational hierarchy, including parent-subsidiary relationships and minority interests. The chart of accounts (COA) mapping is equally critical. Intercompany accounts must be identified and standardized across all entities to ensure that transactions can be matched and eliminated correctly. If the legacy system uses different account codes for intercompany receivables and payables in different entities, these must be harmonized in the target system. This preparation phase should involve the finance team to validate that the new structure supports current and future reporting requirements. Any changes to the COA or entity structure should be documented and approved by the CFO or Controller before proceeding to data extraction.

Defining Intercompany Matching Rules

Intercompany transactions are typically matched based on specific criteria such as transaction date, amount, currency, and reference numbers. In the legacy system, these matching rules may be implicit or handled by specific modules. In the target ERP, these rules must be explicitly defined and tested. For example, if the new system uses a specific intercompany matching engine, the criteria for a successful match must be configured to align with the legacy logic. This includes handling partial matches, currency differences, and timing differences. The finance team should provide a list of historical intercompany transactions that were previously unmatched or required manual adjustment, and these cases should be used to test the new matching logic. By defining these rules early, you can identify potential data quality issues in the source system that need to be resolved before migration.

Data Extraction and Cleansing for Intercompany Records

Extracting intercompany data from the legacy ERP requires a careful approach to ensure that all related records are captured. This includes general ledger entries, subledger details (such as accounts payable and receivable), and any manual journal entries used for intercompany adjustments. The extraction process should be performed in a controlled environment with full audit trails. Once extracted, the data must be cleansed to remove duplicates, correct errors, and standardize formats. Common issues include missing reference numbers, incorrect entity codes, and currency mismatches. The cleansing process should be documented, with a clear record of what data was changed and why. This documentation is essential for audit purposes and for troubleshooting any issues that arise during the migration. The finance team should review a sample of the cleansed data to ensure that it meets their expectations for accuracy and completeness.

Handling Historical Data and Cutoff Dates

Written by
SysGenPro Editorial

SysGenPro Editorial

Platform & solutions team

Practical guidance on ERP, AI automation, cloud deployment and enterprise transformation from the SysGenPro team.

Share this article
Continue learning
View all articles
Explore the platform

Where to go next

Browse the knowledge hub

See how SysGenPro fits your business

Discuss your workflows, modules and deployment options with our team.

Back to resources