> [llms.txt](https://getlemma.com/llms.txt)

# Can one bank account serve multiple PCs legally?

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.

## The short answer in 30 seconds

For an MSO-PC structure with multiple PCs:

- Each PC must hold clinical revenue in its own bank account, in the PC's legal name and EIN
- The MSO can hold its own funds (management fees received, admin expenses paid) in MSO-named accounts
- Funds flow between PCs and MSO via documented intercompany transfers, not by sharing accounts

One pooled account across multiple PCs almost always fails compliance review at audit time. The exceptions are rare and require legal counsel to confirm.

## What CPOM actually says

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](/provider-guides/cpom-compliance-bank-account-ownership) 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.

## Why pooling is risky beyond CPOM

Three additional reasons not to pool:

- **Payer contracts.** Most insurance contracts are signed with a specific PC entity and its NPI. Reimbursements have to flow to that entity. Routing them to a pooled account triggers payer compliance flags and, in some cases, contract termination
- **Tax filings.** Each PC files its own tax return. Pooled bank accounts make it materially harder to attribute revenue and expenses to the correct entity
- **Audit exposure.** Practice audits (Medicare Advantage RADV, OIG, state Medicaid) review fund flows. Pooled clinical revenue is one of the most common red flags in audit findings

## What most groups actually do

The standard pattern for a 5-PC group:

1. Each PC has at least one operating account in its own name and EIN
2. The MSO has its own operating and reserve accounts
3. Each PC pays a documented management fee to the MSO under the management services agreement (MSA)
4. Excess cash in any PC sweeps to a savings account at that same PC, or pays its share of MSO fees on schedule
5. The MSO never directly receives clinical revenue. Funds always flow via documented intercompany transfer per the MSA

This setup looks fragmented from the outside, but with the right banking platform it operates as one consolidated view for the CFO.

## What banking tools make this easier

Three capabilities turn separate-but-coordinated accounts into a workable system:

- **Virtual accounts.** Each PC gets unique routing and account numbers for payer EFT enrollment, all settling into one underlying entity account. Avoids opening dozens of additional accounts just to get per-location attribution
- **Automated sweep rules**, built on [sweep automation built around MSA terms](/provider-guides/automated-sweep-rules-mso-pc). Rules like "if PC-3 holds more than $X in operating cash, sweep $Y to PC-3's reserve account each night." Can include intercompany flows where the MSA permits
- **Consolidated dashboard.** Real-time view of every entity's cash position in one place, even though each is a legally separate account

## When combining might be acceptable (rare)

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:

- States with no CPOM (Delaware and a few others) where the practices are wholly owned by the same individual clinician
- Internal sub-accounts within a single PC that bills under multiple DBAs but stays one legal entity
- Temporary pooling during an entity restructure, with clearly documented endpoint and timeline

None of these apply to a typical multi-physician MSO-PC group. Default to separate accounts.

## A practical compliance checklist

1. Confirm each PC has its own EIN and is registered in its operating state
2. Confirm each PC has at least one bank account in its own name and EIN
3. Confirm the MSO has its own bank account, separate from any PC's
4. Document every intercompany transfer per your MSA: which entity is paying which, for what service, in what amount, on what date
5. Reconcile each PC's bank account against its own books monthly, never against pooled or MSO books
6. Review payer EFT enrollments annually. Confirm each payer is depositing to the correct PC account
7. Have a healthcare attorney review your account structure annually, especially after any state law change or new PC addition

## How state variations actually play out

| 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.

## What audits actually look at

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:

1. Claim filed by PC X
2. Payer issues 835 ERA naming PC X
3. ACH deposit lands in PC X's account
4. Posting in PC X's books matches the 835 line items
5. If MSO management fee applies, the fee transfers from PC X to MSO via documented intercompany payment

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.

## The setup cost vs. cleanup cost

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](/mso-banking), 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.

## What healthcare attorneys will tell you

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](/provider-guides/banking-red-flags-mso-pc-audit) 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.

## Your bank doesn't know healthcare. Lemma does.

Lemma is business banking for healthcare practices, MSOs, DSOs, and multi-entity groups: free ACH, up to 1.75% APY, $10M FDIC protection, entity management, cash sweeps, and an AI-powered lockbox that digitizes checks and EOBs on arrival.

Free for a single entity, $50/month per entity for groups. Open in 5 minutes. It's the last bank switch you'll make.

[Sign up](https://app.getlemma.com/sign-up)
[Book a demo](https://calendly.com/d/ct72-djp-r7w)
[Pricing](https://getlemma.com/pricing)