Discharged Not Final Billed: How the DNFB Clock Quietly Drains Hospital Cash

Every hospital has a pool of money it has already earned but cannot touch yet. The care was delivered. The patient went home. The revenue is real. It just cannot be billed, because the chart is not coded and the claim is not out the door. That gap has a name: discharged not final billed, or DNFB.

Here is the takeaway, stated plainly. Discharged not final billed accounts are cash the hospital has earned but cannot collect, and the longer those accounts sit, the more your cash flow suffers. When you reduce DNFB, you turn completed care into deposited dollars faster, without renegotiating a single contract or seeing a single additional patient. For a CFO, that is one of the cleanest levers in the building.

This piece explains what DNFB is, why it lands on the CFO’s desk, what pushes DNFB days up, and how the right coding staffing and managed coding support bring the number down and keep it there.

What Discharged Not Final Billed Actually Means

DNFB is a standard revenue cycle metric, not internal jargon. The Healthcare Financial Management Association (HFMA) defines it in its MAP Keys, the industry’s shared set of revenue cycle measures. Their MAP Key PB-1, “Days in Total Discharged Not Final Billed (DNFB),” is calculated as gross dollars in accounts receivable for accounts that have been discharged but not yet final billed, divided by average daily gross patient service revenue. You can see the full MAP Keys definitions on the HFMA MAP Initiative page.

Break that formula down and it tells a simple story. The numerator is the dollar value of everything sitting in the “done but not billed” bucket. The denominator is roughly how much revenue you generate on an average day. Divide one by the other and you get DNFB days: how many days of revenue are frozen in accounts that should already be on their way to a payer.

An account lands in DNFB the moment a patient is discharged and stays there until the claim is ready to submit. Most of the time, the thing holding it up is coding. A coder has to review the documentation, assign the right diagnosis and procedure codes, and finalize the chart before billing can generate a clean claim. Until that happens, the account waits. Multiply one waiting chart by hundreds or thousands of discharges a week and you get a number large enough to change how a hospital’s month closes.

One clarification worth making early, because it comes up in every DNFB conversation. You will often hear people cite a “3 to 5 day” DNFB figure. Treat that as a common operational rule of thumb that many revenue cycle teams manage toward, not as an official benchmark published by a standards body. HFMA defines how to calculate the metric, but it does not publish a public numeric target you are required to hit. The right target for your organization depends on your case mix, your payer mix, and your own baseline. What matters is the trend line and whether you are moving it in the right direction.

Why DNFB Is a CFO Problem, Not Just an HIM Problem

Coding backlogs can feel like an operational detail buried inside the health information management department. From the finance seat, they are a cash flow problem with a dollar sign attached.

Think about what a high DNFB balance does to working capital. Money stuck in unbilled accounts receivable is money that is not funding payroll, not covering supplies, and not sitting in the bank earning anything. It is revenue you have already spent resources to produce, held hostage by a processing step. When DNFB days climb, the hospital is essentially extending itself an interest-free loan against its own earnings, and doing it involuntarily.

There is also a downstream risk. Getting a claim out the door late is only the first problem. Once it goes out, it still has to survive the payer. Recent industry data shows how hard that back half of the cycle has become. Crowe reported in 2023 that 31% of inpatient claims to commercial payers were unpaid for more than three months, compared with 12% for Medicare, and that roughly eight cents of every dollar billed to commercial payers is never received. You can read the Crowe findings on payment delays and denials directly.

Put those two realities together. The billing side of the house is already slow and lossy on its own. Every day a chart sits in DNFB before it even reaches a payer stacks on top of that. You are adding self-inflicted delay to a process that is already fighting external delay. The two compound. That is why revenue cycle cash flow is so sensitive to what happens inside coding, and why the DNFB clock deserves attention at the CFO level and not just in a departmental huddle.

Late claims can also brush up against timely filing limits, run into stale authorizations, and create a lumpy, unpredictable cash pattern that makes forecasting harder. None of that shows up as a line item called “coding delay.” It shows up as a cash flow problem the finance team has to explain.

What Drives Discharged Not Final Billed Up

If DNFB is the symptom, it helps to name the causes. In most hospitals, a rising DNFB balance traces back to three pressures, and often all three at once.

1. The Coder Shortage

You cannot code charts you do not have people to code. The credentialed coding workforce has been under real strain, and the data confirms it is not a local or temporary issue. An AHIMA and NORC workforce survey in 2023 found that 83% of respondents saw an increase or persistence in unfilled health information positions over the prior year, and 66% reported persistent understaffing across two years. Among organizations with roles unfilled for six months or more, 40% said those open roles included revenue cycle management positions. The full AHIMA workforce shortage findings lay out the picture.

The demand side is not easing either. The U.S. Bureau of Labor Statistics projects medical records specialist employment to grow 7% from 2024 to 2034, with about 14,200 openings per year, according to its Occupational Outlook Handbook. More demand, a tight supply of credentialed people, and steady turnover add up to open coding seats that stay open. Every empty seat is charts that do not get worked, and DNFB days that creep up.

2. The Backlog Itself

Backlogs are not linear. They compound. When a coding team falls behind, the unworked charts do not just wait politely in a queue. They age. Older accounts get harder to work because documentation questions are staler, the clinicians who could answer a query have moved on to other cases, and the sheer size of the pile demoralizes the team that has to face it every morning.

