Medical Billing Software for Billing Companies Managing 5 to 20 Practices

Short answer

A billing company managing 5 to 20 client practices is past per-client logins and spreadsheet reporting, and not yet at enterprise RCM scale. The decision turns on four things: pricing structure (per practice versus per provider), cross-practice work queues, permission granularity for mixed onshore and offshore staff, and whether one tool shows the full book and each client without compiling exports. The companies that scaled cleanly chose a billing-company-first data model before they needed it.

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

At five practices, most billing companies run four to eight staff, with generalists handling work end to end.

By ten practices, the generalist model breaks. A 10-practice book typically covers 30 to 60 active providers, roughly 12 to 25 FTEs by MGMA benchmarks before offshore augmentation. Two operating models emerge: the client-team model, where each biller owns a portfolio end to end, and the functional model, where staff specialize by claims, posting, denial follow-up, and AR follow-up across all clients. The functional model scales better, but only on software that routes work by function across every client in one queue. A denial specialist on the client-team setup logs into ten instances a day; on billing-company-first software the same specialist works one queue across all ten clients.

Offshore hiring usually starts around 10 to 15 practices, where operational overhead can approach half of gross revenue and offshore staff cost 50 to 70 percent less. The compliance requirement is firm: restrict each offshore biller's PHI access to assigned clients, with an audit log that proves it.

By 20 practices, owners need A/R aging, denial patterns, and ERA exceptions across the full book without compiling 20 separate exports. This is where practice-centric architectures break.

The software cost math at this scale

At 10 practices and 35 active providers:

Tebra publishes its Billing Starter tier at $99 to $199 per provider per month; fuller EHR bundles run $399 to $799. AdvancedMD publishes PM + Medical Billing at $429 per provider per month; managed RCM is 4 to 8 percent of collections. Medi charges $20 per client practice per month with no per-provider fee, with volume pricing available. At 10 practices that is $200 in platform fees; EDI usage adds roughly $800 to $1,100 a month at typical volumes, for a total around $1,000 to $1,300.

The cost difference is structural. Per-provider pricing reflects EHR-bundled platforms selling clinical licensing alongside billing. A billing company whose clients already have an EHR pays for features its team never opens. Medi charges per client practice, so adding providers inside an existing client changes nothing on the invoice. Growing from 35 to 60 providers across the same 10 practices raises a per-provider bill by thousands a month; on Medi it adds $0 in platform fees and only incremental EDI volume. Adding a client costs the per-practice rate, with volume pricing available as the book grows.

See Medi vs Tebra, Medi vs AdvancedMD, and Medi vs CollaborateMD for side-by-side detail.

Where 5-to-20 practice billing companies hit walls

**The login-per-client wall.** A denial specialist working eight isolated instances loses 20 to 30 minutes a day to logging in and reorienting.

**The spreadsheet reporting wall.** At three clients, compiling reports in a spreadsheet works. At twelve it takes hours and produces week-old numbers. Owners need "what is my total A/R right now" answerable in under 30 seconds.

**The permission wall.** Offshore staff become a HIPAA liability when the software cannot scope access precisely. HIPAA Security Rule §164.312(b) requires audit controls proving which user accessed which record in which tenant.

**The growth-pricing wall.** Adding a client that brings eight providers means paying for eight seat licenses before that client's first claim submits. At tight margins, immediate cost against deferred revenue creates real pressure.

**The denial-pattern blindspot.** A specialist in client-level silos can fix a UnitedHealthcare denial for Client A and miss the same CARC code firing across Clients B, C, and D for weeks.

What software needs to do at this scale

**Billing company as workspace, practice as scope.** Queues, reporting, payer setup, and user management run from one workspace. Switching clients is a filter change, not a logout.

**Cross-practice work queues.** Denials, ERA review, AR follow-up, and claim scrubbing queue by function across any combination of clients in one view.

**Granular permissions without separate accounts.** Offshore posters restricted to specific clients, denial leads with cross-client rights, account managers with full portfolio access, all inside one workspace.

**Audit logging on every PHI access.** User, practice tenant, record, timestamp, IP, retained to satisfy HIPAA §164.312(b).

**Aggregated reporting with drill-down.** A/R aging, denial volume, and posting totals across the full book, drillable to any client, current rather than compiled from exports.

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

**One workspace.** Every client practice lives inside one Medi workspace. Switching clients is a context change, not a re-login, and record-level guards prevent accidental cross-practice writes.

**Functional queues across all clients.** The Work Queue routes denial follow-up, ERA review, submission tracking, and AR follow-up by function across all clients in one view.

**Granular permissions, unified audit log.** An offshore biller restricted to four of eight practices does not see the other four. Every PHI access is logged with user, practice tenant, record, and timestamp, retained seven years per HIPAA §164.312(b).

