Why acquired companies cannot produce comparable reports, and which difference to check first

Six things an acquired entity does differently, and not one of them is an error. Only 27% of limited-success acquirers are very confident their reported synergies are real and auditable, against 62% of successful ones. The gap is not deal quality. It is whether the reporting was built to be checked.

You own three companies. You asked for one set of comparable numbers. What came back was three packs that cannot be put next to each other, and the finance teams all insist their figures are right.

They are right. That is the part worth sitting with before any budget gets committed.

Six things that differ, and none of them is an error

Six things an acquired entity does differently, and what each one breaks

None of these is an error. Each was a reasonable decision made by a company that did not expect to be consolidated.

Order matters when you investigate. Calendar and chart of accounts explain most of the gap in most cases, and they are the two cheapest to check.

Source: Thinklytics engagement pattern across the system consolidation engagements in the case library, including a credit union carrying four core banking systems after three acquisitions in five years.

An acquired company was not built to be consolidated. Six decisions were made independently, each reasonable at the time, and each one breaks a different part of a side-by-side report.

Chart of accounts. Different numbers, different depth, different natural groupings. This breaks every line in a comparative P&L.

Fiscal calendar. A 4-4-5 retail calendar against calendar months, or a June year end. This invalidates any period comparison before anything else is even wrong, and it is the first thing to check because it is the cheapest.

Entity and grain. One row per legal entity, per site, per contract, per brand. Anything divided by a count is now wrong.

Policy elections. Revenue recognition timing, capitalisation thresholds, reserve methods. This moves margin, which is why it matters most and surfaces last.

Currency and rate policy. Deal-date, month-end or budget rate, plus a different functional currency. This one hides, because a rate difference is absorbed silently into a growth rate rather than showing up as a discrepancy.

System of record. Which system is authoritative for a customer, a product, a headcount. Every overlap analysis and every customer count depends on the answer.

Work down that list in order. In most estates two or three of the six are in play, not all six, and finding which takes days rather than a discovery phase.

What this looks like from the board seat

Confidence that reported synergies are real and auditable

• Limited-success acquirers. 27%. Very confident the synergies they reported are real and auditable. The deal was announced on numbers nobody can now trace.
• Successful acquirers. 62%. Very confident. The difference is not deal quality. It is whether the reporting was built to be checked.

About one in three acquirers fully achieve their deal thesis objectives. PwC does not publish a sample size for this survey, so read it as a direction and a gap rather than a measured population.

Source: PwC 2026 M&A Integration Survey, executives involved in a merger or acquisition in the previous three years at organisations with annual revenue of $1 billion or more. No sample size disclosed.

PwC's 2026 M&A Integration Survey covers executives involved in a merger or acquisition during the previous three years at organisations with annual revenue of $1 billion or more. Two findings from it are worth quoting.

About one in three acquirers fully achieve their deal thesis objectives. And only 27% of limited-success acquirers are very confident that the synergies they reported are real and auditable, against 62% of successful acquirers.

PwC does not publish a sample size for that survey, so it is a direction and a gap rather than a measured population. Read it that way. The gap is still the useful part: the difference between the two groups is not deal quality, it is whether the reporting was built so the numbers could be checked. A deal announced on figures nobody can trace is a deal that will be defended on anecdote.

The same survey found that in 2020, 59% of acquirers reported having a target operating model in place at signing, and by 2023 that had moved two percentage points to 61%. The planning gap is not closing on its own.

The assumption that costs the most

How many companies actually run one ERP

Standardising the ERP estate is the assumed fix. Almost nobody has done it, including companies that have never made an acquisition.

• Run multi-instance ERP estates
• Rate customisation, integrations and functional scope as complex
• Run a single ERP instance

Source: Forrester Research, The Top Trends Shaping ERP, July 2026, as cited by HSO. Secondary citation: the figures are attributed to the named Forrester report rather than read from it directly.

The reflex answer is to standardise the ERPs. Before funding that, two numbers.

Forrester's The Top Trends Shaping ERP, published July 2026, reports 89% of companies running multi-instance ERP estates and only 7% on a single instance, with 50% rating customisation, integrations and functional scope as complex. Those figures are attributed to the named Forrester report via HSO rather than read from the report directly, so treat the attribution as secondary.

The point survives either way. Most companies that have never made an acquisition have the same multi-ERP estate. So the estate is not what makes the reports incomparable. The six differences above are, and they are mapping problems.

In seven consolidation engagements in our case library, the source systems were kept in every single one and the comparable layer was built above them. A credit union carrying four core banking systems after three acquisitions in five years kept all four. A regional P&C insurer that had bought two carriers over eight years kept four claims systems. A casino group kept five property management systems.

What it costs while it stays this way

Two costs. The direct one is countable and the second one is larger.

The credit union was spending three days of manual work every time it needed a combined member view, and $1.3M a year maintaining four data environments. Its board had refused to approve any further acquisitions until a unified member view existed, which is the direct cost arriving as a strategic constraint. See the credit union system consolidation engagement.

