Banking Is Where the MSO-PC Structure Becomes Operational
Entity separation, payer deposits, EOBs, sweeps, reserves, and MSO management fees all show up in the bank account. Generic business banking was not designed for that.
A PC-MSO structure is not just a set of legal documents. It is a daily operating model. Once patient payments, insurance deposits, payroll, vendor bills, reserves, and MSO fees start moving, the banking layer becomes one of the clearest records of whether the structure is being run cleanly.
Why MSO-PC Banking Is Different
In a typical MSO-PC arrangement, the physician-owned PC is the clinical entity. The MSO provides non-clinical management services under an MSA. That separation matters for ownership, clinical independence, contracts, payer enrollment, tax reporting, and accounting. It also matters for the bank accounts.
Entity separation is not optional
The PC and MSO usually need distinct accounts, permissions, accounting treatment, and paper trails. Blending funds can make it harder to show that the structure is being operated the way the documents say it should operate.
Revenue lands before anyone understands it
A payer deposit may hit the account before the team has matched the ERA, EOB, check image, patient responsibility, and claim-level detail needed to know what was actually paid.
Management fees need a clean path
The PC may owe the MSO a management fee under the MSA, but the movement of funds still needs to follow the agreed fund-flow model, reserve requirements, and any counsel-approved guardrails.
Growth multiplies the banking burden
Every additional state, PC, location, payer, or acquisition can add new accounts, signers, routing details, reporting needs, and reconciliation work.
Where Traditional Banking Breaks
Traditional business banking can work for a single operating company. It starts to strain when a healthcare group needs clean separation and consolidated control at the same time. MSO-PC groups often need both: entity-level boundaries for the structure, and group-level visibility for operators, finance teams, and outside reviewers.
- Separate bank logins for each PC, MSO, location, or acquisition.
- Slow account opening when a structure has many affiliated entities.
- Manual spreadsheets to track payer deposits, transfers, reserves, and entity balances.
- Weak connection between the bank deposit and the remittance information needed for posting.
- Limited tools for controlled sweeps, role-based access, and entity-level audit exports.
- FDIC coverage analysis that depends on the exact account ownership and bank program structure.
The Revenue Cycle Problem
Healthcare payments do not behave like ordinary invoices. An electronic funds transfer can land in the bank while the remittance advice travels separately. Paper checks may arrive with EOBs that still need to be scanned, parsed, and matched. Patient payments may have to be reconciled against balances that changed after insurance adjudication.
That means the finance question is rarely just "did money arrive?" The harder question is which payer, patient, claim, provider, location, and entity the money belongs to.
What Lemma Is Trying to Solve
Lemma is a healthcare-native banking platform designed around the way medical practices get paid. For MSO-PC groups, the interesting part is not just that it offers bank accounts. It is that the account structure, payment tooling, lockbox, EOB parsing, reconciliation, and treasury workflows are aimed at the operational mess that healthcare groups actually face.
Multi-entity visibility
Lemma is designed around medical practices that need to see cash across entities without forcing the finance team to stitch together separate bank portals.
Accounts built around PC/MSO operations
Its MSO-PC materials emphasize distinct accounts, entity-level routing, consolidated dashboards, and fund movement workflows that fit multi-entity healthcare groups.
Reconciliation closer to the cash
Lemma pairs bank activity with healthcare payment context, including lockbox workflows, EOB parsing, and reconciliation tooling for insurance collections.
Sweep and payment workflows
For groups with multiple PCs or locations, automated sweep logic and auditable ACH, wire, RTP, and FedNow payments can reduce manual treasury work.
A better banking layer does not replace legal structure.
Counsel and accounting professionals still need to decide how funds should flow between the PC, MSO, providers, vendors, and reserve accounts. The value of a healthcare-specific banking platform is that it can make the approved model easier to operate, monitor, and document.
See Lemma's MSO-PC banking approachQuestions to Ask Any Banking Partner
Whether you evaluate Lemma or another provider, the banking review should be part of the same implementation process as the MSA, payer enrollment, accounting setup, and compliance review.
- 1Can each PC, MSO, location, or payer stream be represented cleanly without losing consolidated visibility?
- 2How are EFTs, ERAs, EOBs, check images, and deposits matched?
- 3Can permissions separate finance, operator, bookkeeper, reviewer, and practice-level access?
- 4Can the bank export an entity-level audit trail for counsel, accounting, diligence, or board review?
- 5How are sweep rules configured, approved, and documented?
- 6What bank provides the deposit account, what FDIC coverage applies, and how does any sweep network work?
- 7How quickly can new PCs, locations, or acquisitions be onboarded without disrupting payer enrollment?
Explore Lemma
If you are building or operating a PC-MSO/MSO-PC group, Lemma is worth reviewing as a healthcare-native banking option. The most relevant areas to inspect are entity management, lockbox and EOB handling, reconciliation, sweep rules, and payment audit trails.
Explore LemmaBanking and FDIC note
Lemma Technologies, Inc. is not a bank. Banking services are provided by Core Bank, Member FDIC. Deposit insurance depends on the insured bank, depositor, ownership category, account structure, and applicable program terms.
Further reading
Disclaimer: This page provides general educational information and is not legal, banking, tax, or financial advice. Work with qualified counsel, accounting professionals, and banking professionals before setting fund-flow policies for a PC-MSO or MSO-PC structure.