Revenue cycle

Medical billing vs revenue cycle management: what is the difference?

Printed revenue reports and charts on a desk, the kind used to compare medical billing with full revenue cycle management

Vendors use medical billing and revenue cycle management as if they were synonyms, usually because the second phrase sounds larger. They are not the same scope of work. This article defines each, shows where the line between them falls, explains why the difference changes what you pay and who is accountable for what, and gives a short method for working out which one your practice actually needs.

What medical billing actually covers

Medical billing, in the narrow and correct sense, begins once a visit has been documented and coded and ends when the claim has been paid, denied and worked, or written off. The biller takes the charges, checks them against payer rules (claim scrubbing), transmits the claim through a clearinghouse as an 837 transaction, posts the payment from the electronic remittance, works the denials, and sends statements to patients for whatever balance remains.

That is a real and demanding job. A good biller knows each payer’s edits, keeps timely filing deadlines, reads claim adjustment reason codes correctly and knows when to send a corrected claim rather than an appeal. But a biller cannot fix a claim that was doomed at check-in: an expired policy, a wrong subscriber ID, a service that needed authorization. Those problems arrive on the biller’s desk already formed.

  • Charge entry and claim scrubbing
  • Claim submission and clearinghouse rejection handling
  • Payment posting and reconciliation against the remittance
  • Denial rework, corrected claims and appeals
  • Patient statements and balance follow-up

What revenue cycle management covers

Revenue cycle management, or RCM, treats the practice’s revenue as one process that starts when a patient is scheduled and ends when the account reaches a zero balance. Everything medical billing does is inside it. What it adds is the front end and the oversight layer: eligibility and benefits verification before the visit, prior authorization, provider credentialing and payer enrollment, charge capture and coding review, contract and fee schedule management, underpayment analysis, patient financial communication, and reporting that ties all of it together.

The front-end pieces are the ones that most directly determine whether a claim will be paid. HIPAA standard transactions exist for most of them: 270/271 for eligibility, 278 for authorization, 276/277 for claim status, 835 for remittance. CMS maintains the administrative simplification rules that require health plans to support those transactions. A practice doing full RCM uses them systematically; a practice buying billing alone is usually doing the front end by hand, or not at all.

Medical billing vs revenue cycle management, step by step

The easiest way to see the difference is to walk one visit through the process and note who owns each step under each model.

Step in the visitBilling-only scopeRevenue cycle management scope
Scheduling and registrationFront desk works alone, no feedback loopEligibility verified from the schedule (270/271), demographics corrected before the visit
Prior authorizationAbsence discovered when CO-197 arrivesObtained and recorded with units and expiry before the service
Credentialing and enrollmentDiscovered when a provider's claims start rejectingExpirations and Medicare revalidation tracked per provider per payer
Documentation and codingBills the codes the provider selectedSamples charts, gives provider-level feedback, refreshes templates
Charge captureBills what reaches the billing systemReconciles the schedule against charges so nothing is missed
Claim submission, posting, denialsSame under both modelsSame under both models
Underpayments and contractsRarely checkedPayments compared with the fee schedule, variances pursued
ReportingCollections and agingDenials by reason code and point of origin, upstream causes named

Notice that the middle rows are the same in both columns. The disagreement is about whether the top and bottom rows are inside the contract or left to the practice, and that is the part that decides how many claims arrive at the biller already unpayable.

Where coding sits

Coding is the step most often left ambiguous on a proposal. A billing-only service usually bills the CPT and ICD-10 codes the provider selected and stops there; if the provider picks a level the note does not support, the claim goes out that way. An RCM scope typically includes at least a periodic coding audit and often full coding from the note. Neither answer is wrong, but you need to know which one you are buying, because coding errors surface as CO-11, CO-4 and CO-97 denials and, in an audit, as recoupments. Ask whether coding is included, whether the coders are credentialed and how findings reach each provider.

One visit under each model

Take a specialist visit that includes a procedure requiring authorization. Under billing-only, the front desk schedules it, the provider performs it, the biller submits it and three weeks later CO-197 comes back. The biller notes it, the practice absorbs the write-off and the same thing happens next month with a different patient. Under RCM, the scheduling entry triggers an authorization check, the request goes to the payer before the visit, the number and approved units are attached to the encounter and the claim is paid on first pass. The back-end work is identical in both stories. The difference is one step three weeks earlier, and who was responsible for taking it.

Why the difference changes what you pay and who is accountable

Pricing models look similar in both cases: a percentage of collections, a per-claim fee, or a fixed monthly retainer. What differs is what the fee is buying. A billing-only percentage covers the back end and assumes the practice delivers clean, authorized, eligible encounters. An RCM percentage covers the steps that make the encounters clean. If a proposal for full RCM is priced the same as a proposal for billing, one of them is either underscoped or overpriced, and you should ask which.

Accountability follows scope. When a denial for missing authorization comes back under a billing-only contract, it is the practice’s problem; the vendor works it, but the cause was never theirs to fix. Under an RCM contract, the vendor owns the authorization step and the denial is a defect in their process. That is the practical reason the distinction matters: it decides whose job it is when the money does not arrive.

Which one your practice needs

Start from where your revenue is actually leaking, not from what a vendor is selling. Pull your last quarter of denials by claim adjustment reason code. If most of them are coding, bundling and timely filing, your problem is in the back end and a strong billing service may be all you need. If the top codes are eligibility, coverage terminated, authorization absent and provider not enrolled, the problem is upstream, and buying a better biller will not touch it.

Then look at your staffing. A practice with a stable, trained front desk running eligibility on every visit and a manager who tracks credentialing dates already has half of RCM in-house and may only need billing. A practice that has just lost its office manager, or where the physician is the one who notices that a payer contract lapsed, needs the fuller scope. Solo and small group practices tend to be the second case, not because the staff are weak but because there are not enough of them to cover every step.

  • Denials mostly CO-16, CO-4, CO-97, CO-29: a back-end issue, and billing may be sufficient.
  • Denials mostly CO-27, CO-197, CO-22, or provider enrollment rejections: a front-end issue, and you need RCM scope.
  • Nobody tracks credentialing and revalidation dates: you need RCM scope or a separate credentialing project.
  • You cannot say what your denial rate is: you need reporting first, whichever label it comes under.

Questions that separate the two on a proposal

Whatever the vendor calls the service, the proposal should answer these in writing before you compare rates.

DyBilling offers both scopes and prices them differently, as the pricing page sets out. Under either, the work is done inside the client’s existing practice management system, denials are worked and reported by reason code, and a named account manager is responsible for the account. A free A/R review before any agreement is the most direct way to find out which scope your own numbers call for.

  • Which specific tasks are included, and which are explicitly excluded?
  • Who runs eligibility checks and when, and what happens when a patient is found inactive?
  • Who obtains prior authorizations, and is that limited to a list of procedures?
  • Is credentialing and payer enrollment included, or priced separately per provider?
  • Do you report denials by reason code and point of origin, and how often?
  • Do we keep our practice management system, or migrate to yours, and who owns the data if we leave?
  • What is the notice period after the initial term?

Questions This Article Gets Asked

No. Medical billing is a subset of revenue cycle management. Billing covers claim submission, payment posting and denial follow-up. RCM also covers the front-end steps such as eligibility verification, prior authorization, credentialing and coding review, plus the reporting that connects them to what gets paid.

Want This Applied to Your Own Claims?

Send an aging summary and a sample of denials. You get a written read on what is recoverable and which of these problems you actually have.

+1 (551) 550-0170Mon to Fri, 9:00 AM to 6:00 PM ETRequest a Free Billing Audit
Free Billing Audit