Last reviewed: August 2026

Playbook

Revenue leak — the money a surgery center earned and did not keep

Ask a surgery center administrator what their denials cost and you will get a number. Ask what their revenue leak costs and you will get a pause — not because they do not know their business, but because no system they run can produce the figure. Revenue leak is the money the center earned and did not keep. Not the cases it never had, and not the contracts it wishes it had negotiated. The work was done, the patient was treated, and some portion of what that case was worth never arrived. It leaks in four distinct ways, and the reason it stays invisible is structural: each of the four lives in a different system, in a different unit, on a different clock.

Four leaks, four systems, and the total that no system computesA four-row table. Each row is one way revenue leaks: approved cases paid short, receivables aged out, cases that lost money, and rework that surfaces as headcount. For each row the table gives the system the leak lives in, the unit it is counted in, and the clock on which it surfaces — all four different. Every row is drawn the same height, because the page does not say which leak is largest. Below the rows sits an empty outlined band standing for the total, which no system computes.The leakThe systemThe unitThe clockApproved and paid shortPractice managementsystem, vs the contractDollars perremittance lineAt payment — and apayment reads as successReceivables aged outThe accounts-receivableaging reportDays a balance hasaged past 90, past 180When the timely-filingwindow closes it by ruleCases that lost moneyTwo, unjoined: practicemanagement and materialsMargin on one case,in dollarsNever — the margin percase is never computedRework, as headcountThe staffing plan —no cost line anywhereStaff hours that earnno new revenueLater, as a hire toabsorb the reworkTotal revenue leakNo owner, no query, no answer. Every system holds one true fragment and no system holds the arc.
Four leaks, four systems, four units, four clocks — and no row that adds them up. Every band is drawn the same height on purpose: the page does not say which leak is largest, so the diagram does not either.

Leak one: cases that were approved and paid short

The authorization came back affirmed. The case was performed. The claim went out clean. And the remittance paid less than the contracted rate.

This is the largest and quietest of the four, because nothing about it looks like a failure. There is no denial letter, no appeal deadline, no work queue. There is a payment, and payments read as success. Catching it requires comparing every line of every remittance against the rate the contract actually specifies — for every payer, every code, every quarter that rates changed. Almost no center does this line by line, and the ones that spot-check find enough to justify doing it properly.

Denials belong in this category too, but they are one ingredient rather than the headline. A denied case at least announces itself. An underpaid one does not.

Leak two: accounts receivable nobody ever touched

Every center has a work queue, and every work queue has a tail that no one reaches. Claims age past 90 days, then past 180, then past the point where the payer's timely-filing window closes and the balance becomes uncollectible by rule rather than by decision.

Nobody chose to write those off. They aged out while the team worked the accounts in front of them, which were newer, larger, or simply higher in the list. The distinguishing feature of this leak is that it is invisible in exactly the same way an unopened envelope is invisible — the balance sits in the aging report the whole time, correctly, and no one has a reason to look at that row.

Leak three: cases that lost money before they started

A surgery center is a facility business. The economics of any given case are the reimbursement minus what it cost to produce — implants, supplies, staffing, and the operating-room minutes the case consumed.

Some cases lose money. That is not a scandal; it is a fact of any case mix, and centers accept individual negative-margin cases for good reasons. What matters is knowing which ones and how many. Implant-heavy cases at a payer's lower rate can be reliably unprofitable for years without anyone noticing, because the two halves of the calculation live in different places: the reimbursement sits in the practice management system, and the implant cost sits in materials management or on an invoice in a different system entirely. Nothing joins them, so the margin per case is never computed, so the pattern is never seen.

Leak four: rework, which shows up as headcount

The fourth leak does not appear on the profit-and-loss statement at all. It appears in the staffing plan.

The most experienced people in a billing office — the ones who know each payer's quirks — spend a large share of their week on work that produces no new revenue. Chasing documentation from a surgeon's office. Resubmitting a claim that pended for a missing operative note. Assembling the packet for a peer-to-peer review that should not have been necessary. Sitting on hold to confirm a fax arrived.

None of that is billable and none of it is visible as a cost line. It surfaces as “we need another biller” — a hire made to absorb rework rather than volume. A case won on appeal still cost the appeal.

This is the one leak with credible published measurement behind it, and it is worth citing precisely because the other three cannot be sized from outside a specific center. CMS-published research estimates that prior authorization alone consumes roughly 13 hours per provider per week, or about $34,000 per provider per year in administrative time. The CAQH 2024 Index puts a single prior authorization transaction at roughly 24 minutes when handled manually, 16 minutes through a payer portal, and 11 minutes fully electronic.

Those figures describe prior authorization only — one category of rework among several. They are industry research about providers generally, not a measurement of any particular center, and a center's own number is knowable only from its own data.

Why the total does not exist anywhere

Each of the four leaks is individually knowable. The total is not, and the reason is worth stating plainly, because it is not a failure of anyone's diligence.

The practice management system knows what was charged and what was paid. It does not know what an implant cost. Materials management knows the implant cost. It does not know how the case was reimbursed. The schedule knows which block the case occupied and how long it ran. It knows nothing about money. The clearinghouse sees the claim leave and the remittance return, and retains no memory of the authorization that preceded either. The bank knows only that a deposit arrived.

Nothing in that chain follows a single case from the moment it was scheduled to the moment the money landed — or did not. Every system holds one true fragment and no system holds the arc. So the question “what did we earn and not keep last year” has no owner, no query, and no answer, and it goes unasked until a board member asks it.

What changes when the number exists

A total changes three conversations.

It changes the board conversation, because a leak with a number attached is a plan and a leak without one is an anxiety. It changes the payer conversation, because a center that can show which payer underpays which codes, by how much, over which period, is negotiating from evidence instead of impression. And it changes the internal conversation about staffing, because rework that has been measured can be reduced deliberately rather than absorbed by hiring.

None of that requires new clinical data or a new system of record. The information already exists inside the center. It has simply never been assembled into one arc.

What did your center earn last year and not keep?

If that question has no answer inside your own systems, that is the normal condition, not a failure of your team. We will put the four leaks on screen against the shape of your case mix and show you where each one is measured. Thirty minutes.

FAQ

Frequently asked questions