Centralized vs Decentralized ABA Billing: What Actually Works for Multi-Location ABA Operations

You've just acquired your third ABA clinic. Things are running fine across your locations, and revenue is growing. But something subtle has started to break: your billing team can no longer answer simple questions without calling each clinic, denials seem to come in sporadic waves, and you have no visibility into how long it takes for claims to be paid.

The problem isn't volume. Its structure.

Most ABA organizations scale locations aggressively before they scale their revenue cycle infrastructure. The billing decisions you make at 2–3 locations work fine in isolation, but they create cascading problems at 5, 8, or 12 locations. By the time you realize there’s a structural issue, you’ve buried thousands in ABA revenue leakage and created accountability gaps that are extremely difficult to untangle.

The fundamental question is this: Should billing be centralized (handled by a single team or system) or decentralized (managed at the location level)?

This guide explores how centralized and decentralized ABA billing models impact ABA revenue cycle management, denial rates, ABA cash flow management, and scalability across multi-location ABA operations.

Why ABA Billing Structure Matters

Most operators treat billing structure as a back-office decision. However, it is more of a strategic function that can operate in your favor based on its impact.

• Revenue visibility: Do you have complete visibility over all locations and their real-time functions?
• Denial management: Are denials being appealed consistently, or do some locations let them slip?
• Days sales outstanding (DSO): What’s the due time of these payments? Is it lagging by more than 45 days or 75 days?
• Accountability: Are there clear hierarchies for responsibilities and results?
• Scalability: Can your current infrastructure handle 3 or more locations without risk?
• Cost efficiency: Are you paying more in headcount than you should?

The Two Models: Definitions and Reality

Centralized Billing

Definition: A single team handles the entire RCM process of ABA claims management, follow-up, ABA accounts receivable management, and ABA denial management across all locations. All the clinics send their data to a central team that handles the main process.

How it works in practice:

• One billing manager or a specific team of 2-4 people are assigned to manage all locations.
• All the claims are submitted through one EMR or an aggregate data source
• The same team standardizes all the denials, appeals, and AR reports in one place
• Processes are uniform, and everything is stored in one place.

The key operational requirement: Clinic staff must follow consistent intake and documentation protocols and provide accurate data to the central team on time. If clinics operate in information silos or use different systems, centralization becomes a nightmare.

Decentralized Billing

Definition: Each location has a function of its own and handles its own billing responsibilities. A billing coordinator or outsourced vendor handles claims for that specific clinic.

How it works in practice:

• Each clinic has its own billing person or contracts with a local RCM vendor
• Claims are submitted for that location system only
• Follow-up, Appeals, and AR Reports pertain to the local level only
• Reporting is fragmented as each location has a different update
• Processes are split across locations, with each location having its own approach.

The key operational requirement: You need a strong reporting infrastructure and management discipline to maintain oversight, because visibility naturally decreases as responsibility is distributed.

Head-to-Head: Pros and Cons

Where Each Model Breaks - Real Failure Points

Decentralized ABA Billing: Model Failure Points

1. Inconsistent Documentation and Submission

Each clinic's front desk or therapist enters data differently. One location misses a payer requirement, and another doesn't include a required authorization. You spend weeks resubmitting.

2. Denial Leakage

A location's billing person gets overwhelmed or leaves. Denials start piling up in their queue. Some get addressed, others fall through. After 3–4 months, you realize $50K in legitimate claims never got appealed because there was no centralized ABA denial management or tracking.

3. Reporting Fragmentation

You ask your controller, "What's our average DSO?" They have to call each clinic, wait for a response, then do the math. Your board meeting is in two days. You don't get a reliable answer.

4. Payer Relationship Loss

Each clinic talks to payers independently. One location negotiates a contract differently from another. You have no leverage on rates because you're fragmented.

5. Lack of Accountability

A location's billing person says, "That's not my job," and no one owns the outcome. Who's responsible for reducing DSO? Who owns denial management? The answer is unclear, so no one prioritizes it.

Centralized ABA Billing: Model Failure Points

1. Bottleneck Under Growth

Your centralized billing team is 2 people. They're managing 4 locations fine. You add a 5th location, and suddenly they're drowning in volume. Claims start getting submitted late. Follow-up stops happening. DSO climbs.

2. Lack of Local Context

The central team doesn't understand that Clinic B has a Friday-only schedule, or that Clinic C doesn't use a particular payer. They submit claims the wrong way or don't recognize when something is unusual at a specific location. This creates friction and delays.

3. Communication Lag

A clinical manager notices a mistake, but the central team is busy with other priorities. So the communication takes 3 days instead of 3 hours, and the problem compounds by then.

4. Single Point of Failure

