RCM Letter
CultureLong read

What the revenue cycle actually is (and what it is not)

What the revenue cycle actually is (and what it is not) Ask a physician who just bought a practice what RCM means and most will say billing and collections. Ask a hospital CFO the …

Staff Writer · · 12 min read
Culture · July 17, 2026 · 12 min read · 2,664 words

What the revenue cycle actually is (and what it is not)

Ask a physician who just bought a practice what RCM means and most will say billing and collections. Ask a hospital CFO the same question and you will often get the same answer, just delivered with more confident terminology. The shorthand is understandable. Billing and collections are the parts that visibly hurt when they go wrong: claims bounce back, cash slows, staff spend their days chasing payments. But the shorthand is wrong, and the cost of that misidentification shows up on the balance sheet.

The actual definition, as understood by the operational and financial professionals who run these systems, covers all administrative and clinical functions that contribute to the capture, management, and collection of patient service revenue. That scope begins the moment a patient schedules an appointment and does not end until the provider has accepted all payments and reconciled every outstanding balance. Registration, insurance verification, authorization, documentation, coding, claim submission, payment posting, denial management, patient collections. All of it.

When you only actively manage the back end, the upstream errors that created your back-end problems are never seen, never named, and never corrected. They compound quietly, visit after visit, until you are staring at a denial rate that appeared from nowhere. It did not come from nowhere — it came from registration, six weeks ago, in a field someone filled out incorrectly.

Why a straightforward payment process is structurally complex

On paper, the transaction should be clean. A provider delivers a service, the service is coded, the payer remits according to a preset reimbursement schedule. That is the theory. Here is what actually determines what a provider gets paid: the specific terms of its negotiated payer contract, the accuracy of the codes submitted, the compliance requirements of applicable regulations, and the coverage rules of the individual plan the individual patient happens to be enrolled in. Each of those variables changes. None of them stays fixed for long, and they do not change in coordinated ways.

High-deductible health plans have added a consumer-collections dimension that simply did not exist at scale a decade ago. Patients are now responsible for a meaningfully larger share of their own care costs, which puts providers increasingly in the business of collecting from individuals rather than institutions. Those individuals often don't know what they owe before the visit, frequently fail to pay after, and don't respond reliably to standard billing processes.

Value-based payment models press further. Rather than billing for a discrete service, organizations operating under outcomes-based contracts must demonstrate that care met quality thresholds. The financial logic of the encounter now extends well beyond the encounter itself, into documentation trails and outcome reporting that didn't exist in the fee-for-service world.

And underneath all of it: clinicians who become practice owners almost never receive any structured instruction in any of this. RCM is not taught in residency. Physicians inherit a complex, continuously shifting payment environment with no formal preparation, and the cost of early mistakes is immediate and rarely recoverable. It is a bit like handing someone the controls of a commercial aircraft and wishing them luck — the instrument panel is real, the consequences are real, and the training simply never happened.

The three-stage structure that organizes the full cycle

The field has settled on a three-stage model, and it is the right frame. Front end covers everything from scheduling through check-in. Mid-cycle covers the clinical encounter itself, specifically how care gets captured and translated into a billable claim. Back end covers everything after a claim is submitted: payments, denials, patient balances, reporting.

The value of this framework is not that it divides the work into tidy compartments. The value is that it makes visible the fact that the cycle is a chain, and chains have a particular failure property: a break anywhere affects everything after it.

A registration error does not announce itself at registration. It waits two weeks and becomes a denial. An authorization that was never obtained becomes an adjudication failure surfacing in month-end reporting, long after anyone remembers the original scheduling call. The temporal and departmental distance between where an error originates and where it lands is the central management challenge of RCM. Organizations that understand this run the cycle differently than organizations that do not.

Front-end steps: what happens before the patient is seen

Pre-registration is the cycle's first real task. Before the patient arrives, the practice needs accurate demographics, confirmed insurance information, and visibility into any coverage gaps that will affect the visit. Done well, this step makes everything downstream faster and more predictable. Done poorly, it plants errors that cost multiples more to correct later than they would have cost to prevent. The calculus is that simple, and practices routinely get it wrong anyway, spending significant staff hours each week untangling mistakes that a two-minute verification call would have eliminated at the source.

Insurance verification confirms that the patient's coverage is active, that the plan type is understood, and that the provider is in-network. These sound like administrative courtesies. They are the conditions under which a claim will be paid at all.

