FP&A (financial planning and analysis) software with consolidation capabilities can combine data from multiple ERPs (enterprise resource planning systems) while each entity keeps its existing ledger. It connects to the source systems, maps accounts into a group reporting structure, and applies configured currency translation and consolidation rules. Transaction-level drill-down depends on the detail imported from each source.
Can I consolidate multiple ERPs without migrating onto one system?
Yes. Consolidation needs the data from each ERP in one structure, not the systems themselves on one platform. Groups commonly run NetSuite at the parent, QuickBooks Online at small subsidiaries and Sage Intacct at an acquired business, and still report as one company.
Migration has a place, usually when the transactional processes need to be unified: shared purchasing, a single customer master, common approvals. It is a large project. For group reporting alone, migrating every entity onto one ERP is rarely the fastest route to a reliable consolidated income statement.
The work without migration happens in three steps. Connect each ERP so trial balances and transactions load on a schedule. Map each entity’s accounts to the group reporting structure. Apply group rules, such as currency translation and intercompany eliminations, to the mapped data.
Manual spreadsheet assembly can omit an entity. In an illustrative example, a group adds an acquired subsidiary’s trial balance on a new tab but leaves that tab outside the consolidation formula. Revenue is then understated. A connected reporting structure reduces this risk, but finance still needs to validate entity inclusion, mappings and report filters.
Can I manage multiple charts of accounts in one system?
Yes, by keeping each entity’s chart of accounts (CoA) as it is in the ERP and mapping each one to a single group reporting structure. The group reports on the shared structure. Each entity’s controller still posts to the accounts they know.
Different charts cause three kinds of mismatch. Granularity differs: one entity has twelve marketing accounts and another has one. Numbering differs: 6100 is rent in one ledger and software in another. Classification differs: one entity books customer support in cost of revenue and another in operating expense.
Mapping can align account numbers and aggregate detailed accounts into group categories. It cannot recover detail that an entity never recorded. Classification differences need a group decision: if support belongs in cost of revenue for group reporting, map the relevant accounts there while preserving local statements.
Entity-level mappings matter most for shared numbers. A mapping table keyed only on account number will send the second entity’s 6100 into rent. Keying on entity and account together prevents that.
Check each entity’s imported account balances against its ERP trial balance for the same period and currency. Compare debit and credit totals separately, review unmapped and duplicate accounts, and check the reporting categories. A balanced total alone does not prove that every account is included or classified correctly.
How do I handle multi-currency consolidation?
Translate each entity from its functional currency into the group’s presentation currency using the applicable accounting policy. For a non-hyperinflationary functional currency, IAS 21 uses closing rates for assets and liabilities and transaction-date rates for income and expenses. Period averages are acceptable only when they approximate transaction-date rates. Translation differences go to other comprehensive income (IFRS Foundation, IAS 21, 2026).
In an illustrative example, a group translates balances using inconsistent rates and fails to record the resulting translation adjustment. An unexplained difference then appears in the consolidation. Investigate the rate assignments and equity roll-forward instead of posting an unsupported balancing entry.
Rate sources need governance. Decide which rate provider the group uses, which time of day the closing rate is taken, and who approves the rate table each month. Then load the same rates into every report.
Cash needs the same discipline by legal entity. Cash sits in specific entities and bank accounts, so forecast each entity’s receipts and payments in its own currency, then translate and consolidate, with intercompany funding shown on both sides so the group view nets it out.
Foreign exchange (FX) analysis is the second need. Leadership wants to know how much of revenue growth came from currency. That requires restating the current period at prior-period rates, which is simple once rates are stored by period and applied consistently.
How do I run eliminations and allocations across entities?
Identify intercompany balances and transactions with dedicated accounts or a counterparty tag, eliminate them in the consolidation layer, and apply allocation rules to the mapped results. Neither eliminations nor allocations should be posted by hand into a spreadsheet each month.
Eliminations depend on both sides agreeing. In an illustrative example, a management fee of $150,000 charged by the parent should appear as revenue at the parent and expense at the subsidiary. If the subsidiary booked $142,000 because of a timing difference or FX, the elimination leaves $8,000 in the consolidated figures. Reconcile intercompany balances by counterparty before consolidating, and resolve differences at the entity level.
Allocations need rules everyone can read. Shared costs such as corporate IT, rent or the finance team itself are often allocated by headcount, revenue or square footage. Write the rule down, apply it to mapped data, and show the allocated amount as a separate line, so department heads can see their direct costs apart from their share of overhead.
Practitioners know where these processes break first. When a new entity is added, intercompany accounts are often set up late, and its first month of intercompany activity sits in ordinary revenue and expense accounts. Consolidated revenue looks higher than it is until someone traces it. Set up intercompany accounts on day one.
How are EBITDA adjustments handled in consolidated reporting?
Keep adjustments as named, documented items that sit on top of reported results, never as changes to the ledger figures. Adjusted EBITDA (earnings before interest, taxes, depreciation and amortization) should always reconcile back to reported net income, line by line.
Public companies have to show that reconciliation. The SEC’s rules on non-GAAP financial measures require a reconciliation to the most directly comparable GAAP measure (SEC, Release 33-8176, 2003). Private companies reporting to lenders or private equity owners face similar expectations through credit agreements.
Potential adjustments include acquisition costs, restructuring charges and stock-based compensation, but their acceptability depends on the reporting purpose and applicable requirements. Track each approved adjustment with an owner, supporting evidence and a consistent definition. Decide whether it belongs at entity or group level, and do not assume that calling a cost "one-time" makes it eligible.
In an illustrative acquisition example, the board’s adjusted EBITDA includes an integration-cost adjustment that the lender’s definition excludes. Keep the board and covenant measures separately named and reconcile each to net income, with the adjustment policy and supporting records visible.
Covenant calculations deserve their own report, built from the credit agreement’s wording. Lenders read definitions literally.
How do I report to a holdco after acquisitions?
Connect and map an acquired entity for group reporting, with pre-acquisition history kept separate from consolidated actuals. Under IFRS 10, consolidation begins when control is obtained, which may be partway through a reporting period. Confirm the applicable acquisition date and accounting requirements before including results. ERP migration is a separate decision.
The first months after a deal are the hardest. The acquired company’s chart of accounts, fiscal calendar and close timing usually differ from the group’s. Map the accounts first, then align periods. If the acquired entity closes on a 4-4-5 calendar while the group uses calendar months, decide how the periods line up and document it.
Pro forma reporting is the second request. Boards often want to see the combined business as if the acquisition had happened earlier. That uses the acquired company’s history, often available only as management packs, mapped to the group structure and labeled as pre-acquisition.
Private equity holdcos often run several platforms with add-on acquisitions. Each add-on goes through the same steps: connect, map, align periods, set up intercompany accounts and validate against the seller’s numbers.
Validation matters most here. Compare the first month of mapped results against the acquired company’s own P&L. Differences usually point to mappings that need a group decision.
Should I wait until after a merger or restructuring to implement FP&A software?
Usually not, because the transition is when reliable group reporting is most needed. Boards, lenders and owners want consolidated numbers during an integration, and a mapping-based approach absorbs changes in entities and structures as they happen.
FinanceOS®, the foundation underneath Datarails, is built for that kind of change. It connects to each entity’s ERP. It applies multi-entity consolidation, chart of accounts harmonization, currency conversion, intercompany eliminations and allocations, with audit trails and lineage behind every number. A new entity enters through mapping rather than a new spreadsheet tab, and a restructured department becomes a mapping update.
Datarails FP&A then reports and plans on the consolidated data in Excel, Google Sheets or the web application. Drill-down runs from a group line to the entity and its transactions. The guide to multi-entity consolidation and the review of financial consolidation tools go further.
If the legal entity structure is unresolved, agree which parts of the reporting model can be configured now and which should wait. Assess data access, ownership of mappings and the finance team’s capacity before implementation. ERP migration and the reporting project can follow separate plans.
Where to start
Take last month’s consolidation and list the manual steps between the trial balances and the board pack. Separate data collection and mapping from accounting judgments and approvals. For a Datarails walkthrough, bring an entity’s trial balance and test the mapping, reconciliation and drill-down against your own reporting needs.
