Why ABA Billing Falls Behind: Authorization Units, Concurrent Codes, and the Staffing Fix

ABA practices rarely fall behind on billing because nobody is working. They fall behind because the workload is shaped differently than the workflows built to handle it.

Most billing processes, and most billers, are trained around a visit-based model: one patient, one clinician, one encounter, one claim. ABA does not work that way. A single client can generate 20 to 40 hours of billable service per week, delivered in 15-minute units, by multiple people with different credentials, sometimes at the same time, all drawing down against a fixed pool of authorized units that expires on a date the payer chose.

When a workflow designed for encounters meets a service line built on units, three things happen in a predictable order: authorizations run out before anyone notices, concurrent sessions trip claim edits nobody anticipated, and days in AR climbs while the team reworks claims that should have been clean the first time.

This guide walks through where ABA billing actually breaks down and what a staffing model that keeps up with it looks like. For a full walkthrough of the code set, modifiers, and payer rules, see the ABA billing guide.

Why ABA Billing Is Structurally Different

Before looking at the individual failure points, it helps to name the structural differences, because they explain almost everything downstream:

• Unit-based, not visit-based. Nearly the entire adaptive behavior code set is billed in 15-minute units. A three-hour technician session is 12 units of a single code, and the payer authorized a finite number of those units.
• High volume per client. A comprehensive treatment recommendation can run 25 or more hours per week. One client can produce more claim lines in a month than a therapy client produces in a year.
• Multiple rendering credential levels. Registered Behavior Technicians (RBTs) deliver most direct treatment, Board Certified Behavior Analysts (BCBAs) assess, direct, and modify protocols. Payers care which level rendered each line, and many require modifiers to say so.
• Legitimate overlap. A BCBA directing a technician mid-session is a real, billable clinical event under many plans. It also looks exactly like a duplicate or overlapping claim to an automated edit.
• Authorization is the ceiling on revenue. There is no eligibility-and-go in ABA. Almost every payer requires prior authorization for assessment and treatment, and the authorization defines exactly how many units of which codes may be billed in which window.

None of this is exotic to someone who works ABA claims daily. All of it is exotic to a biller who spends most of the week on E/M visits and psychotherapy codes.

The 97151 to 97158 Code Family

The Category I adaptive behavior services codes took effect in 2019 and remain the core of ABA billing:

All of these are 15-minute timed codes. That single fact drives most of the operational complexity: unit counting, rounding rules, session note start and stop times, and the burn-down math covered below. A smaller set of Category III codes (0362T and 0373T) exists for severe destructive behavior protocols, with their own staffing and setting requirements.

Two practical wrinkles catch teams constantly:

• Credential modifiers. Many Medicaid programs and some commercial plans require modifiers such as HO, HN, or HM to identify the rendering credential level, and some require the supervising BCBA's NPI on technician-rendered lines. The same code, billed identically for two payers, can be right for one and denied for the other.
• Same-day combinations. Payers publish rules about which codes can appear together on the same date of service, particularly 97151 alongside treatment codes and 97155 alongside 97153. These rules are payer-specific and change.

Why Unit-Based Authorizations Break Standard Billing Workflows

In most outpatient specialties, an authorization is a gate you pass through once. In ABA, the authorization is a budget you spend down every single day, and the billing function is responsible for knowing the balance.

A typical ABA authorization might grant, for a six-month period: a set number of 97153 units per week, a monthly or weekly allocation of 97155 for protocol modification, a smaller allocation of 97156 for caregiver guidance, and a defined number of 97151 units for reassessment near the end of the period.

The burn-down problem

Here is the failure mode. Scheduling is done by the clinical team based on the treatment plan. Billing is done after sessions happen. Nobody in that loop is comparing scheduled hours against remaining authorized units. So the practice delivers week 22 of a 24-week authorization at full intensity, exhausts the 97153 pool in week 23, and delivers week 24 with no units left. Those sessions are either written off or billed and denied. The clinicians did their jobs. The revenue is simply gone.

The reverse failure is quieter but also expensive: authorized units that expire unused because cancellations and callouts were never made up. The next authorization request then has to explain why the practice is asking for more units than it used, which invites a reduction.

What authorization burn-down tracking actually requires

Practices that stay ahead of this run a standing burn-down process, usually weekly:

• A tracker, per client and per code, showing units authorized, units billed, units scheduled but not yet billed, and units remaining
• Projected exhaustion dates based on the current delivery pace, not the authorized pace
• A reauthorization clock that starts 30 to 45 days before the end date, because the request needs updated assessment data, a progress report, and often a treatment plan revision from the BCBA
• Alerts when utilization drifts meaningfully above or below plan, in either direction

This is genuine, recurring work. It does not happen as a side task of claim submission, and it is the single most common thing missing in ABA practices whose AR is aging. A dedicated prior authorization support function, tracking every active authorization against actual delivery, is the difference between reauthorizations that land before the gap and treatment weeks delivered on hope.

Concurrent Sessions and Overlapping-Time Edits

ABA is one of the few outpatient services where two clinicians can legitimately bill for the same client at the same time. The standard example: an RBT delivers 97153 while the BCBA is present for part of the session delivering 97155, observing, directing the technician, and modifying the protocol.

Whether both lines are payable, and under what conditions, is payer policy, not a universal rule. Some plans pay both when the record shows the BCBA was directing the technician. Some pay 97155 and consider the technician time bundled during the overlap. Some require the overlapping times to be carved apart on the claim. Medicaid programs vary state by state.

