What Is a Clearinghouse in Medical Billing — and Do You Still Need One?

If you've worked in medical billing for more than a week, you've used a clearinghouse — probably without thinking much about it. Claims go in, responses come back, and somewhere in between a clearinghouse is doing work that most billing teams couldn't easily replicate on their own.

But as practice management systems have gotten more sophisticated, direct payer connections have expanded, and automation has entered every corner of revenue cycle management, a fair question has emerged: do you actually still need a clearinghouse? And if so, what should you expect from one?

This article answers both questions — starting with what clearinghouses actually do, where they add real value, where their limitations show, and how to evaluate whether your current setup is working as hard as it should be.

What Is a Medical Billing Clearinghouse?

A clearinghouse is an intermediary that sits between healthcare providers and insurance payers. When your practice submits a claim, it typically doesn't go directly to the payer. It goes to a clearinghouse first.

The clearinghouse receives your claim in whatever format your practice management system produces, translates it into the HIPAA-standard electronic format the payer requires (typically the 837P for professional claims or 837I for institutional), runs it through a series of edits and validation checks, and routes it to the correct payer.

On the way back, clearinghouses receive payer responses — claim acknowledgments, rejections, ERAs — and route them back to your system.

In short: clearinghouses are the translation layer and routing infrastructure of electronic claims processing. They exist because there are thousands of payers, each with their own technical requirements, and no single practice or billing company could maintain direct connections to all of them.

What Clearinghouses Actually Do: The Core Functions

Claims Transmission

The most fundamental function. Your practice management system generates an 837 file; the clearinghouse validates the format, applies payer-specific edits, and submits it. Without a clearinghouse, you'd need a direct EDI connection to every payer you bill — a technical and operational burden most practices can't sustain.

Claim Scrubbing and Pre-Submission Edits

Before a claim reaches the payer, a good clearinghouse runs it through a library of edit rules — checking for missing fields, invalid code combinations, diagnosis-procedure mismatches, NPI issues, and hundreds of other potential errors.

Claims that fail these edits are returned to the biller as rejections before they ever reach the payer. This matters because a rejection (caught by the clearinghouse) is fundamentally different from a denial (issued by the payer after adjudication). Rejections can be corrected and resubmitted quickly, often the same day. Denials require a more involved process and count against your denial rate metrics.

A clearinghouse with strong scrubbing logic catches rejectable errors before they become payer denials. The quality of this scrubbing varies significantly across clearinghouses — it's one of the most important differentiators to evaluate.

Payer Connectivity

Major clearinghouses maintain connections to thousands of payers — commercial, Medicare, Medicaid, workers' comp, and others. When a new payer emerges, changes its EDI requirements, or updates its companion guide, the clearinghouse updates its routing and translation rules. Your practice doesn't have to track any of this.

ERA Receipt and Delivery

Clearinghouses receive 835 ERA files from payers and deliver them to your practice management system for payment posting. For practices enrolled in ERA with major payers, this delivery is automated — payment posting can happen the same day adjudication occurs.

Eligibility Verification (270/271 Transactions)

Most clearinghouses support real-time eligibility checks via the 270/271 transaction — your system sends a 270 (eligibility inquiry), the payer responds with a 271 (eligibility response). This is how your PMS or eligibility verification tool confirms active coverage, copay amounts, and deductible status before a patient arrives.

Claim Status Inquiry (276/277 Transactions)

The 276/277 transaction allows your system to query a payer for claim status — submitted, received, in process, paid, denied — without a phone call. This is the electronic backbone of automated AR follow-up tools, including platforms like SuperDial.

Secondary Claims and COB Data

Clearinghouses facilitate secondary claim submission, often including the COB loop data from the primary ERA. For practices with high volumes of COB billing, a clearinghouse that handles COB data correctly — passing through the 2320/2330 loops cleanly — is worth its weight in reduced manual rework.

The Major Clearinghouses: A Brief Overview

The clearinghouse market has consolidated considerably. A few names dominate:

