Where Revenue Leaks, and Why Cleanup Alone Won't Stop It

Cash is coming in. Payroll is covered. Month-end closes, more or less on time. From the leadership chair, the revenue cycle looks fine.

That is exactly why revenue leaks go unnoticed. When deposits keep arriving, nobody asks about the claims that were denied and never reworked, the payments that arrived but were never posted, or the contract rates a payer quietly underpaid. Those dollars don’t show up as a crisis. They show up as an aging report nobody has time to read.

Most organizations eventually notice and order a cleanup. The backlog gets worked down, the reports look better for a quarter, and then the same problems return. Here’s why, and what it takes to stop the cycle.

Where revenue leaks

Leaks rarely come from one big failure. They come from small gaps on the back end of the revenue cycle that compound month after month.

• Denials that are never reworked. A claim is denied for a missing authorization or a coding issue. The team is busy, the appeal window closes, and the balance quietly becomes a write-off.
• Aged AR nobody owns. Accounts slide past 90 and 120 days. The older they get, the harder they are to collect, and the less likely anyone is to try.
• Payments received but not posted. Insurance payments sit in suspense because the remittance didn’t match or the deposit couldn’t be tied to an account. The money is in the bank, but the ledger says otherwise, and patients may get incorrect statements. (We covered this one in depth in how to clear an unapplied cash backlog.)
• Credit balances that sit unresolved. Overpayments pile up as refunds owed to patients and payers. That is a liability on the books and a compliance exposure.
• Underpayments. A payer pays less than the contracted rate. Unless someone compares what was paid to what was owed, the difference is simply lost.

None of these feels urgent on its own. Together, they can amount to a meaningful share of what the organization actually earned.

Why cleanup alone won’t stop it

A backlog is a symptom. The cause usually sits earlier in the cycle: at registration, eligibility checks, authorization, charge capture, coding or payment posting.

If a front desk keeps entering the wrong insurance plan, the denials keep coming. If a payer’s remittances don’t map cleanly to the practice management system, payments keep landing in suspense. If nobody reviews contract rates, underpayments keep slipping through.

A cleanup clears the pile. It does not change what fills it. That is why so many organizations pay for a cleanup, see a few good months, and then find themselves in the same place a year later, often after adding locations, changing systems or losing an experienced biller.

The real fix is to treat every leak found on the back end as information about where the process upstream is breaking.

How we approach it

At Prosperity Heritage Services, we work where the back end meets the feedback loop. Every engagement does three things.

1. Clear what has piled up. We work down aged AR, post the unposted payments, resolve credit balances and document what was found. The ledger becomes something leadership can trust again.
2. Recover what is recoverable. Not every old balance is worth chasing. We separate what can still be collected, appealed or corrected from what should be written off, so effort goes where the money is.
3. Send root causes back upstream. For each pattern we find, we trace it to where it started and work with the team to fix it, whether that means a registration checklist, a payer mapping, a posting workflow or a contract review.

We do this as an embedded, fractional part of the client’s team, not as an outside vendor who drops off a report. That gives organizations senior revenue cycle expertise without the cost of a full-time director, and it means someone keeps watching once the backlog is gone.

How small leaks add up: an illustration

The figures below are a hypothetical example, not client data.

Picture a multi-location group collecting about $1.2 million a month. Nothing looks wrong. But on the back end:

The first two alone add up to $240,000 a year in revenue the group earned but never kept, under 2% of collections and easy to miss. The other two distort the books and create compliance risk.

A one-time cleanup could recover part of that and resolve the suspense and credit balances. But unless the underpayments and denials are traced to their causes, next year’s numbers look the same.

The question to ask

If your AR has been cleaned up before and the backlog came back, the problem was never only the backlog. The better question is not “how do we clear this?” but “what keeps creating it?”

That is the work we do: clearing what has piled up, recovering what is recoverable, and sending root causes back upstream so the same leaks stop recurring.