Medical Billing Software for Billing Companies Managing 20 to 50 Practices

Short answer

A billing company at 20 to 50 client practices is too large for the workarounds that hold at five or ten clients and too small to absorb an enterprise RCM contract. Three things change at this book size. Per-provider software pricing turns into a real budget line. Automation pressure peaks, because claim volume is high but margin per claim is thin. And cross-team coordination breaks if the software treats each practice as a separate silo. The billing company software evaluation guide has the full framework; this page covers what is specific to 20 to 50 practices.

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 roughly three to eight practices each, and a 12-provider orthopedics group takes more of their time than a two-provider primary-care clinic. They need client-facing reports they can share without reformatting.

Billing teams work by function instead of by client: submitters for all clients' charge entry, posting teams for all clients' ERAs, denial leads for the full denial queue. This is more efficient than billers owning clients A to Z, but it only holds when the software presents cross-practice queues by function. Without that, specialists spend the day switching contexts and the functional model collapses.

Offshore or remote staff are common here, handling posting exceptions, follow-up calls, and denial outreach. The book usually 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

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

Medi charges $1.00 per claim, with no platform fee and no per-practice fee. ERA posting is included in that price. A book of 90 providers across 30 client practices runs 4,000 to 8,000 claims a month, so the claim cost lands around $4,000 to $8,000 a month before eligibility and claim-status usage. That number tracks billed work, not headcount: adding a provider inside an existing practice costs nothing unless that provider generates claims, and the same is true for adding a client practice. The rate drops to $0.90 and $0.80 once monthly volume passes the published thresholds; full schedule at /pricing.

At Tebra's published $399 non-physician standard rate and 90 providers, that runs ~$35,910 per month, so the gap versus Medi's roughly $4,000 to $8,000 a month is large and widens as claim volume per provider stays flat while Tebra's bill keeps rising with provider count regardless of volume. Tebra's cheaper $99 to $199 Billing Starter rate does not apply to the practices modeled here: it is limited to practices submitting fewer than 100 claims per month, and a practice above that for three consecutive months moves to standard pricing. Practices under the cap do qualify and keep the rate, but the seat-price rule still runs against it. At $1.00 per claim a seat is cheaper only when the provider submits more claims per month than the seat costs in dollars, and a $99 seat needs more than 99 claims, which the cap forbids. AdvancedMD's per-provider model produces a far larger number at the same provider count; CollaborateMD does not publish pricing on its own site, with a BestNotes partner rate sheet listing roughly $0.38 per claim (declining with volume) plus about $54 per provider, so get a current quote. Onboarding and implementation add first-year cost that several vendors quote individually; request it before budget approval.

Per-provider pricing is a tax on growth: every new client raises the software bill. That is a structural fact, not a quality verdict. See Medi vs Tebra, AdvancedMD, and CollaborateMD for the side-by-side detail.

Where 20-to-50 practice billing companies hit walls

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

Context-switching overhead. Thirty clients in software that requires a separate login per client is thirty context switches a day for one specialist working a queue. Minor per switch, enormous in aggregate.

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

Permission complexity. At ten practices, access control is often informal and everyone sees everything. At thirty it breaks. An offshore poster with access to every client practice is a HIPAA exposure, and most billing companies find their software cannot scope 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. 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 growth constraint no one names until they hit it.

Where automation actually helps at this scale

Automation pressure peaks in this band. A book of 30 practices with 90 providers generates 4,000 to 8,000 claims a month. Volume is high, but margin per claim does not justify proportional headcount.

ERA auto-posting is the clearest win where a billing company gets it configured well. A mature auto-post pipeline is designed to target 85 to 95 percent touchless processing on clean remittances, freeing the posting team for exception queues; treat that range as a configuration goal to test against your own remittance mix, not an observed rate any vendor should hand you unverified.

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

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

Offshore plus automation is the model that scales. Offshore teams take exception queues, denial outreach, and follow-up calls; automation handles straight-through volume and the eligibility batch. The software has to provide a clear held-line exception queue, tolerance thresholds set 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 to what they own, without switching clients.

Per-practice, per-provider permissioning inside one workspace, not separate logins. An offshore poster is credentialed to four of thirty practices, the rest 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. Set payer setup, fee schedules, and ERA tolerances once at the company level, then override per practice for clients that differ, without rebuilding from scratch each time.

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

