A summary number, by definition, leaves things out
A consolidated P&L for a dental or veterinary service organization is designed to answer one question — how did the whole platform perform this period — and it does that job well. What it isn't designed to do is tell you why, or which of your fifteen, twenty-five, or fifty locations actually drove that answer. A single blended number, by its nature, averages away exactly the kind of variation a sponsor, a lender, or a board most needs to see.
This isn't a criticism of consolidated reporting — every multi-entity business needs a summary view. It's a reminder that the summary is a starting point for a conversation, not the end of one, and that several genuinely different underlying situations can produce a top-line number that looks, on its face, perfectly fine.
Why this is a recurring problem, not a rare one
It's tempting to treat each of the patterns below as an edge case, something that happens to other, less careful platforms. In practice, every one of them shows up regularly across the DSO and VSO space, precisely because the underlying structure — many locations, an MSA-based fee arrangement, acquisitions arriving with inconsistent prior bookkeeping — is common to nearly every platform, not specific to any one operator's carelessness.
The goal of this article isn't to suggest that consolidated reporting is untrustworthy. It's to name the specific, recurring ways a clean-looking total can still be hiding something worth knowing, so a finance team knows exactly where to look before someone else — a sponsor, a lender, a buyer's diligence team — looks first.
A struggling location, offset by strong ones
The most common thing a blended margin hides is exactly what you'd expect: one or two locations dragging on overall performance while several others carry the portfolio's average comfortably above any red flag. A platform-wide adjusted EBITDA margin sitting at a healthy 22% can easily contain a location running at 8% and another at 35%, with the consolidated figure giving no indication that either extreme exists.
This matters beyond curiosity. A weak location left unaddressed for several quarters because the consolidated number looked fine represents lost value that compounds — a location trending down slowly is far easier to intervene on early than one discovered only once its decline has become severe enough to visibly drag the blended total.
A management fee that never got eliminated
When a management fee is booked as an expense at the practice level and revenue at the MSO level but the offsetting elimination entry is missed, the consolidated revenue and expense lines are both overstated by the same amount, even though net income is often unaffected. That last detail is exactly what makes this particular gap so easy to miss for a long time — the bottom line still looks correct, and nobody scrutinizing net income alone would necessarily notice anything wrong.
The problem surfaces the moment anyone calculates a margin percentage or a revenue multiple off the inflated top-line figure — a revenue-based valuation multiple, a margin trend analysis, or a covenant calculation tied to gross revenue can all be quietly distorted by an elimination that was simply forgotten during a busy monthly close, most often on a location added recently enough that it hasn't yet been folded fully into the standard consolidation checklist.
Acquired growth dressed up as organic growth
A platform's total revenue can grow 40% year over year purely because it closed several acquisitions, while its pre-existing locations grew a modest 3% or even declined slightly — both are true simultaneously, and a consolidated total revenue figure alone can't distinguish between them. A sponsor evaluating whether the platform's core operating model is actually working needs the same-store figure specifically, not the blended growth rate.
This distinction gets muddier the faster a platform is acquiring — a location added mid-quarter, if not tagged with a precise acquisition date, can end up partially counted in both the "same-store" and "acquired" buckets, or worse, entirely miscategorized, quietly inflating whichever growth figure a report happens to emphasize.
An add-back schedule nobody has updated
An add-back schedule built once, during an acquisition's initial underwriting, often quietly goes stale — a founding doctor's above-market compensation that was flagged as an add-back at close may have been renegotiated to a market rate a year later, but the original add-back sometimes keeps getting carried forward into every subsequent adjusted EBITDA calculation out of habit rather than active review.
The reverse happens too — a new related-party rent arrangement or a new above-market compensation pattern can emerge at a location well after its initial add-back schedule was set, and unless someone is actively re-reviewing bank activity location by location, that new item never makes it into the normalized figure at all.
The one check that catches most of these before a board meeting
Nearly every pattern above has the same underlying fix: a location-by-location reconciliation against actual bank data, done every reporting period rather than only when a board meeting or a diligence process forces the question. Comparing each location's reported figures against its own bank statement surfaces a struggling location's real numbers directly, catches a missing elimination the moment the fee transaction is traced, and confirms same-store tagging against actual acquisition dates rather than an assumption carried forward from the deal memo.
None of this requires sophisticated modeling — it requires consistency, applied to every location, every period, rather than only when something already looks wrong.
The documentation a real roll-up actually needs
| Documentation | What it catches |
|---|---|
| Location-level bank statements, every account | The underperforming location and the missing elimination |
| Acquisition date per location, tied to bank activity | A same-store figure blended with acquired growth |
| A dated, sourced add-back schedule per location | A normalization figure that's quietly gone stale |
| A documented elimination entry with its source fee transaction | A management fee that never got removed from the total |
The most common findings once someone looks closely
An underperforming location whose decline was visible in its bank activity for two or three quarters before anyone flagged it at the portfolio level. A management fee elimination that was booked correctly for eleven of twelve locations, with the twelfth — usually the most recently acquired — simply missed. A same-store growth figure that turns out to be overstated by several percentage points once acquisition dates are checked against actual bank activity rather than the closing date on the purchase agreement.
None of these findings, individually, tends to be catastrophic. What makes them worth taking seriously is how quietly each one accumulates — a platform that's never looked closely can easily be carrying two or three of these simultaneously without anyone having connected the dots.
An example of what a finding looks like
A platform preparing for a refinancing runs a location-by-location reconciliation for the first time in over a year, comparing each location's reported figures against its actual bank statements.
| Finding | Detail |
|---|---|
| Missed elimination | One location's management fee, ~$14,000/month, never eliminated for five months |
| Stale add-back | A prior owner's above-market comp add-back still applied a year after renegotiation to market rate |
| Same-store misclassification | A location acquired mid-quarter counted as same-store for the full period |
None of these three findings involved anything close to fraud — each was a reasonable oversight given how the roll-up process had evolved informally over several quarters of rapid acquisition. Correcting all three before the lender's diligence team found them independently was considerably less stressful than explaining them reactively during the actual review.
What happens when this surfaces late
Found internally, on your own schedule, any of these patterns is a routine correction — trace the affected locations and periods, fix the process, move on. Found by a lender's diligence team during a refinancing, or by a buyer's quality of earnings team during a sale process, the same finding becomes a credibility question, not just a numbers question — it invites the reviewer to wonder what else might be inconsistent across the roll-up, well beyond the specific item they happened to catch.
That shift in framing, from a routine fix to a credibility concern, is usually the real cost of finding these things late — not the dollar amount of the correction itself, which is often modest, but the extra scrutiny it invites on everything else in the reporting package.
How much runway you actually have once it's found
Unlike a regulatory filing with a hard external deadline, there's no fixed clock on correcting one of these patterns internally — but the practical window shrinks fast once a transaction process is underway. A finding surfaced mid-diligence for a sale or refinancing needs to be understood and, where material, resolved before that process can proceed, which in practice often means days, not the weeks a full manual reconstruction across every affected location might otherwise take.
Outside of an active transaction, the more sensible framing is simply: the earlier, the better — every additional reporting period that passes before a gap is caught is another period of potentially distorted figures that eventually needs to be traced and understood.
Preparing before diligence forces the question
A platform that runs a location-by-location reconciliation every reporting period, as a matter of routine rather than a special exercise, walks into a sale or refinancing process with a genuinely different posture than one that's never looked closely. The former can typically produce sourced, location-level backup for any figure a diligence team asks about within a day or two. The latter often needs weeks to reconstruct the same detail from scratch, under considerably more time pressure.
The value of a periodic internal check
A quarterly, or ideally monthly, location-by-location reconciliation doesn't need to be a major production — it's the same process described in the consolidation guide, repeated consistently rather than treated as a one-time diligence exercise. The value isn't just catching errors — it's that a platform which reconciles regularly develops an accurate, current sense of which locations are actually strong and which need attention, well before that information becomes urgent.
Myths worth retiring
"If net income looks right, the roll-up is fine"
A missed elimination can leave net income essentially unaffected while still distorting revenue, expense and every margin calculated against them.
"Same-store growth only matters for public retailers"
Any multi-location, acquisitive business — DSO and VSO platforms included — needs to separate organic performance from acquisition-driven growth to understand what's actually working.
"An add-back schedule set at acquisition doesn't need revisiting"
A location's underlying economics — ownership, compensation, real estate arrangements — can change well after close, and an add-back schedule that isn't periodically re-reviewed goes stale quietly.
"This kind of gap means something is being hidden deliberately"
The overwhelming majority of these findings are ordinary oversights in a fast-growing, acquisitive business, not deliberate misstatement — but they still need to be found and fixed.
Each of these myths shares the same root cause — trusting a summary figure without checking the specific mechanism that could quietly distort it. None of them requires deep accounting expertise to guard against; they mostly require remembering that a consolidated number is an aggregation, not an independent verification.
When this becomes something more serious
Most of the patterns in this article are routine oversights, correctable with a process fix. They become more serious when a distorted figure has already been relied on for something material — a loan covenant calculation based on an inflated revenue figure, a valuation multiple applied to a same-store growth rate that turns out to be overstated, or an add-on acquisition underwritten against a target's bank data that was never independently verified against its reported numbers.
In those cases, the correction isn't just a going-forward process fix — it may require revisiting a prior calculation or disclosure, which is exactly the kind of situation where involving outside counsel or an accounting firm experienced with DSO and VSO structures becomes worthwhile.
A five-location platform vs. a fifty-location one
A five-location platform can often catch most of these patterns informally — a hands-on CFO who personally reviews every location's bank statement each month has a reasonable chance of noticing an anomaly by memory alone. A fifty-location platform, adding several new locations a quarter, faces a fundamentally different problem — no single person can hold that much detail in their head, and an informal process that worked fine at five locations becomes unreliable well before it reaches fifty.
The patterns themselves don't change with scale — an unfiled elimination is the same kind of gap whether it's one of five locations or one of fifty. What changes is how much a platform can afford to rely on informal, memory-based checking rather than a documented, repeatable process.
How long location-level records should be kept
Keeping every reporting period's location-level bank statements and reconciliation workpapers for at least several years — well beyond a single fiscal year — matters more for a DSO or VSO platform than for a typical single-location business, since a sale, refinancing, or add-on acquisition underwriting can require historical location-level detail going back further than a single year's reporting cycle would preserve.
A checklist before every board meeting
Every location's figures reconciled against its own bank statements this period
Every intercompany management fee confirmed eliminated, not just assumed
Same-store vs. acquired growth tagged against actual acquisition dates
Add-back schedule reviewed for any location's changed circumstances
Any location trending down flagged explicitly, not buried in the blended total
How a review typically unfolds
A location-by-location review usually starts with the locations that haven't been closely examined recently — often the most recent acquisitions, since they carry the highest risk of a missed elimination or an unreviewed add-back. From there, it moves systematically through the remaining locations, comparing reported figures against actual bank activity for each one, flagging discrepancies as they're found rather than waiting until the full review is complete.
A well-organized review of this kind, across a twenty-location platform with reasonably current bank records, typically takes a matter of days rather than weeks — considerably faster when the underlying bank data has already been read and structured rather than needing to be gathered and keyed from scratch.
Does the pattern differ between dental and veterinary platforms
The underlying causes are largely identical across dental and veterinary roll-ups — both operate under similar MSA structures, both acquire practices with inconsistent prior bookkeeping, and both face the same elimination and add-back challenges. Veterinary platforms often carry an additional layer of complexity from emergency and specialty locations, which can run unusual hours and payment patterns — including a higher share of financing-related deposits from third-party pet insurance and payment plans — that make bank statement categorization somewhat more involved than at a typical general-practice location.
Dental platforms, meanwhile, more often deal with orthodontic and specialty locations running multi-year payment plans collected in installments — a revenue recognition nuance that has its own effect on how a location's reported collections compare to its actual monthly bank deposits, worth accounting for the same way as any other timing difference between what's billed and what actually clears the bank.
Life after the gap is found
Once a gap like a missed elimination or a stale add-back is identified and corrected, the more valuable outcome is usually the process change that prevents it from recurring — adding the specific check that would have caught it earlier to the standard monthly close checklist, rather than treating the correction as a one-time fix.
Platforms that treat a finding this way — as a signal to strengthen the process, not just a number to correct once — tend to see meaningfully fewer surprises in their next diligence process, whatever triggers it.
What might change as platforms mature
As the DSO and VSO consolidation wave matures and platforms grow larger, sponsors and lenders are increasingly asking for location-level detail as a standard part of reporting packages, not just during diligence for a specific transaction. That shift makes the location-by-location discipline described throughout this article less of a best practice reserved for sophisticated platforms and more of a baseline expectation for any group operating at meaningful scale.
Platforms that build this discipline early, before it's demanded by an outside party, tend to find it far less disruptive to adopt than platforms that only start once a sponsor or lender specifically asks for it — by then, the gap between what's available informally and what's actually documented can be substantial, and closing it under external pressure is a very different exercise than building it gradually as routine practice.
In short
A consolidated P&L is a genuinely useful summary, and nothing here argues against relying on one. What it can't do on its own is show you which location is struggling, whether every intercompany fee has actually been eliminated, whether your growth is organic or acquired, or whether your add-back schedule still reflects reality. Getting those answers requires location-by-location reconciliation against actual bank data, done every period as routine practice — not just when a board meeting, a refinancing, or a sale process forces the question.
None of the patterns described here require a sophisticated fix — they require consistency, applied the same way to every location, every period, whether or not anything looks obviously wrong at the consolidated level. A platform that builds that habit early tends to find these gaps on its own schedule, in a routine review, rather than on someone else's schedule, during a process where the stakes are considerably higher.