ABA Denial Management: Why Claims Get Denied and How to Fix Them

A denied claim is rarely a surprise in hindsight. Someone booked one session too many. A note was missing. A code did not match the authorization. The real surprise comes later, when the payment was supposed to arrive and a denial shows up instead.

ABA denial management is the work of finding out why claims were denied, fixing and resubmitting them, and changing your process so the same denial does not come back. This guide covers the most common causes of denials in ABA, a simple way to work a denied claim, and what you can do before a claim ever goes out.

Where we mention MeasurePM, we are describing what the company says on its own website, and we will say so.

Why ABA claims are easy to get wrong

Billing for ABA is harder than billing for many other kinds of care. A few reasons stand out.

• Authorizations are unit-based. They approve a number of units within a set period, not a number of visits. Tracking units across many clients, services, and payers is a constant job.
• Several codes, several rules. Each ABA code has its own requirements for who can deliver the service, what documentation supports it, and which modifiers apply.
• Volume. Clients often get multiple sessions a week for a long time, and every session creates a claim. A small error rate still adds up to real money.
• Payers change their rules. A modifier that was optional last year may be required now.
• Documentation standards differ. What one payer accepts, another may not.

None of this means your billing team is doing something wrong. It means the work has more moving parts than a generic system expects.

The most common reasons ABA claims get denied

MeasurePM’s own guide to billing errors names the same handful of causes that show up again and again. Here they are, in plain terms.

1. Billing after an authorization has expired

Sessions keep running on the usual schedule, the authorization end date passes, and nobody notices. By the time denials arrive, weeks of sessions may be affected. Appeals are possible, but the payer’s position is simple: the service was delivered outside the approved period.

2. Going over the authorized units

Every session uses up units. If nobody tracks the running total, a practice can deliver and bill past the approved amount. Claims above the limit get denied, and because the limit is clearly written down, these denials are hard to overturn.

3. The wrong code or modifier

The service delivered, the credential of the person delivering it, and the supervision setup all affect which code applies. Use the wrong code, or the right code with the wrong modifier, and the claim can be denied. The cause is often not obvious from the claim itself, so sorting it out takes time.

4. A credential that does not match the service

A service that needs a BCBA delivered by an RBT. A staff member whose credential has lapsed. Each of these can lead to a denial, and each tends to happen where credential checks depend on someone remembering to do them.

5. Missing or thin documentation

Payers can review claims, and the notes need to show that the service happened, made clinical sense, and was delivered by a qualified person. Vague or incomplete session notes put the claim at risk.

6. Duplicate claims

A claim goes out, no confirmation comes back, someone sends it again, and now two versions exist. Payers can flag the duplicate, and that can cause trouble even for the legitimate original.

7. Missed filing deadlines

Every payer has a deadline for submitting claims, usually counted from the date of service. A claim that misses it can be denied with no real path to recovery.

Where each denial is best caught

Look at that table again. Most of these can be stopped before the claim exists. That is where your effort pays off the most.

How to work a denied claim, step by step

When a denial lands on your desk, use the same steps every time. A routine keeps small problems from piling up.

1. Read the reason the payer gave. Write it down as stated, not as you assume it meant.
2. Sort the cause. Was it an authorization issue, a coding issue, a documentation issue, or something else? Use the categories above.
3. Gather what you need. That usually means the session documentation, the authorization record, and the staff credentials tied to the claim. It helps a lot when these are in one place.
4. Correct and resubmit, or appeal. Check your payer’s rules for how and when to do either.
5. Record the cause. Add it to your denial log (more on that below).
6. Follow the claim until it is paid. A resubmitted claim can come back denied again.

Be honest with yourself about appeals, too. For expired authorizations and extra units, MeasurePM’s guide says appeals are difficult and often unsuccessful. That is a good reason to put your energy into prevention.

Build a denial log, and actually read it

Fixing claims one at a time keeps you busy. Reading your denials as a group tells you what to change. A simple spreadsheet is enough. Track these columns:

• Date of denial
• Client ID (use an ID, not a name, in shared files)
• Payer
• Code and units
• Reason given by the payer
• Your cause category, such as authorization, coding, or documentation
• Who fixed it
• Outcome and date paid

Once a month, sort by cause. If most of your denials come from authorization problems, you may not have a billing problem at all. You may have a scheduling problem, and that calls for a very different fix.

Prevention beats appeals

