Software for ABA Billing Companies

Medical Billing Software for ABA Billing Companies

Short answer

ABA billing companies handle one of the most authorization-intensive revenue cycles in behavioral health. Every client generates hundreds of 15-minute units per month across CPT codes 97151 through 97158, each tied to a specific rendering credential and a pre-approved unit count that payers cap per authorization period. Denial rates of 15 to 25 percent are common for practices without dedicated billing infrastructure, against a 5 to 10 percent healthcare average. The 2025 Roper Technologies acquisition of CentralReach for about $1.65 billion has prompted many ABA organizations to re-evaluate their software stack. Medi is a billing-company-first revenue cycle operating layer that handles claim submission, ERA review, denial queue work, eligibility, and multi-practice work queues through the Stedi clearinghouse. It is not a replacement for ABA practice management, scheduling, or data collection. The right fit is a billing company running ABA alongside a mixed or behavioral-health book. Sources: ABA Coding Coalition.

Why ABA billing is different

Three structural facts separate ABA from most other behavioral health specialties.

First, transaction volume per patient is high. A child receiving 25 hours of weekly therapy generates more than 5,000 billable units a year across multiple CPT codes. A single day of care can produce a claim with 16 units of 97153, two units of 97155, and one unit of 97156, each timed in 15-minute increments. A billing team used to evaluation-and-management codes or session-based psychotherapy will miscalculate units regularly.

Second, authorizations are continuous, not episodic. Most payers approve ABA services in 90-to-180-day windows tied to specific unit counts per code. The billing company tracks real-time utilization against each authorization, alerts providers before units run out, and submits re-authorization 30 to 45 days before expiration. Letting an authorization lapse by a single day turns a clean claim into a retroactive denial.

Third, the payer landscape is fragmented. One ABA practice often navigates Medicaid fee-for-service, multiple Medicaid managed care organizations, and commercial insurers, each with distinct authorization protocols, concurrent billing rules, and fee schedules. What one commercial plan allows for concurrent 97153 and 97155 billing may be denied flat by a state Medicaid MCO in the same county.

Denial rates for ABA practices without dedicated billing infrastructure run roughly 15 to 25 percent, against a 5 to 10 percent healthcare average. Treat the exact figure as directional and confirm against your own book.

The ABA CPT codes (97151-97158) and how units work

All eight Category I codes are time-based in 15-minute increments. Code 97151 includes both face-to-face and bundled non-face-to-face work such as data analysis and report writing; the other codes count face-to-face time only. A qualified healthcare professional in payer contracts generally means a BCBA or BCBA-D; a technician means an RBT or BCaBA working under active supervision.

Two Category III codes, 0362T and 0373T, cover assessment and protocol-modification services when a QHP is on-site directing two or more technicians for patients with destructive behavior. Not all payers recognize these codes, so verify coverage before billing. Education-level modifiers (HM, HN, HO, HP) are required by many state Medicaid and MCO contracts and must be applied per the individual rendering provider's credential, not the practice's highest-credentialed staff member.

Sources: ABA Coding Coalition codes.

Authorizations are the center of gravity

Every payer that covers ABA therapy requires prior authorization before services begin. The authorization specifies which CPT codes are covered, how many units are approved, the date range, the place of service, and often the rendering provider by NPI. A claim that hits any one of those walls returns as a denial.

Authorization management has three phases. Before sessions start, the billing team verifies that an active authorization exists, confirms it covers the specific codes and place of service the provider plans to use, and loads the unit count and expiration into the billing system. A single missed field here can produce weeks of unbillable sessions.

During the period, units are consumed with every session. A patient receiving four hours of direct therapy per day uses 16 units of 97153 daily. A billing company managing 20 ABA clients for one practice needs to track consumption in real time, not in the weekly billing batch, because the clinical team keeps scheduling regardless of remaining headroom.

At re-authorization, the billing company coordinates with the practice's clinical team to submit progress documentation 30 to 45 days before the authorization expires. Late re-authorization is a leading cause of service gaps and retroactive denials. Payers typically require updated treatment plans, functional assessments, and progress notes covering all active codes on the authorization.

