Unbilled Claims in ABA Billing: The Denials That Never Show Up on a Denial Report

There's a category of lost revenue that no report in your billing stack is built to display.

It isn't denials. Denials are visible, coded, and countable, and every billing system in the world has a screen for them. It isn't slow payers either, since those show up as aging balances you can watch and chase.

It's the claims that were never filed at all.

A visit happened. The session was documented. The service was billable. And then the claim didn't go out, and because it didn't go out, no payer ever touched it, no clearinghouse ever acknowledged it, and no denial code was ever attached to it.

Which means it appears nowhere. Not on your denial report, not in your aging buckets, not in your collection rate. In one sample ABA practice audit, unbilled claims accounted for 68% of all open money in the file, and none of it had ever appeared on a single monthly report.

What unbilled claims in ABA billing actually are

An unbilled claim is a date of service that exists in your practice management system with no matching claim at your clearinghouse.

That's the whole definition. Two systems, two lists, and a gap between them.

The reason this is hard to spot is that both systems look fine on their own. Your PMS shows the session. Your clearinghouse shows every claim it received. Neither one knows what the other is missing, and neither one is designed to ask.

It's worth separating unbilled claims from two things they get confused with. A rejected claim reached the clearinghouse and got bounced back before submission, which means it has a status and usually an error message. A denied claim reached the payer and got refused, which means it has a denial code. Both are visible.

An unbilled claim has neither. It's a session that quietly never became a claim.

Why unbilled claims are invisible in standard ABA billing reports

Three structural reasons, and understanding them is what makes the problem obvious in hindsight.

No status means no report. Every report in your billing stack is organized around claim status. Submitted, pending, paid, denied, appealed. A claim that was never created doesn't have a status, so there's no list for it to appear on. Your reports aren't failing. They're answering a question about claims, and this isn't a claim yet.

Your collection rate can't measure it. Collection rate is collected divided by allowed. Allowed amount comes from claims that were adjudicated. An unbilled claim has no allowed amount, because no payer ever priced it.

So it can't lower your collection rate. Ever. You can have a spectacular collection rate and a five-figure unbilled backlog at the same time, and the two numbers will never interact. That's exactly what happened in the sample audit: 98.11% collection rate, $46,200 sitting unbilled.

Aging reports only age balances that exist. If the claim was never created, there's no balance to age, so it never enters a bucket and never crosses the 90-day line that would normally get someone's attention.

The money is aging in real terms. Filing deadlines are running. It just isn't aging anywhere you can see.

Read More About ABA Provider Credentialing: How to Keep Every Provider Billable

How claims go unbilled in the first place

Nobody decides not to bill. It's always a process gap, and the same handful show up repeatedly.

Authorization holds that never get released. A session gets flagged because the auth is expiring or the units are running short. Somebody sets it to hold, intending to sort it out. The auth gets renewed a week later, and the held sessions stay held because nothing prompts anyone to go back.

Missing or unsigned session documentation. The claim can't drop until the note is finished. The note gets finished three weeks later, or doesn't. Either way the claim sits in a queue that nobody reviews on a schedule.

Credentialing gaps. A new BCBA or RBT starts seeing clients before their enrollment is finalized with a payer. Sessions accumulate. Once credentialing comes through, somebody has to go back and file all of it retroactively, and that catch-up batch is easy to lose track of.

Staff transitions. This is the most common one in practices using outsourced ABA billing services. A handoff happens, work in progress falls between the outgoing and incoming person, and neither side knows what the other assumed.

New payer or new client setup. A payer gets added mid-month, the claim format or submission path isn't configured correctly, and claims fail silently before they ever leave the building.

Split billing responsibility. Some practices bill certain payers in-house and outsource the rest. Each side assumes the other has it. In the sample audit, $4,470 sat unbilled on one payer for exactly this reason, and the escalation went out 41 days after the earliest affected date of service.

Notice the pattern. Every one of these is a handoff that nobody closes the loop on.

What unbilled claims actually cost an ABA practice

Two costs, and the second one is worse than most owners expect.

The obvious cost is cash flow. Money you earned that hasn't arrived. In a practice running $130,000 of monthly allowed volume, two months of unbilled charges is a meaningful hole, and it usually shows up as an owner wondering why revenue looks fine on paper but the bank account doesn't.

