Last updated: 2026-09-23
Getting paid for one patient visit takes far longer than the visit itself. This page opens with what happens between a booking and the moment a practice is paid, then defines revenue cycle management in plain terms. The seven stages come next as a table, from the front desk to the last dollar collected. Front end and back end follow, because most of what looks like a back-office coding failure started at a keyboard on the way in. Registration gets its own section, since that's where the breakdown starts and where it's cheapest to stop. Coding comes after it, then claim submission and the scrubbing a file goes through before a payer ever sees it. Payment posting closes the loop and reconciles it. Measurement is next, covering the metric that shows a problem first and how long one cycle should reasonably take. Ownership follows as the risk section, on what happens when nobody owns the work. Outsourcing gets a yes-or-no answer, with the conditions a practice has to meet before it's the right call. Support from a virtual professional comes after that, and the page closes where revenue cycle management meets your other billing workflows, with every source named.
Between a booking and a paid balance sit seven handoffs, and money leaks at every one of them. A front desk takes the appointment and captures a name, a date of birth, an address and an insurance card. Someone checks the plan's active and that the service needs no prior approval. The provider sees the patient and documents what happened. Then a coder turns that note into CPT and ICD-10 codes. A biller builds the claim, scrubs it for errors and files it to the payer. Adjudication follows, the plan pays part of the charge and pushes the rest to the household. Last, somebody posts the remittance and works whatever is still open.
Each handoff belongs to a different person, sometimes a different system, and sometimes a different company. Nobody watches the whole line. That gap is what revenue cycle management exists to close, and it explains why a denial landing in week six traces back to a keystroke in week one.
Revenue cycle management is the set of administrative and financial steps a healthcare organization uses to capture, bill and collect the money it earns from patient care. The cycle opens when a patient calls for an appointment and closes when the account reaches zero, whether that happens through a payer payment, a patient payment, a contractual adjustment or a written-off balance. Nothing in the middle is skippable.
Three counterparties stay in the conversation the whole way through, such as the patient, the commercial health plan, and the government programs Medicare and Medicaid. Each keeps its own rules about what it covers, what documentation proves the service happened, and how many days you get to ask. Revenue cycle management is the discipline of satisfying all three sets of rules on the same encounter.
People shorten the phrase to RCM, and the shorthand hides the point. A practice that bills well and registers badly has not managed a revenue cycle. It's managed one link and left the rest to chance.
Seven stages make up the revenue cycle, and they run in a fixed order because each one inherits whatever the stage before it got wrong. Front-end stages happen before and during the visit. Back-end stages happen after the claim goes out. That split matters, since the two halves are staffed by different people who rarely speak to each other.
| Stage | What happens in it | What an error here costs later |
|---|---|---|
| Patient registration | Name, date of birth, address, guarantor and insurance card captured at booking or check-in | A wrong member ID returns as a rejection weeks later, after the encounter is cold |
| Insurance verification | Coverage, plan type, deductible status, copay and prior authorization requirements checked before the visit | An unverified plan produces a non-covered service and a patient balance nobody warned the household about |
| Charge capture | Services performed during the encounter recorded as billable charges | A missed charge is revenue that never enters the cycle and never shows on any report |
| Medical coding | CPT, HCPCS and ICD-10-CM codes assigned to the documented encounter, with modifiers where needed | A code the note does not support draws a medical necessity denial or an audit |
| Claim submission | Claim scrubbed against payer edits, filed through a clearinghouse and accepted or rejected | A rejected file nobody reworks ages silently until the timely filing window shuts |
| Payment posting | Remittance advice applied line by line against each charge, with adjustments and patient responsibility split out | A misposted write-off hides an underpayment and makes every downstream report wrong |
| Accounts receivable follow-up | Open insurance and patient balances worked by aging bucket until paid, adjusted or written off | An unworked bucket passes its appeal deadline and converts to a write-off by default |
Some practices add credentialing and payer contracting to the list. Both shape what you're allowed to bill and how much you get paid for it, though neither moves with an individual encounter, so they sit alongside the cycle rather than inside it.
The front end of revenue cycle management affects the back end by deciding, before a single code is assigned, whether the claim can be paid at all. Registration and eligibility set the payer, the member ID, the plan type, the deductible status and the authorization requirement. All of those fields get copied forward onto the claim without being re-checked by anyone. A wrong digit in a member ID doesn't announce itself at the desk. It comes back six weeks later as a rejection nobody in billing can fix without calling the patient.
Lag is what makes the connection so hard to see. The team that caused the denial has moved on, and the team receiving it has no route back to the source. So the denial gets reworked, the claim pays on the second pass, and the same error repeats the following Tuesday.
Denials are the honest scoreboard for front-end quality. Sort one month of them by reason code and the registration desk's error rate sits in the top three.
Revenue cycle management breaks down at patient registration because the desk is the only stage where data is typed rather than inherited. Everything downstream copies. The desk creates. It also does the creating under the worst conditions in the building, such as a ringing phone, a full waiting room, a patient who forgot the new card, and a scheduling screen that doesn't force the fields anyone downstream needs.
Four errors do most of the damage. A stale insurance card puts a terminated plan on a live claim. Transposing a member ID or group number becomes a rejection at the clearinghouse. Leaving the guarantor blank sends the patient statement to nobody. One missed secondary plan leaves a household holding a balance it never owed.
None of that's a training problem alone. Registration accuracy is a workflow question, and the step that prevents most of it is a coverage check run before the visit rather than during it, which our insurance verification guide walks through.
Coding fits into revenue cycle management as the translation layer between what a clinician documented and what a payer will recognize. A coder reads the note, assigns CPT or HCPCS codes for the services performed and ICD-10-CM codes for the diagnoses that justify them, then applies modifiers where the circumstances change how a service should be read. Get the pairing wrong and the claim is denied for medical necessity even though the care was necessary and delivered.
Two failure modes matter here, and they pull in opposite directions. Upcoding bills a higher level of service than the documentation supports, which invites recoupment and audit exposure. Downcoding bills lower than the note supports, which quietly funds the payer out of the practice's own pocket. Both start as documentation problems rather than coding problems.
Credentialing bodies exist because the work is technical. The AAPC credentials professional medical coders and billers, so a practice hiring for this seat should ask which credential a candidate holds and whether it's current.
Claim submission adds the last checkpoint where an error is still cheap to fix. A biller assembles the claim, runs it through a scrubber that tests it against payer edits, corrects whatever the scrubber flags, and files it electronically through a clearinghouse. The clearinghouse checks format and basic eligibility, then routes the file onward. Two different failures happen at this point and practices confuse them constantly. A clearinghouse rejection means the claim never reached the payer, so there's no adjudication clock running and no appeal right exists. Denial by the payer means the claim was received, adjudicated and refused.
Timely filing is the deadline that punishes the confusion. A rejected file sitting in a work queue nobody opens ages exactly the way a live claim does, and the filing window shuts on it anyway. The Centers for Medicare and Medicaid Services publishes the claim, code set and billing rules that federal payers hold you to, and its Medicare coding and billing guidance is where those rules sit.
Payment posting closes the revenue cycle by reconciling what the payer says it did against what the practice expected, line by line, until the account balance is true. Electronic remittance advice arrives carrying an allowed amount, a paid amount, a contractual adjustment and a patient responsibility for every service line, plus reason codes explaining any difference. A payment posting specialist applies each of those to the charge it belongs to.
Accuracy at this stage decides whether every report downstream tells the truth. Post a payer's underpayment as a contractual write-off and the shortfall vanishes from the aging report, from the denial log and from anyone's attention. Put a patient responsibility in the wrong bucket and the household gets billed for money the plan still owes.
Closing the line is the other half of the job. Every service line should end in a payment, an approved adjustment, a balance transferred to the patient, or an appeal in flight. A line ending in none of those hasn't closed at all.
Clean claim rate shows a revenue cycle problem first, because it moves the week the problem starts rather than the month after. The metric counts the share of claims that pay on first submission with no edit, rejection or appeal. Days in accounts receivable, the number most practices watch, lags it by a full adjudication cycle and by definition says nothing about a claim that hasn't been rejected yet.
Denial rate sits between the two and it's worth tracking for scale. Experian Health's "State of Claims 2025" survey of 250 healthcare professionals, fielded in June and July 2025, found 41% of providers reporting denial rates of 10% or higher, and 68% saying clean claim submission had become harder than a year earlier.
Track all three on one report basis and the story reads itself. Rising denial rate alongside a falling clean claim rate points at registration and coding, and a practice weighing outside help can compare the field in our ranking of revenue cycle specialist companies.
One revenue cycle should take as long as your slowest payer needs to adjudicate plus whatever lag your own team adds, which is why a national average is the wrong thing to copy. Typical duration varies by payer and by specialty. A surgical practice billing global periods won't ever read like a behavioral health practice billing weekly sessions.
Four inputs set the length, such as charge lag, payer adjudication time, the statement cycle and the appeal path. Charge lag is the gap between the date of service and the day the charge is entered, and it's the piece you control outright. Payer adjudication runs on contract terms rather than goodwill. The statement cycle is a policy the practice writes for itself. Appeals restart the clock, so one denial can double the life of a claim.
Measure yours from date of service, never from date of billing. Aging from the billing date hides every day a charge sat unentered, and a practice carrying a four-day charge lag reads its own performance four days better than it is.
When no one owns revenue cycle management, the work doesn't stop, it just stops being anybody's fault. Each stage keeps running inside its own silo, each team hits its own target, and the revenue falling between them belongs to nobody. Symptoms are specific and they surface in this order.
Ownership doesn't require a new hire. It requires one named person who reads the aging report, the denial log and the clean claim rate on the same day, holds authority to send a problem back upstream, and answers for the number at the bottom.
Yes, a practice should outsource revenue cycle management when claim volume has outgrown the people working it and nobody inside the building owns payer follow-up. No, when there's still capacity in house and someone who knows your payer mix. Volume, in-house capability and payer mix decide which side of that line you're on.
Two purchase models exist and they price on different things. Staffing puts a person in your system at an hourly rate and leaves the strategy, the payer relationships and the outcome with you. Outsourced revenue cycle management sells the outcome and takes a share of what it collects, so Transcure publishes 3% to 5% of monthly collections for its full service, read from that company's own site on 21 August 2026.
Your in-house baseline is the other half of the arithmetic. The Bureau of Labor Statistics "Occupational Employment and Wage Statistics" release puts the median wage for billing and posting clerks at $23.32 an hour (Source: Bureau of Labor Statistics, May 2025), before benefits, payroll taxes, software seats and supervision.
A virtual professional supports revenue cycle management by taking repeatable, documented parts of the cycle off people who can't get to them, such as eligibility checks, charge entry, claim status research, payment posting and aging follow-up. The work lives inside your practice management system and payer portals, which a remote user reaches like anyone on site.
Honest Taskers staffs these seats at $10.00 to $12.65 an hour depending on background, schedule, scope and location. New clients may receive a two-week working trial with their first selected professional. Staff are HIPAA-trained under a dedicated compliance officer, and a Business Associate Agreement is signed before anyone reaches protected health information. Recruiting runs in the Philippines, Latin America, India and Pakistan, and professionals work your US time zone. Most placements complete within one to three weeks of a signed agreement, and the company reports 99.6% average monthly retention.
One limitation deserves naming. This isn't an outsourced revenue cycle service, it's staffing, so your team still owns the billing strategy and the outcome. A remote professional recommends a write-off or an appeal; somebody with signing authority decides it.
Revenue cycle management meets four workflows a practice already runs separately, such as medical billing, medical coding, claim denials and payment posting. Each owns a stage of the cycle, and each has a page of its own.
Medical billing owns the middle of the cycle, from charge entry through claim submission to the posting of whatever comes back. A biller builds the claim, applies payer edits, files it, reads the remittance and works the rejections that bounce. What billing doesn't own is the data it inherits, which is why a billing team can run a clean process on top of bad registration and still watch its denial rate climb. Practices that treat billing as the whole revenue cycle hire a second biller when the real gap sits at the front desk, and our explainer on medical billing marks where that scope ends.
Medical coding feeds the revenue cycle with the codes every downstream step depends on. A coder reads the documentation, assigns CPT, HCPCS and ICD-10-CM codes, and applies modifiers where the encounter calls for them. Payers adjudicate against those codes and nothing else, so a note supporting a service the code doesn't describe gets refused for medical necessity. Coding also sets audit exposure in both directions, since upcoding invites recoupment while downcoding gives away earned money without anyone noticing. A practice deciding whether to add this seat in house or hire it remotely can start with our explainer on what a medical coder does.
Claim denials stall the revenue cycle by sending a completed encounter back to the start with a deadline attached. Every denial carries a reason code, an appeal window and a rework cost the practice pays whether or not the appeal wins. Denials cluster, which is the useful part. Sort a month by reason code and a handful of causes account for most of the volume, and most of those causes sit in registration, eligibility or documentation rather than in billing. Working denials one at a time treats the symptom, while reading them as a report fixes the source, and our guide on how to reduce claim denials covers that loop.
Payment posting returns the truth to the revenue cycle. Until a remittance is posted line by line, the aging report, the denial log and the collection numbers are all estimates. A poster matches every allowed amount, paid amount, contractual adjustment and patient responsibility to the charge it belongs to, then flags the ones that don't reconcile. Posting errors are quiet by nature, because a misapplied write-off closes an account that was never paid and the report looks better for it. Practices outsourcing this step on its own can compare providers in our ranking of payment posting specialist companies.
Stage definitions and the rejection-versus-denial split follow Centers for Medicare and Medicaid Services claims and billing guidance. Coder credentialing comes from the AAPC. Denial figures are Experian Health's "State of Claims 2025" survey of 250 healthcare professionals, fielded June and July 2025. The $23.32 median hourly wage for billing and posting clerks is from the Bureau of Labor Statistics "Occupational Employment and Wage Statistics" release (Source: Bureau of Labor Statistics, May 2025). Transcure's 3% to 5% of monthly collections is that firm's published pricing, read 21 August 2026. Honest Taskers terms come from its published service terms. No fixed duration appears here, because payer mix and specialty decide it.
Request candidates with revenue cycle experience in your payer mix and practice management system.
