Three places hospitals leave revenue on the table without realizing
When we talk to hospital owners about revenue leakage, the first assumption is usually theft. It almost never is. In our experience building hospital systems, the money leaves through gaps in how things get recorded — and the people involved have no idea it is happening, because from where they stand nothing looks wrong.
Here are three places it goes, all of which are invisible in a monthly P&L.
1. Consumables opened in theatre
A surgery runs long. The team opens an extra set of sutures, a second mesh, another pack. In theatre, that is a clinical decision made in seconds and correctly nobody stops to think about billing.
What happens next decides whether the hospital gets paid for it. If the consumption is written on a sheet and that sheet travels to billing later, some of it will not make it — not through dishonesty, but because the sheet is incomplete, or illegible, or arrives after the bill is closed. The item is gone from stock either way. Only the revenue is missing.
This is the cleanest example of the pattern: the hospital has already paid for the item and already delivered the value. Everything needed to bill it existed at the moment it was used. It was lost purely in transit between two records.
2. Stock that expires in the right order
Most pharmacies say they run FIFO — first in, first out. For medicine that is the wrong rule. The correct rule is FEFO: first expiry, first out. A batch received later can easily expire sooner, and if you dispense strictly by receipt date you will hold the short-dated batch until it is worthless.
The difference sounds academic until you look at a write-off register. Expiry losses are usually treated as a cost of doing business, which is why they rarely get investigated. But a large share of them are not inevitable — they are the arithmetic result of picking stock in the wrong order, month after month.
This one compounds quietly. Nobody notices a single expired box. The register only shows the total, and the total gets accepted as normal.
3. Insurance deductions nobody argues with
A TPA settles a claim for less than it was raised for. The remittance arrives with a deduction and a reason code. Somebody records the receipt and moves on to the next claim.
Some of those deductions are legitimate. Some are not — a document that was actually submitted, a tariff applied at the wrong rate, a package rule misread. The only way to know which is which is to reconcile line by line against what was raised, and that takes time the billing team does not have while new claims are stacking up.
So the deduction gets accepted by default. Not because anyone decided to accept it, but because nobody had the hours to challenge it inside the appeal window. Multiply a small average shortfall across a year of claims and this is frequently the largest of the three.
The pattern underneath all three
None of these is a people problem, and none of them is fixed by asking staff to be more careful. In every case the information needed to get paid existed at the moment the event happened. It was lost because the system required someone to move it from one place to another, and that transfer is where things fall through.
Which is why the fix is structural rather than procedural:
- Record consumption at the point of use, so the clinical record and the billing record are the same record and there is no transfer to lose.
- Enforce FEFO in the picking logic rather than in the training manual, so the short-dated batch is the one the system hands over.
- Reconcile remittances against raised claims automatically, so a shortfall surfaces as an exception to review rather than a line nobody reads.
Better reporting does not solve any of this. A dashboard showing you last month's leakage is still a dashboard about money you have already lost. The goal is a system where the leak structurally cannot happen — where there is no second copy of the record to go missing in the first place.