Reducing DNFB: Discharged Not Final Billed in Hospitals

DNFB accumulates in a small number of predictable places. Late charge capture is the most common: a consumable issued in the ward, a procedure done at the bedside, or a service rendered on the last day that reaches billing after the account should have closed. Second is missing clinical documentation — a discharge summary or operative note not completed, which blocks coding.

Third is coding itself, either backlog capacity or a case awaiting clarification from the treating consultant. Fourth is pending investigation results, where a report that has not been finalised holds the whole account. Fifth, and often overlooked, is a payer-side prerequisite: a missing pre-authorisation reference or an incomplete document set that billing knows will cause a rejection, so the account is held deliberately.

That last category deserves its own treatment, because it is a rational hold rather than a failure. Distinguishing deliberate holds from accidental ones is the first analytical step; otherwise the daily review spends its time on accounts that are exactly where they should be.

DNFB is managed daily or not at all. A weekly review lets an account age five days before anyone looks at it, and by then the people who could have resolved it have moved on to other work. The daily review is short — fifteen to twenty minutes — and it works on exceptions rather than the whole list.

The structure that works: accounts are sorted by days since discharge, each carries a hold reason, and the review looks at anything past a defined threshold. Each aged account gets a named owner and an action, and the same account appearing three days running is escalated rather than re-noted. The discipline is in the escalation, not the listing.

Attendance matters. A DNFB review with only billing staff in the room can identify problems but cannot fix the ones caused by medical records, coding, or the wards. Rotating representation from those functions, even briefly, turns the meeting from a report into a resolution mechanism.

Headline DNFB days tells you the size of the problem but not its shape. Two hospitals can both sit at six days with completely different situations: one has a broad, even backlog reflecting a systemic lag, the other has most accounts billing in two days and a handful of large accounts stuck for a month. These need different interventions.

Report the distribution alongside the average. Segment by days-since-discharge bands, by hold reason, and by department, and the actionable picture emerges. A concentration in one specialty usually points to a documentation habit; a concentration in one band points to a process step with a fixed delay built into it.

Set a target that reflects what is genuinely achievable given your coding capacity and documentation turnaround, and hold it stable long enough to see trend. A target that moves every quarter cannot be missed, which means it also cannot be met.

The cash impact of DNFB is direct and easy to quantify, which makes it a useful number for getting attention. Every day of DNFB is roughly one day of gross revenue sitting outside the collection cycle entirely — it has not been billed, so the payer's clock has not even started. Reducing DNFB by two days releases approximately two days of gross revenue in one-time working capital.

Using the illustrative figures from earlier, a hospital at 30 lakh average daily gross revenue that moves from six DNFB days to four releases roughly 60 lakh of cash on a one-time basis, and permanently shortens its cash conversion cycle by two days thereafter. That is a real number that a finance committee will act on, and it usually costs far less to achieve than an equivalent improvement in collections.

There is a second-order cost too. Accounts billed late are more likely to hit payer filing deadlines, more likely to have documentation gaps because the clinical team has moved on, and more likely to be disputed. Late billing does not just delay cash, it reduces the probability of collecting it.

The daily review contains the problem; it does not solve it. Durable DNFB reduction comes from changing where charges and documents originate. Charge capture at the point of service rather than by later data entry removes the largest single cause. Discharge summary completion tied to a defined window, with visible accountability, removes the second.

System design does a lot of the work here. Charges posted directly from the ward, OT, and pharmacy modules as the service happens do not need to be remembered later. A platform such as HealUDoc can post charges from the clinical workflow itself and flag accounts where a required document is missing before discharge rather than after, which converts a billing chase into a ward-level prompt.

Coding capacity is worth checking honestly. If coding is a genuine bottleneck, no amount of review meeting will fix it, and the answer is resourcing or workflow redesign rather than exhortation. Hospitals often discover their coding backlog is a staffing question they have been treating as a discipline question.

DNFB is a metric that regresses. A concerted effort brings it down, attention moves elsewhere, and within two quarters it has drifted back. The reason is that the underlying causes are distributed across departments whose primary work is not billing, and the pull of their own priorities is constant.

Sustaining requires the metric to stay visible to people who can act on it, and to carry consequence. Weekly reporting to department heads, with their own accounts named, keeps it alive far better than a monthly finance report nobody outside finance reads. HealUDoc dashboards can surface department-level DNFB alongside clinical operational metrics so it appears in the same review the department already attends.

Finally, protect the definition. DNFB has a habit of quietly shrinking through reclassification — accounts moved into a new hold category that is excluded from the measure. Fix the definition, document it, and treat any proposal to change it with appropriate suspicion.