The MSA economics problem
A management services organization is paid by physician practices to deliver back-office services: billing, scheduling, HR, finance, technology, real estate. The management services agreement defines the structure. Some MSAs charge a fixed fee. Some charge a percent of collections. Many use a waterfall that combines both. The MSO has to bill across dozens or hundreds of practices, consolidate financials at the parent level, eliminate intercompany activity, and report to investors and partners on platform performance.
As Archer's healthcare services industry page describes, organizations spanning multi-payer billing, grant compliance, and operational complexity outgrow entry-level systems quickly. NetSuite, configured for MSO operations, handles the MSA structure, the intercompany billing, the consolidation, and the practice-level performance reporting on a single platform.
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.
Why generic ERP fails MSO operators
MSA fee calculation
Management fee waterfalls combine fixed components, percentage components, performance components, and tiered structures. Generic ERP billing modules do not support this without significant configuration.
Practice-level visibility
MSO investors and partners want practice-level P and L visibility. Consolidation logic has to support both rolled-up reporting and drill-down to the practice without rebuilding.
Intercompany elimination
Management fees, shared services, and intercompany transfers between the MSO and the practices require systematic elimination at consolidation, not manual journals.
Acquisition integration
MSOs grow by acquisition. Each acquired practice arrives with its own chart of accounts, billing system, and reporting cadence. The integration timeline has to be predictable, not improvised.
How Archer configures NetSuite for MSOs
MSA fee calculation is configured as automated transactions against practice subsidiaries. Fixed fees post on schedule. Percentage fees calculate against actual practice revenue. Waterfall and tier logic runs in the calculation, not in spreadsheets. Contract Lifecycle Management manages the MSA terms, amendments, and renewal cycles.
Practice-level reporting runs natively in NetSuite OneWorld. Each practice is a subsidiary or class, with full P and L, balance sheet, and cash flow visibility. Consolidation runs on the close calendar.
Intercompany elimination is automated. Management fees post against the MSO and against the practice, with elimination entries generated at consolidation. The audit trail is preserved.
Acquisition integration follows a defined playbook. Invoice OCR Capture automates AP onboarding for the acquired practice. Vendor Onboarding consolidates the supplier base. Chart of accounts mapping, opening balance migration, and operational cutover follow a 60 to 90 day timeline that Archer has run repeatedly.
Related on archerinsights.com
- Healthcare services industry page. Multi-payer billing, grant compliance, and operational complexity for healthcare services organizations.
- Hospitals and physician clinics industry page. Adjacent operating model for affiliated practice networks.
- Physicians clinics industry page. Independent practice operating model and EHR-to-NetSuite data flow.
- Medical specialists industry page. Specialty practice revenue cycle and billing complexity.
- Contract Lifecycle Management module. MSA terms, amendments, and renewal tracking.
- Approvals App for SOX-ready workflows. Multi-entity approval routing for sponsor-backed MSOs.
External references
- NetSuite OneWorld global business management
- NetSuite Life Sciences ERP
- CMS Medicaid Program Resources
- ASC 606 Revenue Recognition Standard
Run management fee accounting and consolidation without spreadsheet support
A discovery call with an Archer implementation lead. Bring your MSA structure and growth plan, and leave with a configuration approach that supports both.