Medical Billing Software for Billing Companies Managing 50 or More Practices

Medical Billing Software for Billing Companies Managing 50+ Practices

Short answer

A billing company that manages fifty or more client practices is not a bigger version of a ten-practice billing company. It is a fundamentally different operating entity: formal management layers, multiple specialties under one roof, a likely history of acquisitions or roll-up growth, compliance obligations that enterprise health systems also face, and software procurement decisions that go through stakeholders with different priorities than a founder-owner who also works denials every morning. Most of the vendor comparisons online are written for smaller billing services — ten practices, twenty providers, one owner making every decision. They don't apply well at this scale.

This page is specifically for billing companies managing fifty or more client practices: what this scale actually looks like operationally, which software needs are genuinely different from smaller operators, where Medi fits (and where it honestly does not yet), and how to think about enterprise RCM platforms like Waystar when you are evaluating the full landscape. The short answer is that for some organizations in this segment, Medi is the right operating layer. For others, especially those with large health system clients, complex regulatory requirements, or deep integration demands, an enterprise platform may be the better answer. This page tries to be direct about which situation is which.

---

What a 50-plus practice billing company looks like operationally

A fifty-plus practice billing company is running, at minimum, several hundred providers' worth of revenue cycle work. That almost always means the organization has crossed from owner-operated into genuinely managed — department heads or directors over posting, denials, enrollment, compliance, and account management. The founder may still be involved in sales or culture, but the day-to-day billing decisions are distributed across a leadership layer.

Staff count. The HBMA membership data shows that while most member firms are small to mid-sized (5-100 employees), the association also includes some of the nation's largest billing companies with over 1,000 employees submitting millions of claims. A fifty-practice billing company typically has 75 to 300 staff depending on specialty complexity, offshore leverage, and automation maturity. A hundred-practice firm may have 250 to 600 or more.

Specialty complexity. At this size, the book is rarely homogeneous. A firm managing fifty or more practices almost certainly spans at least three or four specialties — primary care, a few hospital-based groups, some behavioral health, possibly orthopedics or cardiology. Each specialty has its own authorization patterns, payer quirks, denial topography, and coding conventions. That heterogeneity means the denial queue a specialist works looks different than the queue at a twenty-practice shop that only does family medicine.

Ownership structure. The private equity consolidation wave in RCM has accelerated over the past several years. VERTESS reports the sector is experiencing record M&A activity, with PE firms pursuing aggressive buy-and-build strategies — acquiring smaller billing companies and rolling them into platforms. The $8.9 billion take-private of R1 RCM by Clayton, Dubilier & Rice and TowerBrook Capital Partners is the highest-profile example, but the pattern extends well down-market. A billing company managing fifty-plus practices may itself be a PE-backed roll-up, with practices that arrived on different software stacks, different clearinghouses, and different payer enrollment histories. That acquisition history creates real software integration complexity: you are not starting from a clean slate, you are reconciling systems that were never designed to talk to each other.

Governance and compliance requirements. Organizations at this size typically face formal procurement processes, information security reviews, BAA audits, and sometimes client-imposed compliance requirements. A large health system client that represents 15 percent of your book may require vendor attestations you have not previously needed. A PE sponsor may require a SOC 2 Type II audit as part of portfolio hygiene. State Medicaid programs or federal contracts may carry their own overlay requirements. The compliance surface at fifty-plus practices is not the same as at five.

Reporting obligations. A billing company owner managing five practices can look at a dashboard and intuit what is happening. Managing fifty-plus, reports become operational. AR aging across the full book, collections by practice versus target, denial rate trends by specialty, payer settlement patterns — these have to be formally generated, reviewed, and acted on. Account managers need practice-level views they can share with clients. Operations leadership needs cross-book views they can use to staff queues and flag at-risk relationships.

---

The honest question at enterprise scale: is Medi the right fit?

Most billing-company content is written to close a sale. This section is written to help you not make an expensive mistake.

