The same small check, every reporting period
Multi-location roll-up reporting doesn't reward cleverness — it rewards consistency. The same reconciliation check, run the same way, at every location, every reporting period, without exception, is what actually keeps a DSO or VSO platform's numbers trustworthy. The scenarios below are the situations that check gets tested by in practice, and how reading bank statements automatically changes each one.
Why a five-location startup and a fifty-location platform need the same discipline
A platform with five locations might reconcile them by memory and a shared spreadsheet, and mostly get away with it. A fifty-location group running acquisitions every quarter can't — the volume alone makes an informal process unreliable. But the underlying obligation is identical either way: every location's reported figure has to trace to a bank record, every period, regardless of how many accounts that involves. What scales is the tooling behind the discipline, not the discipline itself.
Scenario: the routine monthly close
The reporting period closes, and a controller needs to reconcile eighteen locations' worth of bank statements against the consolidated ledger before the board reporting package goes out two weeks later.
Reading every location's statements automatically, with every transaction tagged consistently, turns a multi-day manual pass into a same-day review — the controller's time goes to the handful of items that don't tie cleanly, not to re-keying every transaction by hand.
Scenario: a diligence team asks about one location's margin
A lender's diligence team, reviewing a refinancing application, asks why one specific location's adjusted EBITDA margin looks meaningfully different from the platform average, with a response expected within a week.
When that location's bank activity has already been read, tagged and normalized, pulling the exact transaction-level backup the question requires is a search, not a reconstruction — the difference between meeting the deadline comfortably and scrambling through a year of paper files.
Scenario: a management fee that doesn't tie out
A location's monthly management fee transfer lands $900 short of what the MSA formula predicts, with no obvious explanation on either the practice's or the MSO's bank statement.
Because every fee transfer is checked against its expected amount as a matter of routine rather than assumed to be correct, the discrepancy is flagged the same month it happens — traced to a collections-basis timing difference before it becomes an unexplained gap discovered during a board review months later.
Scenario: a location quietly underperforming
A location's adjusted EBITDA margin has been drifting down for three consecutive quarters, masked by strong performance at several other locations keeping the blended portfolio total looking healthy.
Because every location's bank data is read and tagged consistently rather than only reviewed at the consolidated level, the trend is visible the moment someone looks at location-level detail — surfaced clearly enough that the platform can decide how to intervene deliberately, rather than discovering the decline only once it's severe enough to visibly affect the blended total.
Scenario: onboarding a new controller mid-year
A platform replaces its controller partway through the fiscal year, and the new controller needs to understand every location's full financial history quickly, without months of tribal knowledge about how the prior controller kept things organized.
A consistent, document-driven process — the same reading and tagging method regardless of who runs it — is far easier to hand off than a process that depends on one person's memory of which locations need extra attention.
Scenario: a platform running two accounting systems
A platform formed by merging two smaller groups runs one legacy accounting system for locations from the first group and a different system for locations from the second, each with its own categorization habits.
Reading every location's bank statements the same way produces one consistent, comparable dataset across both groups without merging the two accounting systems awkwardly — two separate back-office systems, one consistent bank-level reading process behind them.
Scenario: an add-back nobody re-reviewed in a year
A founding doctor's above-market owner compensation, flagged as an add-back at the time of acquisition, was renegotiated down to a market rate a year later — but the original add-back kept getting carried forward into every subsequent adjusted EBITDA calculation.
Because the reading surfaces the actual current recurring payment pattern from each period's bank statements, rather than relying on a static schedule set once at acquisition, the change shows up the next time that location's data is reviewed — a prompt to update the add-back schedule rather than carrying a stale figure forward indefinitely.
Scenario: a board meeting under compressed time
A platform realizes with four days left before a board meeting that its monthly close for six of its locations hasn't been started, after weeks focused entirely on closing two new acquisitions.
Having the bank statements read and structured in minutes, rather than hours of manual cross-referencing per location, turns a genuinely tight deadline into a workable one — the compressed time gets spent reviewing flagged exceptions, not doing the mechanical matching from scratch.
Scenario: preparing for a refinancing
A platform pursuing a refinancing needs to produce documentation tracing every location's reported adjusted EBITDA back to its source bank activity, across several reporting periods and a growing number of locations.
A consistent, documented reconciliation for every location every period — already organized rather than assembled retroactively — makes the lender's diligence review a matter of pulling existing records, not reconstructing a year's history under review pressure.
Scenario: a joint venture location with a minority partner
A location structured as a joint venture with a minority-interest local partner distributes profits according to a specific ownership split, with the distribution memo listing the calculation behind each party's share.
Reading the distribution memo alongside the location's own bank activity confirms the split was calculated and paid correctly, and keeps that location's reported figures properly separated from wholly-owned locations elsewhere in the portfolio.
Scenario: two platforms merging after a sponsor consolidation
A sponsor merges two portfolio companies it owns into a single combined platform, inheriting a second group's books that were kept somewhat differently than the surviving platform's own records.
Reading the acquired platform's historical bank statements the same way as any other source material — regardless of which platform originally generated them — gets that history onto the same traceable footing as the surviving platform's own records, without a lengthy manual re-entry project before the combined portfolio can be reconciled with confidence.
Scenario: a location switching banks mid-year
A location moves its operating account to a different bank partway through the year as part of the platform's standard banking consolidation, and the new bank's statement arrives in a completely different layout — different transaction description format, unfamiliar section headings.
Because the reading works from a statement's own printed structure instead of a fixed template tied to one bank, the new bank's statements are read the same way from the first one onward — no gap in that location's reconciliation history around the transition.
Scenario: an outside accounting firm taking on a new platform client
An outside accounting firm picks up a new DSO client mid-year and needs to understand, from several months of bank statements across twenty-two locations, exactly what's already been reconciled and what still needs review — before any conversation with the sponsor or the prior controller.
Reading several months of statements across every location at once turns what would otherwise be a full week of manual document review into an initial picture ready within a few days, freeing the firm's actual accounting expertise for judgment calls rather than data entry.
Scenario: a wave of acquisitions closing in the same quarter
A platform closes four new locations in a single quarter as part of an aggressive growth push, each arriving with its own legacy bank accounts and bookkeeping habits, all needing to be folded into the roll-up before the quarterly board meeting.
Because reading and tagging documents scales with volume rather than needing more manual hours per location as acquisition activity rises, the wave doesn't demand disproportionately more staff time than a quiet quarter — the review step still needs a person's attention, but the re-keying step that used to grow linearly with the number of new locations doesn't.
What this actually saves
| Task | Typical manual effort | With reading automated |
|---|---|---|
| Monthly close, twenty locations | 3-4 days | Same-day review of flagged items |
| Responding to a lender's diligence request | Days of file retrieval | Hours, mostly review |
| Finding a management fee that doesn't tie out | Weeks, if found at all | Same period it happens |
| Onboarding a new controller or accounting firm | Months of tribal knowledge | A documented, repeatable process |
A typical monthly close
Upload every location's bank statements for the period, let every transaction get read and tagged by location and account type, review the small number of items flagged for confirmation, then reconcile every location against the consolidated ledger's own reported total. See the full step-by-step guide for the detailed process.
Why the structure isn't identical for every platform
Corporate practice of medicine and dentistry rules vary by state, which means the specific MSA structure, the consolidation treatment, and even whether a practice is consolidated as a variable interest entity at all can differ from one location to the next within the same platform, depending on where each practice is located. A platform operating across many states can genuinely face different structural nuances at different locations.
None of that changes the underlying document-reading task — a bank statement is a bank statement regardless of which state's rules ultimately govern that location's consolidation treatment. What it does mean is that the specific accounting treatment for each location is worth confirming with your accounting team directly, rather than assumed to be uniform across every location a platform operates.
Who this is for
DSO and VSO controllers at every portfolio size, PE sponsor finance teams, and outside accounting firms supporting multiple portfolio company clients all run some version of the same reconciliation discipline — the scenarios above apply regardless of size, since the underlying obligation to trace every location's figures to its bank record is identical.
Getting started
Upload one location's bank statement to see the reading in action — no signup required to try it on a real document. See the full multi-location roll-up overview for how everything fits together.
The result of that first upload usually settles the question of fit within minutes, which is generally faster than most platforms expect before actually trying it.
Why generic bookkeeping software falls short here
General-purpose bookkeeping software reads bank transactions into a ledger, which is a real and useful step — but it has no concept of tagging a transaction to a specific location among dozens, matching a management fee transfer to its MSA-defined expected amount, or flagging a recurring payment pattern that looks like above-market owner compensation. Those are DSO/VSO-specific reconciliation tasks that a general ledger tool was never built to handle.
A dedicated accounting or ERP system fills part of that gap — most active platforms rightly use one for the actual consolidated financial statements — but even a good accounting system still depends on someone confirming what it reports actually matches what each location's bank received. That confirmation step, tying each location's bank-side reality to the accounting system's own records, is the specific gap this addresses, alongside whatever accounting system a platform already runs.
| What your accounting system gives you | What this fills in alongside it |
|---|---|
| Consolidated financial statements | Reading the location-level bank evidence those figures actually match |
| A reported total per location per period | An independent, document-traceable check on that total |
| A record of what each location's ledger says happened | A record of what the bank statement says actually arrived |
Handling a spike in acquisition activity
DSO and VSO platform growth isn't evenly distributed across a year — a sponsor pushing to hit an annual acquisition target often closes several new locations in the final quarter, and a single busy quarter can carry as much new-location onboarding as several quieter ones combined. A reconciliation process that's comfortable at the steady-state pace can become genuinely strained during that peak, exactly when finance team attention is already stretched thin by deal closing activity itself.
Because reading and tagging documents scales with volume rather than needing more manual hours per location as activity rises, a peak quarter's reconciliation work doesn't demand disproportionately more staff time than a quiet one — the review step still needs a person's attention, but the re-keying step that used to grow linearly with the number of new locations doesn't.
This matters most in the exact window when a platform can least afford a reporting backlog — the final weeks before a fiscal year-end board meeting, when every hour of finance team time is competing directly against closing the next acquisition and integrating the last one.
What an outside accounting firm actually wants to see
Beyond passing a specific quarter's review, an outside accounting firm generally wants confidence that a platform's reconciliation discipline is consistent period to period across every location, not just clean on the specific one they happened to review closely. A visible, repeatable process — the same tagging and verification steps run the same way every period, with a documented history to show for it — is what actually builds that confidence over time, more than any single clean quarter does on its own.
Platforms with a strong, demonstrable process sometimes find that relationship translates into practical benefits beyond compliance — a faster response when questions arise, and occasionally lower accounting fees, since the firm's own effort is directly tied to how well-organized the underlying documentation already is.
This isn't only for the largest platforms
A five- or six-location platform just past its first few acquisitions benefits from the same rigor a fifty-location group's finance office applies — without needing a dedicated controller headcount to get it. The process is identical at every scale; only the volume changes.
If anything, a smaller platform has more to gain proportionally — a single controller wearing every hat has the least slack to absorb a slow manual reconciliation process on top of everything else running a growing platform already demands, and the least room to have a finding surface at exactly the wrong, already-busy moment.
A small platform is also the setting where a single reconciliation gap is most consequential — with fewer locations overall, one mis-tracked location represents a larger share of the total portfolio, and there's no larger finance team to catch it if the one person handling the close happens to miss it that period.
In that setting, reading and tagging every document the same reliable way isn't a convenience on top of an already-solid process — it often functions as the closest thing to a second set of eyes a small platform has, catching what a rushed manual pass during a busy acquisition stretch might otherwise miss entirely, without adding another task to an already full schedule.