Medical Billing Software for Billing Companies Managing 20 to 50 Practices

Short answer

The 20-to-50 practice billing company sits in a specific band: too large for the workarounds that hold at five or ten clients, not large enough to absorb enterprise RCM contracts. This is where per-provider software pricing starts compounding into a real budget line, where automation pressure is highest because claim volume is real but margins are tight, and where cross-team coordination fails if the software treats each practice as a separate silo. The billing company software evaluation guide covers the full framework; this page focuses on what changes at 20 to 50 practices specifically.

What a 20-to-50 practice billing company looks like operationally

A billing company at this scale typically runs 15 to 50 staff. Ownership manages the business — client relationships, contracts, hiring — not individual claims. Account managers cover the book at roughly three to eight practices each; a 12-provider orthopedics group takes more account-manager time than a two-provider primary-care clinic. They need client-facing reports they can share without reformatting.

Functional billing teams handle work by type rather than by client: submitters for all clients' charge entry, posting teams for all clients' ERAs, denial leads for the full denial queue. This model is more efficient than billers owning clients A to Z, but it only works when the software presents cross-practice queues by function. When it does not, specialists spend their day switching contexts and the functional model collapses.

Offshore or remote staff are common at this scale, handling posting exceptions, follow-up calls, and denial outreach. The book typically represents 50 to 150 providers and $5M to $25M in annual collections — enough that software cost is a real P&L line.

The software cost math at this scale gets ugly fast

Per-provider pricing is easy to ignore at five clients. At thirty it is not. Here is the arithmetic using publicly available 2026 pricing for a billing company with 90 providers across 30 client practices:

The Medi number at 90 providers is the $300 platform fee plus EDI usage at typical volumes — roughly $1,600 to $2,100 in claim submission, ERA posting, and eligibility inquiries per month. That total does not move materially when the book grows from 60 to 120 providers because EDI charges scale with transaction volume, not provider headcount.

At $99 per provider, 90 providers costs $8,910 per month. The gap versus a flat-rate platform is $6,500 to $18,000 per month — $78,000 to $216,000 per year — and widens with every new practice added. Published 2026 onboarding guidance for per-provider platforms runs about $500 per provider on initial setup; at 90 providers, that is $45,000 before a single claim submits in the new system.

Per-provider pricing is a tax on growth. Every new client makes the software bill larger. This is not a quality verdict — it is a structural one. See Medi vs Tebra, AdvancedMD, and CollaborateMD for the side-by-side breakdowns.

Where 20-to-50 practice billing companies hit walls

Most billing companies in this range grew from a smaller base. The walls they hit cluster around four patterns.

Context-switching overhead. Thirty clients in software that requires a separate login per client means thirty context switches per day for a specialist working their queue. The overhead looks minor per switch and enormous in aggregate.

Reporting that requires assembly. Account managers spending two to four hours per client per week building reports the software could generate are doing expensive work by hand. At 30 clients, that is 60 to 120 hours per month on a spreadsheet problem.

Permission complexity. At ten practices, access control is often informal — everyone sees everything. At thirty it breaks. An offshore poster with access to every client practice is a HIPAA exposure. Most billing companies discover their software does not support fine-grained per-practice access inside one workspace.

Payer enrollment as an onboarding bottleneck. Adding the twenty-fifth client means re-running enrollment for every payer that client submits to. In software where this is manual and poorly tracked, each new client costs four to eight weeks of a senior person's time. At one or two new clients per quarter, enrollment is the hidden growth constraint no one talks about until they hit it.

The automation question: where AI and RPA actually help

The 20-to-50 practice band is where automation pressure is highest. A book of 30 practices with 90 providers generates 4,000 to 8,000 claims per month. The volume is real but margin per claim does not justify proportional headcount growth.

ERA auto-posting is the clearest win. A mature auto-post pipeline achieves 85 to 95 percent touchless processing on clean remittances. The value is not replacing the posting team — it is freeing them for exception queues, which is the actual work.

