In most states, pooling clinical revenue across multiple PCs in one account violates CPOM. Here's what's required — and the structure that actually works.
A direct answer to whether MSO-PC groups can pool clinical revenue in one bank account, what CPOM rules say, and the standard separate-account-plus-automation pattern that actually works.
The short version: in most states, no. Pooling clinical revenue from multiple PCs into one bank account violates Corporate Practice of Medicine (CPOM) rules, payer contract terms, or both. Even in states without strict CPOM, fund commingling creates audit risk and operational headaches that almost always outweigh any convenience.
This guide is not legal advice. Consult a healthcare attorney for your specific structure. But the patterns are consistent enough that the answer for almost every multi-PC group is the same: open separate accounts, then use automation to make them feel like one account.
For an MSO-PC structure with multiple PCs:
One pooled account across multiple PCs almost always fails compliance review at audit time. The exceptions are rare and require legal counsel to confirm.
Corporate Practice of Medicine doctrine prohibits non-clinicians from owning, controlling, or directly profiting from clinical practice, and the compliance rules governing PC account ownership (opens in a new tab) follow directly from that principle. Most states have some form of CPOM, but the strictness varies dramatically.
States with strong CPOM enforcement (California, New York, Texas, Illinois, New Jersey, others) treat pooled clinical revenue across PCs as a flag for unauthorized lay ownership. The reasoning: if multiple PCs share an account, who actually controls the funds? If the answer is the MSO or a non-clinician administrator, that's effectively non-clinician control of clinical revenue.
Even states without strict CPOM treat fund commingling between separate corporate entities as a corporate veil issue. If the IRS or a state audit finds blended funds, the legal separation between the PCs and the MSO can collapse, exposing all entities to combined liability.
Three additional reasons not to pool:
The standard pattern for a 5-PC group:
This setup looks fragmented from the outside, but with the right banking platform it operates as one consolidated view for the CFO.
Three capabilities turn separate-but-coordinated accounts into a workable system:
There are narrow scenarios where pooling clinical funds across PCs is potentially acceptable. These are the exceptions, not the rule, and every one of them requires explicit written sign-off from a healthcare attorney:
None of these apply to a typical multi-physician MSO-PC group. Default to separate accounts.
| State group | CPOM stance | Pooling implication |
|---|---|---|
| Strong CPOM (CA, NY, TX, IL, NJ) | Strict prohibition on lay ownership | Pooled clinical revenue is an immediate flag. Separate accounts mandatory |
| Moderate CPOM (most other states) | Restrictions on non-clinician control | Pooling allowed in narrow cases, but adds audit risk. Separate accounts strongly advised |
| No CPOM (DE, plus a few) | No formal restriction | Pooling may be technically legal, but corporate veil and tax concerns still apply |
The "no CPOM" column is misleading. It does not mean fund commingling is safe. Tax attribution, payer contract compliance, and corporate liability separation still argue for separate accounts even where state CPOM does not.
Practical audits, whether by Medicare Advantage RADV, OIG, state Medicaid, or commercial payer SIU teams, look at fund flows from claim to deposit to ledger. The chain has to make sense:
Pooled accounts break step 3 immediately. The deposit lands somewhere that cannot be tied to a specific PC entity, which makes reconciliation against payer remittance and downstream posting much harder to defend.
Setting up multiple per-entity accounts at a generalist business bank takes 35 to 75 days for a 5-PC group, depending on the bank. At a bank built for fast multi-entity onboarding (opens in a new tab), the same setup runs 5 to 10 days because multi-entity onboarding is the assumed default.
Cleaning up a commingled account problem after 12 to 24 months of operation typically takes 6 to 12 months and several attorney engagements. The labor cost alone often exceeds $30,000. Payer EFT re-enrollment can delay incoming reimbursements by 30 to 90 days during cutover. The arithmetic is unambiguous: even a slow upfront setup is cheaper than any cleanup.
Healthcare attorneys who specialize in MSO-PC structures consistently advise the same thing for fund flows: separate everything that's legally separate, document every transfer, and never rely on operational convenience as a justification for compliance shortcuts. They will also tell you that the setup decisions made in year one shape the banking red flags that surface in a PE or payer audit (opens in a new tab) for the next decade. Get the bank account structure right early, and most of the downstream risk handles itself. Skip it, and the cost compounds quietly until something forces a cleanup.
If you are unsure whether your current setup is compliant, the cheapest move is to schedule a one-hour review with a healthcare attorney before adding a new PC, applying for new payer contracts, or considering a sale. The hour usually pays for itself many times over.