Enrollment tracking that surfaces blockers. Payer enrollment status — active, pending, expired — in one view per practice. At 30 practices with 15 payers each, that is up to 450 enrollment relationships, and gaps block claims, so 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 charges $1.00 per claim, with ERA posting included and no monthly fee or per-practice fee. Cost tracks billed claim volume, not provider count and not practice count: adding a provider or a client practice only moves the bill if it adds claims. Usage add-ons on top: $0.25 per eligibility inquiry, $0.20 per claim status inquiry, $1.50 per COB, discovery, or attachment transaction (turned on book by book during onboarding). The per-claim rate moves to $0.90 and then $0.80 at the volume marks published on the pricing page. No contract; month-to-month is available. Migration is free with a 12-month commitment or $100 per practice (capped at $3,000) month-to-month, and data export is always free. Full schedule at /pricing.

Tenancy is one workspace per billing company, with client practices as scoped tenants inside it. Cross-practice queues span the full book by default. Permissions are per-practice and per-provider, with audit logs on 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. Practice-level configuration inherits from billing-company defaults. Reporting aggregates across the book and drills to a single practice 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

Medi is billing-only. It has no 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 fits that ask better.

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

What Medi has not earned yet

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; it is on the roadmap, not on the books.
• No HITRUST certification yet. Some clients require it; Medi does not have it.
• No published enterprise SLAs. An implementation review covers what the contract does commit to, but there is no uptime number with remedies attached.
• 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 asking yet 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, and confirm the other twenty-six are invisible.
• Walk an ERA with a recoupment, a PLB segment, and two lines over write-off tolerance; see where each surfaces and what the audit trail records.
• See all payer enrollment statuses across five client practices in one view, and ask how expiring enrollments surface before they block claims.
• Generate an A/R aging across all practices and drill to one, then ask whether an account manager can share it with a client as-is.
• Get a quote at your current provider count and your projected count in two years, and price the 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 end to end works. At 30 it runs out of scale, and 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 that presents cross-practice queues by function. Without it, the billing company has to choose between scale and specialization.

How does per-provider pricing affect growth, and when does it become a serious problem?

Each new practice adds every provider to the monthly bill, permanently. At a ~$399 per-provider reference, a new five-provider practice costs about $1,995 a month for as long as the client stays, regardless of how many claims that practice actually files. On a per-claim platform like Medi, the same practice adds $1.00 for each claim it generates and nothing more; a slow-volume practice costs little, a high-volume one costs more, but neither carries a fixed per-provider or per-practice tax. The threshold where per-provider pricing matters tracks total provider count: below 20 providers the dollar difference is usually small, between 20 and 50 it shows up on the monthly P&L, and above 50 it is typically material enough to affect client pricing and margin targets. Across that >50-provider range, depending on the reference rate and book size, the monthly gap between a per-provider platform and a per-claim platform commonly runs into the five figures. Run the math at your current rate against your projected two-year claim volume.

What automation is actually reliable at this scale?

ERA auto-posting on clean remittances is designed to target 85 to 95 percent touchless processing with well-configured tolerance thresholds; ask any vendor, including us, to show that rate against your own remittance mix rather than taking it as given. Batch eligibility via 270/271, queued nightly, is reliable and high-ROI. Denial routing by CARC code to specific queues works when the rules are explicit. AI outcome prediction needs direct verification; ask vendors for accuracy metrics before building workflows around it.

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 the moment 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, and private-equity interest in RCM platforms grew through 2025 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 takes 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 a 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 move the rest in waves. Plan payer enrollment — trading-partner agreements, NPI connections, 835 routing — before the first practice goes live, not after. 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 source those from an EHR vendor. The fit is billing companies whose clients have already separated the EHR and billing relationships, or will. Many practices run Epic, athenahealth, eClinicalWorks, Charm, or another EHR and want a billing company on a billing-specific platform. For clients who expect the billing company to deliver the EHR too, Medi is not the answer; see Medi vs Tebra for that comparison.

Sources: Medi pricing · AdvancedMD software pricing · Tebra pricing overview · CollaborateMD rate sheet via BestNotes · MGMA payer payment auditing