What consolidation actually means for a practice roll-up
The math behind a consolidated multi-location roll-up — summing location totals, eliminating intercompany fees, applying add-backs — is straightforward arithmetic. What actually takes work is getting to the point where you can trust that every location's bank account has been gathered, every management fee has been correctly eliminated, and every add-back is grounded in a real transaction, when no single system hands you that confirmation automatically.
This guide walks through that process step by step, from the raw bank statement at each location to a documented, source-backed consolidated roll-up — whether you do it by hand or with a tool that reads the statements for you.
Nothing here assumes a specific accounting system, a specific bank, or a specific portfolio size — the eight steps that follow work the same way whether you're consolidating a five-location startup platform's first quarterly close or a fifty-location group's established monthly routine.
Why this matters more than the final P&L
Two controllers can produce roll-ups that look equally polished and still be sitting on very different risk — one has verified every location's bank data ties out and every intercompany fee is properly eliminated, the other is trusting that each location's self-reported numbers are correct because nothing has obviously gone wrong yet. The roll-up itself is never the risk. The consolidation process behind it is what determines whether the roll-up actually holds up under a sponsor's or a lender's scrutiny.
That's the reason this guide is organized as eight sequential steps rather than a single instruction to "combine the location P&Ls" — each step exists specifically to catch one of the failure modes that turn a straightforward roll-up into a misleading one, and skipping a step tends to reintroduce exactly the error that step was there to prevent in the first place.
Inventory every location's bank accounts
List every operating, payroll and merchant deposit account at every location — not just the accounts your accounting system already knows about. A newly acquired location often keeps a legacy account or two from before the acquisition closed, and those need to be on the list just as much as any account opened after the deal.
Revisit this inventory at least once a quarter, since a location can open or close an account between reporting periods without anyone at the portfolio level necessarily being told right away.
Standardize the chart of accounts across locations
Confirm every location categorizes revenue and expense the same way before combining anything — one location calling a category "lab fees" and another calling the same expense "outside services" will silently distort any category-level comparison across the portfolio, even if the total dollar figures are all correct individually.
Read and structure every location's bank statements
Extract every transaction from every account gathered in step 1, for the exact reporting period being closed. This is the step that turns a stack of PDF or scanned bank statements into structured, usable transaction data — the raw material every later step depends on.
Where a location's reporting period splits across two bank statement cycles, pull both statements rather than approximating from just one — a transaction near the boundary can easily fall on the wrong side of the reporting period if only one statement is used.
Tag every transaction by location and account type
Every transaction gets tagged with its location and its account type — operating, payroll, merchant deposit — so the consolidation can distinguish, for example, a location's clinical revenue deposits from its payroll disbursements when building the roll-up.
Identify and document every intercompany management fee
For every location, find the recurring transfer representing the management fee paid to the MSO under its MSA, and confirm the amount and the date it posted. This is the specific transaction that step 6's elimination depends on being identified correctly.
A management fee that doesn't match the amount the MSA formula would predict is worth a second look before assuming it's correct — a mismatch here often means the fee was calculated against billed collections rather than actual bank deposits, a timing difference worth reconciling rather than ignoring.
Eliminate the intercompany fee per ASC 810-10-45-1
Remove the management fee from both sides of the consolidated total — the expense recorded at the practice level and the matching revenue recorded at the MSO level — so the consolidated figures aren't double-counting the same dollar. This is the step that keeps the consolidated revenue and expense lines accurate, not just the net income figure.
Build the location-level adjusted EBITDA add-back schedule
For every location, surface the recurring owner or clinician compensation pattern, any related-party rent, and any one-time items, so a comparable adjusted EBITDA figure can be built for each location — not just the portfolio total. This is what makes a location-by-location performance comparison meaningful rather than just a raw revenue ranking.
Assemble the roll-up and reconcile it back to the bank
Combine every location's tagged, eliminated and normalized figures into the consolidated roll-up, then confirm the total ties back to the sum of every location's actual bank activity for the period. A roll-up that doesn't reconcile to the underlying bank totals isn't ready for board reporting, no matter how complete it otherwise looks.
Include the date the roll-up was prepared, and the reporting period it covers, directly on the document — a consolidation with no as-of date attached ages quietly and can end up being relied on months after it stopped reflecting reality, with nobody noticing until it's pointed out.
Signs a consolidation is off
A management fee that's off by an oddly specific amount
A discrepancy of a few hundred dollars usually points to a calculation basis mismatch, not a rounding difference — worth tracing to its exact cause rather than writing off.
A location's margin that jumps sharply between periods with no obvious explanation
A sudden jump is worth double-checking — it can be a genuine operational change, or it can be a miscategorized transaction inflating or deflating one period.
The follow-up list has a recognizable pattern
Several unmatched deposits from the same location, or the same missing account appearing repeatedly, usually means step 1 or step 3 needs another pass before the roll-up can be trusted.
A portfolio total that doesn't roughly match what the CFO remembers seeing
Not proof of an error on its own, but worth reconciling — a large gap between the documented total and recollection deserves a conversation before the roll-up is finalized.
When a new acquisition joins mid-close
A location that closes partway through a reporting period needs to be included in the roll-up on a pro-rated basis — its bank activity only counts from the acquisition date forward, not the full period. Rather than trying to estimate a partial-period figure, run the full eight-step process on that location's actual bank statements from the acquisition date to the period end.
Flag the location clearly as a partial-period addition in the roll-up itself, so anyone reviewing the consolidated total understands why that location's contribution looks smaller than a full period would suggest, without needing to ask.
What columns the working roll-up actually needs
| Column | Why it's there |
|---|---|
| Location and account type | Feeds the tagging in step 4 |
| Raw revenue and expense per location | The starting point before elimination and add-backs |
| Management fee amount and elimination flag | Feeds step 6's elimination |
| Add-back category and amount | Feeds step 7's normalized figure |
| Statement source and page | The reference that makes step 8's reconciliation possible |
Keeping the elimination and add-back flags as their own editable columns, rather than immediately netting them into a single adjusted figure, makes it much easier to revise an early judgment call as steps 5 through 7 surface new evidence — auditing a flagged column is far simpler than unwinding an already-netted total.
Double-checking the finished consolidation
Before treating a consolidation as final, add every location's reconciled bank total back together and compare it against the sum reported directly by your accounting system for the same period. A consolidation that accounts for an implausibly small share of the accounting system's total usually means an account was missed in step 1; one that accounts for an implausibly large share usually means an intercompany transfer got counted as external revenue by mistake.
It's also worth re-running step 5's intercompany fee check one final time after the roll-up feels complete — a fresh look with the confirmed eliminations already in mind sometimes catches a small, low-frequency fee transfer that a first pass reasonably treated as resolved.
A quarterly close, start to finish
A regional dental group with eighteen locations consolidates a quarterly reporting period covering forty-two bank accounts across operating, payroll and merchant deposit categories.
| Step | Result |
|---|---|
| Bank accounts inventoried and read | 42 of 42 |
| Management fees matched and eliminated | 18 of 18 |
| Add-back candidates surfaced | 11, across nine locations |
| Locations flagged for further review | 2, unusual one-time transactions |
One of the flagged one-time transactions turns out to be an insurance settlement payment following a minor property damage claim — correctly excluded from recurring operating activity once flagged, rather than left blended into that location's regular quarterly cash flow.
A printable checklist
Every location's bank accounts inventoried, including legacy accounts
Chart of accounts confirmed consistent across every location
Every bank statement read and structured for the period
Every transaction tagged by location and account type
Every intercompany management fee identified and documented
Management fee eliminated per ASC 810-10-45-1
Add-back schedule built for every location
Roll-up reconciled back to the sum of location-level bank totals
How long each step takes
For someone with a steady routine, most steps move quickly once the documents are in hand — steps 3 and 4, reading and tagging every location's bank statements, typically take the most time on a large portfolio. Reading the statements into a structured form once shifts most of that time to a few minutes of upload instead of days of manual data entry across dozens of accounts.
Steps 1, 2 and 8 are comparatively fast once a routine is established — inventorying accounts, confirming the chart of accounts, and final assembly are mechanical once the harder matching decisions in steps 5 through 7 have already been made.
Common mistakes worth avoiding
Consolidating only the accounts the accounting system already knows about
A legacy account from before an acquisition can sit outside the standard system for months without anyone noticing it's missing from the roll-up.
Netting the management fee without documenting it
An elimination made without a clear reference to the specific fee transaction is hard for anyone else to verify later.
Estimating owner comp from a single conversation rather than the bank record
A verbal estimate from a seller or a founding doctor often doesn't match the actual recurring payment pattern in the bank statement.
Forcing a location's numbers to fit the standard chart of accounts without checking first
Assuming consistency instead of confirming it can silently distort category-level comparisons across the portfolio.
How often this actually needs doing
Ideally at the close of every reporting period, so a discrepancy or a missing account is caught quickly — not only when a board meeting makes it urgent. The later a gap is caught, the harder it is to reconstruct exactly what happened at a specific location.
A regular cadence also keeps each individual consolidation small. Letting several reporting periods accumulate before the next check means more transactions to sort through at once, and a longer stretch of time during which an error could have compounded unnoticed across multiple locations.
A monthly rhythm, even for a platform that only reports formally to its board quarterly, tends to work well in practice.
With tooling vs. by hand
By hand, this process is fully workable — many controllers do exactly this for smaller platforms. What a document-reading tool changes is the reading and tagging step itself: instead of manually keying every transaction from every location's statement, the transactions are extracted and tagged automatically, with anything genuinely ambiguous flagged for a human decision.
The eight steps themselves don't change either way — what changes is how much of each step is mechanical versus manual. Steps 1 and 2 stay essentially the same regardless; steps 3 and 4 are where automation does the most work, since reading and tagging transactions across dozens of accounts is exactly the kind of repetitive extraction a document-reading tool handles quickly.
Neither approach removes the judgment steps entirely — step 6's elimination confirmation and step 7's add-back decisions still benefit from a person who understands the platform's specific MSA structure and each location's history, regardless of how much of the mechanical extraction is automated.
If this is your first consolidated close
Start with the most recent reporting period, where the transactions are freshest and easiest to confirm, rather than attempting to reconstruct a full year's history across every location at once. One completed consolidation gives you a working process to extend backward if earlier periods still need it.
It's also worth accepting, on a first attempt, that a few items may end up on a follow-up list simply because the process is new — treat the first pass as a working draft that gets cleaner each time it's repeated, rather than expecting a perfect close on the very first try.
A first-time controller benefits from working alongside someone who's done this before, whether that's an outside accounting firm or a more experienced colleague, precisely for the judgment calls that steps 6 and 7 require — recognizing what counts as a proper elimination and what genuinely needs to be flagged as an add-back is a skill that develops with repetition.
Who this guide is for
DSO and VSO controllers preparing for a board reporting cycle, PE sponsor finance teams overseeing multiple portfolio platforms, and outside accounting firms supporting practice-group clients will all recognize this process — the steps are the same regardless of who performs them.
It's also written to work for someone doing this for the very first time, not just for someone with existing DSO or VSO accounting experience — the eight steps assume no prior familiarity with a specific platform's MSA structure beyond the documents themselves, which is deliberate, since a first-time controller facing their first quarterly close is exactly the audience most likely to need a structured process rather than intuition built from repetition.
Doing this across a growing portfolio
Each location goes through the same eight steps, and the confirmed data from earlier periods makes later periods faster to check — once a location's standard chart of accounts and MSA terms are established, later closes mostly confirm the existing setup rather than requiring fresh discovery.
Treat each period's pass as a confirmation exercise rather than starting from zero — check that previously reconciled locations still line up, then apply step 1's full inventory check specifically to any location added since the last close, watching for a new account that hasn't yet been folded into the standard process.
Over several quarters, this compounding familiarity is where the real time savings show up — a controller who has consolidated six consecutive reporting periods the same way recognizes the portfolio's typical fee structure, its usual add-back categories, and its normal transaction patterns well enough to spot a genuine anomaly almost immediately, rather than having to work it out from scratch every single time.
This is also where the effort of setting up a repeatable process pays off most clearly — a platform that treats its first few consolidations as an investment in a documented, repeatable method spends far less time per location by the time it reaches thirty or forty practices than one that's still improvising a slightly different approach every quarter.
A short glossary
| Term | Meaning |
|---|---|
| MSA | Management Services Agreement — the contract between the MSO and each clinical practice |
| VIE | Variable Interest Entity — the consolidation treatment used when the MSO absorbs most of a practice's economic risk and reward |
| Same-store growth | Revenue growth measured only across locations owned for the full comparison period |
| Add-back | An adjustment to reported EBITDA for a non-recurring or non-market item, used to normalize a location's figure |
These four terms cover most of what comes up while working through the eight steps — MSA and VIE describe the legal and accounting structure behind every location, while same-store growth and add-back explain the two specific comparisons the consolidation is ultimately built to support. Knowing the difference between a same-store comparison and a raw portfolio total, in particular, is what makes step 7's normalization work make sense rather than feel arbitrary.
Handing this off to an outside accounting firm
A roll-up that lives only in one controller's spreadsheet, without the underlying matching documented, is hard for anyone else to trust or extend. Handing an outside accounting firm the consolidated roll-up alongside the source bank statements and the elimination and add-back workpapers means they can verify it themselves instead of taking your word for it. See the full overview for how this fits into the rest of the reporting process.
A good handoff also anticipates the question that comes next, not just the roll-up itself — an accounting firm receiving a platform's consolidated financials will almost always ask why a specific add-back was applied where it was, and having that reasoning already documented turns the handoff into a genuinely useful starting point instead of just a set of numbers to re-verify.
This same documentation habit pays off well beyond any single handoff — a platform that changes accounting firms, brings a new CFO on board, or simply needs to answer a sponsor's question about a prior quarter benefits from the same sourced trail, regardless of who's asking or why.