At fifty-plus practices, the software decision is no longer primarily about per-provider pricing math or which product has the cleanest denial queue UI. It is about whether the vendor's product, compliance posture, support model, and integration capability can hold up at the complexity level your organization actually operates.

Here is the honest situation: Medi is the right answer for some organizations at this scale, and not the right answer for others. The difference depends on three things.

Who your clients are. If your fifty-plus practice book is primarily independent physician practices — primary care, specialty groups, behavioral health, smaller orthopedics practices — Medi is designed for that operating context. The billing company is the workspace, each practice is a scoped tenant, cross-practice work queues work the way your team is organized. If your book includes large health systems, academic medical centers, or hospital outpatient departments with complex inpatient and outpatient billing needs, those clients may need capabilities — clinical documentation improvement, patient access automation, DRG validation — that Medi does not include and is not designed to include.

What your integration requirements are. Medi is a billing-company operating layer. It does not currently publish a public API, and does not support custom EHR integrations, HL7 feeds, or proprietary clearinghouse connections outside of the Stedi network. For a billing company that has grown through acquisition and arrived with four different EHR stacks, two legacy clearinghouse relationships, and a custom-built data warehouse, Medi's integration surface may be too limited. Enterprise platforms like Waystar and athenaIDX are designed with enterprise integration depth in mind. Medi is not.

What your compliance posture is. Medi is HIPAA-compliant and executes BAAs before any PHI workflow goes live. What Medi does not yet have: SOC 2 Type II certification, HITRUST certification, or published enterprise SLAs with contractual uptime commitments. For a smaller billing company, those may not be procurement blockers. For an organization whose largest clients are sophisticated health systems with procurement departments and vendor security questionnaires, the absence of SOC 2 Type II may be a disqualifying gap. That is not a criticism — it is a structural reality about where Medi is in its maturity cycle.

If any of those three points describes your situation, read the next two sections carefully.

---

Where Medi works at this scale

For billing companies managing fifty-plus practices that are primarily independent physician practices and smaller specialty groups, Medi's structure holds up in ways that practice-centric systems do not.

Flat pricing that does not punish growth. At fifty or more providers across many practices, per-provider pricing becomes the dominant cost line. Tebra at $99 per provider per month across two hundred providers is $19,800 per month before onboarding, AI add-ons, or usage fees. Medi's platform fee is $300 per month flat — providers and practices are unlimited under that fee. EDI usage runs on top, typically $1,300 to $1,700 per month at the claim and ERA volumes a fifty-practice book generates, for a total in the range of $1,600 to $2,000 per month. The pricing structure means adding ten practices next quarter does not trigger a repricing conversation. See Medi pricing for current rates.

Billing-company-first architecture that does not degrade at scale. The tenant model matters more at fifty practices than it does at five. Medi treats the billing company as the workspace and each practice as a scoped tenant inside it. A denial specialist can work every practice's outstanding denials from a single queue without context-switching. A poster can process ERAs from multiple practices in one session. Practice-scoped permissions mean an offshore team member can be restricted to the specific practices they are assigned without separate login instances. That architecture does not change as you add practices.

Cross-practice reporting that is not bolted on. The reporting layer covers the full book — AR aging by practice, collections against targets, denial rates by payer and specialty, ERA exception patterns — with drill-down to the claim level. At fifty-plus practices, a manager who has to open each practice separately to assemble a book-level view is spending time on a problem the software should solve.

Denial and recovery queues that reflect how your team is organized. Billing companies at this scale are typically organized by function — posting teams, denial specialists, follow-up coordinators, appeal leads — not by practice. Medi's queue structure is designed for that functional model. A denial specialist who owns all behavioral health denials across the book works one queue, not fifty.

Migration and legacy AR handling for acquisition-driven growth. If your fifty-practice book arrived partially through acquisition, Medi's migration approach — legacy AR closeout in the prior system, parallel posting runs for two weeks, practice-by-practice rollout — is designed for exactly that scenario. The multi-practice billing company operations guide documents how that rollout pattern works in practice.

