Connected business operations. Flexible deployment.
A practical guide for CIOs and ERP consultants on managing intercompany transactions during multi-company ERP migrations, covering data mapping, reconciliation, and risk mitigation.
Handling intercompany transactions during a multi-company ERP migration requires a rigorous approach to data mapping, reconciliation, and validation to ensure financial integrity across legal entities. The primary risk is the misalignment of intercompany balances, which can lead to consolidation errors, audit failures, and operational disruptions. The recommended approach involves a phased strategy: first, profile and cleanse source data to identify open intercompany items; second, map entity relationships and chart of accounts structures between source and target systems; third, execute a trial migration with full reconciliation; and finally, perform a cutover with strict go/no-go criteria based on balance verification. This process protects business data, maintains operational continuity, and ensures that the new ERP system accurately reflects the financial position of all entities.
The preparation phase is critical for identifying potential issues before technical execution begins. Start by profiling the source ERP data to understand the volume, structure, and status of intercompany transactions. Identify all open intercompany receivables and payables, as these are the most complex items to migrate. Closed transactions may be migrated for historical audit purposes, but open items require careful handling to ensure they can be settled in the new system. Next, map the legal entities from the source system to the target system. This includes defining the parent-child relationships, ownership percentages, and functional currencies for each entity. Any discrepancies in entity definitions must be resolved before migration to prevent data loss or misallocation.
Intercompany transactions rely on specific account codes for receivables and payables. Ensure that the chart of accounts in the target ERP system includes the necessary intercompany accounts for each entity. If the source and target systems use different chart of accounts structures, create a detailed mapping table that translates source account codes to target account codes. This mapping must be validated by finance stakeholders to ensure that the accounting treatment remains consistent. For example, if the source system uses a single intercompany account for all entities, but the target system requires entity-specific accounts, the migration script must split the data accordingly. This step is essential for maintaining the integrity of the general ledger and enabling accurate consolidation.
Before migration, cleanse the source data to remove duplicates, correct errors, and standardize formats. Intercompany transactions are particularly prone to duplication if they are recorded in both the selling and buying entities. Use automated scripts to identify and flag duplicate entries, and work with finance teams to resolve them. Additionally, standardize date formats, currency codes, and entity identifiers to ensure that the data can be transformed correctly. Data cleansing reduces the risk of migration errors and improves the accuracy of the reconciliation process. Document all cleansing activities to maintain an audit trail and ensure transparency.
The technical execution phase involves transforming the cleansed data into the target system's format and loading it into the new ERP. Use a data migration tool or custom scripts to apply the mapping rules defined in the preparation phase. The transformation logic must handle currency conversion, if necessary, and ensure that intercompany transactions are linked correctly between entities. For example, if Entity A sells to Entity B, the migration script must create a receivable in Entity A and a payable in Entity B, with matching amounts and dates. This linkage is crucial for reconciliation and consolidation. Load the data into a staging environment first to test the transformation logic and identify any errors before proceeding to the production system.
Open intercompany items require special attention during the technical execution phase. These items represent transactions that have not yet been settled between entities. When migrating open items, ensure that the aging and status are preserved in the target system. If the target system supports intercompany matching, configure it to automatically match open receivables and payables based on transaction references. If automatic matching is not available, plan for manual reconciliation after migration. Document the status of each open item and assign ownership to specific finance teams for follow-up. This approach ensures that open items are not lost or misclassified during the migration.
If the source and target systems use different functional currencies, or if intercompany transactions involve multiple currencies, currency conversion must be handled carefully. Use the exchange rates that were in effect at the time of the transaction to convert amounts to the target currency. Do not use current exchange rates, as this can distort the financial position. Document the exchange rates used for each transaction and ensure that they are consistent across all entities. If the target system supports multi-currency accounting, configure it to handle intercompany transactions in their original currencies and convert them for reporting purposes. This approach maintains the accuracy of the financial statements and supports accurate consolidation.
Validation is the most critical phase of the migration process. Perform a full reconciliation of intercompany balances between the source and target systems. This includes comparing the total receivables and payables for each entity, as well as the individual transaction details. Use automated reconciliation tools to identify discrepancies, and work with finance teams to resolve them. Additionally, test the consolidation process in the target system to ensure that intercompany transactions are eliminated correctly. This test should be performed in a staging environment using representative data. If any discrepancies are found, investigate the root cause and correct the migration script or data before proceeding to the next phase.
Reconciliation procedures should be detailed and documented. Start by comparing the trial balances of the source and target systems for each entity. Then, drill down to the subledger level to compare individual intercompany transactions. Use matching criteria such as transaction date, amount, and reference number to identify corresponding entries. Flag any unmatched items for review and resolution. The reconciliation report should include a summary of matched and unmatched items, as well as the total differences. This report serves as a key input for the go/no-go decision and provides an audit trail for the migration process.
Involve finance stakeholders in user acceptance testing (UAT) to validate that the migrated data meets their requirements. UAT should include scenarios such as creating new intercompany transactions, settling open items, and generating consolidation reports. Finance users should verify that the data is accurate and that the system behaves as expected. Document any issues found during UAT and resolve them before cutover. UAT provides a final check on the migration process and ensures that the new system is ready for production use.
The deployment phase involves the final data load and cutover to the new ERP system. Define a cutover plan that includes the sequence of activities, responsible roles, and timing. Freeze all intercompany transactions in the source system during the cutover window to prevent data inconsistencies. Perform the final data load, including any transactions that occurred after the last trial migration. Run the reconciliation process again to verify that the final data is accurate. Obtain go/no-go approval from key stakeholders, including the CFO and IT director, based on the reconciliation results and UAT feedback. If the go decision is made, proceed with the cutover and communicate the change to all users.
The cutover runbook should be a detailed, step-by-step guide that includes all activities, owners, and time estimates. It should include checkpoints for data validation, system health checks, and user communication. Define rollback triggers, such as critical data errors or system failures, and document the rollback procedure. The runbook should be tested in a staging environment before the actual cutover to ensure that the team is prepared for any issues. A well-defined runbook reduces the risk of cutover failures and ensures a smooth transition to the new system.
Define clear go/no-go criteria for the cutover decision. These criteria should include the results of the final reconciliation, the status of UAT, and the health of the target system. For example, the go decision may require that all intercompany balances match within a defined tolerance, that all critical UAT issues are resolved, and that the system is performing within acceptable parameters. Document the criteria and obtain sign-off from key stakeholders before the cutover. This approach ensures that the decision is based on objective data and reduces the risk of proceeding with a flawed migration.
After go-live, enter the stabilization phase, which involves monitoring the system, resolving issues, and supporting users. Establish a hypercare period with dedicated support teams available to address any issues that arise. Monitor intercompany transactions closely to ensure that they are being recorded and settled correctly. Perform daily reconciliations during the first week to identify and resolve any discrepancies quickly. Provide training and support to finance users to help them adapt to the new system. Document all issues and resolutions to build a knowledge base for future reference. The stabilization phase is critical for ensuring that the migration is successful and that the new system delivers the expected benefits.
Implement ongoing reconciliation processes to ensure that intercompany balances remain accurate over time. Automate the reconciliation process where possible to reduce manual effort and improve accuracy. Monitor key metrics such as the number of unmatched items, the aging of open intercompany items, and the frequency of reconciliation errors. Use these metrics to identify trends and areas for improvement. Regular reconciliation ensures that the financial data remains consistent and supports accurate reporting and consolidation.
Use the lessons learned from the migration process to improve future ERP projects. Conduct a post-implementation review to identify what went well and what could be improved. Document the findings and share them with the project team and stakeholders. Use the insights gained to refine the migration methodology, improve data quality, and enhance user adoption. Continuous improvement ensures that the organization becomes more efficient and effective in managing ERP migrations and upgrades over time.
Managing risk is essential for a successful ERP migration. Identify potential risks such as data loss, system downtime, and user resistance, and develop mitigation strategies for each. For data loss, implement robust backup and restore procedures and test them regularly. For system downtime, plan for a cutover window that minimizes impact on business operations and communicate the schedule to all stakeholders. For user resistance, provide comprehensive training and support to help users adapt to the new system. Regularly review the risk register and update it as new risks emerge. Proactive risk management reduces the likelihood of migration failures and ensures that the project stays on track.
Handling intercompany transactions during a multi-company ERP migration requires a structured, disciplined approach that prioritizes data integrity and financial accuracy. By following the steps outlined in this guide, organizations can mitigate risks, ensure a smooth cutover, and achieve a successful migration. The key is to invest time in preparation, validation, and stabilization, and to involve finance stakeholders throughout the process. With careful planning and execution, intercompany transactions can be migrated accurately, supporting the organization's financial reporting and operational continuity in the new ERP system.
Common questions on this topic. Talk to our team for anything specific to your business.
The biggest risk is the misalignment of intercompany balances, which can lead to consolidation errors, audit failures, and operational disruptions. This occurs when transactions are not correctly linked between entities or when data is lost or duplicated during migration.
Open intercompany items should be migrated with their status and aging preserved. Configure the target system to automatically match open receivables and payables where possible, and plan for manual reconciliation if automatic matching is not available. Assign ownership to finance teams for follow-up.
Historical closed transactions are typically migrated for audit purposes, while open items are migrated to ensure continuity. New transactions should be created in the target system after cutover. The decision depends on the organization's audit requirements and the complexity of the data.
Verify intercompany balances by performing a full reconciliation between the source and target systems. Compare trial balances, subledger details, and consolidation reports. Use automated tools to identify discrepancies and resolve them before go-live.
The chart of accounts defines the account codes used for intercompany receivables and payables. Ensuring that the chart of accounts is aligned between source and target systems is critical for accurate data mapping and reconciliation. Mismatches can lead to data loss or misallocation.
Currency conversion must be handled carefully to maintain the accuracy of financial statements. Use the exchange rates that were in effect at the time of the transaction to convert amounts to the target currency. Document the rates used and ensure consistency across all entities.
Learn how standardizing professional services ERP processes improves forecast accuracy, delivery governance, and financial visibility by aligning project operations with financial controls.
Learn how to build a robust hypercare plan to ensure ERP stability after migration. Covers risk management, support structures, and validation strategies for CIOs and IT leaders.
Learn how to implement workflow governance in construction ERP systems to eliminate approval bottlenecks, standardize financial controls, and ensure accurate project reporting through robust process architecture.
Discuss your workflows, modules and deployment options with our team.
Back to resources