The revenue cycle steps, explained in order, are scheduling, registration and eligibility before the visit; charge capture and coding after it; claim submission, remittance and payment posting; then denials, appeals and patient balances. Front desk staff own the first steps, coders the middle, and billers and payment posters the rest, until the account reaches zero.
The front-end revenue cycle steps: scheduling, registration and eligibility
The front-end revenue cycle steps happen before the patient is seen. Scheduling books the visit, registration records who the patient is and who pays, and the eligibility check confirms that the coverage is active for the date of service. Mistakes here travel through every later step, so the front end sets the quality of the whole cycle.
Scheduling looks like a calendar task, but it starts the billing record. The scheduler captures the patient's name, date of birth, reason for the visit and, for a new patient, the insurance plan they expect to use. That last detail decides whether a referral or prior authorization is needed before the appointment.
Registration fills in the rest. The patient completes an intake form with demographics, insurance details, history and consent checkboxes, and the front desk copies the insurance card. Medicare adds its own duty here: the CMS page on provider billing responsibilities says providers must determine whether Medicare is the primary or secondary payer, and recommends a questionnaire asked at each admission for hospitals and at the time of service for physicians.
The eligibility check confirms the plan will recognize the visit. When it runs electronically, it uses a HIPAA standard: 45 CFR 162.1202 on the eCFR names the X12 270/271 eligibility benefit inquiry and response. When a service needs approval first, the request and answer use the X12 278 named in 45 CFR 162.1302, the referral certification and authorization standard.
The mid-cycle revenue cycle steps: charge capture and coding
The mid-cycle revenue cycle steps turn a visit into billable codes. Charge capture records every service, supply and drug provided during the encounter. Coding translates the clinical documentation into diagnosis and procedure codes that payers accept. The output of the mid-cycle is a complete, coded charge ready to become a claim.
Charge capture starts with the clinician. In a clinic, a provider selects services on an encounter form or in the electronic health record, and those selections become charge lines. In a hospital, departments post charges from a chargemaster as services happen. A missed charge at this point is lost revenue, because no later step will invent a service nobody recorded.
Coding uses three code sets. Diagnoses use ICD-10-CM, and the CMS ICD-10 page posts the new ICD-10-CM codes the CDC announces each year, effective October 1. Procedures in the office use HCPCS, which the CMS HCPCS page splits into Level I, the CPT codes maintained by the American Medical Association, and Level II, a standardized system used mainly for products, supplies and services that CPT does not include. Inpatient procedures use ICD-10-PCS.
The coder's job is to match codes to what the record supports. When the documentation is thin, the coder sends a query back to the clinician instead of guessing. That query loop is one of the main reasons charges wait days between the visit and the claim.
Many billing offices add a short review between coding and the claim. A biller checks that every charge has a diagnosis linked to it, that the rendering and billing providers are filled in, and that the insurance on the charge matches the insurance verified at registration. The check takes minutes per account, and it catches the mismatches that otherwise come back weeks later as denials.
The back-end revenue cycle steps: claims, remittances and payment posting
The back-end revenue cycle steps happen after the claim leaves. The billing team builds and sends the claim, the payer adjudicates it and returns a remittance, and a payment poster records what was paid, adjusted and owed. The back end is where the practice learns whether the front end and mid-cycle were done right.
Claims follow prescribed formats. On paper, 42 CFR 424.32 on the eCFR names the CMS-1500 for physicians and suppliers and the CMS-1450 for institutional providers; the CMS-1500 versus UB-04 guide compares the two paper forms. The same section says an initial Medicare claim may be paid only if it is submitted electronically, apart from listed exceptions. Electronic claims use the X12 837 transaction set out in 45 CFR 162.1102, the claims standard, in professional, institutional and dental versions.
Timing matters. For Medicare, 42 CFR 424.44 on time limits for filing claims says a claim must be filed within one calendar year after the date of service. For every other payer, check the contract for its own limit. While a claim is pending, the team can ask the payer for its status with the X12 276/277 named in 45 CFR 162.1402, the claim status standard.
The payer's answer comes back as a remittance. Electronically, that is the X12 835 under 45 CFR 162.1602 on remittance advice. On paper, it is an explanation of benefits (EOB). The poster matches each line to the claim, records the payment and the adjustments, and moves any patient share to the patient's account. The claims and medical bills category covers the claim forms and their fields in detail.
Which revenue cycle steps produce the most paperwork?
The revenue cycle steps that produce the most paperwork are registration and payment posting. Registration generates intake forms, insurance card copies and consent pages for every new patient. Posting generates EOBs, remittances and deposit records for every payment. Coding produces fewer pages but depends on long clinical documents.
The table below lists every step with the role that usually owns it, the main document it handles and the system where its data lands. The roles and systems are typical, not universal.
| Step | Usual owner | Main document | System it lands in |
|---|---|---|---|
| Scheduling | Scheduler or front desk | Appointment request, referral | Practice management calendar |
| Registration | Front desk | Intake form, insurance card | Practice management system |
| Eligibility and authorization | Front desk or authorization specialist | 270/271 response, 278 response | Practice management system |
| Charge capture | Clinician, charge entry staff | Encounter form, chargemaster entry | EHR and billing system |
| Coding | Coder | Visit note, operative report, discharge summary | Billing system |
| Claim submission | Biller | CMS-1500, UB-04, 837 | Clearinghouse and payer |
| Remittance and posting | Payment poster | EOB, 835, deposit record | Billing system ledger |
| Denials and appeals | Denial specialist | Denial line, appeal letter, records | Work queue, payer portal |
| Patient balances | Patient accounts staff | Patient statement | Billing system, payment portal |
Paper concentrates where a document arrives from outside the practice. Intake forms come from patients, EOBs come from payers and outside records come from other providers. Each of those arrives as a page that someone must read and type into a system. The post on where manual data entry slows the revenue cycle counts the cost of that re-keying at each step.
Schema Care works on the incoming pages in that table: it reads intake forms, EOBs, claim forms and billing statements into fields, and holds any field it is unsure of for a person to check against the page. The list of documents Schema Care reads shows the fields it returns for each type.
Who owns each revenue cycle step in a small practice versus a hospital?
Ownership of each revenue cycle step depends on team size. In a small practice, two or three people cover every step, and the same biller may code, submit and post. In a hospital, each step has its own department, such as patient access, health information management, billing and cash posting, with handoffs between them.
The small practice
A small practice usually splits the cycle between the front desk and a billing office. The front desk schedules, registers and checks eligibility. The clinician selects codes in the EHR. One or two billers review the codes, submit claims, post payments, work denials and send statements. Some practices hand the back end to an outside billing company.
The advantage is that the same person sees the whole account. The drawback is that a biller who is posting EOBs all week is not working denials, and nothing escalates when one person is out.
The hospital
A hospital assigns each step to a department. Patient access handles scheduling, registration, eligibility and authorization. Health information management handles coding from the medical record. Patient financial services builds and follows up claims, and a cash posting team records remittances. Each handoff is a point where a detail can be lost, so hospitals rely on work queues and edits to move accounts between teams.
Whatever the size, the revenue cycle automation guide covers which of these steps software can take over and which still need a person.
When a revenue cycle step loops back: denials, appeals and patient balances
A revenue cycle step loops back when a claim is denied, appealed or leaves a patient balance. Instead of ending at payment, the account returns to an earlier step: a registration fix, a coding correction, a resubmission or a statement to the patient. Each loop restarts part of the cycle, and each adds days before the account closes.
Denials arrive on the remittance. Each adjusted line carries a reason code from the X12 Claim Adjustment Reason Codes list, which describes the codes as explaining why a claim or line was paid differently than it was billed. The code points back to the step that failed. CARC 27, expenses incurred after coverage terminated, points to registration and eligibility. CARC 197, precertification or authorization absent, points to the authorization step. CARC 16, lacks information or has submission or billing errors, usually points to claim creation. How to route each reason to the right queue is covered in denial intake, reason codes and routing.
Appeals have their own clock. For Medicare fee-for-service, the CMS page on Original Medicare appeals lists five levels, starting with a redetermination by the Medicare Administrative Contractor. 42 CFR 405.942 on the eCFR sets 120 calendar days from receipt of the initial determination to request that redetermination.
Patient balances close the loop. After the payer pays, the deductible, coinsurance or copay moves to the patient's account and goes out on a statement. The CMS guide to the explanation of benefits tells patients that an EOB isn't a bill and that the provider's bill should not be higher than the patient balance it shows. That is a useful check for the practice too: a statement that exceeds the EOB's patient balance usually means a posting error.
A worked example of one loop
This fictional example follows one claim. Every value is made up. Example patient Dana Ruiz, example member ID XKT400118, visits on March 3. The claim, example claim number 26-0441, bills $180.00. The EOB denies it with CARC 27 because the plan on file ended in February. The front desk calls the patient, records the new plan and checks eligibility again. The biller resubmits, the new plan allows $120.00, pays $90.00 and assigns $30.00 coinsurance, and the statement to the patient shows $30.00. One wrong field at registration sent the account back through four steps.