The real cost is timely filing. Every payer sets a window from date of service, and that clock runs whether or not a claim exists. Some ABA payers allow 180 days. Plenty allow 90. Some allow 60.

That range is what makes unbilled claims dangerous rather than just annoying. A 60-day payer with a two-month unbilled backlog means the oldest sessions in that batch are already past saving. Not disputed, not appealable. Gone.

There's a compounding effect too. Unbilled claims almost never come alone. The gap that caused them, a held queue nobody reviews, a credentialing lag, a broken handoff, is still open, so the backlog keeps growing until someone goes looking. Which is why practices tend to find two months of it rather than two days.

How to find unbilled claims in ABA billing

The check is straightforward. It's just nobody's job by default.

Pull dates of service from your PMS. Pick a closed month, one that's at least 30 days old so normal submission lag isn't a factor. Export every billable session for that month, with client, date, and CPT code.

Pull submitted claims from your clearinghouse. Same month, same fields.

Match them. Client plus date of service plus code. Whatever's in the first list and not the second is unbilled.

Sort what's left by payer and by age. Age matters more than dollar value here, because a $200 claim about to hit a 60-day wall is more urgent than a $2,000 claim with five months of runway.

Check each one against that payer's filing window. Anything already outside it goes to write-off review rather than the submission queue. Chasing dead claims wastes hours your team could spend on live ones.

The first time you run this it takes a few hours and it usually finds something. Practices that have never checked tend to find a backlog rather than a handful. That's normal, and it's not a reflection on anyone. It's what happens when a process has no owner.

If a few hours a month isn't realistic, this is the check SparkzABA automates. Its AI-powered RCM report runs the same match, PMS dates of service against clearinghouse submissions, across your entire file rather than one sample month, and prices what it finds by payer and by remaining filing window.

Because the model reads the AR comments column too, it catches the softer version of the problem as well: sessions marked as billed in a note with no corresponding claim behind them, or an unbilled batch buried inside a generic escalation comment covering seven payers at once. That's how the $46,200 in the sample audit surfaced. It wasn't on any report, and no one had flagged it, but the gap between the two lists was there in the data the whole time.

The weekly control that stops it recurring

Finding the backlog once solves this month. It doesn't solve next month.

The fix is a weekly reconciliation with a rule attached: any date of service older than seven days with no claim on file gets flagged that week, and the flag goes to a named person with a deadline.

Seven days is the number that matters. It's short enough that you're catching problems while the cause is still fresh and someone remembers what happened, and long enough that normal documentation lag doesn't generate false alarms.

Run weekly, this control removes the entire failure mode. In the sample audit, a weekly reconciliation would have caught the June problem in early July, when every affected claim was still comfortably inside every payer's filing window. Instead it surfaced in late July, by which point the 60-day payer's June dates were already at risk.

The cost of the control is maybe an hour a week. The cost of not having it, in that one file, was $46,200 at risk.

FAQs

How do I know if my ABA practice has unbilled claims right now?

Compare one closed month's billable sessions in your PMS against claims submitted to your clearinghouse for that same month. If the counts don't match, you have unbilled claims. This works regardless of whether billing is in-house or outsourced, and it doesn't require any cooperation from your billing team to run.

Can unbilled claims still be submitted after months have passed?

It depends entirely on the payer's timely filing window and the date of service. Some ABA payers allow 180 days from DOS, others allow 90 or 60. Check the window per payer, then per claim, because one batch of unbilled charges can contain claims that are both recoverable and already expired.

Whose responsibility are unbilled claims if I outsource ABA billing services?

Contractually it varies, and that's worth reading before you assume. Practically, the reconciliation belongs to whoever holds both data sets, and that's usually you, since the PMS is yours. Most billing agreements cover working submitted claims. Far fewer cover verifying that everything billable was submitted at all.

Start with one month

You don't need a project for this. Pick last month, pull two lists, and match them.

If the numbers line up, you've spent an hour confirming your billing process is sound, which is worth knowing. If they don't, you've found revenue that no report in your ABA revenue cycle management stack was ever going to show you, and you've found it while the filing clock is still running.