Medical Billing Software for Billing Companies Managing 50+ Practices

Short answer

At fifty-plus client practices, the software question changes from "which denial queue is cleanest" to "can this vendor hold up at our complexity and compliance level." A book this size is managed, not owner-operated: directors over posting, denials, and enrollment; three or four specialties; often acquisition-driven growth with mismatched legacy stacks; and procurement that runs through security reviews and BAA audits.

Medi is the right operating layer for a fifty-plus book made of independent physician practices and specialty groups: the billing company is the workspace, each practice is a scoped tenant, and per-practice pricing is $20 per client practice per month with volume pricing available. It is not the right answer if a meaningful share of your book is health systems or hospital outpatient departments that require SOC 2 Type II, HITRUST, enterprise SLAs, or HL7 and custom-API integration. For those clients, an enterprise platform like Waystar is built for the job. The inflection point is client type, not practice count.

---

What a 50-plus practice book looks like operationally

A fifty-plus practice billing company runs several hundred providers' worth of revenue cycle work, which puts it past owner-operated and into a managed leadership layer.

**Staffing.** Expect 75 to 300 staff depending on specialty mix, offshore leverage, and automation maturity; a hundred-practice firm may run 250 to 600. HBMA membership spans 5-person shops to firms over 1,000 employees submitting millions of claims a year.

**Specialty mix.** The book is rarely homogeneous. Fifty-plus practices almost always spans three or four specialties, each with its own authorization patterns, payer quirks, and denial topography. A specialist's denial queue here looks nothing like a family-medicine-only shop's.

**Ownership.** Private-equity roll-ups are now mainstream in RCM. VERTESS reports record M&A, and the $8.9 billion take-private of R1 RCM set the high-water mark, but the buy-and-build pattern runs well down-market. A fifty-plus book may itself be a roll-up of practices that arrived on different software, clearinghouses, and enrollment histories. You are reconciling systems that were never built to talk to each other.

**Compliance surface.** Formal procurement, infosec reviews, BAA audits, and client-imposed requirements come with the territory. A health-system client that is 15 percent of your book may demand attestations you have never needed; a PE sponsor may require SOC 2 Type II as portfolio hygiene; federal and Medicaid contracts add their own overlays.

**Reporting.** At five practices an owner intuits the numbers. At fifty-plus, reporting is operational. AR aging across the full book, collections against target, denial trends by specialty, and payer settlement patterns have to be generated and acted on. Account managers need practice-level views to share with clients; leadership needs cross-book views to staff queues and flag at-risk accounts.

---

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

Most billing-company content is written to close a sale. This is written to keep you from an expensive mistake.

At fifty-plus practices the decision is no longer about per-provider math or queue UI. It is whether the vendor's product, compliance posture, support model, and integration capability hold up at your real complexity. Medi fits some organizations at this scale and not others, and it comes down to three things.

**Who your clients are.** If the book is primarily independent physician practices, specialty groups, and behavioral health, Medi is built for that context. If it includes large health systems, academic medical centers, or hospital outpatient departments, those clients may need clinical documentation improvement, patient-access automation, or DRG validation that Medi does not include and is not designed to.

**What your integration requirements are.** Medi is a billing-company operating layer. It does not publish a public API and does not support custom EHR integrations, HL7 feeds, or clearinghouse connections outside the Stedi network. If you have grown through acquisition into four EHR stacks, two legacy clearinghouses, and a custom data warehouse, Medi's integration surface may be too narrow.

**What your compliance posture is.** Medi is HIPAA-compliant and executes a BAA before any PHI workflow goes live. It does not yet hold SOC 2 Type II, HITRUST, or published contractual uptime SLAs. For a smaller shop those may not block procurement; for an organization whose largest clients run formal vendor security questionnaires, the SOC 2 Type II gap can be disqualifying.

If any of those describe you, read the next two sections carefully.

---

Where Medi works at this scale

For a fifty-plus book of independent physician practices and specialty groups, Medi's structure holds where practice-centric systems strain.

**Per-practice pricing, with volume pricing as the book grows.** At several hundred providers, per-provider pricing is the dominant cost line. Tebra charges $99 to $199 per provider per month for its billing-only tier (Billing Starter); fuller EHR bundles run $399 to $799. At $99 per provider, 200 providers is roughly $19,800 a month before onboarding, AI add-ons, or usage. Medi charges per client practice. Adding providers inside a practice never changes the platform fee; only adding practices does, with volume pricing available as you grow.

Medi charges $20 per client practice per month, with volume pricing available. EDI runs on top at published rates: $0.70 per claim (line-blind, ERA included, no separate 835 fee), stepping to $0.65 from 501 to 5,000 claims a month and $0.55 beyond 5,000; $0.25 per eligibility check; $0.20 per claim status check; and $1.50 per COB, discovery, or attachment transaction. 277CA files and posting PDFs are included. See Medi pricing.