Think of three checkpoints: before the session, after it, and before the claim goes out.

Before the session: scheduling checks

Many denials trace back to the schedule. On its billing page, MeasurePM notes that practices tracking authorizations by hand often catch mismatches only after a claim is denied. Good ABA scheduling software should know a client’s authorization and a staff member’s credentials before a session is confirmed. According to its website, MeasurePM checks staff credentials before a session is booked and builds schedules with client authorizations in mind.

After the session: documentation

Notes are easier to get right while the session is fresh. ABA data collection software helps when session records live in the same system as your claims. MeasurePM’s billing page says session documentation from its data collection tool supports the same claim your billing team is tracking, so the records and the claim stay consistent.

Before submission: a quick review

A short checklist catches a lot. MeasurePM’s own revenue cycle checklist suggests a few habits worth copying:

• Require completed session notes before claims are submitted
• Review coding before submission
• Track authorization use every week
• Make sure clinical staff know each payer’s documentation requirements

Automation can take some of this off your plate. MeasurePM says claims generate and submit automatically once a session is complete, and that billing connects to scheduling, so each claim traces back to a session that was actually authorized. Your team can then spend its time on exceptions instead of data entry.

What to look for in denial management software

Not every tool handles this the same way. MeasurePM’s guide to common ABA billing errors describes what purpose-built billing software should do, and it makes a handy shopping list:

• Authorization dates and units tracked in real time, with alerts as limits get close
• Scheduling connected to billing, so sessions past an authorization end date are hard to book
• Codes and modifiers tied to the service type and the provider’s credential
• Provider credentials tracked, with warnings before they expire
• Documentation visible before a claim goes out
• A check for duplicate claims
• Filing deadlines tracked by payer
• HIPAA-compliant handling of client data

On its billing page, MeasurePM also says denials are tracked and managed in the same system that submits claims, with a KPI dashboard showing revenue, utilization, and claims performance. As with any tool, ask to see it work on a real claim.

Mistakes that keep denials coming back

• Fixing the one claim but never asking why it was denied
• Having no clear owner for denials, so everyone assumes someone else has it
• Waiting until the end of the month to look at the numbers
• Never telling clinical staff what billing needs from their notes
• Assuming every payer follows the same rules, when requirements differ by payer

The last one catches many clinics. A short cheat sheet for each of your main payers can save a lot of rework.

Where MeasurePM fits

MeasurePM is an all-in-one, HIPAA-compliant ABA platform that combines data collection, scheduling, and billing. The company says more than 10,000 providers use it, including about 750 BCBAs, and it reports a billing collection rate in the high 90s. Those are the company’s own figures, so test them against your own claims. Every feature described in this guide comes from the company’s website.

It will not be the right fit for every clinic. If you are still comparing options, our guide to the best ABA practice management software covers what is out there.

Frequently asked questions

What is ABA denial management?

It is the process of tracking denied claims, finding the cause, fixing and resubmitting or appealing them, and changing your workflow so the same problem does not repeat. Good denial management looks at patterns, not just single claims.

What are the most common reasons ABA claims are denied?

According to MeasurePM’s guide to billing errors, the usual causes are billing after an authorization expires, going over authorized units, using the wrong code or modifier, a credential that does not match the service, missing documentation, duplicate claims, and missed filing deadlines. Your own denial log will show which ones hit your clinic hardest.

Can denials for expired authorizations or extra units be appealed?

You can try, but MeasurePM’s guide says these are difficult to appeal and often unsuccessful, because the authorization limits are clearly documented. That is why catching them before the session or the claim is the better plan.

Can software reduce the time spent on denials?

It can help in two ways. Better checks before submission mean fewer preventable denials. And when a denial does happen, having session documentation, authorization records, and staff credentials in one system makes it faster to gather what you need. Software does not replace staff judgment, though. Someone still has to own the process.

Is billing connected to scheduling in MeasurePM?

Yes, according to MeasurePM’s billing page. Every claim is linked back to a scheduled session that was authorized, and denials are tracked and managed in the same system that submits claims.

The bottom line

Strong ABA denial management has two parts. You work the denials you already have, and you fix the habits upstream that create them. Most of the savings come from the second part: booking with authorization in mind, documenting right away, and reviewing claims before they leave.

If you want to see how scheduling, documentation, and billing work together on a real claim, you can book a free demo and walk through your own workflow.