The Decision That Compounds

At 5 PCs, the question is small. At 50 PCs, the answer reshapes how your treasury team spends its day.

The decision is structural: does each professional corporation get its own real bank account, or does each PC get a virtual sub-account under a single master? On a spreadsheet they look equivalent. In operations, they are not.

This article is for CFOs and treasury leads at multi-entity healthcare platforms. We compare virtual accounts, true sub-accounts, and separate accounts on reconciliation, sweeps, FBO structure, payer EFT routing, and what audit cares about.

Definitions, Quickly

Separate accounts means each PC has its own bank account at the bank: distinct account number, distinct routing number (or shared routing depending on the bank), distinct statement, distinct everything. The bank treats each PC as a separate customer.

Virtual accounts (sometimes called virtual ledger accounts or VAs) means there is one real bank account at the bank. The bank issues distinct virtual account numbers for each PC, all backed by the same master. Payer ACH lands at the virtual number, which routes internally to the right PC for reporting and reconciliation.

True sub-accounts are a middle ground: one banking relationship, multiple legally distinct accounts that report up through a parent. Less common in healthcare, more common in fintech.

How They Compare on Reconciliation

Separate accounts: each PC reconciles independently. If a payer sends Aetna's ACH for the dermatology PC into the wrong account, you find out at month-end. Reconciling 50 separate statements is a part-time job.

Virtual accounts: payer ACH lands at the virtual number tied to a specific PC. Reconciliation is automatic per PC. The master account just sees the same totals roll up. You catch routing errors immediately because the system flags them.

Winner: virtual accounts, by a wide margin, once you cross 10 PCs.

How They Compare on Sweeps

Separate accounts: sweeps require either a sweep agreement at each bank (operationally complex) or a daily manual process to push excess balances to a central reserve. Most platforms end up doing this on Fridays. By Friday, the cash has been sitting all week earning zero.

Virtual accounts: sweep policies live at the master account level. "Any virtual balance above $500K end of day sweeps to the reserve" runs automatically. No human touches it.

Winner: virtual accounts, especially as your reserve grows past $5M.

How They Compare on Payer EFT Routing

Separate accounts: each payer EFT enrollment uses the PC's distinct account number. Payers store this. If you ever consolidate banking, every payer needs a re-enrollment. That is the consolidation pain we wrote about in the previous post.

Virtual accounts: each PC has its own virtual account number that the payer sees. Re-enrollment within the same bank is trivial because the master account does not change. Re-enrollment across banks requires the same notification but is easier to sequence.

Winner: virtual accounts, with a meaningful gap.

How They Compare on FBO and Audit

Separate accounts: legally distinct. Each PC's funds are clearly segregated. CPOM-compliant by default. Auditors love this.

Virtual accounts: legally one account, with internal allocation to each PC. The bank's master account holds all the funds, but the virtual account architecture preserves the same effective segregation through bookkeeping. CPOM compliance depends on documentation: the trust agreement, the FBO designation, and the operating agreement language need to explicitly establish that the virtual accounts are For Benefit Of each specific PC.

Winner: even, with a caveat. Virtual accounts require slightly more documentation work upfront but are equally defensible if the documentation is clean.

The Cost Picture

Separate accounts: monthly maintenance per account ($15-$60 per PC per month at most banks), per-item ACH fees per PC (if not waived), and 50 separate statements that someone has to download and reconcile.

Virtual accounts: typically a flat platform fee at the healthcare-native bank, with free ACH, free virtual account provisioning, and one statement that breaks down by PC.

At 50 PCs, the difference is real money. $15 per account per month across 50 PCs is $9,000 per year in just maintenance, before reconciliation labor.

When Separate Accounts Still Win

Regulatory ambiguity. If you operate in a state where your CPOM counsel is not confident that virtual accounts meet the segregation standard, default to separate. Audit defensibility is worth the operational overhead.

The Recommendation, Stated Plainly

For 90% of multi-entity healthcare platforms, virtual accounts under a healthcare-native bank are the better architecture once you cross 10 entities. The reconciliation, sweep, payer routing, and cost advantages compound. The audit risk is manageable with good documentation.

The remaining 10 percent (regulatory ambiguity, PC-level borrowing, anticipated carve-outs) should default to separate accounts and accept the overhead. Make the call deliberately. Do not default to either by accident.