By
November 15, 2026
10 min read
Why ABA Billing Software Breaks Down for Multi-Location Behavioral Health Providers
Why ABA billing is harder than almost any other specialty's billing
ABA billing breaks the assumptions built into most medical billing software because the unit of work isn't a visit, it's a block of time, billed in 15-minute increments, with modifiers that change by payer and by state, authorizations that expire on a rolling 90/60/30-day clock, and a credentialing requirement (BCBA, BCaBA, RBT) that has to be verified separately for every payer a clinic touches. Most practice management systems were built for appointment-based specialties. ABA is a time-based, session-stacked, authorization-gated specialty, and that mismatch is where the billing breaks down.
A single ABA claim can involve CPT codes like 97153 (adaptive behavior treatment by protocol) or 97155 (treatment with protocol modification), each tied to exact session minutes, a specific rendering provider credential, and a modifier set that differs depending on whether the payer is a commercial plan, a state Medicaid program, or a Medicaid managed-care organization operating in a different state than the clinic's home office. Get the modifier wrong, bill a session that ran one minute over the authorized block, or submit a claim after a renewal lapsed, and the claim bounces. Do that across six payers and three states, and the denial rate stops looking like noise and starts looking like a structural problem.
What is ABA billing software actually supposed to do
At a baseline, ABA billing or practice management software needs to do five things well: track authorizations with alerts before they expire, generate claims with the correct time-based CPT codes and payer-specific modifiers, match completed sessions to submitted claims (increasingly a compliance requirement, not a feature), scrub claims before submission to catch coding errors, and keep BCBA/RBT credential and supervision records current per payer.
The vendor field covering this is genuinely fragmented. Platforms like CentralReach, RethinkBH, Motivity, AlohaABA, Theralytics, and ClinicTracker each do a reasonable job of this for a single-state, single-entity practice. None of them has run away with the category, and that's worth noticing: when a market doesn't converge on a dominant platform after a decade, it usually means the underlying workflow resists standardization. ABA billing resists standardization because every state Medicaid program writes its own authorization and modifier rules, and payers inside the same state often disagree with each other too.
This is also why the top search results for "aba billing software" and "aba practice management software" are almost entirely vendor comparison pages and billing-service marketing. Every one of them is trying to sell a specific platform or outsourced billing service. None of them is written from the buyer's side of the table, which is exactly the gap a growing provider group runs into the moment it stops being one clinic.
Where off-the-shelf ABA platforms break down past a certain scale
The breaking point isn't a single number, it's a combination: once a provider group operates across more than two or three state Medicaid programs, carries more than roughly 15-20 locations, or employs more than 40-50 billable clinicians (BCBAs and RBTs combined), off-the-shelf ABA software tends to stop being "all-in-one" and starts being the system you configure workarounds around.
Three specific failure modes show up again and again in multi-location ABA groups, especially the PE-backed roll-ups that have been acquiring behavioral health clinics aggressively over the past several years (trade press like Behavioral Health Business tracks these deals on an ongoing basis, and the consolidation trend shows no sign of slowing):
Authorization tracking collapses at volume. A single-location practice can manage 90/60/30-day renewal windows with a shared spreadsheet and a diligent office manager. A 25-location group with a few thousand active authorizations across a dozen payers cannot. Most platforms surface an expiring-authorization dashboard, but dashboards require someone to look at them every day, and the failure mode isn't "the software didn't warn us," it's "we had 40 open alerts and missed three."
Credentialing sprawl multiplies with every acquisition. Each BCBA and RBT has to be credentialed, per payer, often per state, and re-verified on a schedule set by the Behavior Analyst Certification Board and by each payer's own re-credentialing cycle. When a platform acquires its fifth or sixth clinic, it's inheriting that clinic's clinicians, its payer contracts, and its credentialing status, all on different timelines. This is close to the exact problem Genta AI Solutions solved for a healthcare staffing firm, where credentialing workflows that took 120 days got cut to roughly 30 by automating document intake and verification instead of leaving it to manual tracking.
State-by-state rule conflicts don't resolve themselves. A platform configured correctly for California Medicaid rules will produce clean claims there and silently wrong ones in Texas or Florida, because modifier requirements, authorization unit definitions, and EVV obligations vary by state. Off-the-shelf software handles this inconsistently because it was built to be configured once, not re-configured per acquisition.
Does EVV apply to your ABA practice, and why it matters for claims
In most states, yes, and increasingly so. Electronic Visit Verification was mandated under the 21st Century Cures Act for Medicaid-funded personal care and home health services, and a growing number of states have extended EVV or EVV-adjacent verification requirements to behavioral health and ABA service delivery, particularly for sessions delivered in the home rather than a clinic. The federal guidance lives with CMS's EVV program rules, but implementation is state-by-state, which means a multi-state ABA group can be fully compliant in one state and exposed in another without realizing it.
The practical problem isn't philosophical, it's mechanical: EVV data (clock-in, clock-out, GPS or device verification, service location) has to match the session data on the claim before that claim can be considered clean. If the EVV system and the billing system are different tools that don't talk to each other reliably, someone on staff is manually reconciling two data sets for every session, every day, across every location. That reconciliation gap is one of the most common sources of claim rejections we see in behavioral health billing generally, and it compounds the authorization-expiry problem instead of standing apart from it.
Why ABA claim denial rates climb as provider count grows
Denial rates in ABA climb with scale because the error sources are additive, not averaged out. A single clinic with one state's rules and a handful of payers can hold a low denial rate through discipline and a good biller. A 30-location group operating across five states inherits five sets of modifier rules, five sets of authorization formats, and whatever credentialing gaps came with each acquisition. Every one of those is a distinct way to generate a denied claim, and they don't cancel each other out, they stack.
This is the same pattern we've written about in healthcare denial management more broadly: denial rates are rarely a training problem at scale, they're a systems problem, where the fix isn't "hire more billers" but "stop generating denials in the first place" by catching authorization expiry, modifier mismatches, and EVV gaps before the claim goes out, not after it bounces. The authorization-expiry piece specifically overlaps with what we've covered in prior authorization automation ahead of CMS's 2027 interoperability deadline, which applies to behavioral health payers as much as it does to any other specialty with time-boxed authorizations.
Build, buy, or augment: a decision framework for growing ABA groups
Most ABA groups don't need to rip out their practice management platform. They need to be honest about which layer is actually failing. Here's the framework we use when a client brings us this exact problem:
Buy (or keep what you have) if: you operate in one or two states, under 15 locations, and your denial rate is under roughly 8-10%. At this scale, a well-configured off-the-shelf platform plus a disciplined RCM process is usually cheaper and faster than building anything custom. The fix here is process, not software: tighter authorization calendars, a dedicated credentialing owner, cleaner payer contracts.
Augment if: your core platform handles claims generation fine but authorization tracking, EVV matching, or credentialing verification keeps falling through the cracks across locations. This is the most common situation we see, and it's rarely an "AI problem" in the way vendors pitch it. A thin automation layer that sits on top of your existing platform, pulling authorization expiry dates into a single queue, cross-checking EVV data against session logs, and flagging credentialing gaps before a claim goes out, often fixes 70-80% of the denial problem without a full rebuild. This mirrors what we found with a utility billing client: most of the revenue recovery came from process automation and system integration, not from anything exotic in the model itself. The diagnosis mattered more than the AI (see the case studies for the arithmetic behind that one).
Build if: you're past 30-40 locations across more than three states, acquiring new clinics on a regular cadence, and your platform's reporting can't give a CFO a clean, consolidated denial and authorization picture across the portfolio. At that point, the cost of continuing to patch around a platform not built for multi-entity, multi-state behavioral health billing usually exceeds the cost of a purpose-built authorization and claims workflow that owns your billing logic outright, built around your payer mix rather than a generic one.
What to ask before consolidating ABA billing across acquired clinics
If you're a COO or VP of RCM at a PE-backed platform mid-roll-up, bring these questions to every vendor conversation and every internal build decision:
Can the system show authorization status across every acquired clinic in one view, or does each location's data live in its own silo until someone manually consolidates it?
Does the platform handle multi-state modifier logic natively, or does it require a separate configuration (and a separate person who remembers it) per state?
How does EVV data get matched to claims, automatically or manually, and does that process differ by state?
Who owns BCBA/RBT credentialing tracking across payers today, and what happens to that tracking when you acquire a clinic with a different payer mix?
What's your current denial rate by location, and can you actually get that number broken out by clinic within a day, or does it take a week of manual pulls?
If the answer to the above is "we don't know," that's the tell that the platform, not the people, is the constraint.
If you're working through this decision, this is close to what our Discovery phase maps out before we recommend anything, and we're happy to compare notes or walk through what an authorization-and-billing automation layer would look like for your specific payer mix. For teams weighing whether to fix this with internal engineering or outside help, it's worth reading through how an automation layer gets scoped and built before committing either way.
The demand side of this problem isn't slowing down. The CDC's latest surveillance report puts autism spectrum disorder prevalence at 1 in 31 U.S. children, a 384% increase since 2000, which is a large part of why ABA provider groups keep growing and why PE platforms keep consolidating them. Billing systems built for a 3-location practice were never going to hold up against that growth curve without someone rethinking the workflow underneath them.
Frequently asked questions
What is the best ABA practice management software?
There isn't a single best platform; CentralReach, RethinkBH, Motivity, AlohaABA, and Theralytics all serve the category credibly, and the right fit depends on your state footprint, payer mix, and clinic count. For single-state practices under roughly 15 locations, the choice mostly comes down to support quality and reporting depth. Past that scale, the harder question is whether any off-the-shelf platform can hold up, not which one is "best."
What software do medical billing companies use for ABA claims?
Outsourced ABA billing services typically use the same core platforms providers use directly (CentralReach, RethinkBH, ClinicTracker) combined with internal clearinghouses and scrubbing tools layered on top. The value they add isn't usually proprietary software, it's dedicated staff tracking authorization windows and payer-specific rules across clients, which is the same operational gap multi-location providers eventually have to solve in-house or automate.
Why do ABA therapy insurance claims get denied so often?
Most denials trace back to three sources: authorization lapses (a session billed after the 90/60/30-day window expired), modifier errors on time-based CPT codes like 97153 and 97155 that vary by payer and state, and EVV data that doesn't match the submitted claim. None of these are rare edge cases; they're the default failure modes of the billing workflow itself, and they scale with provider count.
Does EVV apply to ABA therapy sessions?
In many states, yes, particularly for Medicaid-funded sessions delivered in the home. The federal EVV mandate under the 21st Century Cures Act covers personal care and home health services, and a number of states have extended equivalent verification requirements to behavioral health. Coverage varies by state, so a multi-state ABA provider needs to check requirements state by state rather than assume one policy applies everywhere, per CMS's EVV guidance.
How much does ABA billing software cost for a multi-location provider?
Off-the-shelf ABA practice management platforms typically run from roughly $100-$300 per clinician per month depending on feature tier, which adds up fast across a 30+ location group with dozens of billable clinicians. An augmentation layer (automating authorization tracking, EVV matching, or credentialing checks on top of an existing platform) is usually a fixed project cost in the tens of thousands rather than a recurring per-seat fee, and tends to pay for itself through reduced denials within one to two billing cycles.
