Camber
Multi-state specialty care

How multi-state expansion breaks specialty care revenue cycle operations

For specialty healthcare businesses, multi-state expansion is a growth milestone. It is also, almost immediately, a revenue cycle operations problem.

8 min read

The cost of multi-state billing complexity

For specialty care businesses, multi-state expansion is a growth milestone. It is also, almost immediately, a revenue cycle operations problem. Most organizations underestimate the revenue cycle impact until the denials start stacking and the P&L starts absorbing costs that were never budgeted for.

A provider that runs a tight, high-performing revenue cycle operation in one or two states opens new markets and assumes the same processes will transfer. But unfortunately, they do not. Payer mixes shift. Medicaid programs differ by state. Prior authorization rules, EVV requirements, credentialing timelines, and modifier logic all vary. A revenue cycle built for one state's inputs will generate errors at scale when forced to absorb ten states' worth of variation, and every error has a cost.

The cost is measurable, and it falls hardest on specialty providers. According to CAQH's Administrative Transaction Costs by Provider Specialty report, behavioral health providers spend an average of 25 minutes obtaining a single manual prior authorization at a cost of $14.92 per transaction, compared to $7.60 for generalists. For ABA, pediatric therapy, substance use disorder, and long-term care providers, where prior authorization is required on nearly every service, that gap multiplies quickly. A conservative mid-market operator managing 500 active clients across multiple states, with 6-month authorization cycles and two to three concurrent authorization types per client, processes roughly 160-250 manual prior authorization transactions per month. At CAQH's documented rate, that is between $29,000 and $45,000 per year in prior authorization overhead alone. That's before accounting for a single denial.

Prior Authorization: Average Cost Among Provider Specialties. 2023 CAQH Index.

$0.00$2.00$4.00$6.00$8.00$10.00$12.00$14.00$16.00$4.47$6.94$7.60Generalist$6.61$9.05$15.12Specialist$6.83$11.18$14.92BehavioralistElectronicPartially ElectronicManual

The financial cost of managing state variation manually

The financial exposure is straightforward. Revenue cycle gaps of even two to three weeks can represent hundreds of thousands of dollars in delayed or lost revenue for a mid-size multi-state operator. For a PE-backed organization measured on EBITDA and cash flow, that signals a reporting problem.

The root cause is almost always the same. Billing teams manage state-level differences through memory, spreadsheets, and individual expertise. Knowledge lives in people. When those people leave, the knowledge walks out with them. And in revenue cycle operations, individual expertise is notoriously difficult to retain and transfer. The result is a system whose financial performance is directly tied to the stability of its staffing, which is not a system at all.

Why standard systems break under state variation

Most revenue cycle platforms were designed to process claims, not to operationalize payer-specific logic across multiple regulatory environments. They assume stable inputs. In reality, every state you add introduces a new set of variables: different Medicaid rates and billing codes, distinct EVV mandates (for example, Colorado Medicaid requires EVV where others do not), credentialing requirements that vary by payer and state, prior authorization rules tied to specific CPT codes, and local BCBS or Medicaid plan rules that determine how denial follow-up actually works.

When a rules engine does not account for these differences across payers, modifiers, places of service and state, the result is a higher initial denial rate, slower cash, and more manual remediation.

This issue is not confined to any single state. It is a structural feature of how specialty care claims are processed nationally. A 2024 study by RTI International, drawing on claims data from more than 22 million individuals across all 50 states, found that patients went out-of-network 3.5 times more often to see a behavioral health clinician than a medical or surgical clinician. It also found that in-network reimbursement for behavioral health office visits was on average 22% lower than for equivalent medical/surgical visits. Virginia's own 2025 Mental Health Parity Report illustrates what this looks like at the claims level: substance use disorder office visit claims were denied at a rate of 30.6%, nearly five times the 6.7% denial rate for medical/surgical office visits in the same market. The billing complexity driving these outcomes multiplies when you add states. Each denial that requires manual appeal adds cost to collect and extends days sales outstanding.

The two-layer framework for scalable multi-site RCM

Scalable multi-state RCM has two distinct financial levers. The first determines your cost-to-collect. The second determines your net collections rate. Most organizations invest in one and neglect the other, and the P&L reflects it.