**Migration with a cap that favors large books.** No contract is required. Migration is free with a 12-month commitment, or $100 per practice month-to-month, capped at $3,000 total. At scale the cap is the point: a 60-practice month-to-month migration costs the same $3,000 as a 100-practice one. Data export is always free, with no termination fee.

**Tenant model that does not degrade.** Medi treats the billing company as the workspace and each practice as a scoped tenant. A denial specialist works every practice's denials from one queue; a poster processes ERAs from several practices in one session; an offshore team member can be scoped to assigned practices without separate logins. That structure does not change as you add practices.

**Cross-practice reporting that is not bolted on.** The reporting layer covers the full book, with AR aging by practice, collections against target, denial rates by payer and specialty, and ERA exception patterns, drilling to the claim. A manager who opens fifty practices separately to build a book-level view is doing work the software should do.

**Queues organized the way your team is.** Billing companies at this scale are organized by function, not by practice. Work surfaces and routes by function across the book: denials, ERA exceptions, and follow-up land in the right specialist's queue regardless of which practice they came from, and items can be assigned to scoped staff without practice-switching.

**Acquisition-driven migration handling.** If the book arrived partly through acquisition, Medi's approach, legacy AR closeout in the prior system, two-week parallel posting, and practice-by-practice rollout, is built for that. The multi-practice billing company operations guide documents the rollout pattern.

---

Where Medi is not yet the right fit

• **No SOC 2 Type II yet.** Medi is pursuing it but has not completed the audit cycle. Health systems, large physician groups, and FQHCs with formal vendor security requirements often require SOC 2 Type II or HITRUST as a minimum. If that describes your clients, document the gap in any evaluation.
• **No HITRUST yet.** HITRUST folds HIPAA, NIST, ISO 27001, and PCI DSS into one framework and is increasingly required by large payers and hospital systems. Medi does not hold it. For a book with hospital clients that mandate HITRUST, this is a binary compatibility issue.
• **No published enterprise SLAs.** Medi does not publish contractual uptime SLAs with remedies. For a PE-backed firm with portfolio reporting obligations, or one carrying service-level commitments to its own clients, that may not fit the procurement framework.
• **No public API or custom integration layer.** Connecting Medi to a proprietary data warehouse, custom analytics, a legacy clearinghouse, or an EHR over HL7 is not supported today. Enterprise platforms like Waystar and athenaIDX are built for that; Medi is not there yet.
• **No enterprise support tier.** The support model is not structured around dedicated account teams, SLA-backed response times, or escalation paths. If you need named account management and contractual support commitments, clarify the current structure before signing.
• **Clinical documentation integrity is out of scope.** Hospital outpatient departments and complex inpatient billing usually involve CDI. Medi does not include CDI, DRG validation, or documentation improvement. Waystar and athenahealth do.

---

What software has to do at this scale

Whatever platform you choose, a fifty-plus book needs capabilities a five-practice shop does not.

**Multi-level permissions.** The model has to support billing-company admins, practice-level account managers, cross-practice functional specialists, scope-restricted offshore staff, and client-facing read-only users. Single-tier permissions or per-practice instances do not work here.