Sources: MBW RCM prior authorization checklist.

Who can render and bill

The billing error most likely to trigger a payer audit in ABA is a rendering-provider mismatch: a claim that lists an RBT as the rendering provider for a QHP-only code, or a BCBA credentialed with the practice's Tax ID but not enrolled with the specific payer.

RBTs can serve as rendering providers on 97153 and 97154. They cannot independently bill 97151, 97152, 97155, 97156, 97157, or 97158, which require a QHP. The RBT's NPI must appear on the claim for technician-delivered codes, and the RBT must be credentialed or enrolled with the payer before any claim is submitted.

BCBAs must be individually credentialed with each payer under the Tax ID they bill through. A newly hired BCBA cannot be billed under a credentialed colleague while enrollment is pending; most commercial payers treat that as misrepresentation. Credentialing timelines for new BCBAs run 60 to 120 days with major carriers, which creates revenue gaps a billing company should flag at onboarding.

When a BCBA personally delivers direct treatment rather than supervising an RBT, the BCBA is both rendering and supervising provider. When the BCBA supervises an RBT delivering 97153, the RBT is the rendering provider and the BCBA appears as supervising provider. Billing the wrong NPI in the rendering field on either scenario triggers a denial. Many payers now require NPI and taxonomy for both billing and rendering providers on every claim, and claims missing that data reject at the clearinghouse before adjudication.

Sources: MBW RCM BCBA supervision guide.

Concurrent and overlapping session denials

The most technically difficult denial category in ABA is concurrent billing: submitting 97153 (technician treatment) and 97155 (BCBA protocol modification) on overlapping time units for the same patient on the same date.

The clinical reality is common. A BCBA observes and directs an RBT's session in real time, makes live protocol adjustments, and both providers are face-to-face with the patient at once. The billing question is whether the payer allows both codes for those overlapping minutes, and the answer varies by payer and state. Some commercial plans allow concurrent billing when documentation confirms both providers were present and performing distinct, billable activities. Some Medicaid programs allow it when the BCBA is on-site making real-time modifications with timestamped notes. Other programs, including several MCO contracts, deny any overlapping units for the same patient as a duplicate claim. The denial reason is typically CO-97 or CO-4.

The documentation standard for concurrent billing is high. Session notes must record the specific protocol change the BCBA made during each 15-minute interval of overlap, not just that the BCBA was present. Vague "supervision provided" language fails payer audits. A billing company handling concurrent claims across payers needs a way to flag which payers allow the combination and to maintain documentation checklists per payer, because one policy mismatch across a 20-client practice produces dozens of wrongly submitted claims a week.

Sources: Praxis Notes on concurrent documentation.

Payer variability

All 50 states require some form of autism insurance coverage, but the mandate applies primarily to fully insured, state-regulated plans. Self-funded employer plans governed by ERISA are generally exempt, so a billing company may have a commercially insured ABA client whose employer plan covers no ABA services at all despite state law.

The gap between Medicaid and commercial rules is wide. Medicaid is often the largest single payer for ABA billing companies, and reimbursement rates vary sharply by state. Several states reduced ABA rates through 2025 and 2026 in response to spending growth, which makes clean-claim collection velocity especially important. Billing companies holding aged ABA claims during a rate negotiation face compounded risk. Medicaid programs and MCOs also impose hard authorization stops that commercial payers sometimes waive on appeal: a commercial denial for units over auth is often reversible with a peer-to-peer request, while a Medicaid MCO denial for the same reason usually is not.

Commercial payers add their own variability. Some require a separate authorization per CPT code, some bundle all ABA codes under one authorization with a combined cap, and some restrict telehealth to 97155, 97156, and 97157 while denying 97153 by video. Modifier 95 is the standard telehealth indicator for most commercial plans; some Medicaid contracts still require GT, and billing both on the same line triggers a rejection.

Sources: HHS OIG work plan.

Where ABA billing companies lose money

The denial patterns that produce the most recoverable leakage in ABA cluster around a few causes.

