Home/White Papers/Unit Economics of the Session

Series · Paper 03 of 05 · ABA Revenue Engine

ABA claims are engineered, not submitted.

An ABA claim reconstructs a labor record: who delivered which protocol, under whose supervision, for exactly how many 15 minute units, under which authorization. Every fact is independently verifiable and independently deniable. Clean claim engineering front loads the work so claims clear the first time.

Engineer my clean claim rate → Read the companion methodology

First pass resolution

96 to 98%

ASP-RCM ABA clients

Denial reduction

30 to 40%

vs prior baseline

Collections

+20 to 30%

improvement

Benchmark target

Below 5%

denial rate

Exhibit 1 · cost per outcomeFirst pass is the cheapest money in revenue cycle.

Every claim that clears on first pass costs a fraction of one that denies. Rework multiplies the cost, appeal multiplies it again, and a share of denied claims never comes back at all. Read the diagram like a tolerance chart: the further right a claim drifts, the more it costs to hold the same dollar.

Exhibit 1 · Relative cost per claim outcome. Every claim that clears on first pass costs a fraction of one that denies; a share of denied claims never comes back at all.

WHAT THIS MEANS Clean claim engineering is not perfectionism. It is the lowest cost collections strategy that exists, because prevention is priced in single dollars and recovery is priced in multiples.

Exhibit 2 · the core ABA code familyA small code set with an enormous rule surface.

Six CPT lines carry nearly the entire ABA revenue book, and each one fails in its own characteristic way. Every row below is a spec: the service, the credential tier it renders under, and the failure mode that most often sends it back.

CPT	Service	Renders under	Common failure
97151	Behavior identification assessment	BCBA / licensed provider	Units exceed authorized assessment hours
97153	Adaptive behavior treatment by protocol	Technician (RBT)	Credential modifier missing or wrong tier
97154	Group adaptive behavior treatment	Technician	Group ratio unsupported by the note
97155	Protocol modification	BCBA	Concurrent 97153 overlap mishandled per payer rule
97156	Family adaptive behavior guidance	BCBA	Caregiver present attestation missing
0362T / 0373T	Severe behavior, team based	Physician or QHP led team	Team composition not documented

Exhibit 2 · The core ABA CPT code family with renders-under tier and most common failure mode per code.

Exposure 01

SPEC · UNITS

Unit mathematics

15 minute increments plus payer specific rounding conventions. One universal rounding habit means systematic overbilling of some payers and underbilling of others.

Exposure 02

SPEC · TIER

Credential tiers

The same hour reimburses differently for BCBA, BCaBA, and RBT. Claim, schedule, note, and credential file must agree simultaneously.

Exposure 03

SPEC · NOTE

Documentation depth

In audit, the note is the claim. Start and stop times, protocols, and supervision attestations must independently support every unit billed.

Exposure 04

SPEC · POS

Telehealth variants

Place of service and modifier rules diverge by payer and state, and they change fast. Yesterday's clean configuration is today's denial cluster.

Exhibit 3 · anatomy of one unitInside a single 15 minute unit.

One billed unit is not one fact. It is six facts that must all hold at once. Read the exploded spec: any single callout failing is sufficient grounds for the payer to deny the whole unit.

Exhibit 3 · Exploded specification of one 15 minute ABA unit. All six facts must hold simultaneously for the line to survive adjudication and audit.

Exhibit 4 · the integrity chainFive checkpoints between session and submission.

Clean claim engineering is a production line, not a scrubber bolted to the end of one. Each checkpoint catches the failure class that belongs to it, and the last checkpoint feeds every miss back into the first four.

ASP-RCM FRAMEWORK · The Session to Claim Integrity Chain

Before the session

Schedule integrity

Active auth with sufficient units, correct credential tier, matching location and telehealth status.

After the session

Documentation sufficiency

Times, protocols, attestations, signatures. Failing notes return to the BCBA or RBT the same week.

At charge entry

Unit and modifier validation

Units recomputed under the correct payer rounding convention; modifiers checked against the credential file.

Before submission

Payer rule screening

Concurrency, frequency, place of service, and state program edits applied from a maintained rule library.

After adjudication

Denial feedback loop

Every denial coded to the checkpoint that should have caught it. The chain strengthens with each failure.

WHAT THIS MEANS The feedback loop is the difference between a checklist and a system. A checklist stays the same size forever. A system converts every denial into a permanent rule, which is why first pass performance compounds instead of plateauing.

Proof and controlsWhat the chain produces in practice.

Portfolio results · ASP-RCM ABA client base

The chain in production across 42 states

Across single site clinics and multi state organizations, on commercial, Medicaid, and Tricare mixes, the pattern repeats. First 90 days: documentation and unit findings dominate and become standing rules. Second quarter: denials fall 30 to 40 percent against baseline and first pass stabilizes at 96 to 98 percent.

Collections improve 20 to 30 percent, driven by claims that succeed the first time rather than surviving appeal. BCBAs and RBTs stop experiencing billing as an adversary, because documentation returns arrive the same week with a specific fix.

96 to 98%first pass sustained

30 to 40%denial reduction

20 to 30%collections lift

Composite figures across anonymized ASP-RCM ABA engagements; results vary with baseline and payer mix.

Control 01

Same week note returns

Documentation fixes happen while the session is fresh, not at month end. Sufficiency failures fall by an order of magnitude.

Control 02

Payer rounding library

Each payer's unit convention codified once and applied automatically. Rounding disputes disappear from the denial mix.

Control 03

Credential file validation

Modifiers validated against the rendering provider's actual credential record, never against habit.

Control 04

Top five payer edits first

The edit library starts where the volume is. Five payers typically cover the large majority of ABA claim flow.

FAQFour questions billing managers ask us.

What clean claim rate should an ABA practice target?

Benchmark targets are a 95 percent clean claim rate and 90 percent first pass resolution. Practices running the full integrity chain sustain 96 to 98 percent first pass.

Where do most ABA claim errors originate?

Upstream, at scheduling and documentation, before the billing team ever sees the claim. That is why a smarter scrubber at the end of the line cannot fix the problem alone.

How fast should failed documentation return to BCBAs and RBTs?

Same week. Corrections made while the session memory is fresh are faster, more accurate, and build clinical buy in instead of resentment.

Does the integrity chain slow down submission?

No. It front loads minutes to save weeks. Claims that pass five checkpoints adjudicate in days; claims that skip them spend months in appeal queues.

ABA Revenue Engine · keep readingThe rest of the series.

Series · Paper 01

The Authorization Ledger

Why every ABA denial story starts before the first session: running authorizations as a managed unit inventory.

Read Paper 01 →

Companion methodology

The Three-Way Match Handbook

Schedule, note, and claim reconciled line by line. The verification discipline behind the integrity chain.

Read the handbook →

Reference

80 Denial Patterns

The field reference of denial patterns, mapped from code to root cause to fix, that feeds the denial feedback loop.

Open the reference →

Where are your clean claims being lost?

Our team will audit a sample of your recent ABA claims against the five checkpoints and show you precisely where first pass revenue leaks, at no cost.

Engineer my clean claim rate See the ABA billing service

Aparna Suresh, CPBCertified Professional Biller · President and Founder, ASP-RCM Solutions