Medi for Multi-Practice Billing Companies

Short answer

Billing companies do not run one practice; they run a book of client practices, often eight to thirty at a time. The software that fits a solo practice running its own billing usually forces a billing company to manage separate logins, separate reports, and separate configurations per client. That is not a workflow problem — it is a tenancy problem. When the software treats the practice as the workspace, every cross-practice action is working against the data model. Medi treats the billing company as the workspace and the practice as a scoped tenant inside it, so cross-practice denials, ERA posting, aging, and work queues are the default, not the exception.

Tebra and AdvancedMD are the two most widely used practice-management platforms in the independent-practice market. Both are designed with the practice as the primary workspace. That design works well for a practice that runs its own billing. It is a poor fit for a billing company managing eight or more clients, because every cross-client report, permission assignment, or denial queue requires either context-switching between separate instances or working around an architecture that was never built for this pattern. Neither Tebra nor AdvancedMD publishes pricing per-practice for billing-company accounts specifically; both price per provider, per month.

Medi is designed for the opposite case: a billing company that needs to see denials, ERA batches, A/R aging, and submission queues across every client from one authenticated session, with per-practice configuration that does not have to be replicated manually for each new client. Medi is not an EHR, not a clearinghouse-only tool, and not a fit for a solo practice running its own billing. It is purpose-built for the billing-company model. See Medi pricing, the billing company operations guide, or book a demo to see the workspace in context.

Sources: Multi-Practice Billing Company Operations · Medi Pricing · G2 Medical Billing Software Category

---

The problem with running a multi-practice book on single-practice software

When a practice-management product treats the individual practice as the tenant, every billing company using it is running a workaround. The workaround shows up in predictable places.

**Context switching.** A denial specialist working eight clients in a practice-as-tenant product has to log into, or at minimum switch the full application context to, each client one at a time. There is no combined denial queue showing CARC 97 across every client, filterable by payer. Each client is its own island.

**Permission management.** Billing companies hire in ways single-practice software does not anticipate. An offshore poster who should access three of eight clients, but not the other five, needs that restriction enforced at the data level — not by asking staff to remember which tab not to open. In a practice-as-tenant product, that usually means separate accounts and separate login credentials, which compounds as the book grows.

**Reporting.** An owner who needs to show a client their A/R aging does not want to aggregate a spreadsheet manually from eight separate exports. Cross-practice reporting in practice-as-tenant products is either absent or bolted on as an aggregate layer that does not drill back to individual records.

**Configuration duplication.** When you add a new client, payer enrollment, fee schedules, scrub rules, ERA posting policies, and write-off tolerances all need to be set up. In a billing-company-as-tenant product, a new client inherits billing-company defaults and you configure the exceptions. In a practice-as-tenant product, every setup step starts from scratch.

None of this means Tebra or AdvancedMD are poor products; they are well-regarded for the practices they were designed for. The mismatch is architectural, not a defect. A practice that wants a fully integrated EHR and practice management suite, with clinical notes, scheduling, and billing in one place, is a genuine Tebra or AdvancedMD use case. A billing company managing eight to thirty client practices that needs to work denials, ERAs, and aging across all of them from one workspace is not.

---

How Medi handles multi-practice work

Medi is organized around the billing company as the workspace. Practices are scoped tenants inside it. Every workflow below is how the product actually works, not aspirational copy.

One workspace, all clients

A Medi user logs in once. The practice context is a persistent selector in the UI, not a separate login. Switching from one client practice to another does not require a new authentication or a page reload that loses your place in a queue. Audit logging captures every context switch, every PHI access, and every write action with user, practice, timestamp, and record.

Cross-practice work queues

The Work Queue in Medi routes by function: Submissions, Follow-Up, Denials, ERA Review, Aging. A denial specialist opens the denials queue and sees denials across every client practice they are permissioned to access. One filter brings the view down to a single client or a single payer. The queue does not require the specialist to know which clients have open CARC 97s today; the queue surfaces them.

ERA batches are reviewed in one ERA Review surface. An ERA from one client's Aetna payer and an ERA from another client's UHC payer appear in the same session. The poster applies adjustments, confirms CARC/RARC codes, and posts payments without switching sessions.

Per-practice configuration

Each client practice in Medi holds its own payer enrollment, fee schedules, custom scrub rules, ERA posting policies, and write-off tolerances. When a billing company adds a new client, the new practice inherits billing-company-level defaults and the account manager configures only the exceptions. Nothing has to be recreated from scratch.

Payer enrollment is per practice because each client's providers enroll separately. Scrub rules can be tightened per payer per practice when one client's payer has idiosyncratic requirements. ERA posting policies can be set more or less aggressively per practice based on the client's preference.

A/R and reporting across the book

A/R aging aggregates across all practices for owners and supervisors with book-level access. The same report drills down to a single practice for an account manager presenting to one client. Denial volume by CARC code and payer, ERA posting volume, productivity by user, and payer performance are all reportable at the billing-company level and at the individual-practice level.

Permissions that match how billing companies hire

