A hospital can complete the patient encounter, document the care, post most charges, and still have no claim ready to send. The revenue is recorded operationally, but the account remains unbilled. That gap is captured by a key hospital revenue cycle measure: DNFB.
DNFB stands for discharged not final billed. It represents discharged patient accounts that have not reached final bill status. When DNFB grows, cash does not move because the payer has not yet received a claim to adjudicate.
At RCMGen, we view DNFB as a pre-bill workflow signal. It can point to coding delays, missing documentation, charge capture problems, bill holds, unresolved edits, or other issues that prevent an account from moving from discharge to claim generation.
What DNFB means
The Healthcare Financial Management Association includes Days in Total Discharged Not Final Billed as a standard revenue cycle MAP Key. HFMA defines DNFB as gross dollars in accounts receivable for patient accounts that have been discharged but are not yet final billed, including accounts in suspense and pending final-billed status.
HFMA describes the metric as a trending indicator of the claims generation process and notes that it can identify revenue cycle performance issues that affect cash flow. The current HFMA MAP Keys provide the formal definition and calculation framework.
Why DNFB is different from final billed not submitted
DNFB and final billed not submitted to payer are related but different stages. In DNFB, the account has not reached final bill status in the patient accounting workflow. In final billed not submitted, the claim has been generated but remains held before successful payer submission, often because of claim edits or transmission issues.
HFMA separates these measures because they point to different operational problems. A growing DNFB balance directs attention toward pre-bill functions such as documentation, coding, charge capture, and account holds. A growing final-billed-not-submitted balance points more toward claim editing, scrubber, clearinghouse, or transmission problems.
Providers need this separation to avoid sending every unbilled account to the same team.
Common reasons accounts remain in DNFB
DNFB can build for many reasons. A physician may not complete documentation. Coding may be waiting for a discharge summary or operative note. An ancillary department may not have posted a charge. A high-dollar implant or drug charge may require validation. A patient status question may need utilization review. An account may also be sitting in a standard bill hold even though no true defect exists.
Our hospital revenue cycle services connect clinical documentation, coding, charge capture, claim generation, and denial feedback because these functions all affect how quickly a discharged account can become a clean claim.
How DNFB affects cash flow
DNFB delays the start of payer adjudication. Every day an account remains unbilled is a day when the payer has not started its own processing clock. Even if the payer later pays quickly, the hospital has already lost time before submission.
This is why DNFB can weaken cash performance without appearing as a traditional denial. The account has not failed at the payer. It has not reached the payer yet.
Charge capture and documentation are closely connected to DNFB
Documentation creates a similar balance. Coders need enough clinical information to assign codes accurately, but unnecessary waiting can extend the unbilled period. Hospitals need clear escalation for incomplete charts and defined ownership for documentation deficiencies.
Our article on revenue leakage in healthcare explains how missed charges, authorization issues, payer underpayments, and unresolved balances can create losses across the revenue cycle. DNFB belongs in that broader discussion because unbilled services cannot convert to cash.
Bill hold days should be controlled, not ignored
Many hospitals use a standard bill hold or suspense period after discharge so late charges can post and coding can finish. A reasonable hold can protect claim accuracy. An unmanaged hold can hide workflow problems.
Revenue cycle leaders should know the expected bill hold by account type and compare that expected period with the actual age of DNFB accounts. Once an account exceeds the normal hold, it should move into an exception workflow with a specific owner and reason.
How to analyze a DNFB queue
A useful DNFB review goes beyond a total dollar amount. The queue should be segmented by age, service line, facility, payer, account value, and hold reason. Leaders should be able to see whether the delay is concentrated in a department, physician group, coding team, or technical workflow.
At RCMGen, we connect pre-bill performance with claim submission and A/R outcomes so the organization can see whether a reduction in DNFB leads to faster claim release and improved cash conversion.
DNFB and clean claim performance should be reviewed together
Reducing DNFB by final billing every account as fast as possible can create another problem if claims leave with missing or incorrect information. The hospital can trade unbilled A/R for payer rejections and denials.
The better objective is timely final billing with accurate claim content. DNFB, charge lag, clean claim rate, claim rejection rate, denial rate, and days in A/R should therefore be reviewed as connected measures.
Our medical billing services use claim scrubbing and payer-specific edits after charge and coding work is complete. The handoff matters because speed without claim quality only moves the delay to a later stage.
What hospital leaders should ask about DNFB
Leaders should understand how much revenue is in DNFB, how old it is, why it is held, who owns each hold reason, and how quickly exceptions are cleared. They should also know whether the reported DNFB includes intentional suspense days and whether high-dollar accounts receive a separate escalation path.
The metric is most useful when it leads to operational action. A dashboard that shows DNFB rising without identifying the source of the backlog does not solve the cash-flow problem.
Frequently asked questions
What does DNFB stand for?
DNFB stands for discharged not final billed. It refers to discharged patient accounts that have not yet reached final bill status.
Is DNFB the same as accounts receivable?
DNFB is part of unbilled receivables, but it is different from billed A/R because a claim has not yet been finalized and released for payer adjudication.
Why does high DNFB affect hospital cash flow?
The payer cannot begin adjudicating the claim until the hospital generates and submits it. Longer pre-bill delays therefore postpone reimbursement.
Should a hospital try to reduce DNFB to zero?
Not necessarily. Normal bill holds and required documentation or coding work can create legitimate DNFB. The focus should be on reducing avoidable delay while maintaining claim accuracy.