Eligibility batch verification is high-ROI and underused. Running 270/271 eligibility checks across all client practices the night before appointments — automatically — eliminates a category of front-end denials without additional staff.

Denial routing works when rules are explicit. Routing CO-97 denials from a specific payer to the appeals queue with the right template is reliable. Outcome prediction AI requires more scrutiny; ask vendors for specific accuracy metrics before building workflows around those outputs. The AI medical billing reality guide covers where to trust the claims.

Offshore-plus-automation is the model that scales. Offshore teams handle exception queues, denial outreach, and follow-up calls. Automation handles straight-through volume and eligibility batch. The software has to provide: a clear held-line exception queue, tolerance thresholds configurable per practice and per payer, and an audit trail of every auto-post decision.

What software needs to do at this scale

Cross-practice queues by function. Denial leads, posting teams, and follow-up coordinators see their full workload across the book — filtered by what they are responsible for — without switching clients.

Per-practice, per-provider permissioning inside one workspace. Not separate logins. One workspace where an offshore poster is credentialed to four of thirty practices, the others are invisible, and every PHI access is logged with user, tenant, timestamp, and record per HIPAA Security Rule §164.312(b).

Practice-level configuration that inherits from billing-company defaults. Billing-company-level defaults for payer setup, fee schedules, and ERA tolerances, with practice-level overrides for clients that differ — without rebuilding from scratch per client.

Account-level reporting account managers can use directly. A/R aging by practice, denial rate by payer, collection rate trends — in a format that is a client deliverable, not a spreadsheet project.

Enrollment tracking that surfaces blockers. Payer enrollment status — active, pending, expired — visible in one view per practice. At 30 practices with 15 payers each, there are potentially 450 enrollment relationships. Gaps block claims; surfacing them before submission matters.

See multi-practice billing company operations for the full operational framework behind these requirements.

How Medi fits a 20-to-50 practice billing company

Medi prices around the billing company, not per provider. $300 per month, flat. EDI usage — $0.25 per first claim line, $0.20 per paid ERA line, $0.20 per eligibility inquiry — scales with transaction volume. A book of 30 practices and 90 providers pays the same platform fee as a book of 5 practices and 15 providers.

The tenancy is one workspace per billing company; client practices are scoped tenants inside it. Cross-practice queues work across the full book by default. Permissions are per-practice, per-provider, with audit logs covering every PHI access. ERA auto-posting surfaces held lines in a review queue with CARC and RARC codes translated, BPR totals visible, and per-line resolution available. Practice-level configuration inherits from billing-company defaults. Reporting aggregates across the book and drills to individual practices without leaving the report.

See Medi vs Tebra, CollaborateMD, AdvancedMD, and Waystar for the comparisons that matter at this scale. The demo lets you test the cross-practice workflow live; pricing has the full EDI usage schedule.

When you outgrow Medi (honest answer about enterprise needs)

Medi is billing-only. It does not include an EHR, scheduling, charting, or patient engagement modules. Clients who expect those from their billing company need a different vendor for that scope; Tebra or AdvancedMD may fit that ask better.

At enterprise scale — 100-plus practices, hospital-level engagement, institutional UB-04 billing at volume, dedicated professional services — enterprise platforms like Waystar or athenahealth are built for that model. The billing company that fits Medi best has clients using a separate EHR, a billing-only relationship, and cares about pricing predictability across a growing provider count more than bundled clinical features.

What Medi has not earned yet

Honest disclosure that scales — the 20-to-50 segment is where certification questions start to matter, so the gaps deserve naming:

• No SOC 2 Type II certification yet. Most enterprise clients in this segment will eventually ask. The roadmap includes it; the badge does not exist today.
• No HITRUST certification yet. Some clients require it; Medi does not have it.
• No published enterprise SLAs. Implementation review covers the contractual boundary; published uptime guarantees are not in place.
• No customer reference list yet. Early-stage product. Clients evaluating at this scale should weigh that against the cost-of-software math.

