The Stages of the Revenue Cycle, in Depth
The revenue cycle is a sequence, and every stage sets up the next. This article goes stage by stage — from scheduling to the last worked balance — to show what happens at each step, where revenue leaks, and how an early choice becomes a paid claim or a denial later. For the big picture first, start with What Is Revenue Cycle Management?.
Updated 6 min read
On this page
Key takeaways
- The cycle groups into three phases: front-end (before and at the visit), mid-cycle (turning care into charges), and back-end (getting paid).
- Most back-end pain has a front-end cause — an eligibility miss or a missing authorization surfaces much later as a denial.
- Each stage has a natural failure mode and a downstream metric it moves, so the cheapest fix is almost always upstream.
- Every concept named here has a single canonical home — a glossary term, a metric page, or a workflow — that this article links to rather than redefining.
How the stages fit together
A single claim moves through the same ordered path every time, and the stages group into three phases — front-end (before and at the visit), mid-cycle (turning care into charges), and back-end (getting paid). The What Is RCM? overview introduces that grouping; the three sections below walk each phase in depth. The grouping is not academic — it is the fastest way to locate a problem, because most back-end symptoms trace to a front-end or mid-cycle cause.
One concept, one home
Front-end: before and at the visit
The front-end is where revenue is most cheaply protected, because a few minutes of accuracy here prevents hours of rework later.
Scheduling & registration
Patient demographics and insurance details are captured when the appointment is booked. A transposed policy number, a misspelled name, or an outdated plan entered here does not fail now — it fails weeks later as a returned or denied claim, which is why registration accuracy is a revenue control, not clerical detail.
Eligibility & verification
Coverage is confirmed active for the date of service and the planned care, and the patient's share is estimated. This is usually done electronically through an eligibility verification inquiry. A large share of denials trace back to an eligibility miss — inactive coverage, the wrong plan on file, or a non-covered service.
Prior authorization
Where a payer requires prior authorization for a service, it is obtained before the care is delivered. A service that needed authorization but was provided without it is one of the hardest denials to overturn, so tracking each payer's requirements is a front-end discipline.
Patient estimate
With coverage confirmed, the practice can tell the patient what to expect to owe — reducing surprise bills and the disputes and slow collections that follow them.
Mid-cycle: turning care into charges
The mid-cycle converts what happened clinically into a billable, correctly coded claim. Two failure modes live here: billing for less than was done, and coding it in a way the payer will not accept.
Clinical documentation
The provider's record of the encounter is the evidence behind every code and the basis of medical necessity. Coding can only be as complete and defensible as the documentation it rests on.
Charge capture
Every billable service is recorded so none is dropped between the exam room and the claim — charge capture. A missed charge is silent revenue loss: care delivered but never billed, and nothing downstream can recover a charge that was never captured.
Back-end: getting paid
The back-end turns a coded claim into collected cash — and is where front-end and mid-cycle quality is finally tested.
Claim scrubbing & submission
The claim is checked against payer edits and sent — typically through a clearinghouse that scrubs it and routes it to the payer. A clean claim passes those edits on the first pass; a claim rejected at the clearinghouse can be fixed and resent before it ever counts as a payer denial.
Payer adjudication
The payer reviews the claim against the plan and decides what to pay — adjudication. Medicare follows rules set by the CMS, state Medicaid programs follow federal CMS requirements plus their own state rules, and commercial payers apply their own plan and policy terms.
Payment posting
The decision returns on a remittance advice — electronically, the ERA — and the patient receives the matching EOB. Payments and contractual adjustments are posted so each balance reflects reality and any patient responsibility is billed correctly.
Denials & appeals
A denied or underpaid claim is investigated, corrected, and appealed rather than written off, and its root cause is fixed to prevent repeats. The denial appeal process sets out that work step by step.
A/R follow-up & reporting
Open balances in accounts receivable are worked to resolution — the older a balance, the less likely it is to be collected — and reporting closes the loop by showing where revenue moved and where the cycle can improve.
Where each stage is measured
Each stage has a metric that reveals whether it is working. Reading them together — not one in isolation — is how a healthy cycle is judged; each metric's definition and how to calculate it live on its own page.
- Submission quality (front-end and mid-cycle) → clean claim rate
- Adjudication outcomes → denial rate
- Collection speed (back-end) → days in A/R
- Revenue captured → net collection rate
Tip
Why upstream fixes beat downstream firefighting
Because the stages are sequential, a problem is cheapest to fix at its source. A rise in back-end denials is frequently solved not in the appeals queue but in front-end eligibility and mid-cycle coding — the stages that created the denial in the first place. Managing the revenue cycle as one connected process, rather than a set of separate tasks, is what makes that upstream fix visible.
See how the whole sequence is run for a practice on the Medical Billing Services page.
Frequently asked questions
What are the three phases of the revenue cycle?
Front-end (scheduling, registration, eligibility verification, prior authorization, and patient estimates), mid-cycle (clinical documentation, charge capture, and medical coding), and back-end (claim scrubbing and submission, adjudication, payment posting, denials and appeals, and accounts-receivable follow-up). The phases run in order, and each sets up the next.
Which stage causes the most denials?
Denials appear at the back-end, during adjudication, but their causes usually sit in the front-end and mid-cycle: an eligibility miss, a missing prior authorization, incomplete charge capture, or a coding choice the payer will not accept. That is why prevention is concentrated upstream, even though the symptom shows up downstream.
What is the difference between charge capture and medical coding?
Charge capture records that a billable service was performed, so it is not dropped between the exam room and the claim. Medical coding translates that captured service into standardized CPT and ICD-10 codes the payer can adjudicate. Capture is about completeness; coding is about accuracy.
Key terms in this article
Plain-language definitions, defined once on their glossary pages.
Continue learning
Go deeper on the cycle — the overview, the metrics that measure it, and the choice of who runs it.
What Is Revenue Cycle Management?
The big-picture overview this article goes deeper on.
Revenue Cycle KPIs
How the metrics for each stage are read together.
In-House vs. Outsourced RCM
Who should run the stages — a balanced decision framework.
The Denial Appeal Process
The step-by-step workflow for the denials-and-appeals stage.
Medical Billing Services
How the full sequence is run for a practice.
Revenue cycle metrics
Every KPI's definition, calculation, and how to read it.
Glossary
Plain-language definitions of the terms used here.
Authoritative sources
- Centers for Medicare & Medicaid Services (CMS) (opens in a new tab)
The U.S. agency that administers Medicare and Medicaid and sets many billing and coverage rules.
- American Medical Association — CPT (opens in a new tab)
Maintains the CPT code set used to report medical procedures.
- X12 (opens in a new tab)
Maintains the EDI transaction standards used for eligibility, claims, and remittance.