Authorization exhaustion happens when clinical staff keep scheduling and delivering sessions after the approved unit count is consumed. The provider delivers care in good faith, the claim arrives with no headroom, and it denies. Without real-time unit tracking, the billing team often discovers the problem days or weeks later when the EOB returns.

Units over authorization is a distinct pattern where the units submitted for a date of service exceed what the authorization permits for that code that day or week. Some authorizations include daily or weekly frequency limits in addition to a total cap, so a four-hour 97153 session against a three-hour daily cap produces a partial denial on every claim until corrected.

Rendering provider mismatch is the third major category: billing a BCBA who has not completed enrollment, listing the supervising BCBA's NPI for an RBT-delivered 97153 session, and failing to update the rendering provider when a new clinician takes over mid-authorization.

CPT-to-authorization mismatch is less common but expensive. The clinical team moves a client from technician-only treatment to protocol modification, but the authorization on file still covers only 97153 and not 97155, so every 97155 claim denies until the authorization is amended.

Late filing is a slow leak. High-volume ABA practices accumulate a backlog of unsigned notes, which delays submission past payer filing windows. Most payers enforce 90-to-120-day timely filing limits, and sessions delivered but not submitted within that window are written off.

Sources: common ABA claim denials.

The CentralReach switching window

In 2025, Roper Technologies announced the acquisition of CentralReach from Insight Partners for about $1.65 billion. CentralReach is the dominant practice management, data collection, and RCM platform for ABA providers, serving a large base of professionals. Roper is a diversified software holding company, and the acquisition validates ABA software as a mature vertical market. Roper has said it will operate CentralReach independently under its existing leadership.

What the acquisition produces for ABA organizations and their billing companies is a window of strategic re-evaluation. Large acquisitions like this commonly bring pricing reviews at renewal, roadmap shifts that favor portfolio priorities over niche feature requests, and renewed concern among practices about vendor dependency. The switching consideration for billing companies is specific. CentralReach combines practice management, clinical data collection, scheduling, and billing into one integrated platform, and billing companies embedded in that stack have historically been pulled toward its billing module or toward CentralReach-first RCM services. As practices question the stack after the acquisition, some are separating the clinical workflow layer, where CentralReach has genuine depth, from the claims and revenue cycle layer, where a dedicated billing-company RCM tool can serve the back office better. A billing company that runs multiple specialties and manages ABA as part of a mixed book is a strong candidate for a standalone RCM layer independent of any practice management vendor.

Sources: Roper and CentralReach announcement.

How Medi handles ABA billing-company workflows

Medi is built for billing companies, not individual practices. The model is a single operator account that manages multiple practices, with role-based permissions scoped to the practice or provider level.

Authorization tracking. Medi stores authorization records per client, per payer, per CPT code, with unit counts and date ranges. Staff can see remaining units against submitted claims and flag authorizations approaching expiration. This is a tracking layer, not an automated scheduler; the billing company's clinical liaison still initiates re-authorization with the practice.

Claim submission and scrubbing. Claims flow through Stedi to payer clearinghouses, and the billing team reviews scrub results before submission. ABA-specific combinations such as concurrent 97153 and 97155 can be surfaced as review items where payer rules require separate handling.

ERA review. When payers return 835 files, Medi maps payment lines to individual claim lines and surfaces denial reason codes at the service-line level. For ABA claims with multiple codes per date of service, each code's adjudication result is visible separately rather than collapsed into a claim-level status.

Denial queue. Denied claims enter a structured queue with reason codes, payer response text, and action surfaces for writing off, appealing, or correcting and resubmitting. The queue filters by denial code, payer, practice, and age, which helps a billing company managing ABA alongside other specialties triage by pattern across practices.

Multi-practice work queues. A billing company can see ABA claims across all its ABA clients in one view, filter to a single practice, or assign work to specific staff, with permissions scoped so a biller working only on one practice cannot view another's claims.

