Consistent numbers across a portfolio are built, not inherited. Here is how to design one reporting pack that scales from two portfolio companies to ten.
Key takeaways
STEP 01 OF 10
Start from what the law actually requires, then decide how far past it to build. The CBCA obliges directors to present comparative financial statements to shareholders at every annual meeting, covering the period since the corporation’s last financial year alongside the immediately preceding year, together with an auditor’s report where one exists CBCA s. 155. That is an annual floor, not a management tool — a fund overseeing several portfolio companies needs a monthly cadence the statute never contemplates.
Treat the annual statutory filing as the one number every portfolio company’s pack has to reconcile back to, even though the monthly pack itself runs on a faster, less formal cycle. A reporting pack that cannot be traced to the year-end statements is not actually consolidatable, whatever it looks like month to month.
STEP 02 OF 10
Every portfolio company arrives with its own chart of accounts, usually inherited from whatever bookkeeper or accountant it used before the fund acquired it. Rebuilding each one from scratch wastes the acquired company’s own institutional muscle memory; mapping each company’s existing chart to one standardized reporting taxonomy, maintained centrally, gets the same consolidated output without forcing every business to change its day-to-day bookkeeping.
The mapping itself is the asset, not any individual company’s chart. Keep it in one place, version it whenever a company’s own chart changes, and review it whenever a new portfolio company is acquired — a mapping built once for the first company rarely survives contact with the second unchanged.
STEP 03 OF 10
Fix the reporting calendar in calendar-month terms, independent of any individual portfolio company’s fiscal year-end. A company acquired mid-year with a fiscal year-end that does not match the fund’s other holdings should still report on the fund’s monthly cycle from day one — reconciling to its own statutory year-end is a separate, once-a-year exercise, not a reason to run a different monthly rhythm.
Set one submission date and one review date, both fixed, and treat a late submission the same way regardless of which portfolio company misses it. A reporting pack that arrives on a different schedule from each company defeats the point of consolidating them in the first place.
STEP 04 OF 10
Owner-compensation, one-time and related-party add-backs are the single most common source of inconsistency across a multi-company portfolio’s reporting, precisely because “there is no fixed revenue or profit threshold” separating SDE-style reporting from EBITDA-style reporting per deavo’s own SDE-vs-EBITDA analysis — brokers and buyers exercise judgment company by company, and a fund inheriting several businesses acquired at different points inherits several different judgment calls with them.
Write the add-back policy once, at the fund level, and apply it to every portfolio company’s monthly pack the same way — even where a company’s own prior practice was different. The point of a single reporting pack is comparability across the portfolio, and comparability is exactly what an inconsistent add-back policy destroys first.
STEP 05 OF 10
Put the operating KPIs ahead of the financial statements in the pack’s structure, not after them. A sponsor reviewing five or six companies a month reads the financial page for confirmation, not discovery — the KPI page is where an emerging problem actually shows up first, usually weeks before it moves the trailing-twelve-month revenue line enough to be visible in the numbers everyone already expects to see.
Standardize which KPIs appear for every company regardless of sector — gross margin trend, customer or contract concentration, days sales outstanding — and add sector-specific ones underneath rather than instead. A pack that swaps its entire KPI set company to company forces the reader to relearn what matters every single month.
STEP 06 OF 10
Portfolio companies acquired at different times almost never share identical accounting policies on inventory costing, revenue recognition timing, or overhead allocation, and forcing an immediate policy change on every acquisition is disruptive for a marginal reporting benefit. Build an explicit consolidation bridge instead — a documented set of adjustments applied at the roll-up stage that reconciles each company’s own-books number to the fund-wide standard.
Document the bridge the same way an auditor would document a reclassification, with a clear line from the company’s own trial balance to the consolidated figure. A bridge nobody can reconstruct six months later is worse than no standardization at all, because it looks precise without actually being auditable.
STEP 07 OF 10
Keep lender covenant reporting structurally separate from the internal management pack, even where the underlying numbers overlap heavily. A covenant test is calculated exactly as the credit agreement defines it — a specific EBITDA definition, a specific measurement period — and conflating it with the fund’s own, more flexible internal add-back policy risks a covenant certificate that does not actually match what the credit agreement requires.
Name a single person responsible for the covenant calculation on each portfolio company’s facility, separate from whoever prepares the monthly management pack, even if it is the same individual wearing two hats. The separation of responsibility matters more than the separation of the person.
STEP 08 OF 10
Decide in advance who has final say when a portfolio company’s own finance team disputes how the fund-level roll-up has treated one of its numbers. Without a named owner, this becomes a recurring, unproductive negotiation every reporting cycle rather than a settled process — and it typically resurfaces hardest at exit, when the quality-of-earnings review a buyer’s advisors run will ask exactly the same question.
A Chartered Business Valuator’s Expert Report standard exists specifically to give an independent opinion on “the quantum of financial gain/loss” where a number is genuinely disputed CBV Institute Practice Standards 310/320/330 — worth knowing as the escalation path even if it is rarely actually invoked at the monthly reporting level.
STEP 09 OF 10
The red flags a buyer’s diligence team looks for at exit — related-party pricing that is not arm’s length, receivables growing faster than revenue, margins moving without an obvious explanation the pattern deavo’s own reading-financials guide describes — are exactly the items a monthly reporting pack should already be tracking on every portfolio company, not items discovered for the first time when a buyer’s advisors show up.
Building that discipline into the monthly cycle means the fund walks into its own eventual exit process already knowing what a quality-of-earnings review will find, instead of learning it under time pressure during someone else’s diligence.
STEP 10 OF 10
Automate the mechanical parts of the roll-up — trial balance imports, the standardized chart-of-accounts mapping, variance calculations against budget — and keep every judgment call, particularly add-back decisions, with one named person accountable for consistency across the portfolio. Automation without a named judgment-owner tends to drift silently, one small exception at a time, until the pack no longer means what it claims to mean.
Retain the underlying support for every add-back and adjustment for at least six years, matching the federal statutory retention period for corporate books and records ITA s. 230(4)(b) — not because the monthly pack itself is a tax filing, but because the same underlying figures eventually feed the numbers that are.
A newly acquired portfolio company is, by definition, the one entity in the portfolio that has not yet been mapped into the standardized reporting taxonomy, and the temptation is to let its first few months run on its own inherited format until things settle down. That is exactly backwards — the first weeks after closing are when a new acquisition is easiest to remap, before its own team has re-entrenched around old habits; see taking over operations in the first fortnight for the sequence that gets the mapping done in the same window as everything else.
Build the reporting-pack mapping into the acquisition checklist itself, alongside banking and payroll cutover, rather than treating it as a separate finance-department project that starts once the deal team has moved on to the next target.
A standardized reporting pack maintained consistently over several years is, in effect, a pre-built quality-of-earnings file — trailing-twelve-month figures, normalized add-backs with their own documented history, and a KPI trend line a buyer’s diligence team would otherwise have to reconstruct from scratch. That shortens exit diligence measurably, and a shorter diligence period is itself a form of value, whether or not it shows up as a line item in the price.
It also protects against the opposite failure: a portfolio company sold with reporting so inconsistent with the fund’s other holdings that a buyer’s advisors treat every number with suspicion by default, extending diligence and, more often than sponsors expect, moving the price.
Monthly production and monthly review should be the same cadence — a pack that is produced monthly but only reviewed quarterly loses most of its early-warning value, since the KPI page exists specifically to surface a problem before it shows up in a quarter’s worth of financial statements.
No — standardize a small, fixed core set across every company, such as margin trend, concentration and days sales outstanding, and layer sector-specific metrics underneath. Forcing an identical KPI set onto businesses in genuinely different sectors produces a pack that looks consistent without actually being useful.
Name one person — often an external controller or fractional CFO retained across the portfolio — explicitly responsible for applying the add-back policy consistently. The title matters less than the fact that it is one person’s job, not each portfolio company’s own bookkeeper making the call independently.
They can share a source, but keep the outputs distinct. A single document trying to serve both purposes tends to compromise either the covenant calculation’s precision or the management pack’s flexibility, usually without anyone deciding that trade-off deliberately.
A 30-minute call is enough to tell you whether AI pays for itself here.
Nobody publishes Canadian transaction data, so every valuation in this country quotes an American benchmark. We are building the Canadian one — multiples, asking-to-sale spreads and days on market, by sector and by city. Leave an email and you will see it first.
No pitch, no listings. One email when the first report lands.