What this means operationally:

• Session notes need precise start and stop times for each rendering clinician, not just the session as a whole. Overlap questions are settled by the times in the record.
• The billing team needs a payer-by-payer concurrency grid: who allows 97155 concurrent with 97153, who requires specific documentation language, who denies on overlap and requires appeal with records.
• Overlapping-time denials need to be recognized for what they are. They routinely arrive as duplicate-service or mutually-exclusive-procedure denials, and a biller who does not know the concurrency rules will write them off or rebill them incorrectly.

A practice with five or six technicians in the field generates these situations daily. Getting them right once is knowledge. Getting them right at volume is staffing.

Supervision Billing: RBTs, BCBAs, and the Lines Between Them

The RBT model is what makes ABA scalable clinically, and it is also a standing billing risk, because payers draw hard lines around who did what.

• Direction versus supervision. Time the BCBA spends directing the technician with the client present is generally billable as 97155. Administrative supervision of the RBT without the client, required by the credentialing board, is generally not separately billable to the payer. Practices that blur this line create audit findings.
• Rendering identity. Technician-delivered services must be billed reflecting the technician's credential level, with the supervising BCBA identified where the payer requires it. Billing technician time under the BCBA's identity at the BCBA's rate, without a payer policy that explicitly supports it, is one of the fastest routes to a recoupment.
• Credential currency. An RBT whose certification lapsed, or whose payer enrollment was never completed in a state that requires it, can invalidate weeks of otherwise clean claims. Someone has to own the roster.

Payer Audits Are a When, Not an If

ABA has been a sustained utilization review and audit target for both Medicaid programs and commercial payers, for a simple reason: it is a high-hour, high-spend, fast-growing benefit delivered largely by non-licensed technicians. Prepayment review, postpayment record requests, and recoupment demands are normal events in this specialty, not signs a practice did something wrong.

What auditors look at maps directly to the failure points above:

• Session notes with start and stop times that support the units billed, signed by the rendering clinician
• Units billed within the authorization, for the codes authorized, in the window authorized
• Concurrent claims supported by documentation showing distinct, payable activity
• Rendering and supervising credentials that match the claim and were current on the date of service
• Treatment plans and progress data that support medical necessity for the requested intensity

A practice whose billing operation already tracks units, times, credentials, and authorizations as a daily discipline can answer a record request in days. A practice that reconstructs this at audit time is negotiating from weakness.

Why Generalist Billers Struggle With ABA

None of this is a criticism of generalist billers. A biller who is excellent across family medicine and outpatient therapy is excellent at a visit-shaped workload. ABA asks for different reflexes:

• Thinking in units and burn-down rates rather than encounters
• Reading overlapping-time denials as concurrency policy questions rather than duplicates
• Holding a payer-by-payer grid of modifier, supervision, and same-day-combination rules
• Treating the authorization tracker, not the claim queue, as the primary control surface
• Building claims from session data that arrives from field staff, with all the note-chasing that implies

The volume compounds the knowledge gap. Because every client produces dozens of lines per week, a small error rate becomes a large denial pile quickly, and the rework itself crowds out the proactive work, which creates the next round of errors. That is the spiral behind most "our ABA billing is three weeks behind" conversations, and it shows up directly in the practice's clean claim rate and days in AR before anyone names it.

What a Dedicated ABA Billing Staff Model Looks Like

The practices that keep ABA billing current tend to converge on the same structure, whether the people sit in-house or with a staffing vendor:

• An authorization owner. One person accountable for the burn-down tracker, expiration calendar, and reauthorization submissions, working ahead of the treatment calendar rather than behind it.
• A daily claims cadence. Sessions from the data collection or practice management system reconciled against schedules, converted to claims, scrubbed against the payer grid, and submitted daily or every other day. Weekly batching is how three-week backlogs start.
• Denial work sorted by cause. Authorization denials, concurrency edits, credential mismatches, and documentation requests each have different fixes and different owners. Working them as one undifferentiated queue guarantees repeat denials.
• ERA posting and reconciliation kept current. With this many lines, unposted remits hide underpayments and make the burn-down math wrong, because billed units cannot be trusted.
• A payer rules grid that someone maintains. Concurrency, modifiers, telehealth allowances, and same-day rules, reviewed when payers publish updates, not discovered by denial.

For many ABA practices the honest math is that this is one to three full-time roles, needed reliably, in a labor market where experienced ABA billers are scarce and turnover restarts the learning curve. That is why dedicated offshore staffing has become a common answer: a trained specialist who works only your practice's ABA billing, inside your existing practice management system and payer portals, following your protocols, at a staffing cost that makes full-time coverage viable. That model, and how it applies to ABA specifically, is laid out on our ABA therapy billing page.

The Bottom Line

ABA billing falls behind when it is treated as a variant of ordinary outpatient billing. It is not. It is a unit-budgeted, multi-credential, concurrency-prone, audit-exposed workload that rewards teams who track authorizations like inventory and submit claims like a daily discipline.

Related reading:

• ABA Billing Guide
• ABA Therapy Billing Support
• Prior Authorization Support
• Behavioral Health Billing Support

This article is for general operational education and is not legal, coding, clinical, or payer-contract advice. Code descriptions, modifier requirements, concurrency rules, and authorization policies vary by payer, plan, and state and change over time. Verify current requirements directly with the applicable payer before providing or billing services.

Frequently Asked Questions