How to handle intercompany transfers in an MSO-PC

What an intercompany transfer actually is

An intercompany transfer is a payment between two legal entities under common ownership or contract, recorded on the books of each entity. In an MSO-PC group, the most common types are:

• PC pays MSO for management services (the management fee), covered in depth in how MSO management fees are calculated and documented (opens in a new tab). This is the largest recurring intercompany flow.
• MSO pays PC for cost reimbursements where applicable (supplies bought centrally, then distributed).
• PC pays sister PC for shared services where multiple PCs share clinicians, equipment, or staff.
• Owner distributions from a PC to its owners, which are technically not intercompany but require similar documentation.

Each transfer is a real-world ACH or wire payment, not a paper journal entry. The actual money moves between accounts. The accounting entries on each entity's books reflect the actual cash movement.

The documentation each transfer needs

Every intercompany transfer should be supported by:

• A reference to the underlying agreement (Management Services Agreement for PC-to-MSO; cost-sharing agreement for PC-to-PC).
• The date the payment was made.
• The amount and the formula or basis it was calculated from (percentage of revenue, flat fee, cost-plus, etc.).
• The source account (entity, account number) and the destination account.
• A line item on each entity's general ledger reflecting the transfer.

That's the audit-defense package. If a regulator asks "why did $40,000 flow from PC-3 to the MSO on March 15," you should be able to answer with the agreement clause, the calculation, and the GL entries from both entities, in under five minutes.

Common intercompany flow patterns

Three patterns cover most groups:

Percentage-of-collections management fee

The PC pays a fixed percentage of its collected revenue (typically 8 to 18 percent) to the MSO each month. Easy to calculate, easy to defend, and adjusts naturally to PC-level revenue swings.

Cost-plus management fee

The MSO bills the PC for documented expenses incurred on the PC's behalf (admin staff time, rent allocation, software licenses) plus a fixed margin (typically 5 to 15 percent). More accurate than percentage-of-collections but requires more documentation per cycle.

Hybrid (fixed + variable)

A flat monthly base fee plus a smaller percentage of collections. Used when the MSO incurs significant fixed overhead that doesn't scale with PC revenue, but still wants some upside as the PC grows.

Whichever pattern you use, the management services agreement should spell out the formula clearly. Banks and auditors need to verify each transfer against the formula.

Frequency: Monthly, quarterly, or real-time?

Most MSO-PC groups settle management fees monthly. The cadence balances three concerns:

• Operational simplicity. Monthly aligns with billing cycles and payroll runs.
• Cash flow management. Monthly transfers smooth MSO cash flow without leaving the PC starved between payments.
• Audit clarity. Monthly intervals leave a clean trail per period.

Quarterly works for smaller groups where management fee amounts are modest and the audit overhead is the main concern. Real-time (sweep on every PC deposit) works for large groups using healthcare-native banking with automated MSA-aligned sweep rules. Real-time is most defensible only when each transfer can still tie back to the MSA formula.

How to automate without losing the audit trail

Automation is the difference between a CFO spending half a week on intercompany flows and the CFO spending half an hour reviewing exceptions. Three capabilities matter:

• Rule-based sweeps, following the sweep rule patterns that implement MSA terms automatically (opens in a new tab). The bank can run "transfer X percent of yesterday's deposits from each PC to the MSO each night" or similar rules that reflect MSA terms.
• Per-transfer reference fields. Every automated transfer should carry a memo or reference indicating the MSA clause and calculation basis.
• Immutable transfer logs. The bank exports a per-period log of every intercompany transfer with timestamps, amounts, source, destination, and reference, exportable for accounting and audit defense.

Generic business banks rarely support rule-based intercompany sweeps. Healthcare-native banks built for intercompany automation (opens in a new tab) do. The result is intercompany flows that match the MSA exactly, every cycle, without manual ACH entry.

Tax treatment of intercompany transfers

Intercompany transfers have specific tax implications. Talk to your CPA, but the broad strokes:

• Management fees paid by PC to MSO are deductible business expenses for the PC and taxable income to the MSO.
• Reasonable transfer pricing matters. The IRS pays attention to whether the management fee reflects fair market value for the services rendered. Inflated management fees that effectively shift profit to the MSO can be challenged.
• State tax nexus may apply if the MSO and PC are in different states. Some states have specific rules on management services agreements with out-of-state MSOs.
• Documentation supports the tax position. The MSA and intercompany transfer logs are your defense if the management fee is challenged.