---

Where Medi is not yet the right fit at enterprise scale

This section is direct because the alternative — glossing over gaps and letting you discover them in a procurement conversation — wastes everyone's time.

No SOC 2 Type II certification yet. Medi is pursuing SOC 2 Type II but has not completed the audit cycle. For billing companies whose clients include health systems, large physician groups, or federally-qualified health centers with formal vendor security requirements, this is a real procurement obstacle. Many enterprise clients require SOC 2 Type II or HITRUST as a minimum vendor qualification. If your organization is in that situation, document this gap explicitly in any vendor evaluation.

No HITRUST certification yet. HITRUST certification consolidates HIPAA, NIST, ISO 27001, and PCI DSS requirements into a single audit framework and is increasingly required by large payers and hospital systems as a vendor condition. Medi does not hold HITRUST certification. For enterprise billing companies whose book includes hospital clients with HITRUST vendor requirements, this is a binary compatibility issue.

No published enterprise SLAs. Medi does not publish contractual uptime SLAs. For a PE-backed billing company with portfolio reporting obligations, or a billing company that has contractual service-level commitments to its own clients, the absence of an externally-published SLA with remedies may not fit the procurement framework.

No public API or custom integration layer. If your organization needs to connect Medi to a proprietary data warehouse, a custom analytics platform, a legacy clearinghouse relationship, or an EHR via HL7 feeds, Medi does not currently support those integrations. Enterprise RCM platforms like Waystar and athenaIDX are built with enterprise integration teams in mind. Medi is not at that point.

No enterprise support tier. Medi's current support model is not structured around dedicated account teams, SLA-backed response times, or enterprise escalation paths. A billing company managing fifty-plus practices that requires named account management and contractual support commitments should clarify the current support structure directly before signing.

Clinical documentation integrity is not in scope. If any of your client practices are hospital outpatient departments or involve complex inpatient billing, CDI is likely part of the revenue cycle workflow. Medi does not include CDI, DRG validation, or clinical documentation improvement capabilities. Waystar and athenahealth do.

---

What software needs to do at this scale

Regardless of which platform you choose, a billing company managing fifty or more practices needs software to do things that are categorically different from what a five-practice shop needs.

Multi-level permission architecture. The permission model has to support billing-company administrators, practice-level account managers, functional specialists with cross-practice access, offshore staff with restricted scope, and client-facing users with read-only access to their own practice data. Single-tier permissions or practice-by-practice instance models do not work at this scale.