The instinct most multi-state operators follow is to standardize everything: one process, one workflow, one set of rules applied uniformly across every state. Standardization at the process level is the right instinct. It is what drives down cost-to-collect and removes the manual overhead that stacks as you add states. But forcing uniform inputs onto a system that was never designed for state-level variation is what erodes net collections rate. Every state you enter with incomplete payer logic is a state where your first-pass paid rate is lower than it should be and a portion of your authorized revenue never gets collected.

Scalable multi-state RCM requires two distinct layers, each solving a different financial problem:

Layer 1: Standardized operations

This is where you build scale. A consistent daily claim submission cadence, a shared claims lifecycle from session to adjudication, centralized KPI tracking across all states, and a denial management workflow that does not depend on who is at their desk. These are the fixed costs of running a billing operation. Getting them right means every new state you enter inherits a system that already works, rather than inheriting a set of manual processes that need rebuilding from scratch.

Standardized operations reduce cost-to-collect. Every claim that moves through an automated, consistent workflow rather than a manual one costs less to process, reaches adjudication faster, and generates cash sooner.

Layer 2: Localized logic

This is where you protect margin. State-specific payer rules encoded into your rules engine rather than held in someone's memory. Modifier logic structured by provider type and payer. Prior authorization tracking tied to specific state-payer combinations. EVV and credentialing requirements maintained as structured, updatable data.

The financial case here is about net collections rate. Every state you enter with incomplete or incorrect payer logic is a state where your first-pass paid rate is lower than it should be, your denial rate is higher, and a portion of your authorized revenue never gets collected. For a multi-state operator billing $20M annually, a two percentage point gap in net collections rate between your best and worst-performing states represents $400,000 in recoverable revenue sitting on the table.

The distinction between the two layers matters because it determines where you invest. Organizations that try to localize everything end up with chaos: a different process for every state, no operational consistency, and a billing team that cannot scale. Organizations that try to standardize everything end up with a rules engine that generates denials the moment it hits a state it was not designed for. The ones that get it right build one system and feed it fifty sets of inputs, one for each state.

How to protect margin as you scale across states: Four operational priorities

01
Encode payer rules, don't rely on people to know them

Every state-payer combination carries logic that should live in your system, not in someone's head. When Medicaid rates change or payer policies update, that change needs to propagate automatically across every affected claim. The practices that absorb the highest denial costs when entering a new state are the ones whose billing infrastructure has no mechanism for absorbing a rule change without human intervention. At scale, it is a margin problem that shows up directly in your net collections rate.

02
Separate your operational cadence from your exception workflow

The daily billing run should be automated. Exceptions like credentialing issues, authorization holds, and unloaded sessions should surface through a structured queue, not an inbox.

03
Measure and track performance at state and payer level

First Pass Paid rate, Initial Denial Rate, and AR Aging by state and by payer are the metrics that tell you where a new state is underperforming before the problem multiplies. If you cannot see those metrics broken down at the state level, you cannot manage multi-state operations with any precision.

04
Treat onboarding a new state as a system configuration

What credentials are needed? Which payers require electronic claims registration? What are the authorization timelines? These questions should have answers in your infrastructure before the first claim is submitted.

Interactive Tool

Explore reimbursement risks across U.S. states

Explore and compare reimbursement risks across U.S. states using our interactive map.

Absorb state-level variation without adding headcount

The math on multi-state billing complexity is unforgiving. Margin erosion is quiet. It leaks through denial patterns that go undetected at the portfolio level, through payer rule changes that no one catches in time, and through new states that spend their first six months in a reactive billing posture while the P&L absorbs the cost.

Camber is built for specialty care organizations that cannot afford that leakage. It automates 80-90% of the claims lifecycle, encodes ABA and behavioral health-specific payer logic at the state and modifier level, and surfaces real-time performance data broken down by state and payer across your entire portfolio, so underperformance is visible before it becomes a write-off.

A billing system that absorbs state-level variation without creating more manual work, more denials, or more margin leakage is not an operational investment. It is a margin protection strategy. For a scaled multi-state operator, the difference between a system that localizes payer logic and one that does not is measurable in net collections rate, cost-to-collect, and ultimately in the EBITDA multiple your organization commands.