Clearinghouse
A clearinghouse is a third-party EDI intermediary that receives electronic claims, checks and reformats them, then forwards them to payers and returns electronic responses. A clearinghouse often also handles eligibility checks, electronic remittances, and claim status transactions between providers and payers.
What it means
What a clearinghouse is
A clearinghouse is a HIPAA-covered entity that sits between your billing system and your payers. It receives electronic transactions such as 837 claims and 270 eligibility requests, runs them through format and business-rule checks, converts them into the payer's preferred format, and routes them to the correct payer.
On the way back, the clearinghouse receives payer responses and status files. That usually includes 999 acknowledgements, 277CA claim status, 271 eligibility responses, and 835 electronic remittances. Your practice-management or RCM platform reads those files so you can see which claims passed, which rejected, what paid, and what denied.
From a compliance angle, a clearinghouse is a business associate or a covered entity under HIPAA, since it handles protected health information in EDI form. Contracts, BAAs, and connectivity setups all run through the clearinghouse before your first claim goes out.
Why clearinghouses matter operationally
Clearinghouse performance and configuration hit revenue directly. A bad setup or a narrow payer connection list can mean hundreds of claims stuck in clearinghouse rejection with zero cash coming in. Every day a claim sits in "rejected at clearinghouse" is an extra day in A/R and an extra day closer to timely filing limits.
Clearinghouses usually run front-end edits that catch missing or invalid data before claims reach the payer. That can be very valuable, but it can also mask payer-specific rules. If your clearinghouse is only running generic edits, your team may feel good about a high "accepted" rate, then get hammered by payer denials on the back end. The cost shows up as higher denial rate, more rework hours, and longer days in A/R.
For behavioral health, connectivity is as important as edits. A clearinghouse that connects to all the big commercial medical payers but has weak Medicaid MCO and carve-out coverage will look fine in a sales deck and fail you in production. Your real risk is that claims for your core BH book of business quietly sit in "cannot route" or "no connection" queues while commercial med-surg claims fly through.
How RCM teams use and read clearinghouse data
Operationally, your team should treat clearinghouse data as the first checkpoint in the claim's life. A clean workflow will:
- Monitor batch acknowledgements so you know a file was accepted.
- Review clearinghouse rejections daily, fix the claim-level issue, and resubmit.
- Distinguish rejections at the clearinghouse from denials at the payer in your reports.
- Use clearinghouse status to confirm whether a payer ever received the claim when you appeal.
Most clearinghouses expose claim status in a few key buckets: accepted, rejected, in process, forwarded to payer, and sometimes payer-accepted or payer-rejected based on 277CA. Your billing platform may surface these with slightly different wording, but you want to know two things on every account: did the clearinghouse accept the claim, and did the payer ever formally receive and acknowledge it.
For behavioral health episodes, especially residential, PHP, and IOP, watch segment-level edits. A single invalid revenue code or modifier on day 14 of a 30-day residential stay can cause the clearinghouse to reject the entire 837 file or the entire claim line. If you miss that in your daily clearinghouse work queue, the clock ticks on all 30 days for timely filing and your cash forecast for that month is wrong.
Common mistakes
- Treating clearinghouse rejections as payer denials in your denial-rate reporting, so residential and IOP claims that never reached the payer make your payer mix and denial metrics look worse and hide where the real fix belongs.
- Onboarding a clearinghouse without validating Medicaid and behavioral health carve-out connections for your top plans, then discovering that Optum Behavioral, Carelon/Beacon, or Magellan claims sit in "no connection" status while commercial BCBS claims get paid.
- Failing to configure all NPIs, taxonomy codes, and billing locations correctly at the clearinghouse, which leads to all claims from a new PHP site rejecting at the front end for weeks because the clearinghouse vendor profile was never finalized.
- Ignoring 999 and 277CA acknowledgement reports and only looking at the practice-management system's "submitted" status, so an 837 batch that never truly made it into payer systems is not caught until you see a thirty-day gap in payments.
- Relying entirely on generic clearinghouse edits for behavioral health coding, so claims with ASAM-level related revenue codes or telehealth modifiers 95 and 93 look "clean" at the clearinghouse but then deny at the payer for invalid coding or missing prior authorization.
Why it matters in behavioral health
Behavioral health revenue often runs through Medicaid, Medicaid MCOs, and separate behavioral health vendors that administer carved-out benefits. For those lines of business, clearinghouse reach into the right MCOs and BH vendors matters more than a big headline number of payer connections. A clearinghouse that connects to every commercial PPO but not your state's main behavioral health ASO is a real revenue risk.
Before you rely on a clearinghouse, validate that it connects to the specific behavioral health vendors your clients' plans carve out to. That usually means loading a list of your top payers by charge volume, then mapping each to the actual claims address or payer ID used for BH. Ask the clearinghouse to confirm support for those exact payer IDs and transaction types, including claims and 835 ERA.
In long-episode services such as residential treatment, PHP, and IOP, clearinghouse rejection management needs a daily rhythm. Per-diem or multi-unit claims that reject at the clearinghouse push the entire episode closer to timely filing risk and distort your A/R metrics. Your team should be able to quickly filter for high-dollar behavioral health claims rejected at the clearinghouse and get corrections out the same day.
Carve-outs and concurrent authorization rules add another wrinkle. A claim can clear the clearinghouse but still deny at the BH vendor if days exceed the authorized units. You want clearinghouse edits tuned to catch the basics, then payer-side denial analytics that specifically track CO-197 and similar codes tied to concurrent auth limits.
How AI can help with Clearinghouse
AI agents can monitor and interpret clearinghouse data at the volume and speed humans cannot sustain. An AI agent can watch every 999 and 277CA file, recognize patterns like "all PHP claims from location X are rejecting for billing provider ID" and flag a configuration problem before it becomes a 4-week cash slowdown. It can also classify clearinghouse rejections by root cause and surface concise worklists for human billers instead of leaving them to dig through raw EDI.
Supabill's claims-scrubbing agent holds payer and clearinghouse rules in context, surfaces edit explanations in plain language, and routes each claim to the right follow-up queue. A separate denials and remittance agent reads every 835 and status response, so clearinghouse rejections never get mixed in with true payer denials. The limit is that AI cannot negotiate connectivity, sign contracts, or decide which clearinghouse networks you join. Humans still own vendor selection, payer escalations, and any judgment calls that involve policy risk or clinical nuances.
FAQ
How is a clearinghouse different from a billing system or practice management system?
A billing or practice management system is where you create encounters, charges, and claims. A clearinghouse is the EDI post office and rule engine that sits between that system and the payer. The clearinghouse receives electronic files from your billing system, applies format and business-rule edits, converts them into each payer's accepted format, sends them along, then routes acknowledgements and remittances back. Some vendors bundle both functions into one platform, but under the hood the clearinghouse role and the practice-management role are still distinct layers. Source
Are clearinghouse rejections considered denials when calculating denial rate?
Operationally, no. A clearinghouse rejection means the claim never reached the payer's adjudication system, so there was no true payer decision to pay or deny. In denial-rate reporting you normally track clearinghouse rejections separately as front-end scrub errors, and only count payer-level denials from 835 and 277CA data as denials. That distinction matters in behavioral health, where configuration mistakes can cause large batches of Medicaid or residential claims to reject at the clearinghouse before they ever hit the BH vendor. Source
Can a provider submit claims without using a clearinghouse?
Yes, some payers support direct data entry on their portals or direct EDI connections, and small practices sometimes use those instead of a clearinghouse. The tradeoff is operational: managing multiple payer-specific connections or portals is time-intensive, and you lose the benefit of a single edit engine and a unified work queue. For multi-payer behavioral health programs, especially with many MCOs and carve-outs, a clearinghouse usually cuts down on manual portal work even if you keep a few high-volume direct connections. Source
What should a behavioral health provider ask a clearinghouse before signing up?
Start with a list of your top behavioral health payers by charge volume and ask the clearinghouse to confirm connectivity for those exact payer IDs, including Medicaid MCOs and any carved-out vendors such as Optum Behavioral or Carelon/Beacon. Confirm which transactions are supported for each payer, claims and 835 ERA are the minimum, and ask about their edit library for behavioral health codes, common revenue codes, and telehealth modifiers 95 and 93. Also clarify how soon you can see and work clearinghouse rejections after submission, since long-episode services are sensitive to delays. Source
Who is responsible for HIPAA compliance when using a clearinghouse?
Under HIPAA, clearinghouses are covered entities when they translate nonstandard data into standard EDI for another covered entity, and are usually also business associates to providers. You, as the provider, are responsible for having a compliant contract and BAA in place and for managing user access to the clearinghouse portal. The clearinghouse is responsible for securing the EDI environment and handling PHI according to HIPAA rules. CMS provides general guidance on how clearinghouses fit into the HIPAA Administrative Simplification framework. Source
Related terms
Clean Claim Rate is the percentage of submitted claims that pass payer and clearinghouse edits and can be paid without correction. The metric tracks how many claims are accepted on the first pass, with no rework needed.
Remittance advice is the payer's official notice explaining how a claim was paid, adjusted, or denied, usually sent electronically in the HIPAA 835 format. An ERA lists allowed amounts, patient responsibility, payer write‑offs, and denial or adjustment codes for each claim and service line.
Denial rate is the percentage of submitted claims that are denied by payers during a defined period. The metric can be calculated based on claim counts or dollar amounts and is usually reported at first submission or across the full claim lifecycle.
Coordination of benefits (COB) is the process payers use to decide which plan pays first when a patient has more than one active policy, and how the remaining balance can be billed to other coverage. Coordination of benefits affects claim routing, payment order, and how much a behavioral health provider can collect from each payer and from the patient.
Related denial codes
Claim lacks information or has a submission error
Procedure code inconsistent with modifier / missing modifier