This is one of the areas where MSO-PC groups most often need professional help. A healthcare-savvy CPA review every 1 to 2 years catches drift before it becomes a tax problem.

Common mistakes that trigger audit findings

• Untimed or irregular transfers. Management fees that flow whenever the bookkeeper remembers, instead of on a documented monthly schedule, suggest discretionary movement and look like commingling.
• Round-number transfers without a calculation basis. A flat $50,000 monthly management fee with no documentation of how that number was derived is harder to defend than a percentage-of-collections transfer.
• Reverse-direction flows. The MSO transferring money into a PC account, except for documented cost reimbursement, blurs the entity boundary.
• Transfers that don't tie to MSA terms. If the MSA says 12 percent of collections and the actual transfer is 18 percent, that mismatch is a finding.
• Missing GL entries on one side. Each transfer must appear on both the source and destination entity's books.

A sample setup for a 5-PC group

Concrete example. The MSA defines a 14 percent management fee. Each PC's monthly intercompany flow:

1. Day 1 of each month: pull total PC collections for the prior month from the bank report.
2. Calculate 14 percent.
3. Initiate ACH transfer from the PC's operating account to the MSO's operating account, with memo: "MSA management fee, [month-year], 14 percent of collections, $X."
4. Post the transfer to the PC's books as a management fee expense, and to the MSO's books as management fee income.
5. Reconcile both sides at month-end close.

Multiplied across 5 PCs and automated via sweep rules at a healthcare-native bank, the entire process is 15 to 20 minutes of CFO review per month instead of half a day.

What Lemma handles, and what it does not

Lemma's automated sweep rules support MSA-defined intercompany flows: percentage-of-collections, fixed-amount, hybrid. Each transfer carries a memo with the rule reference for audit defense. The consolidated dashboard shows every intercompany transfer across the structure in one view.

Lemma does not write your MSA, set the management fee percentage, or replace your CPA's tax review. It executes intercompany flows according to whatever rule you and your advisors have already defined.

How sister-PC transfers work

Less common but worth understanding, and distinct from whether pooling funds across PCs is ever compliant (opens in a new tab) in the general case. When two PCs in the same group share a clinician, equipment, or admin staff, the cost has to be allocated cleanly to avoid one PC effectively subsidizing another.

The standard pattern:

1. Sign a cost-sharing agreement between the two PCs (separate from the MSA), specifying what's shared, how cost is allocated, and on what schedule.
2. The PC bearing the cost (the "host" PC) pays the vendor or staffer in the normal course.
3. The host PC invoices the sister PC for its share each month.
4. The sister PC pays via ACH with a memo referencing the cost-sharing agreement.
5. Both PCs record the transaction on their books.

Done this way, sister-PC transfers do not violate CPOM (because the funds are exchanged for documented services or shared resources, not pooled). They do create extra paperwork. Most groups minimize sister-PC transfers by routing shared resources through the MSO instead, which has cleaner audit defense.

What to review each year

Intercompany flows drift over time as the practice grows, payer mix changes, and clinician headcount shifts. An annual review catches drift before it becomes a problem:

• Compare actual management fee transfers to MSA-defined formula. Material variance triggers a recalculation.
• Review fair-market-value of management services with the CPA. If admin staff costs have risen meaningfully, the management fee may need a documented adjustment.
• Confirm the MSA still reflects the actual services the MSO provides. If the MSO has added or dropped services since the MSA was signed, amend it.
• Reconcile sister-PC transfers against cost-sharing agreements. Same drift risk applies.

Cost: typically 2 to 4 hours of CFO time plus a CPA review. Cost of skipping: a finding in any audit that touches the prior 3 to 5 years.

One last note. Practices considering a sale or restructure should clean up intercompany flow documentation 12 to 24 months in advance. Buyers and their counsel scrutinize this area heavily, and unclear flows depress valuation or trigger holdbacks. The cleanup work is the same regardless of timing, but doing it under deal pressure is much more expensive than doing it as part of normal operations.