The regional insurer's cost was what did not happen. Four claims systems, each with its own policy numbers, loss codes and date formats. The data science team spent 18 months trying to build a usable training dataset and failed twice, with an underwriting initiative worth $8.4M sitting behind it. Loss ratio reporting accuracy was running at 71 of every 100. See the regional insurer claims unification engagement.

A cloud provider had let 14 business units build separate warehouses over eight years. There was no cross-unit reporting of any kind, the estate cost $4.7M a year to maintain, and previous consolidation attempts had stalled on business unit resistance rather than on technology.

Why building another report does not settle it

Same reason it does not settle a single-company metric dispute. Each entity is already producing a correct figure under its own rules, so a group-level report applying a fourth set of rules produces a fourth number. Now the portfolio CFO has four.

The thing that makes two entities comparable is a written mapping, signed by someone, that says which account maps to which, which calendar converts how, which rate applies to which balance, and what is deliberately not comparable yet. That last item is the one most programmes leave out, and writing it down is what stops it surfacing in a board meeting.

The single-company version of this problem is in why sales and finance report different revenue, and the mechanism is identical. Multiple entities just multiply it.

What we would do first

Pick one metric that matters to the investment case and one period. Have each entity write down how it computes that metric, in prose, before anyone looks at the data.

Then work down the six differences in order, calendar first, chart of accounts second. The output is a short list of which differences are actually in play across your estate. That list is the entire scope of the mapping work, and it is also what tells you whether you need the reporting layer or the ERP programme.

Delivery sits in data foundation for the mapped layer, system consolidation where sources are being retired, and data 360 consultant where customers and products overlap across entities. On SAP estates mid-migration, SAP data readiness and migration. The full set of work in this area sits under the data underneath is not ready.

Frequently asked questions

Why can't an acquired company produce comparable reports?

Because six things differ and none of them is a mistake. The chart of accounts, the fiscal calendar, the entity grain, the accounting policy elections, the currency and rate policy, and which system is authoritative for a customer or product. Each was a reasonable decision made by a company that did not expect to be consolidated. Put the two P&Ls side by side and every line is computed under different rules, so the comparison is invalid before anyone looks for an error.

Which difference should we check first?

The fiscal calendar, then the chart of accounts. Those two explain most of the gap in most cases and they are the two cheapest to check: a 4-4-5 retail calendar against calendar months, or a June year end, invalidates every period comparison before anything else is even wrong. Policy elections come third and matter most, because they move margin. Currency is the one that hides, because a rate difference is absorbed silently into growth rates.

Is this a data quality problem?

No, and treating it as one wastes the budget. A data quality problem means the same rule applied to the same source gives an unreliable answer. Here each entity reliably produces a correct figure under its own rules. The work is mapping, not cleansing: one account map, one entity map, one calendar map, one rate policy, one set of elimination rules, and a written register of what is deliberately not comparable yet.

Do we have to standardise the ERPs to fix it?

Usually not, and the assumption is expensive. Forrester's The Top Trends Shaping ERP, July 2026, reports 89% of companies running multi-instance ERP estates and only 7% on a single instance, so most companies with no acquisition history have the same estate. In seven consolidation engagements in our case library the source systems were kept in every one and the comparable layer was built above them, including a credit union that kept four core banking systems after three acquisitions.

How bad does this get at board level?

PwC's 2026 M&A Integration Survey, covering executives involved in a deal in the previous three years at organisations above $1B revenue, found only 27% of limited-success acquirers very confident that their reported synergies are real and auditable, against 62% of successful acquirers. About one in three acquirers fully achieve their deal thesis objectives. PwC does not publish a sample size, so read it as a direction rather than a measured population. The practical version is that the deal was announced on numbers nobody can now trace.

What does it cost while it stays this way?

Direct cost first, and it is countable. A credit union carrying four core banking systems after three acquisitions spent three days of manual work every time it needed a combined member view, and $1.3M a year maintaining the four environments. The larger cost is what does not happen: a regional insurer's data science team spent 18 months trying to build a usable training dataset across four claims systems and failed twice, and a $8.4M underwriting initiative sat blocked behind it.

How long does it take to get comparable numbers?

In our case library, 13 to 30 weeks, and the duration tracked the number of source systems rather than the size of the company. Four claims systems took 13 weeks. Five property management systems took 18. Four core banking systems took 20. Eleven campus warehouses took 24. Fourteen business unit warehouses took 30. The first usable comparison usually arrives well before the end, because it only needs the mapping that exists so far.

Where should a portfolio CFO start?

Take one metric that matters to the investment case and one period, and have each entity write down how it computes that metric before anyone looks at the data. Then work down the six differences in order, calendar first. The output is a list of which differences are actually in play for your estate, which is the entire scope of the mapping work, and it takes days rather than a discovery phase.

The work behind this

Seven consolidation engagements in the case library brought multiple source systems onto one set of comparable numbers, from four claims systems at a regional insurer to 14 business unit warehouses at a cloud provider. In all seven the source systems stayed in place.

System consolidation and data foundation engagements.