ABA Billing Denial Codes Explained: What Every Code Means and How to Fix It Fast

Denials Are Not Dead Ends — They're Diagnoses

Every denial code is a message. Payers aren't just saying "no" — they're telling you exactly what broke down in the claim, the authorization, the eligibility check, or the documentation. The agencies that recover denied revenue fastest are the ones that treat denial codes like diagnostic data, not paperwork.

This guide walks through the denial codes that show up most often in ABA billing, what's actually causing them, and the steps your billing team should take within 24–48 hours of receiving each one.

How to Read a Denial: ERA vs. EOB

Before diving into specific codes, it's worth clarifying where you'll find them. Most commercial payers and Medicaid managed care plans send Electronic Remittance Advices (ERAs) with standardized codes in two formats:

• CARC (Claim Adjustment Reason Code): The primary denial or adjustment reason — attached to every line or claim-level denial.
• RARC (Remittance Advice Remark Code): A secondary code that adds detail to the CARC. Often the most actionable part.
• Group Code: Tells you who is financially responsible — CO (contractual obligation), PR (patient responsibility), OA (other adjustments), or PI (payer initiated).

When your ERA lands, the combination of Group Code + CARC + RARC tells the full story. Reviewing only the CARC and skipping the RARC is one of the most common reasons rework takes longer than it should.

The Most Common ABA Billing Denial Codes

CO-4 — Service Not Covered / Inconsistent with Modifier

What it means: The procedure code and modifier combination you submitted doesn't match what the payer expects for that service category.

In ABA billing this usually means: You billed a 97153 (adaptive behavior treatment) with a modifier the payer doesn't accept, or used the wrong place-of-service code alongside it. Some payers require a specific modifier to distinguish telehealth from in-person; others restrict certain modifiers to supervising BCBAs only.

Fix it: Pull the payer's fee schedule and billing guidelines. Confirm the exact modifier rules for each CPT code. Resubmit with the corrected modifier combination. If you believe your original submission was correct, initiate a formal appeal with the payer's billing manual as supporting documentation.

CO-11 — Diagnosis Inconsistent with Procedure

What it means: The ICD-10 diagnosis code on the claim doesn't support medical necessity for the billed procedure.

In ABA billing this usually means: The claim went out with a diagnosis code that isn't on the payer's covered diagnosis list for ABA services. Some payers only cover ABA under F84.0 (Autistic disorder). Others have expanded to include F84.5, F41.x, or intellectual disability codes — but only with specific clinical criteria met in the authorization.

Fix it: Cross-reference the diagnosis on file with the payer's covered diagnosis policy. If the correct diagnosis is documented in the clinical record but was entered incorrectly on the claim, this is a clean corrected claim. If the diagnosis genuinely isn't covered, a peer-to-peer review or formal appeal with clinical documentation may be required.

CO-15 — Authorization / Precertification Missing or Invalid

What it means: The service was rendered without a valid prior authorization, or the auth number on the claim doesn't match the payer's records.

In ABA billing this is one of the most expensive denial types. Services rendered outside of authorized dates, beyond authorized units, or under an expired auth all trigger this code.

Fix it:

1. Verify the auth number was included on the claim and matches exactly what's in the payer portal.
2. Check authorized dates — did the service date fall within the auth period?
3. Check authorized units — was the claim submitted for more units than the auth covered?
4. If the auth was valid and the denial is a payer error, submit a corrected claim with documentation of the authorization.
5. If services were legitimately rendered outside authorization, contact the payer immediately about a retro-authorization — timelines vary by payer and state.

Authorization tracking gaps are the root cause here. Agencies that monitor remaining units in real time — rather than auditing after the fact — catch this before the claim is ever submitted.

CO-22 — Coordination of Benefits (COB)

What it means: The payer believes another insurance plan is primary, and you didn't submit a COB claim correctly.

In ABA billing this often surfaces: when a client has both private insurance and Medicaid. Medicaid is almost always the payer of last resort. The commercial plan must be billed first, and the EOB from the commercial plan must accompany the Medicaid claim.

Fix it: Obtain the correct primary payer information from the family. Bill the primary payer, collect the EOB, then submit to the secondary with the primary's EOB attached. Update your eligibility records to reflect the correct payer order going forward.

