I’ve seen many finance review conversations in ABA practices start similarly: “We came up short last month. What happened?” The team starts pulling reports and works backward through three or four weeks of activity until somebody finds the thing. A credentialing gap, a payor contract update nobody flagged, or a batch of claims that stopped moving.
Nobody saw those things in time. KPIs and executive dashboards are great, but they tell you what already happened. The early signals live somewhere else.
Here are the three I see come up most in conversations with practice owners, administrators, and billing leads.
#1: Claims That Shouldn't Exist in the First Place
In an ABA billing system that's set up right, certain claims should never make it into circulation. If they're showing up, something upstream is broken, and the breakage is almost always older than the claim itself.
We're talking about things like:
- A claim submitted under a provider whose credentialing with that payor isn't fully active yet.
- A claim billed against a contract that has a stale or incorrect rate or a service code the payor doesn't actually cover.
- A claim that exceeds the authorization parameters (units, date range, place of service).
More than a billing story, each of these is a configuration story. What’s behind it is frequently a credentialing record that wasn't updated when a BCBA® moved from supervised to fully independent status. Or a contract amendment from the payor that arrived in someone's inbox in July and never got entered. Often, an authorization that was approved for 80 units a month but somehow the schedule is generating 92.
The hard part is that ABA practices usually find out about these claims the same way they find out about most billing issues: after the rejection or denial comes back. By then the damage is an unpaid claim, plus the rework and the fixing of whatever pattern is still feeding it from upstream.
If you're seeing a steady trickle of claims that “shouldn't be possible,” it's worth asking whether your records for credentialing, contracts, and authorizations are staying in sync with what your billing team is working from day to day. When those drift apart, even a little, the claims are typically the first place you'll see it.
When credentialing status, payor contract terms, and provider eligibility live inside the same workflow that generates claims, the upstream record is always current when a claim is created.
Want to know if this is happening in your practice?
Pull last month's denials and tag the ones that came back for credentialing, contract, or authorization reasons. If more than 5 to 10% of your denials trace back to one of those three buckets, your upstream records and your billing system aren't talking to each other often enough.
#2: Accounts Receivable That Sit Past 30–60 Days Without a Clear Next Step
Aging AR doesn't tell you much on its own. Every practice has some. The important question is: For the AR that's sitting there, what's the next move, and when is it scheduled to happen?
If a claim is at day 35 and there's a clear note saying “appeal filed 9/22, response expected by 10/15,” that means your system is working. The dollars haven't landed yet, but they're moving and you know it.
If a claim is at day 35 and nobody can tell you what's happening with it, or the answer is some version of “we'll get to it,” that's a sign something is not healthy in your billing workflow. By day 60, that same claim has grown into something messier: timely filing windows are tightening, the original payor adjudicator probably isn't reachable anymore, and the appeal pathway gets harder the further out you go.
When AR drifts without follow-up, you don't notice the cash impact for another 30 to 45 days, because revenue recognition lags the actual problem. By the time the cash gap shows up in a finance report, you've got two months of unresolved AR, not one. That's why you should treat these as early warning signs and not as cleanup projects.
A useful gut check
Pick a random claim from your 31-to-60 day bucket right now and ask your billing manager what the next step is. If you get a confident, specific answer in under 30 seconds, you're in good shape. If you get hesitation or a search through tabs, that's the signal.
#3: Claims That Are Submitted but Stop Moving Through the ABA Billing Flow
Submission is not the finish line. Plenty of teams treat it that way because once a claim leaves the system, it feels handled.
If your team is also feeling stretched thin at the submission stage itself, that's usually a sign of something different going on inside your billing workflow. What I’m talking about here happens after submission, when claims should be moving but aren't.
A healthy claim has motion. It moves from submitted to acknowledged by the clearinghouse, to received by the payor, to adjudicated, to paid or denied. Every one of those transitions has a timestamp, and in a well-functioning billing operation, you can see when something has gone too long without one.
The risk shows up when claims fall into a quiet middle state. Submitted, but not acknowledged. Acknowledged, but not adjudicated. Sitting in a place where no one is actively rejecting them and no one is actively paying them. They didn't error out and they didn't get denied. They're just... still.
This is the most overlooked of the three signs because nothing about it generates an alert. There's no rejection notice. There's no aging bucket flagging it (yet). The claim looks fine on the surface because it's "out the door." The only way to catch it is to watch the flow itself. Practically, that means tracking how long each claim has been in its current state, and flagging the ones that have been there too long, even when nothing's technically wrong.
Try this on Monday
Open your claims queue and filter for anything submitted 21+ days ago that hasn't been acknowledged or adjudicated. The size of that pile is your blind spot. The ones in there longest are usually the ones nobody is going to remember to follow up on.
📌 Further reading: When Claims Have No Status: The Most Overlooked RCM Risk in ABA
Why These Three Signs Matter More Than Monthly Revenue Reports
Monthly revenue reports are confirmation tools. They tell you, with high accuracy, what already happened. They are not, and were never designed to be, an early warning system.
Here's the timing problem in concrete terms. A credentialing gap that produces a denied claim today doesn't affect your reported revenue until the claim ages out of expected payment timelines and either gets resubmitted, appealed, or written off. That can be 30, 60, sometimes 90 days. The same happens with stalled claims and with unresolved AR. The financial consequence shows up a full reporting cycle (or two) after the operational cause.
This is why so many revenue slowdowns feel sudden when they aren't. The conditions that produced last week's number have been accumulating since the quarter started. The ABA leaders who spot these early are looking at a different layer of data.
When ABA Teams Have Early Visibility, Revenue Stays Predictable
When the three signals above are visible inside the same system that runs your scheduling, your session notes, your authorizations, and your billing, the pattern of work changes.
Configuration issues get caught at intake or at the contract level instead of after a denial. Aging AR doesn't drift, because every claim that's still open has a visible owner and a visible next step. Nothing's living in someone's head or in a spreadsheet on a desktop somewhere.
The practices that get this right tend to share a few traits:
- Their billing team isn't constantly in firefight mode.
- Their clinical team isn't getting last-minute requests to redo notes from three weeks ago.
- Their leadership isn't surprised by the monthly numbers, because they've been watching the conditions that produce them.
This is what Motivity was created for: keeping session documentation, scheduling, authorizations, credentialing, and billing connected, with the guardrails that catch upstream issues before they turn into downstream denials.
When billing volume or payor complexity has grown past what manual oversight can handle, our Revenue Cycle Management team works directly inside that same system, so the early signals don't sit unanswered.
Stay Ahead of Cash Flow Slowdowns in Your ABA Practice
Revenue stalls in ABA practices are rarely mysterious. They're a stack of small operational signals that didn't get attention soon enough. The teams that stay ahead have built the habit of looking at billing one layer deeper than the monthly report, and they have a system that helps them keep that habit.
If any of these three signs sound familiar, let’s talk. Book a 30-minute consultation with our RCM team. We'll look at where these signals would show up in your current setup, and what early visibility could look like for a practice your size.
_____________________________________________________________________________
Key Takeaways
- Cash flow problems in ABA practices show up in operational signals 30–90 days before they show up in finance reports.
- The three early signs to track are: malformed claims (configuration issue), aging AR with no defined next step, and submitted claims that stop progressing.
- Catching them early depends on credentialing, contracts, authorizations, and billing being connected to the same workflow.