Fifty-two jurisdictions. One claim.
Every state ABA mandate, Medicaid program, and TRICARE region interprets the same CPT codes differently. Organizations fail at scale when the rules live in the heads of experienced billers instead of an enforced, versioned library. This paper maps where jurisdictions actually diverge and how to bill across all of them without a denial spike.
The thesisRules belong in a versioned library, not in billers' heads.
A multi-state ABA organization does not have one billing rulebook. It has one per jurisdiction per payer family, and those rulebooks disagree on covered codes, credentials, documentation, telehealth, and deadlines. The organizations that scale cleanly are the ones that codified the differences before the first claim. The ones that struggle are the ones asking experienced billers to remember them.
Exhibit 1 · the jurisdiction mosaicFifty-two tiles, and the rules diverge on every one.
Fifty states, the District of Columbia, and the TRICARE Autism Care Demonstration each interpret the same ABA CPT codes through their own coverage design. Tile shading shows how intensely rules diverge from the common baseline. The mosaic is deliberately abstract: the point is the density of difference, not any single state's grade.
Exhibit 2 · the scale problemExpansion multiplies the rule surface, not just revenue.
Each new state stacks its Medicaid design, mandate interpretation, documentation statutes, telehealth posture, and filing windows on top of every payer family you bill. The combinations grow multiplicatively. Somewhere between five and ten states, no biller's memory can hold the surface.
Exhibit 3 · the divergence mapWhere jurisdictions actually diverge.
Five divergence categories account for most multi-state ABA billing failures. Each one varies by jurisdiction, and each one produces a distinct, recognizable failure signature on the claim side.
| Divergence category | What varies by jurisdiction | Failure it causes |
|---|---|---|
| Medicaid program design | Covered codes, unit caps, allowable credentials, supervision ratios, MCO sub rules | Unexplained denial clusters in the new state |
| Assessment instruments | Required standardized instruments in authorization packets, notably under the TRICARE Autism Care Demonstration | Packets rejected regardless of clinical quality |
| Documentation statutes | Session note elements specified in state regulation | Notes sufficient in one state, legally deficient next door |
| Telehealth posture | Remote eligible codes, modifiers, place of service values | Clean looking claims that deny on arrival |
| Filing and appeal windows | Timely filing deadlines range widely across programs | Winnable claims forfeited on timeliness alone |
The home state habit
Rules from the founding state applied universally. The most common and most expensive multi-state failure mode.
The silent manual update
A state revises its coverage policy and nobody is assigned to notice. The gap surfaces months later as a denial pattern.
The retrospective audit
A documentation rule missed for two years becomes a repayment demand with interest. Denials are the cheap symptom; audits are the expensive one.
The resignation risk
When compliance lives in an expert's memory, the compliance posture is one resignation away from a gap.
Exhibit 4 · the matrix methodFrom scattered knowledge to an enforced rule asset.
The defense is not smarter memorization. It is an operating framework that turns every jurisdiction requirement into a written, dated, source-cited rule that gets applied to every claim automatically.
Every requirement written as a testable rule: code, payer, state, condition, consequence. Ambiguity resolved at codification, not at claim time.
Rules carry effective dates and source citations. Old rules retire, never overwrite, so any historical claim evaluates against its date of service.
Every claim screened pre-submission against the jurisdiction rule slice for its state and payer family. The published layer is the ABA Payer Policy Matrix: 52 jurisdictions, 8 payer families, 244 sourced cells.
Every bulletin, denial pattern, and regulatory update enters structured intake and propagates portfolio wide. The matrix refreshes monthly.
A rule learned defending one clinic protects every client in that jurisdiction permanently.
Ask any billing partner two questions.
How many jurisdiction specific rules do you enforce automatically, and what happens when a state updates its manual? If the answers involve experienced staff remembering things, the posture is fragile.
Exhibit 5 · new state launch sequenceExpansion without the denial spike.
The launch sequence inverts the usual order: the rules go live before the claims do. Read the rail left to right.
The new state's rule slice goes live: Medicaid design, mandates, statutes, telehealth, windows.
Credentialing and enrollment dependencies mapped against go live.
One page: documentation elements the new state requires that the home state did not.
New state claims run at mature state first pass rates. No reverse engineering period.
Entering new states with the rules in front of the claims
The standard failure mode is the new state denial spike: 60 to 120 days of elevated denials while the team reverse engineers local rules from remittance codes. ASP-RCM inverts the sequence: the Jurisdiction Matrix slice activates before the first claim, and enrollment dependencies are sequenced against go live. The same sequencing runs inside every multi-state ABA billing services engagement ASP-RCM operates.
Across expansion engagements the result is consistent: first claims in the new jurisdiction clear at the same 96 to 98 percent first pass rates as the mature states.
Reference toolThe live companion to this paper.
Every divergence category above maps to a sourced cell.
ASP-RCM maintains an interactive ABA Payer Policy Matrix covering 52 jurisdictions and 8 payer families. Each of its 244 cells is hyperlinked to its primary source, and the matrix is refreshed monthly. When a rule described in this paper changes mid-year, the matrix is where the update lands first. Use it as the live companion to this static paper.
Open the ABA Payer Matrix →FAQFour questions expansion teams ask us.
Why do new states generate denial spikes?
Because rules are learned from denials instead of from source manuals. The spike is the cost of reverse engineering, and it is entirely avoidable by codifying before the first claim.
What makes TRICARE different for ABA?
The Autism Care Demonstration imposes precise assessment instrument and outcome measure requirements. A packet missing the required instrument fails regardless of clinical quality.
Why version rules instead of updating them?
Post payment audits evaluate claims against the rules in force on the date of service. Versioned rules let any historical claim be defended against its own era.
Does a shared rule library really benefit each client?
Yes, structurally. A rule discovered defending one clinic immediately protects every client billing that jurisdiction. Single practice operations cannot learn at that speed.
Keep reading · ABA Revenue Engine seriesThe papers on either side of this one.
Clean Claim Engineering for ABA
How the first pass rate is designed, not hoped for: the pre-submission disciplines that keep ABA claims from ever meeting a denial queue.
Read Paper 03 →The 2026 ABA Payer Policy Survival Guide
The year Medicaid and commercial payers rewrote the ABA rulebook together: rate cuts, prior auth shifts, and the TRICARE ACD extension.
Read the survival guide →Is your footprint bigger than your rule library?
Our team will map your current and planned states against our jurisdiction library and flag the gaps, at no cost. You keep the map either way.