CO-97 — Payment Included in Another Service

What it means: The payer considers the billed service to be bundled into another procedure already paid on the same date of service.

In ABA billing this typically hits: when a BCBA bills 97155 (protocol modification) on the same date as 97153, and the payer's system auto-bundles them. It can also occur when assessment codes (97151, 97152) are submitted alongside treatment codes on the same date without proper documentation that they were distinct, separately identifiable services.

Fix it: Review the payer's bundling edits. If the services were genuinely separate and medically necessary, submit an appeal with session notes demonstrating that the assessment and treatment activities were distinct. Some payers require a modifier (e.g., 59 or XE/XS) to override the bundling edit.

CO-167 — Diagnosis Not Covered

Similar to CO-11 but applied at the claim level rather than the line level. The entire claim is denied because the diagnosis isn't on the payer's covered list for ABA. Appeal pathway: submit clinical records supporting medical necessity and reference the payer's coverage policy language. In some states, autism insurance mandates require coverage regardless of internal payer lists — cite the statute in your appeal.

PR-204 — Service Not Covered / Not a Covered Benefit

What it means: The Group Code PR means patient responsibility — the payer is saying this isn't a covered benefit under this specific plan.

In ABA billing: Some employer-sponsored plans have ABA exclusions even in states with autism mandates, because self-funded ERISA plans are exempt from state mandates. This is a billing dead end with most payers, but it's worth verifying the plan type before writing it off. If the plan is fully insured, the state mandate applies and you can appeal.

Quick-Reference Denial Code Table

What to Do in the First 48 Hours After a Denial

Time is money in denial management. Most payers have appeal windows of 90–180 days from the denial date — but the longer a denial sits, the more it gets buried. Set up a workflow that forces action within two business days of an ERA posting.

1. Tag the denial by code and payer so you can spot patterns. A single CO-15 is a one-off fix. Fifteen CO-15s from the same payer in one week is an authorization workflow problem.
2. Separate clean corrected claims from formal appeals. A billing error (wrong modifier, typo in auth number) gets a corrected claim. A clinical dispute (payer says not medically necessary) gets an appeal with documentation.
3. Document every action. Note the date, what was submitted, who you spoke to, and the reference number. If a denial escalates to external review, this paper trail is your evidence.
4. Track the resubmission. A denial resolved but never resubmitted is revenue that never comes back. Follow up on every corrected claim and appeal until it posts as paid or you have a final determination.

The Denial Patterns That Point to Upstream Problems

Individual denials get fixed claim by claim. But denial patterns reveal process failures that will keep generating revenue loss until you fix the root cause.

If you're seeing CO-15 repeatedly, your authorization tracking isn't alerting staff before units are exhausted. If CO-22 keeps appearing, your eligibility verification at intake is missing secondary coverage. If CO-11 is recurring, your intake or credentialing process isn't checking covered diagnosis policies by payer before enrollment.

Running a monthly denial analysis by CARC code and payer is one of the highest-ROI activities a billing manager can do. It turns reactive rework into proactive process improvement.

When to Escalate to an External Appeal

If an internal appeal is denied and you believe the service was medically necessary and covered under the plan, most states give you the right to an Independent Medical Review (IMR) or external appeal. This is especially relevant for CO-167 and medical necessity denials. The external reviewer is a neutral third party — and in ABA, where clinical outcomes data is strong, external reviews often reverse payer denials. Don't skip this step on high-dollar claims.

How Documentation Quality Affects Denial Rates

Many denials that look like billing problems are actually documentation problems in disguise. A claim denied for medical necessity usually means the session notes in the payer's system didn't support the level of service billed. Before submitting any appeal on a CO-50 or CO-167, pull the session notes and ask honestly: do these notes clearly document the treatment goals, the specific interventions used, and measurable progress? Vague notes lose appeals. Specific, data-driven notes win them.

This is why documentation audits — reviewing notes before claims go out — are the most cost-effective denial prevention tool available to ABA agencies. Catching a note that doesn't support 97155 before the claim submits is infinitely cheaper than chasing an appeal 60 days later.