Change Healthcare (now Optum) — The largest clearinghouse by transaction volume in the U.S. Nearly every major payer connects through Change Healthcare's network. The 2024 cyberattack that took Change Healthcare offline for weeks exposed just how much of U.S. claims infrastructure depends on a single intermediary.

Availity — A payer-owned clearinghouse with strong connectivity to BCBS plans and broad commercial payer reach. Availity's portal is also widely used for eligibility verification and claim status checks independent of EDI submissions.

Waystar — Formed from the merger of Navicure and ZirMed, Waystar has built a strong presence in mid-size and enterprise health systems, with analytics and denial management features beyond basic claim routing.

Trizetto (Cognizant) — Common in larger health systems and billing companies; strong on institutional claims and complex payer environments.

Office Ally — A lower-cost option popular with small practices; less feature-rich than enterprise options but functional for straightforward claim volumes.

Apex EDI / Claim.MD / others — Various regional and specialty clearinghouses serve specific niches or geographies.

Your practice management system almost certainly has preferred clearinghouse integrations — some PMS platforms have exclusive relationships, others let you choose.

The Value Clearinghouses Add (When They Work Well)

At their best, clearinghouses provide:

Speed. Claims that go through a clearinghouse with strong payer connectivity and fast routing reach payers sooner than almost any alternative. Faster submission means faster adjudication means faster payment.

Error prevention. Pre-submission scrubbing catches errors before they become payer denials. For practices with high clean claim rates, the clearinghouse's edit library is doing real work.

Operational simplicity. One connection to one clearinghouse reaches hundreds of payers. Managing payer-specific EDI requirements, enrollment, and connectivity updates is the clearinghouse's problem, not yours.

Compliance. HIPAA mandates specific transaction standards for electronic claims. Clearinghouses maintain compliance with evolving standards so practices don't have to track regulatory changes to EDI specifications.

Visibility. A good clearinghouse portal gives you submission status, acknowledgment receipts, and rejection details in one place — a valuable audit trail when a payer claims they never received a claim.

Where Clearinghouses Fall Short

Clearinghouses are infrastructure. They route and validate claims. What they don't do — and were never designed to do — is work your AR, follow up on denials, or take action on what the claim responses tell you.

Rejections require human follow-up. A clearinghouse that flags a rejection has done its job. Correcting the claim and resubmitting it is still on your team.

Denials are invisible to the clearinghouse. Once a claim passes clearinghouse edits and reaches the payer, the clearinghouse's role is largely over. Payer denials that come back on the ERA aren't the clearinghouse's problem — they're yours.

Claim status queries return data, not action. The 276/277 transaction tells you a claim is pending or denied. It doesn't call the payer, escalate an issue, or do anything with that information. Acting on claim status still requires human judgment or additional automation.

Scrubbing quality varies and has limits. Clearinghouse edits catch formatting and structural errors. They don't catch clinical coding errors, medical necessity issues, or nuanced coverage mismatches — the kinds of errors that become denials after a human (or payer AI) reviews the claim.

The infrastructure risk is real. The Change Healthcare outage was a stress test that the industry largely failed. Practices and billing companies that routed everything through a single clearinghouse had no fallback. Redundancy — a second clearinghouse enrollment, direct payer connections for high-volume payers — is worth considering as risk management.

Do You Still Need a Clearinghouse?

The short answer: for most practices, yes — but it's worth understanding exactly what you're relying on them for, and what you're not.

Here's how the calculus breaks down:

You definitely still need a clearinghouse if:

• You bill more than a handful of payers (i.e., almost everyone)
• You want pre-submission claim scrubbing before claims hit payers
• You need ERA delivery integrated with your practice management system
• You want eligibility and claim status transactions flowing electronically
• You can't justify maintaining direct EDI connections to individual payers

You may be able to reduce clearinghouse dependency if:

• Your practice management system has direct payer connections for your top payers (some do — Epic and Athena, for example, have direct connections with major commercial payers and Medicare)
• You're a very high-volume biller who can negotiate and maintain direct connections cost-effectively
• You're willing to manage payer-specific enrollment and EDI requirement changes yourself

The questions worth asking about your current clearinghouse:

• What's your clean claim rate, and how much of that is attributable to clearinghouse scrubbing vs. upstream coding quality?
• How quickly are rejections returned, and what does your workflow look like for correcting and resubmitting them?
• Are your ERA enrollments complete, or are some payers still mailing paper EOBs that should be electronic?
• Do you have a backup plan — a secondary clearinghouse enrollment or direct connections — for your highest-volume payers?
• Are you actually using the claim status (276/277) functionality, or is your team still calling payers to check claim status manually?

That last question matters more than most billing leaders realize. The 276/277 infrastructure exists at the clearinghouse level. Whether your team or your tools are actually using it to eliminate manual payer calls is a separate operational question.

Clearinghouses and the Evolving RCM Technology Stack

It's worth being clear about where clearinghouses fit in a modern RCM technology stack — because their role is more narrow than their central position in claims flow might suggest.

A clearinghouse handles:

• Claim formatting and transmission
• Pre-submission edits
• ERA/EOB delivery
• Eligibility and claim status transactions (the infrastructure layer)

A clearinghouse does not handle:

• AR follow-up and denial management
• Appeals and resubmissions
• Patient billing and collections
• Payer call follow-up
• Denial trend analysis and root cause work

The gap between "the clearinghouse told me the claim was denied" and "the denial is resolved and the claim is paid" is where RCM teams spend the majority of their time — and where modern automation tools operate.

Tools that automate payer outreach, denial follow-up, and claim status calls work on top of the clearinghouse layer, using the transaction data the clearinghouse delivers as inputs. The clearinghouse gets the claim to the payer and the response back to you. What happens next is a different workflow entirely.

Choosing or Evaluating a Clearinghouse

If you're assessing your clearinghouse relationship — whether you're starting fresh or reconsidering an existing one — here are the factors that actually move the needle:

Payer connectivity breadth. Does the clearinghouse connect to every payer you bill? Check specifically for your Medicaid plans, specialty payers, and workers' comp carriers — these are where gaps appear most often.

Scrubbing rule depth and updates. How many edit rules does the clearinghouse run? How quickly do rules update when payers change requirements? A clearinghouse with outdated edit libraries will pass claims that should be caught.

Rejection turnaround time. How quickly are rejections returned after submission? Hours matter — same-day rejection visibility means same-day correction is possible.

ERA enrollment support. Does the clearinghouse actively help you enroll for ERA with payers where you're still receiving paper EOBs? Some clearinghouses are proactive here; others leave enrollment entirely to you.

Portal usability and reporting. Can you easily see submission status, rejection reasons, and historical claim data? Good visibility reduces the need for payer calls on basic status questions.

Support quality. When something breaks — a payer connection goes down, a claim type starts rejecting unexpectedly — how fast and effectively does support respond? This is often where clearinghouse quality differences are most visible in practice.

Pricing structure. Most clearinghouses charge per transaction. Understand the pricing for each transaction type — 837 submissions, 270/271 eligibility checks, 276/277 status queries — and whether your current usage pattern is cost-effective.

Redundancy and uptime. The Change Healthcare episode raised this issue for the entire industry. Ask directly: what's the clearinghouse's uptime SLA, and what's the contingency if their network goes down?

The Bottom Line

Clearinghouses are not glamorous. They don't generate excitement at revenue cycle conferences. But the claims translation, routing, and pre-submission scrubbing they provide are foundational to electronic billing — and most practices couldn't replicate that infrastructure independently.

What they are not is a complete RCM solution. They move claims. They don't work AR. The gap between claim submission and paid claim is filled by your billing team's work, your denial management processes, and increasingly by automation tools purpose-built for the follow-up and outreach that clearinghouses were never designed to handle.

So yes, you still need a clearinghouse — but you should be clear-eyed about what you're getting from it, what you're not, and whether the rest of your technology stack is filling the gaps it leaves behind.

SuperDial automates the payer outreach and claim follow-up that happens after the clearinghouse's job is done — eliminating manual calls for claim status, denial follow-up, and prior authorization without adding headcount. Learn how we help RCM teams close the gap between claim submission and collected revenue.

‍