**Two-directional reporting.** Reports have to face inward for operations (worst payers across the book, practices above the 90-day aging threshold) and outward for clients (a practice's monthly performance summary). One-directional reporting leaves a gap that fills with manual spreadsheets.

**Enrollment at portfolio scale.** A fifty-plus book may carry several hundred active EDI, ERA, and EFT enrollments. Tracking renewals, managing trading-partner agreements across clearinghouses, and onboarding new practices without losing ERA flow is a real discipline. Software that treats enrollment as an afterthought creates recurring onboarding delays.

**Audit logging with real scope and retention.** PHI access logging is a management tool here, not a checkbox: who accessed which records, when, under what permission. HIPAA Security Rule §164.312(b) requires audit controls; enterprise clients may require six or seven years of retention and on-demand export.

**ERA exception handling at volume.** A fifty-plus book may receive hundreds of ERA files a day. Held lines, PLB segments, recoupments, write-off tolerance, and posting variances have to clear efficiently. A system that needs manual review of every exception line at volume turns a workflow problem into a staffing problem.

**Layered billing rules without collisions.** Practice-level rules (payer fee schedules, write-off policies, modifier handling) have to layer cleanly over system defaults. 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 here because it is the platform most often raised when a large billing company asks whether it has grown past what a billing-company-first product can support.

Drawn from the Medi vs Waystar comparison: Waystar is built for health systems, hospitals, and integrated delivery networks that process hundreds of thousands of claims a year and want one vendor spanning CDI, prior authorization, patient financial access, AI denial prevention, and autonomous workflow agents. Waystar does not publish pricing; enterprise health-system agreements commonly run $200,000 to $1,000,000 or more a year, with implementation measured in months. Those numbers reflect hospital-scale design, not a billing service's needs.

For an independent billing company whose clients are mostly independent practices, Waystar is almost always the wrong product. It genuinely comes up in three scenarios:

• Your largest client is a health system already on Waystar and wants you to connect into its instance. You are not replacing your platform; you are handing claims into the client's enterprise system.
• A PE-backed firm has acquired its way into large physician groups or hospital outpatient departments, and the question is whether those acquired clients need health-system capabilities Medi does not provide.
• The billing company is itself being positioned for acquisition by a health system or large RCM firm on Waystar. That is a transaction-level conversation, not a software evaluation.

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

---

What a 50-plus practice billing company should verify

The evaluation questions at this scale differ from a smaller shop's. Prioritize these.

---

Frequently asked questions

Is Medi designed for billing companies this large?

For the right kind of book, yes. The architecture, billing company as workspace, practices as scoped tenants, per-practice pricing that falls with volume, cross-practice queues, does not break the way per-provider pricing or single-tenant models do at scale. Medi charges per client practice, so adding providers inside a practice never changes the fee, and volume pricing is available as the book grows. What changes at this scale is the compliance and integration surface: if your clients require SOC 2 Type II, HITRUST, or enterprise SLAs, Medi does not meet those today. That is a real constraint for some organizations and a non-issue for others.

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

At minimum, confirm a BAA before any PHI is handled and current HIPAA compliance. Beyond that, the two that matter most in enterprise billing-company procurement are SOC 2 Type II (security, availability, processing integrity, confidentiality, and privacy, verified by independent audit over a 6-12 month observation period) and HITRUST (HIPAA, NIST, ISO 27001, and PCI DSS in one framework). Large payers and hospital clients increasingly require both. The Jorie AI compliance overview is a useful primer. 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 criteria owner-operated firms do not have. A PE sponsor typically requires formal vendor security reviews, contractual uptime commitments, integration with portfolio reporting, and sometimes SOC 2 Type II as portfolio hygiene. If the firm has been acquired or is positioning for acquisition, the acquirer's stack preferences may override an operational one. With nearly half of 2024 healthcare-IT transactions involving PE buyers per Capstone Partners, this is a mainstream procurement context, not an edge case.

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

Rarely, and only at the high end. The Retool 2026 Build vs. Buy Report found 35 percent of enterprises have replaced some SaaS with custom software. For RCM, custom development starts to make sense when proprietary payer relationships, specialty-specific claim logic, or acquired-system integration exceed what commercial platforms support, and the firm has engineering capacity to sustain a codebase. The threshold is high: custom billing software typically runs $50,000 to $300,000 to build plus ongoing engineering. Most fifty-plus firms are better served buying and configuring a platform well, though the calculus shifts toward 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-plus per year range, with implementation and EHR integration fees on top; third-party aggregators put the low end near $11,000 a year for smaller organizations. The pricing is custom-quoted and requires a sales engagement. For a billing company rather than a hospital, the real question is whether the enterprise modules, CDI, prior authorization, AltitudeAI agentic workflow, will be used, or whether you would pay for an enterprise platform to use a subset of its clearinghouse and claim-submission capabilities. See the Medi vs Waystar comparison.

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

A lot. A book that is 80 percent primary care and behavioral health has straightforward requirements. Add ten orthopedics groups and three cardiology practices through acquisition and you now have procedure-level complexity, multiple fee schedules with contractual adjustment logic, authorization tied to imaging and surgical scheduling, and denial patterns unlike primary care. No platform excels at every specialty equally. KLAS Research is the best external source for specialty-specific performance data. For independent specialty groups, Medi handles the operating layer regardless of specialty, though complex facility-side billing (UB-04, inpatient grouping, DRG) is outside its current scope.

Is there a size at which the Medi-versus-enterprise decision becomes clear?

Roughly, yes, and it is set by client type, not practice count. Firms managing primarily independent physician practices, even past a hundred, are usually better served by a billing-company-first platform than by enterprise health-system software. The inflection point is when a meaningful share of revenue, say 20 percent or more, comes from health systems, hospital outpatient departments, or FQHCs with enterprise procurement requirements. At that point the question becomes whether one platform serves the full book or the book should run in two operating layers. That is a genuine strategic call; a revenue cycle advisor like VERTESS or an M&A advisor with RCM experience is often worth the time before a decision of that scale.

How current is this page?

Last reviewed 2026-06-07. The RCM M&A market, compliance requirements, and vendor capabilities in this segment move fast. The primary external sources for current information are KLAS Research, HBMA, MGMA, and VERTESS for M&A context. Vendor positioning for Waystar and Medi should be verified directly 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*