Cross-practice analytics with client-grade output. Reports have to work in two directions: inward-facing for operations (where are my worst-performing payers across the book, which practices are above 90-day aging threshold) and outward-facing for client relationships (here is your practice's monthly performance summary). Systems that produce only one type of reporting leave a gap that gets filled with manual spreadsheet work.

Enrollment management at portfolio scale. A fifty-practice billing company may have several hundred active payer enrollment relationships across EDI, ERA, and EFT. Tracking renewal dates, managing trading partner agreements across clearinghouses, and onboarding new practices' enrollment without losing ERA flow is a genuine operational discipline. Software that treats enrollment as an afterthought creates recurring onboarding delays.

Audit logging with appropriate retention and scope. At this scale, PHI access logging is not just a compliance checkbox — it is a management tool. Who accessed which records, when, and under what permission is operationally relevant when you have offshore staff, multiple client practices, and a security incident response obligation. HIPAA Security Rule §164.312(b) requires audit controls; enterprise clients may require six or seven years of retention and on-demand export.

Reliable ERA exception handling at volume. A fifty-practice billing company may receive hundreds of ERA files a day. The exception workflow — held lines, PLB segments, recoupments, write-off tolerance decisions, posting variances — has to be efficient at that volume. A system that requires manual review of every exception line at high volume is not a workflow problem, it is a staffing problem.

Custom payer behavior and client billing rules without collisions. Practice-level billing rules (specific payer fee schedules, write-off policies, modifier handling) have to layer cleanly on top of system-wide defaults without creating conflicts that a biller has to manually adjudicate. At fifty practices, the combinatorial space is large enough that bad rule architecture shows up as recurring error patterns.

---

The Waystar question: when enterprise RCM is the right answer

Waystar is mentioned in this page because it is the platform most commonly referenced when a large billing company is trying to understand whether it has grown past what a billing-company-first platform can support.

The honest answer, drawn from the Medi vs Waystar comparison: Waystar is built for health systems, hospitals, integrated delivery networks, and enterprise RCM operations that process hundreds of thousands of claims annually and want a single vendor relationship spanning CDI, prior authorization, patient financial access, AI-powered denial prevention, and autonomous workflow agents. As of Waystar's Spring 2026 showcase, its AltitudeAI layer has prevented $15.5 billion in denials and reduced denial appeal time by 90 percent for enterprise clients. These are genuinely impressive numbers that reflect what the platform is designed to do at hospital scale.

For an independent billing company managing fifty-plus practices whose clients are primarily independent physician practices, Waystar is almost always the wrong product. The pricing structure ($200,000 to $1,000,000 or more annually for enterprise health system agreements), the implementation timeline (measured in months), the product surface (CDI, DRG validation, autonomous AI agents), and the procurement model (custom-quoted, no published tiers) are all built for health system buyers, not billing services.

The scenarios where Waystar genuinely comes up for a billing company:

• A billing company's largest client is a health system that already uses Waystar and is asking the billing company to connect into its Waystar instance. In this case, the billing company is not replacing its own platform with Waystar — it is figuring out how to hand claims off to a client's enterprise system.
• A PE-backed billing company has grown through acquisition into a territory where some clients are large physician groups or hospital outpatient departments. The question is not whether Waystar is better than Medi — it is whether the acquired entity's clients need capabilities that only a health-system platform provides.
• A billing company is itself being positioned for acquisition by a health system or a large RCM services firm that uses Waystar. In this case, platform alignment is a transaction-level conversation, not a software evaluation.

For everything else — independent physician practices, specialty groups, behavioral health, DME, smaller orthopedics and cardiology groups — Waystar's enterprise overhead is unlikely to produce a better daily billing experience than a billing-company-first platform. The KLAS Research database is the best external source for validated buyer feedback on how enterprise RCM platforms perform in real-world deployments.

---

What should a 50-plus practice billing company verify in software?

The evaluation questions for a large billing company are different from the questions a smaller one asks. Prioritize these.

---

Frequently asked questions

Is Medi designed for billing companies this large?

Medi's architecture — billing company as workspace, practices as scoped tenants, flat platform pricing, cross-practice queues — works at fifty-plus practices for the right kind of book. The structure does not break at scale the way per-provider pricing or single-tenant models do. What changes is the compliance and integration surface: if your client base requires SOC 2 Type II, HITRUST, or enterprise SLAs, Medi does not currently meet those requirements. That is a real constraint for some organizations at this scale and not a meaningful constraint for others.

What compliance certifications should we require from any vendor at this scale?

At minimum, confirm that the vendor executes a BAA before any PHI is handled and holds current HIPAA compliance. Beyond that, the certifications that matter most in enterprise billing company procurement are SOC 2 Type II (which covers security, availability, processing integrity, confidentiality, and privacy through an independent third-party audit over a 6-12 month observation period) and HITRUST (which consolidates HIPAA, NIST, ISO 27001, and PCI DSS requirements into a unified audit framework). Large payers and hospital clients increasingly require both. The Jorie AI compliance framework overview is a useful primer on what each certification covers. Medi holds HIPAA compliance and BAA coverage but does not yet hold SOC 2 Type II or HITRUST.

How does private equity ownership affect software evaluation at this scale?

It adds evaluation criteria that owner-operated billing companies do not have. A PE sponsor will typically require formal vendor security reviews, contractual uptime commitments, integration with portfolio reporting infrastructure, and sometimes specific certifications like SOC 2 Type II as portfolio hygiene. If the billing company has been acquired or is positioning for acquisition, the acquiring entity's software stack preferences and vendor requirements may override an operational preference. The M&A consolidation in RCM — nearly half of healthcare IT transactions in 2024 involved PE buyers per Capstone Partners — means this is not an edge case. It is a mainstream procurement context.

When should a large billing company consider building its own software?

The Retool 2026 Build vs. Buy Report found that 35 percent of enterprises have replaced at least some SaaS with custom software. For RCM specifically, custom development starts making sense when proprietary payer relationships, specialty-specific claim logic, or acquired-system integration demands exceed what commercial platforms support, and when the organization has the engineering capacity to sustain a custom codebase. The threshold is high: custom billing software typically costs $50,000 to $300,000 to build initially, plus ongoing engineering overhead. Most billing companies at fifty-plus practices are better served buying a commercial platform and investing in configuring it well than building from scratch — but the calculus shifts as you approach health-system scale.

What does Waystar actually cost for a billing company at this scale?

Waystar does not publish pricing. Enterprise health system agreements commonly fall in the $200,000 to $1,000,000 or more per year range, with implementation and EHR integration fees layered on top. The pricing is custom-quoted and requires a sales engagement. Third-party review aggregators put the low end at roughly $11,000 per year for smaller organizations. For a billing company rather than a hospital, the relevant question is whether Waystar's enterprise modules — CDI, prior authorization, AltitudeAI agentic workflow — will actually be used, or whether the billing company would be paying for an enterprise platform to use a subset of its clearinghouse and claim submission capabilities. See the Medi vs. Waystar comparison for the full structural breakdown.

How does specialty mix affect the software decision at fifty-plus practices?

Significantly. A billing company where 80 percent of the book is primary care and behavioral health has straightforward specialty requirements. The same company that picks up ten orthopedics groups and three cardiology practices through acquisition now has procedure-level complexity, multiple fee schedules with contractual adjustment logic, authorization workflows tied to imaging and surgical scheduling, and denial patterns that are completely different from primary care. No software platform excels at every specialty equally. KLAS Research is the best external source for specialty-specific performance data on enterprise RCM platforms. For smaller independent specialty groups, Medi's workflow handles the billing-company operating layer regardless of specialty, though complex facility-side billing (UB-04, inpatient grouping, DRG) is outside its current scope.

Is there a billing company size at which the Medi vs. enterprise decision becomes clear?

Roughly, yes. Billing companies managing primarily independent physician practices — even at one hundred or more practices — are usually better served by a billing-company-first platform than by enterprise health-system software. The inflection point is not practice count; it is client type. When a meaningful portion of the book (say, 20 percent or more of revenue) comes from clients who are health systems, hospital outpatient departments, or federally-qualified health centers with enterprise procurement requirements, the compliance and integration demands shift materially. At that point, the conversation becomes whether one platform can serve the full book or whether the book should be managed in two operating layers. That is a real strategic question, and there is no one-size answer. Talking to a revenue cycle advisory firm like VERTESS or a specialized M&A advisor with RCM experience is often worth the time before a platform decision of that scale.

How current is this page?

Last reviewed 2026-05-18. The RCM M&A market, compliance requirements, and vendor capabilities in this segment change quickly. The primary external sources for current information on enterprise RCM are KLAS Research, HBMA, MGMA, and VERTESS for M&A context. Vendor-specific positioning for Waystar and Medi should be verified directly with each vendor before any procurement decision.

---

*Related reading: Billing company software evaluation guide — Multi-practice billing company operations — Medi vs. Waystar — Medi vs. Tebra — Security and compliance at Medi — Billing company operations — Pricing — Request a demo*