Prerequisites
- Both entities formed with EINs
- Employer registrations in every state with employees, for both entities
- A clear list of who is employed by which entity
Who employs whom
The clinical support staff question is genuinely state-dependent. Medical assistants working under clinical supervision look clinical; in some analyses they are MSO-employable, in others not. Get a state-specific answer rather than defaulting either way. See What an MSO can and can’t do.
Steps
1
Register both entities as employers in every state
Per state, per entity:
- Income tax withholding registration
- Unemployment insurance registration
- Any local or municipal taxes
- Workers’ compensation coverage
2
Choose the payroll setup
Test the two-employer case in the demo. Many payroll products assume one business with one EIN. Ask directly: can I run two employers under one login, with separate funding accounts and separate tax filings? A product requiring two entirely separate instances is workable but is not the integration it was sold as. See Bundled payroll and processing.
3
Fund each payroll from the correct entity's account
Clinical payroll from the PC’s account. Non-clinical from the MSO’s.This is not a bookkeeping preference. Paying clinical payroll from the MSO’s account means the MSO is compensating clinicians for practicing, which is the CPOM prohibition.
4
Design benefits for parity
Two employers, one team. If the PC’s clinicians and the MSO’s staff sit in the same office with materially different benefits, you have a morale problem and a recruiting problem.Aim for the same health plan design, the same PTO policy, and the same retirement plan structure across both. Note that offering identical plans across two unrelated employers has its own compliance considerations — controlled group and affiliated service group rules can affect retirement plan testing and ACA obligations. This is a real question for your benefits advisor, not a formality.
5
Handle multi-state payroll as you expand
Each new state means registrations for both entities, state-specific withholding, state unemployment insurance, and any state-mandated programs — paid leave, disability, retirement mandates.Remote employees create nexus in their state of residence. Track where people actually work, not where they were hired.
6
Get contractor classification right
Note also that a contractor clinician still must be credentialed and linked to the PC’s payer contracts to bill for their services.
PEOs
A professional employer organization becomes a co-employer, handling payroll, benefits, and compliance.
A PEO co-employing your clinicians deserves specific analysis. In a CPOM state, the question of whether a lay co-employer employing physicians to practice creates exposure is not obvious. Some groups use a PEO for the MSO only and keep the PC’s payroll direct. Raise it with healthcare counsel before signing.
Verify it worked
- Both entities registered as employers in every state where each has employees
- Clinicians employed by the PC
- Non-clinical staff employed by the MSO
- Clinical support staff classification confirmed with counsel
- Clinical payroll funded from the PC’s account; non-clinical from the MSO’s
- Payroll provider handles two employers without separate instances
- Benefits designed for parity, with controlled-group implications reviewed
- Contractor classifications reviewed by employment counsel
- Multi-state registrations current as you expand