5.1 The Revenue Cycle Overview

What the Revenue Cycle Is

The revenue cycle is the full set of clinical and administrative functions that capture, manage, and collect payment for the services a healthcare organization provides. It begins before the patient arrives (scheduling) and does not end until the account balance reaches zero. Health Information Management (HIM) professionals own critical middle steps — coding and documentation integrity — and supply the data that drives every downstream metric.

The cycle is conventionally divided into three phases:

Front-End: Getting the Account Right

The front-end exists to prevent downstream denials. Registration collects accurate demographic and guarantor data; a single wrong digit in a member ID can cause an eligibility denial. Insurance verification (eligibility) confirms active coverage, the plan, and patient financial responsibility. Prior authorization secures payer approval before a service is rendered — a missing authorization is one of the most common and most preventable denial types.

Front-end errors are the cheapest to fix and the most expensive to ignore: an estimated majority of denials originate here. Point-of-service collection of copays and deductibles also improves cash flow and reduces bad debt.

Stages of the cycle, in order

1. Pre-registration / scheduling
2. Registration and insurance verification
3. Prior authorization / utilization review
4. Charge capture during the encounter
5. Coding and documentation review
6. Claim generation and scrubbing (edits)
7. Claim submission to payer
8. Payment posting and remittance reconciliation
9. Denial management and appeals
10. Patient billing and collections; account zero-balanced

Middle and Back-End

In the middle phase, charge capture records every billable service. The chargemaster — also called the charge description master (CDM) — is the master file mapping each service or supply to its CPT/HCPCS code, revenue code, department, and charge amount. Coders translate the documented care into ICD-10-CM/PCS and CPT/HCPCS codes that determine the reimbursement group (for example, the MS-DRG on an inpatient claim).

The back-end submits the claim, posts payments and adjustments from the remittance advice, works denials, and pursues outstanding accounts receivable (A/R).

Key Revenue-Cycle Metrics

• Days in A/R = (net A/R ÷ average daily net patient revenue). It estimates how long, on average, money sits uncollected. A common benchmark is under ~50 days, with the percentage of A/R aged over 90 days kept under ~15-20%.
• Clean claim rate = claims accepted on first submission with no edits or rejections, divided by total claims. High performers reach 90-95%+. Every claim that fails scrubbing adds rework cost and delays cash.
• Denial rate = claims denied ÷ claims submitted. An initial denial rate under ~5% is the common target; high denial rates signal front-end or coding breakdowns.
• Net collection rate = payments collected ÷ payments owed after contractual adjustments — it measures how much of collectible revenue is actually captured.

Trap: Days in A/R and the denial rate move together — fixing front-end eligibility lowers denials, which in turn lowers A/R days.

How HIM Drives the Cycle

Health Information Management sits at the hinge of the revenue cycle. Coders convert documented care into the codes that determine the payment group, and Clinical Documentation Integrity (CDI) staff make sure the record supports those codes. If documentation is thin, the coder must assign a lower-severity code, the MS-DRG drops, and reimbursement falls — even though the patient received the same care. This is why HIM productivity and accuracy directly affect cash, not just compliance.

The cycle is also a handoff chain: each phase depends on the one before it. A registration typo (front-end) becomes an eligibility denial (back-end) weeks later, after the cost of the entire encounter has been incurred. Because the error surfaces far downstream, the people who could have prevented it never see the consequence — which is why revenue-cycle teams measure and report metrics back to the originating department.

Why the metrics interlock

• A low clean claim rate forces rework, which raises days in A/R.
• A high denial rate ties up cash in appeals and inflates aged A/R (the over-90-day bucket).
• A falling net collection rate means legitimate revenue is leaking — often from unworked denials or write-offs that should have been appealed.

Discharged-Not-Final-Billed (DNFB)

A closely watched HIM metric is discharged-not-final-billed (DNFB) — accounts where the patient has left but the claim cannot drop because coding or documentation is incomplete. Every day an account sits in DNFB is a day of delayed cash. A coding backlog directly inflates DNFB and days in A/R, which is why staffing the coding department is a financial decision, not just an operational one. Many organizations set a DNFB target measured in days of revenue (for example, under 5 days).

Reducing DNFB usually means closing documentation gaps faster, adding coder capacity, or automating chart completion reminders — each of which shortens the lag between discharge and a dropped claim. Because the dollar value sitting in DNFB can run into the millions for a large hospital, executives track it daily alongside total A/R.