If your client mix already requires SOC 2 Type II evidence on contract, Medi is not the right fit today. If your clients are not yet asking and you are choosing on pricing structure, the certification gap is a known forward risk, not a present blocker.

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

• Open a denial queue across fifteen client practices in one view without switching contexts
• Restrict a test user to four of thirty practices inside one workspace; verify the other twenty-six are invisible
• Walk through an ERA with a recoupment, a PLB segment, and two lines over write-off tolerance; see where each surfaces and what the audit trail shows
• See all payer enrollment statuses across five client practices in one view; ask how expiring enrollments surface before they block claims
• Generate an A/R aging across all practices and drill to one; ask whether an account manager can share it directly with a client
• Get a quote at your current provider count and at your projected count in two years; calculate all-in cost including onboarding, EDI usage, and any per-provider add-ons

The billing company software evaluation guide has the full demo checklist. Billing company operations covers the operational framing behind each point.

Frequently asked questions

What is the biggest operational difference between a 10-practice and a 30-practice billing company?

The functional team model. At 10 practices, a biller owning three or four clients A to Z works. At 30, that model runs out of scale. Billing companies shift to functional specialists: submitters for all clients' charge entry, posters for all clients' ERA, denial leads for the full queue. That shift requires software presenting cross-practice queues by function. Without it, the billing company chooses between scale and specialization.

How does per-provider pricing affect growth?

Each new practice adds every provider to the monthly bill, permanently. At $99 per provider, a new five-provider practice costs $495 per month forever. On a flat-rate platform, the same practice adds $0 to the platform fee; only the incremental EDI usage is new. Above 50 providers, the monthly gap between a per-provider platform and a flat-rate platform is often $5,000 to $20,000 per month.

At what provider count does per-provider pricing become a serious problem?

Below 20 providers, the absolute dollar difference is usually small. Between 20 and 50 providers, the difference shows up on a monthly P&L. Above 50 providers, it is typically material enough to affect client pricing and margin targets. Run the math at your current rate against your projected two-year provider count.

What automation is actually reliable at this scale?

ERA auto-posting for clean remittances — 85 to 95 percent touchless processing is achievable with well-configured tolerance thresholds. Batch eligibility verification via 270/271, queued nightly, is reliable and high-ROI. Denial routing by CARC code to specific queues works when rules are explicit. AI outcome prediction requires direct verification; ask vendors for accuracy metrics before building workflows around those outputs.

How should offshore staff access be managed in a 30-practice billing company?

Per-practice, per-provider access inside one workspace with audit logging on every PHI access — user, tenant, timestamp, record — per HIPAA Security Rule §164.312(b). Separate logins per client become a maintenance problem at 30 practices and a compliance gap if an offshore biller touches the wrong client's records. See multi-practice operations for the full framework.

How does M&A activity affect software decisions at this scale?

The 20-to-50 practice billing company is an active acquisition target. Private equity interest in RCM platforms grew through 2025 and into 2026. Software with clean cross-practice reporting, complete audit logs, and exportable practice-level data is worth more in due diligence than software where reporting requires spreadsheet assembly. If an exit is on the horizon, the software stack is part of the story a buyer reads.

What does migrating to a new platform look like at this scale?

Phased, not a cutover. Leave trailing 60 to 90 days of open A/R in the old system, migrate forward-only starting with the simplest practices, run parallel ERA posting for two weeks to reconcile totals, then migrate the rest in waves. Payer enrollment — trading partner agreements, NPI connections, 835 routing — should be planned before the first practice goes live, not after it. At 30 practices, enrollment planning is a six-to-eight-week parallel workstream.

Is Medi a fit if some of my clients still need an EHR?

Medi is billing-only. Clients who need scheduling, charting, or a patient portal need to source those from an EHR vendor. The fit is billing companies whose clients have already separated the EHR and billing relationships, or are willing to. Many practices use Epic, Athena, eClinicalWorks, Charm, or another EHR and want a billing company running on a billing-specific platform. For clients expecting the billing company to deliver the EHR too, Medi is not the answer — see Medi vs Tebra for that comparison.