Medi's permission model is per-practice, per-role, inside one workspace. An offshore poster can be restricted to three of eight client practices, with audit logs proving they did not access the other five. A denial specialist can have access to all eight clients with the ability to edit denial records but not void payments. An owner has full-book access. These restrictions are enforced at the data level, not by policy alone.

Pricing designed for the billing-company model

Medi charges $20 per client practice per month (graduated: $15 per practice for practices 26–50, $10 per practice for 51 and above). There is no per-provider fee and no contract. Per-line EDI: claim submission $0.25 first line, $0.20 additional; ERA $0.25 first paid line, $0.20 additional paid line, with denied lines at $0. Eligibility and claim status checks are $0.20 each. Migration is free with a 12-month term, or $100 per practice as a one-time fee (capped at $3,000). Data export is always free; there is no early-termination fee. Full details at /pricing. A cost estimate for your specific book size is available at the pricing calculator.

---

What Medi is not

Being honest about fit matters more than closing a deal with the wrong buyer.

**Medi is not an EHR.** It does not provide scheduling, clinical notes, prior-authorization submission, or automated coding. If the practice you are billing for needs a single system that covers clinical and billing workflows in one product, Medi is not that system. Tebra and AdvancedMD offer integrated EHR and billing suites; that is a genuine advantage for the practices that need it.

**Medi is not a clearinghouse-only tool.** Claim submission routes through Stedi as Medi's single clearinghouse partner. Medi is a full revenue cycle management platform: claim building, scrubbing, submission, denial management, ERA review and posting, payment posting, patient statements, and A/R follow-up. The clearinghouse is one component of that workflow, not the whole product.

**Medi is not for solo practices running their own billing.** The per-practice pricing model and the multi-practice workspace design are built for billing companies. A solo practice with one provider and no billing staff is not the target user. That practice might be better served by a per-provider product designed around a single-practice workflow.

**Medi is not a fit if you need integrated scheduling or clinical documentation.** The workflow boundary is billing: from the time a claim is ready to build through payment posting and follow-up. Anything on the clinical side of that line is outside Medi's scope.

---

Frequently asked questions

What makes Medi different from Tebra or AdvancedMD for a billing company?

The architecture. Tebra and AdvancedMD are designed with the practice as the primary workspace. A billing company using either product works across clients by context-switching between separate practice instances. Medi treats the billing company as the workspace; client practices are scoped tenants inside it. That means cross-practice denial queues, ERA review, A/R aging, and permissions all operate from one authenticated session. For the practices they were designed for — particularly those that want an integrated EHR and billing suite — Tebra and AdvancedMD have genuine advantages Medi does not offer. The fit question is whether you need integrated clinical tools (Tebra/AdvancedMD) or purpose-built multi-practice billing-company operations (Medi). See Medi vs Tebra and Medi vs AdvancedMD for a direct comparison.

How does pricing work for a billing company with twelve client practices?

At twelve client practices, Medi charges $20 per practice per month, or $240 per month total. No per-provider fee; no per-seat fee. Per-line EDI costs accrue separately based on claim volume. The graduated discount applies starting at practice 26. Full details and a book-level estimate are at /pricing and the pricing calculator.

Can I restrict a staff member to only some of my client practices?

Yes. Permission assignment in Medi is per-practice, per-role, inside a single workspace. A biller can be granted access to four of twelve client practices without a separate login. The other eight practices are not visible to that user. Every PHI access is audit-logged with user, practice, timestamp, and record, which supports HIPAA Security Rule §164.312(b) compliance review.

Does Medi handle ERA posting across multiple client practices?

Yes. ERA batches from different client practices appear in one ERA Review session. The poster can work through ERAs from multiple clients without switching contexts. Posting applies adjustments and CARC/RARC codes per claim line and writes back to the correct practice record automatically. See the multi-practice billing company operations guide for more detail on how ERA workflows span practices.

What happens when I add a new client practice?

When a new client practice is added in Medi, it inherits billing-company-level defaults for payer enrollment references, scrub rules, and ERA posting policies. The account manager then configures the client-specific exceptions: which payers are enrolled, any custom scrub rules the client's payer mix requires, and posting policy overrides. User access to the new practice is granted practice by practice; existing users do not automatically see the new client. Migration support is included free with a 12-month term or available at $100 per practice as a one-time fee, capped at $3,000 for the full book.

---

A note on the pricing figures here

The pricing shown for other vendors is gathered from their public pricing pages where they publish one, and from third-party aggregators, reseller materials, and customer reports where they do not. Many of these vendors do not publish their pricing, so these figures are approximate, may not reflect negotiated or current rates, and can change without notice. Treat them as a starting point and confirm current pricing with each vendor directly. Where a vendor does not publish its pricing, this page says so rather than presenting an estimate as fact. Medi's own pricing is published in full at /pricing.

---

Sources: Multi-Practice Billing Company Operations · Medi Pricing · Billing Company Operations · Medi vs Tebra · Medi vs AdvancedMD · Book a Demo