Virtual accounts and separate accounts solve different problems in a multi-entity healthcare group. Treating them as substitutes is a common, expensive mistake.

Here's the practical difference, when each is required, and why most MSO-PC structures need both.

What Each One Is

A separate account is its own legal account in its own legal entity's name and EIN. The bank treats it as a distinct customer with its own KYC, statements, and tax reporting.

A virtual account is a unique routing number and account number that looks separate to a payer but settles into one underlying legal entity's master account. The bank treats the virtual layer as a routing convenience, not a separate customer.

From a payer's view, both look the same: a unique routing number and account number to send EFT deposits to. From the bank's view, they're entirely different objects.

When You Need Each

• Per-PC: separate account. CPOM rules and tax filings require legal separation between PCs. Virtual accounts can never substitute here.

• Per-location within a single PC: virtual account. Lets each location enroll for payer EFT separately without requiring a new legal entity per location.

• Per-provider within a single PC: virtual account. Used when individual clinicians need their own routing for EFT enrollment, common in groups with productivity-based compensation.

• Per-purpose (operating, payroll, reserve) within a single PC: separate account. Better for fraud isolation and audit clarity.

A 5-PC, 12-location group with provider-level attribution might run 15 to 20 separate accounts (across all PCs and the MSO) with 30 to 40 virtual accounts on top for payer routing. Sounds like a lot, but the operational complexity all flows through a single dashboard.

The Mistakes to Avoid

Two patterns repeatedly create problems:

• Using virtual accounts to fake legal separation between PCs. Virtual accounts cannot satisfy CPOM because they are not separate legal entities. Multiple PCs sharing one underlying account, even with virtual routing layered on top, is still pooled clinical revenue.

• Opening separate accounts for every location and provider. That turns a 5-PC group into a 30-plus-account operations problem. Use virtual accounts inside each PC for per-location attribution and keep separate accounts at the entity level only.

The right rule of thumb: separate accounts at the legal-entity boundary, virtual accounts for everything below it.

What Lemma doesn't do: it doesn't make virtual accounts CPOM-compliant for cross-entity pooling. Per-PC legal separation still requires per-PC separate accounts. What Lemma does provide is both layers (legal-entity separate accounts plus per-location and per-provider virtual accounts) at account opening, with no per-virtual-account fees.

Open a free Lemma account in 5 minutes per entity. Multi-entity onboarding in 5 to 10 days, virtual accounts for per-location and per-provider routing, automated sweep rules per MSA, and FDIC coverage up to $10M per entity via IntraFi sweep.For groups expecting payer EFT enrollment work, virtual accounts also save time. Each virtual account has its own routing and account number that can be filed with payers immediately, in parallel with the underlying entity setup. That parallelism alone can shave 30 to 60 days off a multi-PC, multi-location go-live.