Since there’s a singular POC, there’s a chance of them being unavailable, and your entire revenue cycle stops functioning without authority. You have no redundancy.

5. Inconsistent Prioritization

The central team is working on several high-dollar claims, but a smaller location has urgent insurance questions. That location gets deprioritized. Clinic managers feel like they're not being served.

What Works at 3 Locations Breaks at 10

There's a critical threshold that most operators miss. At 1–3 locations, you can succeed with either model. The owner or operator can see everything. If decentralized, you maintain oversight through force of will. If centralized, one person can handle it.

But at 5+ locations, the model you chose in year two becomes a serious constraint. Here's why:

• Decentralized at 5+ locations: Inconsistencies compound. You have 5 different billing processes, 5 different payers being managed differently, and 5 different reporting systems. The time you spend trying to maintain consistency exceeds the time you'd spend if you just centralized.
• Centralized at 5+ locations (without infrastructure): Your central team becomes the bottleneck. They have no leverage to say no, and you can't hire proportionally because you don't have enough work for a 4th full-time person. Stuff falls through.

The operators who navigate this successfully don't choose one model. They choose a hybrid model with centralized control and localized support.

What High-Performing Organizations Actually Do

After working with dozens of ABA organizations, we've seen a consistent pattern among those with strong financial performance and clean operations. They use a centralized-with-local-input model.

The Framework

Centralized Control:

• One person or team owns denial management across all locations
• All claims are submitted from a single system or unified process
• AR aging and DSO reporting are centralized; you see everything
• Payer relationships are managed centrally (one point of contact per payer)
• Appeals and follow-up are tracked and standardized

Localized Input:

• Each clinic has a designated authority member who ensures the paperwork and documentation are correct and feeds it to the central team on time.
• The local staff have escalation rights, so they can always contact the clinic on a priority basis.
• The central teams have regular check-ins with each location to understand their current challenges and solve them with urgency.
• The Local staff is trained on the main process and understands their role, while embracing responsibilities overhead.

Key Operating Principles

1. Single Source of Integration

All locations feed into a single EMR or centralized claims management system. There's no translation layer, no fragmented spreadsheets. This is non-negotiable for centralized control to work.‍

2. Clear Accountability

The central billing team owns outcomes (DSO, denial rate, collection accuracy). Each clinic owns inputs (documentation, data entry, and timely submission). Everyone knows their job.

‍3. Transparent Metrics

You report DSO, denial rate, and collection percentage by location and in aggregate, monthly. Clinic managers can see how their documentation affects outcomes. The central team can see where bottlenecks are.

‍4. Standardization With Flexibility

Your core processes are standardized. But you allow for location-specific variations when necessary.

Why this works: You get the complete visibility and efficiency of the centralization model and avoid the disconnect of multiple locations. It's the best of both models.

The Financial Reality of ABA Revenue Cycle Structure

Billing structure isn't abstract. It directly impacts four financial metrics that matter to buyers and investors:

1. Revenue Realization (Direct Cash Impact)

Decentralized organizations typically collect 92–95% of eligible revenue. Decentralized organizations average 88–91% because of denial leakage, write-offs, and inconsistent follow-up.

For an $8M revenue organization, that's a difference of $320K–$480K annually.

2. Days Sales Outstanding (Cash Flow Impact)

Centralized organizations average 45–50 days DSO. Decentralized organizations average 55–70 days.

The ABA cash flow management impact of a 15-day difference: If you're billing $30K per week, a 15-day lag means $450K in perpetually outstanding cash that you're funding.

3. Administrative Cost (Margin Impact)

Centralized billing at scale costs 1.5–2% of revenue. Decentralized billing costs 2.5–3.5% of revenue, and this ratio gets worse as you scale.

At $8M revenue: Centralized = $120–160K in billing labor. Decentralized = $200–280K.

4. Valuation Impact (Buyer/PE Perspective)

Buyers look at these metrics carefully:

• Revenue quality: Is it predictable and clean, or is it fragmented and risky?
• Operational scalability: If I buy this and add 5 more locations, does the current structure hold?
• Management infrastructure: Can this business run without the founder?

A well-designed, centralized billing operation is a material positive for ABA practice valuation. Decentralized, fragmented billing is a red flag. Buyers will discount EBITDA and assume they'll need to invest in fixing it after the acquisition.

Evaluate Your Billing Structure

Most ABA organizations haven't done a structured assessment of their ABA billing services and operations. The hidden cost of a suboptimal structure is significant—often $200K–$500K annually in direct and indirect losses.

We've built a diagnostic framework that operators use to assess:

• Your current billing structure and its impact on DSO and denial rates
• Revenue leakage from process gaps
• Staffing efficiency and cost optimization opportunities
• Scalability constraints and infrastructure needs