Discharged Not Final Billed explained
DNFB is the facility counterpart to unbilled AR. Coding backlogs and missing documentation are the usual drivers.
Daily review of DNFB accounts keeps claims moving and protects cash flow.
Where Discharged Not Final Billed fits in the revenue cycle
Discharged Not Final Billed sits within across the entire revenue cycle, as a measurement layer. It is a revenue cycle metric or reporting concept used to measure financial and operational performance.
Discharged Not Final Billed is also referred to as DNFB. You'll encounter it on payer communications, billing reports, and in conversations between front-office, coding, and accounts-receivable teams.
Why Discharged Not Final Billed matters for your practice
You can't improve what you don't measure. Revenue cycle KPIs turn day-to-day billing activity into signals leadership can act on, flagging where cash is stuck, which payers are slow, and where denials are concentrating. Defining these metrics consistently is what makes benchmarking and goal-setting meaningful.
- Measures financial or operational revenue cycle performance
- Used for benchmarking, goal-setting, and root-cause analysis
- Consistent definitions make trends and comparisons reliable
- Common examples include days in A/R and net collection rate
Discharged Not Final Billed in practice
Knowing what Discharged Not Final Billed means is only useful if it changes what your team does. In a modern revenue cycle, that means catching issues related to reporting & KPIs earlier, documenting and coding them correctly, and using technology to flag exceptions automatically rather than discovering them after a claim is denied.
This is exactly where a specialty-built revenue cycle platform earns its keep: by encoding the rules behind terms like Discharged Not Final Billed directly into the workflow, so clean claims go out the first time and your team works by exception instead of chasing problems after the fact.
