Why ABA Claims Get Denied — and How to Fix the Pattern

Denials are noisy. They feel random in the moment — one comes back for a missing auth, another for a modifier, a third because the payer thinks the client wasn't eligible. But over a few weeks, the noise turns into a shape.

In many clinics, a handful of repeat denial reasons cause most of the damage. Find those, fix the process behind each one, and your collections can climb without changing a single clinical hour.

The usual suspects

In ABA, the denial reasons we see most often are:

• Missing or expired prior authorization
• Modifier mismatch (HO, HM, HN, U-series — rules vary by payer; see the CPT codes to watch)
• Eligibility lapse on date of service
• Duplicate claim from re-submission without a corrected-claim indicator
• Place-of-service code that doesn't match the payer's policy

None of these are clinical problems. They're process problems. They happen because someone, somewhere in the workflow, didn't have the right information at the right time.

On the EOB, each denial carries a reason code. The exact codes vary a little by payer, but the same few show up again and again: CO-197 when an authorization is missing, CO-4 when the modifier doesn't fit the code, CO-27 when coverage had ended before the date of service, CO-18 for a duplicate, and CO-5 when the place of service doesn't match.

How to find your pattern

Pull your last 60 days of EOBs and group denials by reason code. (Unworked denials are also why AR keeps growing.) You don't need fancy software — a spreadsheet works. Sort by frequency. The top three are your fix list.

For each one, ask: where in the workflow does this break? Auth issues usually trace back to intake. Modifier issues usually trace back to the biller working from outdated payer rules. Eligibility issues usually trace back to the front desk skipping a check.

Fix the process, not the claim

Reworking and resubmitting a denied claim recovers the money once. Fixing the process recovers it every week after. Once you know your top denial reason, build a small check into the workflow that catches it before submission — not after.

A 30-minute weekly denial review

You don't need a big project. You need the same short routine every week:

1. 1Pull every denial that came back this week.
2. 2Tag each one with its reason code and the step in the workflow where it started.
3. 3Work each one within 2 business days: fix it, appeal it, or write down why it can't be won.
4. 4Look at your top reason and add one check upstream that would have caught it.
5. 5Next week, see whether that reason came back.

This is the weekly rhythm behind payments and denials.