The MSA economics that define MSO operations
A management services organization is paid by physician practices to deliver back-office services: billing, scheduling, HR, finance, technology, real estate, vendor management. The management services agreement defines the fee structure. Some MSAs charge a fixed monthly fee. Some charge a percent of collections. Many use a hybrid that combines fixed components with variable components and performance triggers.
The MSO has to bill those fees across every practice subsidiary, consolidate financials at the parent level, eliminate intercompany activity at consolidation, and report to investors and partners on platform-level performance with practice-level visibility. Organizations spanning multi-payer billing, grant compliance, and operational complexity outgrow entry-level systems quickly.
The work below is the configuration that handles MSA billing, intercompany elimination, and consolidated reporting in NetSuite OneWorld. NetSuite's multi-entity framework supports the structure natively when configured for the operating model.
An MSO's reporting requirements look simple from the outside. Per-practice P and L, consolidated platform reporting, intercompany elimination. The complexity is in running all three on one system without spreadsheet support.
Step 01: Subsidiary structure and chart of accounts
Each practice is a subsidiary in NetSuite OneWorld. The MSO entity sits as a parent. A common chart of accounts runs across all subsidiaries with location and department dimensions providing the practice-level granularity for reporting.
Key configuration decisions:
- Subsidiary per practice rather than class or location. Subsidiaries support full P and L, balance sheet, and cash flow at the entity level, which investors and partners typically require.
- Intercompany consolidation enabled at the parent. Elimination accounts created for management fees, shared services, and intercompany transfers.
- Currency: single currency for US-only MSOs. Multi-currency for MSOs operating internationally, with foreign currency translation running on the close calendar.
- Fiscal calendar aligned across all subsidiaries. Practice acquisitions inherit the platform calendar at integration, not the legacy practice calendar.
Step 02: MSA fee structure as a configured object
The MSA terms live in Contract Lifecycle Management, not in a static fee schedule. Each practice has an MSA record with effective-dated terms. The structure supports the common fee patterns:
Fixed monthly fee
A flat amount per month, regardless of practice performance. Posts on a defined schedule (typically the first of the month) as an intercompany invoice from the MSO to the practice.
Percentage of collections
A percent of cash collected by the practice during the period. Posts at period close after collections are reconciled. Calculation runs against the practice's revenue accounts with the rate stored on the MSA record.
Tiered structure
Different rates at different collection levels. Example: 6 percent of the first 1 million in monthly collections, 5 percent on the next 1 million, 4 percent thereafter. NetSuite saved searches and SuiteScript calculations apply the tiers correctly.
Waterfall with performance components
A base fee plus a performance fee triggered by specific metrics (collection days, denial rate, new patient growth). Performance triggers are evaluated at period close. The performance fee posts as a separate intercompany invoice.
Pass-through expenses
Some MSAs include pass-through reimbursement for specific costs (technology, real estate). These post separately from the management fee, with full documentation for audit purposes.
Step 03: The intercompany transaction pattern
Every management fee posts as a pair of transactions: an invoice at the MSO and a bill at the practice. NetSuite OneWorld supports this with intercompany journal automation.
| StepMSO entityPractice subsidiary | ||
|---|---|---|
| Fee calculation | Calculate management fee based on MSA terms | Practice revenue posted, available for fee calculation |
| Invoice generation | Intercompany invoice from MSO to practice | Intercompany bill from MSO posts automatically |
| Approval | Approvals App routes for review | Auto-approves on MSO invoice approval |
| Payment | Cash settlement or intercompany loan accrual | Cash settlement or intercompany loan accrual |
| Consolidation | Revenue recognized | Expense recognized |
| Elimination | Revenue eliminated against expense | Expense eliminated against revenue |
At the consolidated level, the management fee disappears. It exists in subsidiary-level reporting for practice-specific P and L. It does not double-count in platform reporting.
Step 04: Practice-level reporting and drill-down
Per-practice P and L runs natively in NetSuite OneWorld. Each practice subsidiary has its own complete financial statements. Aggregation rolls up to platform reporting. Drill-down goes the other direction: from platform total to practice to provider to transaction.
Provider-level reporting underneath the practice uses class or department dimensions. Production by provider, by service line, by location is queryable from transaction-level data. This is the operational reporting that DSO and physician practice operating leaders manage to.
Step 05: Acquisition integration playbook
MSOs grow by acquisition. Each acquired practice has its own historical books, billing system, and reporting cadence. The integration timeline determines how quickly the practice contributes to platform performance reporting.
Archer's 60 to 90 day acquisition integration playbook:
- Days 1-15: Chart of accounts mapping. Practice management system integration plan. Opening balance reconciliation.
- Days 16-45: Subsidiary setup. Historical data migration for trailing periods. MSA terms loaded into Contract Lifecycle Management. Vendor Onboarding consolidates the supplier base. Invoice OCR Capture automates AP onboarding.
- Days 46-60: Parallel run with legacy system. Validation of reporting. User training.
- Days 61-90: Cutover. First close on NetSuite. Platform reporting includes the acquired practice.
The playbook is repeatable. Each acquisition follows the same pattern. The integration timeline is predictable, not improvised.
Step 06: SOX readiness for sponsor-backed MSOs
Sponsor-backed MSOs operate under SOX requirements. Segregation of duties, access controls, and audit trail capabilities have to be baked into the ERP. Archer's Approvals App for SOX-ready workflows handles the approval routing with the audit trail SOX requires. Role definitions align to the control framework. SOX testing runs against system reports, not against custom queries.
What the configured MSO close looks like
With the configuration in place, month-end runs on the platform. Practice revenue closes by mid-month. Management fees calculate and post automatically. Approvals route and clear. Intercompany eliminates at consolidation. Platform P and L is available on day 5. Practice-level P and L is available the same day. Investor reporting runs from the same data.
Without the configuration, the close runs on spreadsheets. Management fees are calculated in Excel. Intercompany journals are manual. Practice-level P and L requires reconstruction. The investor report arrives late and contains errors.
Related on archerinsights.com
- Healthcare services industry page. Multi-payer billing, grant compliance, and operational complexity.
- NetSuite for MSOs hub. Foundation configuration for MSO operations.
- NetSuite for dental DSOs hub. Adjacent multi-location healthcare operating model.
- Hospitals and physician clinics industry page. EHR to NetSuite data flow.
- Contract Lifecycle Management module. MSA terms, amendments, and renewal cycles.
- Approvals App for SOX-ready workflows. Multi-entity approval routing and audit trail.