Official X12 description
“Type of bill is inconsistent with patient status.”
Source: X12 Claim Adjustment Reason Codes. The X12 External Code Lists are the single authoritative source for every CARC descriptor — always verify against the current release before building a claim-scrub rule.
What CARC 306 actually means
CARC 306 denies institutional claims where TOB (type-of-bill) and patient-status discharge code don't align — e.g., outpatient TOB with inpatient discharge status. Correct and resubmit.
Common root causes
- TOB/discharge-status mismatch.
Prevention checklist
- Institutional claim scrubber validates TOB + discharge status + patient-type triplet.
Appeal strategy — step by step
Most CARC 306 denials clear faster with the right remediation than with a formal appeal. Work the steps in order and escalate only when a lower-effort path has been ruled out.
- 1Correct and resubmit.
Sample appeal-letter language for CARC 306
Edit the bracketed fields before sending. This template is a starting point; a payer-specific appeal form may still be required — check the provider portal first.
Payer-specific notes
Payer-specific behavior for CARC 306 publishes here as the QuickIntell anonymized denial ETL ingests sufficient volume. In the meantime, consult the payer directory for the relevant provider manual and appeal form.
How common is CARC 306?
Out of 306 seeded CARCs, ranked by combined US monthly search volume for "CARC 306", "CO-306 denial", and "denial code 306".
Platform frequency ranks publish once the anonymized denial-rate pipeline reaches the publication threshold (strategy §12 Phase 2).
How QuickRCM prevents CARC 306
QuickRCM catches the root causes above before the 837 leaves the clearinghouse:
- Claim-scrub rules fire on every root cause listed above — the scrub references the same X12 CAS segment logic that drives the denial, so what the payer checks, QuickRCM checks first.
- When a denial lands, QuickRCM routes it to the correct worker with the documentation bundle already attached (op note, LCD citation, modifier rationale, EOB, primary 835).
- Appeal templates tuned to each CARC (including this one) pull the supporting facts from the claim and fill the bracketed fields automatically.
Frequently asked questions — CARC 306
What does CARC 306 mean?
CARC 306 is an X12 Claim Adjustment Reason Code. The official definition is: "Type of bill is inconsistent with patient status." In plain English, the payer is telling you cARC 306 denies institutional claims where TOB (type-of-bill) and patient-status discharge code don't align — e.g., outpatient TOB with inpatient discharge status. Correct and resubmit.
How do I resolve a CARC 306 (CO-306) denial?
Start with the most common root cause: TOB/discharge-status mismatch. First step: Correct and resubmit. See the full remediation and appeal checklist on this page before filing a formal appeal.
Is CARC 306 patient responsibility?
No — CARC 306 is typically carried under CO (Contractual Obligation) or OA (Other Adjustment), which means it is the provider's responsibility, not the patient's. Do not bill the patient unless the 835 CAS group code is PR.
What does CARC 306 look like on an EOB or 835 remittance?
On the 835 ERA, CARC 306 appears in Loop 2110 CAS segment as "CAS*CO*306*{amount}". On a paper EOB the same code prints in the Adjustment/Denial Reason column with the X12 description: "Type of bill is inconsistent with patient status." — usually paired with one or more RARC remark codes in the same remittance line for additional context.
Can CARC 306 be appealed successfully?
Yes — when the root cause does not apply to the specific claim. Overturn rates are strongest when the appeal cites the X12 definition, the payer's own published policy, and documentation that rebuts the payer's rationale. The sample appeal language block above is a starting point; always adapt it to the payer's reconsideration form.
Disclaimer
This page is operational reference for medical-billing professionals. It is not legal, clinical, or contractual advice. X12 code descriptors are maintained by the X12 External Code Lists; always verify against the current X12 release and the payer's own published policy before submitting or appealing a claim.