Prior authorization, when required, means obtaining payer approval before a procedure is performed. The administrative burden is substantial, the process is routinely friction-heavy, and providers who cite authorization failures as a primary driver of their denial rates are not describing an edge case. Authorization-related denials account for close to a third of the industry's total denial volume.

When front-end work is done accurately, patients receive realistic cost estimates before they arrive, checkout conversations are less contentious, and claims move through adjudication faster. Front-end failures are the most preventable category of denial in the revenue cycle, and also the category where disciplined process investment produces the most unambiguous return.

Mid-cycle steps: translating clinical care into billable claims

Once the patient is seen, mid-cycle work begins. Charge capture comes first: documenting every service, procedure, and supply used during the encounter. If something is not captured, it cannot be billed. That sounds obvious. It also fails with enough regularity to represent a genuine revenue leak across the industry, not a rounding error.

Medical coding translates the clinical record into the standardized numeric language (ICD-10 and CPT codes) that payers use to determine what a service was and what it should cost. Coders work from documentation written by clinicians, and the quality of that documentation has an enormous effect on what the coder can actually do with it. When a note is vague or incomplete, the coder's options narrow, and the resulting claim will not reflect the full complexity or medical necessity of the encounter. A 2023 study identified that more than four in ten clinical notes lack sufficient specificity to support optimal coding, with downstream financial consequences estimated in the tens of billions annually in underpayments. Revenue that was earned and at least partially documented, but never collected.

The output of all mid-cycle work is a claim. A clean claim is accurate, complete, and compliant with all applicable payer rules before it is ever submitted. Best-in-class organizations achieve clean claim rates at or above 95% on first submission. Getting into the high nineties means front-end and mid-cycle work is being done consistently well. Organizations hovering in the low eighties are often convinced they have a back-end problem when the problem is two stages upstream.

Back-end steps: from claim submission to final payment

Claim submission initiates the payer's adjudication process. Speed matters. The faster a clean claim is submitted, the faster the cash conversion cycle runs. Delays in submission, absent a legitimate operational reason, are simply deferred revenue.

Payment posting records what the payer actually remits against what was expected. This step is not passive data entry. It is where underpayments and contract variances surface, and practices that post payments without analyzing them against contracted rates leave recoverable money on the table every single month.

Denial management is the process of analyzing rejected claims, identifying root causes, and determining the appropriate next step: resubmission, appeal, or a process change upstream. That last option is the one most often skipped. If the same denial reason appears repeatedly, filing repeated appeals is not a strategy. It is a habit that preserves the problem.

Patient billing and collections handle whatever balance remains after payer adjudication: copays, deductibles, non-covered services. This is the part of the revenue cycle that most directly shapes how a patient experiences the financial dimension of their care, and it is handled poorly far more often than the industry would like to admit.

Reporting and analytics close the loop. Days in accounts receivable, denial rates by category, clean claim rates, collection ratios: these KPIs reveal where the cycle is leaking and where an intervention will actually move the numbers. Without them, you are managing by gut feeling rather than evidence — and in RCM, gut feelings do not show up on a balance sheet until the damage is already done.

Claim denials as the revenue cycle's most visible pressure point

Approximately 11.8% of all medical claims were initially denied in 2024, up from 10.2% in 2020. That is not a blip. It is a sustained trend moving in one direction. Medicare Advantage plans have been the sharpest pressure point, with MA-related denials spiking 59% in a single year, reflecting both the accelerating growth of the MA market and an increasingly aggressive adjudication posture among those payers.

The financial scale is hard to absorb. More than $262 billion in claims are denied annually. After accounting for the cost of appeals, administrative processing, and unrecovered revenue, the industry loses an estimated $20 to $25 billion net. The administrative cost per denied claim rose from $43.84 in 2022 to $57.23 in 2023. Denials are expensive to fight even when you win.

The root causes trace almost entirely to front-end and mid-cycle failures. Missing or inaccurate data accounts for roughly 45% of denials; authorization failures account for another 36%. These are not adjudication disputes about clinical judgment or coverage philosophy. They are process failures that occurred before the claim was ever submitted. Most of what ends up in denial management was entirely preventable two stages earlier.

The most actionable data point: 63% of denied claims that are appealed are eventually recovered. Most denials are not substantive payer disagreements about coverage. They are recoverable errors, which means the revenue lost to them is not lost to payer judgment. It is lost to internal process failure. Fix the process, and the denial rate moves.

What well-managed RCM produces across the organization

The financial outcomes of high-functioning RCM are the most legible: improved cash flow, reduced days in accounts receivable, fewer write-offs. These show up in reporting and shift the organization's financial position in ways that are measurable and attributable.

