The Source of the Leakage

Six weeks after the denial push, the numbers look fine. AR days are down. Cash posted is back on pace. The report that started the whole effort is now the report being used to end it.

Nothing in that picture tells you whether anything was fixed.

Leakage gets discussed as if it lives in a department. Registration. Verification. Authorization. Documentation. Billing.

The source is not a department. It is the distance between the point where a preventable problem enters the workflow and the point where somebody finally catches it, with no owned step in between. Everything downstream is just a measure of how far the water traveled before anyone noticed.

The entry points are ordinary

That is why they survive.

A member ID gets keyed from an old card and the inactive response is never worked. Eligibility was run, so verification is marked complete, though the response can confirm coverage without settling how this service will be covered at this level of care and this location. An authorization is on file, but for a different level of care than the one billed. Documentation describes the treatment delivered but does not support the level of care billed. And somewhere ahead of all of it, a patient was given a number that was never explained, never documented, and never revisited.

None of this is exotic. Each one has a moment where it could have been caught. What varies between organizations is not whether the errors occur. It is whether anyone owns the catch.

The one that takes ninety days to surface

The patient responsibility conversation is the least visible of the five and the most durable, because it fails silently.

A balance disputed in month three often begins as a conversation that was never finished in week one. Not skipped. Started, handled verbally by whoever happened to be available, and never written into a form that someone else could pick up. By the time the final balance is available after adjudication, the person who had the original conversation has moved on, the patient remembers a different number, and there is no record to reconcile against.

It arrives looking like a collections problem. It started as an ownership gap that took a full quarter to become visible, and by then it presents as a patient dispute rather than as a step no one was assigned.

Why the dashboard stays green

When the numbers recover and the workflow has not changed, look for the person absorbing the difference.

They are not a hero, and reading them that way is how this gets misapplied. They are a symptom. They have been in the building long enough to know which errors surface where, so they fix registration problems from inside the billing queue, catch the authorization mismatch before the claim goes out, and rework the file quietly enough that nothing gets logged as rework. The work is real and it is good. It is also unwritten, which means it cannot be taught, staffed, audited, or replaced.

Somebody in the building already knows where the breakdowns are. That knowledge is sitting in a head instead of in a workflow.

The reporting cooperates with this. Days in AR and cash posted are outcome measures. They show the downstream result, not where the work began or what it cost to produce. Clean claim rate can have the same blind spot from the other side: unless corrections made before submission are tracked separately, a file that took four manual fixes and a file that took none look identical on the way out.

Measure at the origin

If you want to see the gap rather than the recovery, the measures have to sit at the point where the problem starts.

• Financial clearance completed before service, not eligibility run

• Authorization on file that matches the level of care and the dates actually billed

• Estimated patient responsibility presented, acknowledged, and documented before admission

• Changes during care assigned to an owner by the workflow, not absorbed by whoever notices

• Final patient responsibility communicated when finalized claim information posts to the account, not when the patient calls to dispute the statement

• Rework tracked by where the error started, not by who resolved it

Three questions that get there faster

If that person took three weeks off, what happens to the numbers?

Can you name the step where the error was introduced, or only the step where it was caught?

Is the rework written down anywhere a second person could run it?

If the answers are unclear, the leak is still open. The numbers just found someone to route around it.

Freddy Khalil is the Founder and Principal of Grace Advocacy & Compliance. This article reflects the operational perspective behind GAC, shaped by his experience across behavioral health direct care, admissions, financial communication, and patient-responsibility operations. It provides general operational information and is not legal, clinical, compliance, or billing advice.

Confidential inquiry. Response within one business day.