**Per-practice pricing.** Adding a practice adds $20 per client practice per month, with volume pricing available. Adding providers inside a practice changes nothing. EDI usage scales with claim and ERA volume; the schedule is at /pricing.

**Per-practice configuration in one admin layer.** Payer enrollment, fee schedules, scrub rules, and ERA posting policies are per-practice under one billing-company-level admin surface.

See multi-practice billing company operations, the billing-company operations overview, pricing, and book a demo.

When you outgrow Medi

The honest answer about when to look elsewhere:

• **When clients need an EHR, scheduling, or charting from you.** Medi does not include these. Tebra, AdvancedMD, or athenahealth fit that ask; Medi does not.
• **When clients own their own system and plan to stay.** If a client controls its EHR instance and the billing company works inside it, Medi is not a fit.
• **When your specialty is primarily institutional billing.** Medi is organized around professional billing. Verify complex facility or institutional claim formats before committing.
• **When you are running 50-plus practices at enterprise scale.** Medi is calibrated for independent billing companies, not hospital-system RCM. As the book crosses 20, see billing software for 20 to 50 practices.

What Medi has not earned yet

Honest disclosure, applied at every size tier:

• No SOC 2 Type II certification yet. It is on the roadmap; the badge does not exist today.
• No HITRUST certification yet. Same posture.
• No published enterprise SLAs. Implementation review covers the contractual boundary; published uptime guarantees are not in place.
• No customer reference list yet. The product is early-stage, and family-billing operations are the live testbed.

Most clients in this segment do not contract on SOC 2 evidence, so a 5-to-20 practice book usually does not require the certifications above. The disclosure is here for symmetry: every size tier should see the same honesty about what Medi has and has not earned.

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

• **Practice switching.** Move between three clients in under 30 seconds. A login screen means per-client-instance architecture.
• **Cross-practice denial queue.** Open a denial queue across the full book, apply a payer filter and a CARC code filter, and confirm the specialist can work the list without switching contexts.
• **Offshore permission restriction.** Restrict a test biller to four of eight practices, confirm the other four are invisible, and ask to see the audit log proving enforcement.
• **Cross-book A/R aging.** Pull an aggregated A/R aging report and drill into one practice. Confirm it is real-time, not an export.
• **ERA exception workflow.** Find a held ERA line and walk the posting decision: write-off tolerance, override rights, PLB segment visibility.
• **Audit log query.** Pull the log for one PHI read. Confirm user, practice tenant, record, timestamp, and IP are present.

For the full evaluation framework, see the billing company software evaluation guide.

Frequently asked questions

What is the right software for a billing company with 8 client practices?

It depends on whether clients need an EHR from you and whether per-provider pricing is cutting margin. A functional team benefits most from billing-company-first software with cross-practice queues and per-practice pricing that does not grow with provider headcount. A company whose clients expect a combined EHR-and-billing relationship should stay on a per-provider EHR platform.

How many staff does a 10-practice billing company typically have?

MGMA benchmarks cite roughly 2.7 billing staff per physician. A 10-practice, 35-provider operation might run 12 to 18 domestic FTEs plus offshore staff. HBMA publishes staffing-ratio surveys specific to billing companies.

Why does per-provider pricing hurt more at 10 practices than at 2?

At ten practices with 40 providers, Tebra's published Billing Starter at $99 to $199 per provider runs roughly $3,960 to $7,960 a month before add-ons. A billing company on 10 to 15 percent gross margins cannot absorb software cost that scales proportionally with revenue.

Can a 15-practice billing company use Tebra or AdvancedMD?

Yes, both publish billing-company offerings. The question is whether per-provider pricing and practice-as-primary-tenant architecture match how the team actually works. Test the cross-practice workflows your team runs every week in any demo before deciding.

How does offshore billing staff access work in billing-company software?

In a practice-as-tenant system the workaround is separate credentials per client, which fragments audit logs. In a billing-company-as-tenant system, one account covers specific practices under one unified audit log, which is what HIPAA §164.312(b) audit controls require.

What is the difference between a client team model and a functional model?

In a client-team model, each biller owns a portfolio end to end. In a functional model, staff specialize by function across all clients. The functional model scales better but depends on software that routes work by function across every client in one queue.

What should a billing company verify in a contract at this scale?

Audit-log retention (seven years against HIPAA §164.312(b)), BAA scope including AI subprocessors, whether per-practice configuration can be exported, and pricing terms for provider-count changes mid-term.

How current is this guide?

Last reviewed 2026-06-07. Tebra publishes Billing Starter at $99 to $199 per provider per month at tebra.com/pricing/overview. AdvancedMD publishes PM + Medical Billing at $429 per provider per month at advancedmd.com/software-pricing. Operational data draws on Tebra's Medical Billing Benchmark Report 2025. All vendor pricing changes; verify current quotes directly.