A backlog also has a nasty way of hiding. On paper the team is coding a normal volume of charts each day. What the daily productivity number does not show is that new discharges are arriving faster than the team can clear them, so the queue keeps growing even while everyone works hard. By the time DNFB days spike on the dashboard, the backlog has usually been building for weeks. Catching it early, and having surge capacity ready to throw at it, is the difference between a bump and a crisis.

3. System Changes and EHR Transitions

Big system changes hit coding productivity hard, at least for a while. The clearest historical example is the ICD-10 transition. During that changeover, coder productivity dropped roughly 50% initially before recovering over about a year, according to a compilation of ICD-10 productivity data citing industry sources including AHIMA, HIMSS, and WEDI.

Treat that as an analogy, not a prediction. An EHR go-live, a coding platform swap, or a major workflow redesign is not identical to the ICD-10 transition, and there is no reliable single number for how much a given Epic or other EHR go-live will slow your coders. What is dependable is the shape of the curve. Productivity dips when people learn new screens, new templates, and new query workflows, and it takes time to climb back. During that dip, charts pile up and DNFB rises. Hospitals that plan for the dip, and staff for it, come out the other side without a cash flow scare. Hospitals that assume productivity holds steady tend to get surprised.

How to Reduce DNFB and Keep It Down

Bringing discharged not final billed under control is not a mystery. It comes down to having enough qualified coding capacity, aimed at the right accounts, with quality controls that keep the claims clean. That is exactly where the right staffing and managed coding partner earns its keep.

At Medovent Solutions, the health information management and coding work is built around domestic, credentialed coders and managed models with quality assurance built in. The company’s line, “large enough to scale, small enough to care,” describes the practical balance a hospital actually needs here: enough bench to cover a backlog or a go-live, and enough attention that the work does not turn into an anonymous production line. Here is how that translates into a lower DNFB number.

Fill the open seats with experienced, credentialed coders. The most direct way to reduce DNFB is to stop leaving charts unworked. Domestic coding staffing closes the gap between how many discharges you produce and how many charts you can actually finalize each day. Because the coders are credentialed and experienced, they are productive quickly rather than needing months to ramp. You can see the scope of the coding and health information management services Medovent provides on their HIM page.

Deploy surge capacity against the backlog. A standing backlog needs more than your baseline team. It needs a temporary lift that clears the aged accounts without burning out permanent staff or pulling them off current-day work. Managed coding lets you add capacity for a defined push, drive DNFB days back down, and then return to a steady state. The point is to attack the pile deliberately instead of hoping the existing team slowly digs out.

Staff ahead of system changes. If you know an EHR transition or coding platform change is coming, the time to add coding capacity is before the go-live, not three weeks after DNFB has already spiked. Building in extra coverage during the productivity dip keeps unbilled accounts receivable from ballooning while your team learns the new environment. This is one of the highest-return uses of temporary coding support, precisely because the slowdown is predictable.

Keep quality in the loop. Speed alone is a trap. A chart coded fast but coded wrong just moves the problem from DNFB to the denial queue, and a denied claim is often slower to collect than one that waited an extra day for accurate coding. Managed models with quality assurance keep accuracy and throughput moving together, so the claims leaving DNFB are clean claims that actually get paid.

Fix the documentation upstream. Coders can only code what the record supports. When physician documentation is thin or ambiguous, charts stall in queries and DNFB creeps up for reasons that have nothing to do with coder speed. Strengthening documentation at the source reduces the query volume that gums up coding. That is why clinical documentation integrity sits directly upstream of a healthy DNFB number. Better documentation means fewer stalls, faster final coding, and cleaner claims.

Do those things together and the DNFB clock stops working against you. Charts get coded on time, claims go out clean, and the cash you already earned shows up in the bank on a predictable schedule instead of an anxious one.

Frequently Asked Questions

What does discharged not final billed (DNFB) mean?

DNFB refers to patient accounts where the patient has been discharged but the claim has not yet been final billed, usually because the chart is not fully coded. It represents revenue the hospital has earned but cannot yet submit to a payer. HFMA’s MAP Keys define it as gross dollars in accounts receivable for discharged, not final billed accounts divided by average daily gross patient service revenue.

Is there an official target for DNFB days?

No standards body publishes a required numeric target. Many revenue cycle teams manage toward a 3 to 5 day range, but treat that as a common operational rule of thumb rather than an official benchmark. HFMA defines how to calculate the metric; it does not set a public target number. The most useful goal is a steady baseline appropriate to your case mix and payer mix, plus a downward or stable trend.

Why does DNFB matter so much to the CFO?

Because it is cash flow. Dollars sitting in unbilled accounts receivable are not funding operations. High DNFB days delay billing on revenue you have already earned, and that delay stacks on top of the payment lag that already exists on the payer side. Reducing DNFB accelerates cash without adding volume or changing contracts.

How can a hospital reduce DNFB quickly?

The fastest levers are adding experienced, credentialed coding capacity to close open seats, deploying surge staffing to clear an aged backlog, staffing ahead of EHR or system changes, and pairing all of it with quality assurance so the claims leaving DNFB are clean. Strengthening physician documentation upstream reduces the query stalls that push DNFB up in the first place.