How to Identify Potential Bottlenecks in the Revenue Cycle

By Two Pillars & Co Advisory Group · Sources checked October 2026

What is a revenue cycle bottleneck?

A bottleneck is the stage in a process that limits throughput. In the revenue cycle, accounts move from scheduling through registration, service, charge capture, coding, billing, payment and follow-up. If coding takes 12 days because of staffing, every account waits, however fast the other steps are. The delay increases days in accounts receivable, ties up cash and raises the risk of timely filing problems. Identifying the real constraint matters because improving a non-bottleneck stage does not speed the process.

Which indicators point to bottlenecks?

The Healthcare Financial Management Association’s MAP Keys include several stage-specific measures. Days in total discharged not final billed (PB-1) divides the gross dollars in accounts discharged but not yet final billed by average daily gross patient service revenue, and is described as a trending indicator of the claims generation process.^[1] Days in final billed not submitted to payer (PB-2) isolates delays between billing and submission, and total charge lag days (PB-4) measures the average days between date of service and the posting of each charge.^[1]

Clean claim rate (CL-1) is the share of claims that pass edits requiring no manual intervention, an indicator of the quality of data collected.^[1] Aged A/R measures show how much of the receivable is old, and net days in accounts receivable divides net patient receivables by average daily net patient service revenue.^[1] The Flex Monitoring Team’s survey found that net days revenue in accounts receivable was among the three indicators rated most useful by critical access hospital administrators.^[2]

How do you locate the bottleneck?

Trace a sample of accounts through the stages and record the time spent in each: from discharge to coding complete, from coding to final bill, from bill to submission, from submission to payment, and from denial to resolution. The stage with the longest average and the widest spread is the first suspect. Compare current values with the last 12 months and with any external benchmarks you use.

Look for queues. Work queues for coding, edits, denials and follow-up should show the number of accounts, their age and the staff assigned. A queue that grows week after week is a bottleneck. Ask staff where work piles up and why.

An invented example: discharged not final billed days are 6.5, higher than the 4.0 the hospital had a year ago. A trace shows that coding of inpatient accounts averages 5 days because two coders left and were not replaced, while billing and submission take under a day. The bottleneck is coding capacity. Hiring or contract coding would reduce days in DNFB; improving the billing step would not. The numbers are illustrative only.

What causes bottlenecks?

Common causes are staffing gaps, training gaps, system downtime or changes, poor documentation that requires queries to clinicians, rules that route many accounts to manual review, unclear ownership of queues, batch processing that creates peaks, and dependence on single individuals. Volume surges and payer rule changes can also overload a stage that was adequate before.

Because causes are often organizational, solutions involve workflow design, staffing and communication as much as technology. Automation can help, but only after the process is understood; automating a broken workflow just produces errors faster.

How do you fix and monitor them?

Address the constraint with the least costly effective change: add capacity, reduce the work arriving at the stage, simplify rules, improve upstream quality or reassign tasks. Then re-measure to see whether the constraint has moved; it often does. Set targets for stage-specific indicators and review them weekly in a short operating meeting.

Keep the target in context: speed must not come at the expense of accuracy, since a fast but wrong claim costs more than a slow, correct one. The interactive example below uses invented figures to illustrate how time at each stage adds to days in accounts receivable.

Frequently asked questions

What to do next

1. Trend DNFB days, charge lag and clean claim rate for 12 months.
2. Trace 30 accounts through every stage.
3. Review work queue size and age weekly.
4. Fix the longest constraint and re-measure.