Medi does not provide clinical data collection, treatment plan authoring, session scheduling, or RBT timekeeping. Those belong in the practice management system, whether CentralReach or an alternative. Medi plugs in where claims are ready to submit and works backward to authorization tracking and forward through ERA posting and denial resolution. See the denial management workflow guide for how the denial queue works across specialties.

When Medi is not the right fit

Medi is not the right tool if the billing company's entire book is pure ABA and the team needs scheduling, data collection, and billing in one integrated system, which is what platforms built for that integrated model provide. It is not the right fit if the company relies on automated session-note-to-claim generation from a clinical data system and needs native integration with that system's claim output, since Medi assumes claims are built by billers rather than auto-generated from notes. It is not the right fit if the practices are Medicaid-dominant and require direct state portal submission that bypasses commercial clearinghouses, because Medi submits through Stedi. And it is not the right fit if the company needs its RCM software to manage RBT payroll, supervision ratios, or credential-expiration reminders, which are practice operations rather than revenue cycle.

What should an ABA billing company verify in software?

How does the system track authorization units in real time, and when does it alert staff as consumption approaches the limit? A system that updates unit counts only after ERA posting, rather than after submission, leaves blind spots that fill with denied claims. Can authorization records store per-code unit limits in addition to an overall cap, since some payers authorize a large block of 97153 and a small block of 97155 under one number? How does ERA review handle multi-code ABA claims, and can staff see exactly which code was denied and why? Can the denial queue be filtered and sorted by denial code and payer across multiple practices at once? How does the system handle concurrent 97153 and 97155 claims: flag for review, scrub automatically, or pass through? And what is the clearinghouse path for Medicaid submissions, with documentation of successful submissions to the specific state MCOs in the company's territory?

Frequently asked questions

Can an RBT be listed as the rendering provider on a claim?

Yes, for technician-delivered codes: 97152, 97153, and 97154. The RBT must be credentialed or enrolled with the specific payer, and the RBT's own NPI must appear in the rendering provider field. RBTs cannot be the rendering provider on QHP-only codes: 97151, 97155, 97156, 97157, or 97158.

What happens when ABA authorization units run out mid-month?

Claims for sessions delivered after units are exhausted deny as services exceeding the authorized quantity, and the denial is usually not reversible without a new or amended authorization approved prospectively. Some payers grant a retroactive extension under documented emergency circumstances, but that is payer-specific and not assured. The practical answer is real-time unit tracking and clinical-team communication before the authorization runs out.

Do all 50 states require commercial insurers to cover ABA?

All 50 states have autism insurance mandate laws, but they apply primarily to fully insured, state-regulated plans. Self-funded employer plans governed by federal ERISA law are generally exempt. A billing company will encounter self-funded employer plans that cover no ABA services, which need to be identified at eligibility verification before the first session.

Is concurrent billing of 97153 and 97155 allowed?

It depends entirely on the payer. Some commercial plans and select Medicaid programs allow concurrent billing when both providers are face-to-face with the patient and documentation records distinct, simultaneous services. Other payers deny any overlapping time units as duplicate claims. Maintain a payer-by-payer concurrent billing reference and build documentation checklists around the highest-scrutiny payers in your mix. See the denial management workflow guide for handling CO-97 patterns.

How is ABA billing different for a billing company versus in-house staff?

A billing company manages ABA across multiple practices, which compounds payer variability: the same commercial plan can have different rules per employer group, and different practices carry different MCO contracts in the same state. Billing companies also run the credentialing and enrollment pipeline for multiple BCBAs across practices, which makes rendering-provider mismatches more likely without a structured enrollment process. Multi-practice queue visibility is necessary, because per-practice claim lists do not scale.

What is the typical filing window for ABA claims?

Most commercial payers enforce timely filing limits of 90 to 180 days from the date of service. Medicaid programs vary by state, from 90 days to one year. ABA practices with high session volume and slow note-signing are especially exposed, so the billing company's workflow should include a pending-note aging report that flags service dates approaching the filing cutoff.

For a broader view of denial workflows across specialties, see the denial management workflow guide. For behavioral health more broadly, see behavioral health billing companies. For a structured platform comparison, see the billing company software evaluation guide, or request a demo.