What a clearinghouse actually does between your claim and the payer.
"The clearinghouse accepted it" gets treated as good news more often than it should. A clearinghouse is a real and useful checkpoint, but it's checking one narrow thing — whether the claim is structurally correct — and that's a different question from whether the payer is going to pay it.
Key takeaways
- 837 out, 835 back. The claim travels as an 837P or 837I; the payer's response comes back as an 835 remittance.
- The clearinghouse validates format, not coverage. It checks whether the claim is legible and complete — not whether the payer owes you money.
- Acceptance and payment are two separate gates. A claim can clear the clearinghouse perfectly and still be denied by the payer.
- Companion guides are free payer-specific rules. Payers and clearinghouses publish their own field requirements — use them before reverse-engineering the same rules from denials.
The transaction flow: how a claim actually travels
The path from encounter to payment runs through a specific sequence of systems, and knowing where each checkpoint sits tells you what kind of problem shows up where. Your practice management or billing system compiles the encounter — codes, modifiers, diagnoses, identifiers, dates — into an 837 transaction: 837P if it's a professional claim (the electronic equivalent of a CMS-1500), 837I if it's institutional (the electronic equivalent of a UB-04). Both are HIPAA-standard formats, which means every payer that accepts electronic claims has to be able to receive and process them in this structure.
That 837 file doesn't go straight to the payer. It goes to a clearinghouse, which acts as an intermediary between your system and every payer you bill — often dozens of them, each with its own connection requirements. The clearinghouse validates the file, translates it if needed for the specific payer's system, and forwards it on. The payer receives the claim, adjudicates it — decides what's covered, what's paid, what's adjusted, and what's denied — and generates an 835, the electronic remittance advice, which flows back the same way: payer to clearinghouse to your system, where it's posted against the original claim.
Two files, two directions, two different jobs: the 837 asks the payer to pay, the 835 tells you what actually happened. Everything about scrubbing and clearinghouse validation concerns the outbound 837; everything about denial management and appeals concerns the inbound 835. Understanding which side of that line a given problem sits on is most of what determines whether the fix is a quick correction or a longer process.
What a clearinghouse validates — and what only the payer catches
A clearinghouse's checks are real and worth taking seriously, but they're narrower than the phrase "claims processing" tends to suggest. It confirms the 837 is structurally valid against the HIPAA transaction standard, checks that fields the standard requires are present and correctly formatted, applies any payer-specific companion guide rules that have been loaded into its system, and flags obvious problems — an invalid NPI format, a malformed date, a missing required segment. Where a claim fails one of these checks, it's typically rejected back to you immediately, often within minutes to hours, well before it would ever have reached the payer at all.
What a clearinghouse cannot do is adjudicate. It has no access to the patient's specific plan benefits, no visibility into whether a particular procedure is covered under that plan's terms, no way to evaluate medical necessity against the payer's coverage policy, and no record of whether a prior authorization was actually obtained and is on file. All of that lives entirely inside the payer's own adjudication system, and none of it is checked until the claim has already passed clearinghouse validation and arrived there.
| Checkpoint | Validates | Does not validate |
|---|---|---|
| Clearinghouse | 837 structure, required fields, format, payer companion-guide rules | Coverage, medical necessity, benefit status, prior authorization on file |
| Payer adjudication | Coverage, medical necessity, benefits, coordination of benefits, contracted rate | Nothing upstream — by the time it reaches here, the file is assumed structurally sound |
Why acceptance isn't payment
This is the distinction that costs practices the most when it's missed: a clearinghouse acceptance message is not a payment commitment, and treating it as one is exactly how a preventable denial reaches a payer instead of getting caught earlier. A claim can be a perfectly formatted 837 — every field present, every identifier correctly matched, every code current — and still be denied, because the diagnosis doesn't support medical necessity under that payer's policy, or the patient's benefits for that service were already exhausted, or a required prior authorization was never obtained. None of those are things a clearinghouse checks, because none of those are format problems.
The practical habit this argues for is simple: stop treating a clearinghouse acceptance report as confirmation that a claim is clean, and start treating it as confirmation of one thing only — that the claim is legible enough for the payer to actually look at it. What the payer decides once it does look is a separate question, answered only when the 835 comes back, and a scrubbing program that only checks what the clearinghouse checks is only solving half the problem.
Companion guides: payer-specific rules you don't have to reverse-engineer
Most payers and clearinghouses publish companion guides — documents describing that specific payer's additional field requirements layered on top of the baseline 837 standard. These are worth building directly into your submission process, because unlike the payer-specific edits you build from your own denial history, a companion guide is a rule the payer has already written down for you. It doesn't require a single denied claim to discover it.
Practices that never look at companion guides end up discovering the same rules the hard way, one rejected or denied claim at a time, when the information was published and available the whole time. Pulling the companion guide for each payer you bill regularly, and checking your submission process against it once, is a small amount of work that prevents a category of errors that would otherwise take months of remittance data to identify on your own.
Not sure what your clearinghouse is actually catching?
We review your clearinghouse edit configuration against your payer mix's own companion guides, and close the gaps that let preventable denials through.
Frequently asked questions
What transaction format does a clearinghouse process?
The 837 — 837P for professional claims (the CMS-1500 equivalent) and 837I for institutional claims (the UB-04 equivalent). Both are HIPAA-standard electronic transactions. The payer's response comes back as an 835, the electronic remittance advice, which reports what was paid, adjusted, or denied.
Does clearinghouse acceptance mean the payer will pay the claim?
No. A clearinghouse validates that the 837 file is structurally correct and complete — it has no visibility into coverage, medical necessity, benefit exhaustion, or prior authorization status. Those decisions belong to the payer's adjudication system, which runs after the clearinghouse has already passed the claim through. A claim can clear the clearinghouse and still be denied by the payer.
What is a companion guide?
A document a payer or clearinghouse publishes spelling out that payer's specific field requirements on top of the baseline 837 standard. Companion guides are one of the few sources of genuinely payer-specific submission rules that don't have to be reverse-engineered from denial history, because the payer has already written them down.
Confirm before you rely on this. Payer edit rules, clearinghouse requirements and timely filing limits change and vary by payer. The process information on this page reflects standard industry practice as of August 2026 and is provided for general education — verify current requirements directly with your clearinghouse and payer mix before relying on it.