Hospital revenue leakage: where it happens, how to stop it

Where does revenue actually leak in an OPD+IPD hospital?

A revenue leak is simply a gap between what a clinical or operational event should have billed and what the hospital actually collected. It's rarely fraud — far more often, it's a step that depends on someone remembering to raise a charge, chase a payment, or check a balance, and one day they don't. In a busy Indian OPD+IPD hospital, that gap opens up in the same handful of places, over and over: unbilled consultations, medicines dispensed before payment, tests run before payment clears, discharges that ignore an outstanding balance, discounts nobody double-checked, cash that doesn't reconcile at close, doctor payouts calculated from a figure that changed, and package or tariff prices billed out of date — all inside the same GST billing workflow the hospital already runs every bill through. Each one has a same-day check that catches it, and a process control that prevents it recurring — that pairing, not a once-a-month audit, is what actually closes a leak.

1. Unbilled consultations

How it happens: a patient is registered and seen, but no bill is ever raised for the visit — most often where registration and billing are two separate steps, or a walk-in is seen outside the normal queue.

Daily check: reconcile the day's encounters against the day's bills — any visit with no matching bill line is a leak, found the same day, not discovered weeks later.

Control: make the charge part of creating the visit, not a separate step someone has to remember, with a defined waiver or void path for genuinely no-charge cases (a doctor reviewing their own follow-up, a visit that was cancelled) rather than simply never billing it.

2. Medicines dispensed without full payment

How it happens: pharmacy dispenses against a prescription while billing is still pending, or takes a partial payment and the balance is never chased afterward.

Daily check: a list of pharmacy sales below full payment for the day — a queue that surfaces on its own, not a filter a biller has to remember to apply.

Control: treat an underpaid dispense as an exception that needs a reason and an approver, not a silent partial sale — a genuine emergency dispense is still possible, but it becomes visible and accounted for instead of invisible.

3. Tests run before payment clears

How it happens: a lab order is billed correctly the moment it's placed, but nothing checks payment status again before the specimen is collected or the report is released — so an order can travel all the way to a released report with an unpaid or part-paid bill behind it.

Daily check: a same-day list of specimens collected or reports released against an order that isn't fully paid.

Control: a payment check at collection and again at report release, with the same authorised-exception path for genuine urgent cases — STAT tests, emergencies — so the control never becomes the reason care is delayed.

4. Discharges with outstanding dues

How it happens: discharge is a clinical decision, and the bed/discharge workflow doesn't require the balance to be checked before the patient leaves — so a discharge with a real outstanding balance quietly passes as routine.

Daily check: for every discharge, the outstanding balance at the moment the bed was freed — not the balance the next morning, after collections staff have had a chance to work on it.

Control: a billing-clearance step before discharge is finalised — a cleared balance, an authorised credit, or an explicit waiver, never a silent zero. If the patient has an advance deposit on file, apply it to the balance first, rather than treating the full amount as a fresh shortfall.

5. Unapproved or self-approved discounts

How it happens: whoever has permission to apply a discount can also approve it — so there's no real separation between offering a concession and signing off on it.

Daily/weekly check: discounts applied, grouped by who applied them, checked against who is actually authorised to approve at that value.

Control: a request-then-approve workflow where the person requesting a discount is never the person approving it, with the reason recorded against both steps.

6. Cash drawer variance

How it happens: cash collected during the day doesn't match the system-expected total at closing — sometimes a genuine counting error, sometimes an unrecorded refund, sometimes something worse — but without a daily close, small variances go unnoticed and compound.

Daily check: a per-cashier day close — counted cash against system-expected cash — with the variance called out explicitly, never netted away against other differences.

Control: a mandatory daily close, done by someone other than the cashier who collected the cash, with the variance trend reviewed weekly. An occasional ₹50 difference is noise; the same cashier showing a variance every week is a pattern worth a direct conversation.

7. Doctor payout errors

How it happens: doctor payouts — revenue-share, per-visit or per-procedure fees — are usually calculated from a report pulled separately from live billing, so a correction made to a bill afterward (a discount, a void, a refund) doesn't automatically flow into the payout figure, and a doctor gets paid against a number that no longer matches the bill.

Check, before marking a payout run paid: that its total still ties back to the underlying bills as they stand today, not as they stood when the report was first pulled.

Control: a clear draft-then-paid lifecycle for payout runs, so a draft can be corrected and recalculated before it's finalised, rather than a figure that's paid and then has to be clawed back.

8. Package and tariff mismatches

How it happens: a package price (a delivery package, a day-care procedure package) is billed at a stale rate, or a per-diem room tariff doesn't match what's actually configured for that room category — usually because the tariff master and the bill were edited independently of each other.

Periodic check: at least monthly, compare billed package and tariff rates against the current tariff master and flag anything that doesn't match.

Control: generate package and per-diem bill lines directly from the tariff master, not retyped — a rate change in one place becomes a rate change everywhere, and a mismatch becomes something to investigate, not routine.

A weekly revenue review checklist

• Encounters vs bills raised, reconciled for the full week, not just the current day.
• Pending exceptions by type — unbilled consultations, pharmacy/lab shortfalls, discharge shortfalls — counted and aged, oldest first.
• Discounts applied this week, grouped by who applied them, against each person's actual approval limit.
• Cash-close variance trend by cashier, flagged if the same person repeats week over week.
• Payout runs this week — still draft vs marked paid, and whether any paid run needed a correction afterward.
• Any package or tariff mismatch found, and whether the tariff master or the bill line was the one that was wrong.
• One person owns this review — ideally whoever can see collections, discounts and payouts together, not each department checking only its own numbers in isolation.
• Revenue per occupied bed for the week, tracked alongside the leakage numbers — our ARPOB calculator is a quick way to see whether closing a leak is actually moving the underlying number.

Common mistakes

• Treating revenue leakage as a month-end finance problem instead of a daily operational one — by month-end, the transaction detail needed to fix the root cause is usually gone.
• Gating a step on payment with no exception path — a gate that also blocks a genuine emergency gets switched off by staff under pressure, and then protects nothing at all.
• Reviewing collections and discounts separately, so a manager who can approve their own discount is never actually checked.
• No reconciliation between the tariff master and what's actually billed, so mismatches surface only when a patient complains.
• Marking payout runs paid before confirming the underlying bills are final.