The operational outcomes are equally real, if harder to headline. Lower administrative cost of billing and appeals, reduced compliance exposure, fewer staff hours spent correcting upstream errors. These represent genuine savings even when no one in the organization can name a specific line item for them.

What gets underappreciated is how much RCM quality eventually surfaces in the patient experience. Accurate pre-visit cost estimates. The absence of a surprise bill three weeks after discharge. A smooth conversation about a remaining balance. None of these moments feel like revenue cycle to the patient. They feel like whether the financial part of their care was handled with competence or whether it was handled chaotically. That perception is a downstream function of how well the cycle ran.

The compliance dimension carries its own weight. Clean documentation trails, properly coded claims, and consistent authorization practices reduce exposure to audit risk and fraud investigation. Poor RCM is not only a financial liability — it is a regulatory one, and those two categories of exposure do not resolve on the same timeline or with the same remedies.

How AI and automation are reshaping each stage of the cycle

As of early 2024, most group practices have automated 40% or less of their revenue cycle operations. That figure grounds any honest conversation about AI in RCM, because it establishes that the transformation is real and materially underway while also establishing that it is nowhere near complete.

Where AI is currently deployed: prior authorization screening, autonomous coding, eligibility verification, denial prediction, payment posting. At the organizations doing this well, these are not pilots. They are in production, and the results are concrete. Autonomous coding reduces coding time by roughly half while improving accuracy. More than 30% of healthcare organizations were piloting or actively planning autonomous coding solutions in recent years.

The more consequential emerging category is agentic AI. Unlike rule-based automation, which follows a fixed decision tree and stops when it encounters something outside its parameters, agentic systems make autonomous decisions across multi-step workflows, adapt to shifting payer behavior in real time, and do not require human handoffs at every stage. Rule-based automation removes repetition from the cycle. Agentic AI removes the need for constant human supervision of complex, variable processes. Those are different things, and the distinction matters for how organizations should be planning their investments.

Close to three-quarters of executives now cite automation and AI as their highest priority for revenue cycle investment over the next year. That level of consensus reflects a field that has moved decisively from evaluating the technology to deploying it, imperfectly and urgently.

One thing AI does not change: the stages of the revenue cycle. Front end, mid-cycle, and back end remain structurally the same. What shifts is where human attention is required and where errors can be intercepted before they become denials. The cycle's architecture is fixed. The distribution of human labor within it is actively being renegotiated.

The persistent challenges that technology alone does not resolve

Staffing volatility is the most pervasive operational problem in RCM, and no software resolves it. Nine in ten healthcare leaders report revenue cycle labor challenges. Turnover in RCM roles ranges from 11% to 40% depending on the role and organization. That means the granular, practice-specific knowledge of particular payer quirks, documentation patterns, and denial histories is being rebuilt constantly. Every departure is a knowledge loss. Every new hire is a months-long ramp before the person is genuinely productive. You can automate a workflow; you cannot automate institutional memory.

Cybersecurity exposure is structural to how RCM systems are built. They concentrate personal, medical, and financial data in ways that make them high-value targets by design. The Change Healthcare cyberattack made the stakes concrete: a single breach caused cascading cash-flow disruptions across thousands of practices simultaneously. The data concentration that makes RCM systems powerful is the same concentration that makes them catastrophic when compromised.

Coding specificity is a human and workflow problem that technology can assist but not solve. Autonomous coding systems are only as good as the documentation they are given. A vague clinical note cannot be recovered at the coding stage, no matter how sophisticated the system processing it. The 41% of clinical notes lacking sufficient specificity for optimal coding is a physician documentation problem, and it requires intervention before the encounter note is ever signed, not after.

Payer complexity does not hold still. Coverage policies change, authorization requirements shift without notice, and regulations are revised. Any organization that believes automation can substitute for the ongoing work of tracking payer-specific requirements will accumulate denials it did not anticipate, running processes that no longer match the current rules. This happens to organizations that are genuinely committed to their technology investments. The investment itself is not the failure. The assumption that it eliminated the need for ongoing human vigilance is.

The pattern across all of these challenges is the same. A failure at registration propagates forward. A documentation gap propagates forward. A staff departure or a technology breach propagates forward. Managing RCM effectively means accepting that every stage depends on the integrity of what came before it, and that shoring up one part while ignoring another is not optimization. It just moves the leak.

Sources

  1. pmc.ncbi.nlm.nih.gov
  2. hfma.org
  3. athenahealth.com
  4. r1rcm.com
  5. os-healthcare.com
  6. gebbs.com