Separate organic and acquired revenue growth in portfolio reporting

Use labels that describe the actual calculation

Reported growth compares the approved consolidated revenue totals for two periods using their respective reporting populations. Comparable growth holds the defined population and other specified assumptions consistent. Organic growth needs an explicit company-approved definition; do not use the word as a substitute for documenting which acquisitions, disposals, currencies, or other adjustments were excluded.

A same-location view may differ from a same-company view when a company opens or closes locations. A pro forma enlarged-business comparison needs supported historical figures for the acquired business and an agreed treatment of reporting differences. It cannot be derived just by deleting acquisition revenue from the current total. Keep the data needed for each view and label incomplete comparisons as such.

Start with a bridge that has no other moving parts

In the synthetic acquisition workbench, the legacy business produced $20 million in Q2 2025 and $22 million in Q2 2026. A company acquired on April 1 contributes $5 million in Q2 2026. Both periods use the same currency, calendar, revenue policy, and legacy population, with no eliminations. Current reported revenue is therefore $27 million.

Reported growth is ($27m − $20m) ÷ $20m = 35%. Legacy comparable growth is ($22m − $20m) ÷ $20m = 10%. Acquired contribution is $5m ÷ $20m = 25 percentage points of reported growth. Those contributions add to 35% because they use the same prior reported denominator. The acquired company itself did not grow by 25%; its own growth needs its own eligible prior-period revenue.

Change the denominator when the comparable population changes

Now use a separate fictional scenario with prior reported revenue of $20 million, including $1 million from a business later disposed of. Retained operations therefore had a $19 million prior base and produce $21 million this period at constant currency. Acquisitions contribute $5 million, and currency translation reduces the current reported amount by $0.2 million. Current reported revenue is $25.8 million.

The bridge is $20m − $1m + $2m + $5m − $0.2m = $25.8m, or 29% reported growth. Retained-business comparable growth is $2m ÷ $19m, approximately 10.53%. The same $2 million change contributes 10 percentage points to reported growth because that bridge uses the original $20 million denominator. These percentages describe different bases; forcing them to match would make one view incorrect.

Retain a comparison contract beside the visual

Record the entity or location population, comparison periods, acquisition and disposal dates, partial-period policy, currency basis, and source versions. Define how intercompany activity and reclassifications enter the bridge. A company acquired mid-quarter should not be presented as a full quarter of consolidated actuals unless that is the explicitly approved reporting view.

If the prior comparable revenue is zero, a growth percentage is undefined under this calculation. Show the absolute movement and an unavailable percentage with a reason. Missing history is different from verified zero activity and should retain its own exception. In Power BI, Microsoft's DIVIDE function can return a blank for a zero denominator; the report still needs a clear explanation of why the comparison is unavailable.

Use the bridge to direct review, not to claim causation

Once the bridge reconciles, investigate the retained change through supported drivers such as volume, price, mix, or location performance. A favorable comparable result does not establish which initiative caused it. Preserve the operating context, review period, and baseline before crediting a value-creation project. Link the reported total to the source and the comparable view to its inclusion record.

Use the acquisition overview for the broad onboarding process and the mapping guide for source classification. This growth contract belongs between them and the performance dashboard: it specifies the population and denominator that the visuals must preserve, regardless of which reporting tool renders the chart.

• Name every reporting population and retain its membership by period.
• Reconcile the bridge in currency amounts before presenting percentages.
• Use one stated denominator for percentage-point contributions.
• Calculate comparable growth against the actual comparable base.
• Separate acquisition, disposal, currency, and operating effects.
• Label estimated or pro forma history and retain its approval.
• Test zero, missing, and changed comparison populations before release.

Primary sources

• Microsoft: DAX DIVIDE and zero-denominator behavior

Related services and experience

• Portfolio performance analytics (Implementation service)
• Private equity analytics toolkit (Ungated methods and synthetic evidence)
• Portfolio operations dashboard (Synthetic evidence first published 2026-09-09)
• Acquisition reporting workbench (Interactive synthetic mapping and revision exercise)
• Acquisition account mapping (Mapping contract and validation checks)
• Private equity portfolio analytics (Industry practice)