How the Healthcare Revenue Cycle Works

A claim can be perfectly coded and still arrive too late, carry the wrong member details, omit an authorisation or ask the wrong payer to pay. By the time billing sees the problem, the revenue risk may already be built into the account. That is the central lesson in understanding how the healthcare revenue cycle works: money is influenced from the first appointment contact, not only when a claim leaves the practice.

The revenue cycle is the connected process that turns a patient encounter into an accurately recorded, properly submitted and fully resolved account. It crosses the front desk, clinical team, coding, billing, payer follow-up, patient communications, finance and compliance. Each group can protect or weaken the same dollar.

The healthcare revenue cycle in 11 stages

1. Scheduling and pre-registration: capture the patient, service, provider, location and appointment details before the visit.
2. Eligibility and benefits: confirm active coverage, plan, effective dates, network status and relevant benefit information close enough to the service date to be useful.
3. Prior authorisation: determine whether the planned service needs payer approval, submit the required information and track the decision.
4. Point-of-service financial communication: give an appropriate estimate, explain known patient responsibility and collect according to practice policy.
5. Documentation and coding: the clinician documents the encounter; authorised coding staff translate supported services and diagnoses into the required code set.
6. Charge capture and reconciliation: make sure every completed service that should create a charge reaches the billing system once, with the right provider, place and date.
7. Claim preparation and submission: validate claim data, resolve edits, transmit through the chosen route and confirm acceptance.
8. Remittance and payment posting: post payer and patient payments, adjustments and contractual amounts accurately to the correct account.
9. Denial and accounts-receivable follow-up: classify unresolved balances, correct or appeal where appropriate, bill secondary coverage and work accounts before deadlines.
10. Patient billing and collections: send clear statements, answer questions, manage payment arrangements and apply compliant collection policy.
11. Reporting and improvement: reconcile financial results, trace leakage to its originating stage and change the process.

The stages are a loop rather than a relay race. A denial analyst may discover that a registration field is regularly wrong. Payment posting may expose a payer configuration problem. Patient calls may show that estimates are unclear. Those findings must return to the team that can prevent the next account from failing.

The front end is where avoidable rework is prevented

Front-end controls operate while the practice can still clarify coverage, secure information, discuss cost or reschedule a service when clinically and contractually appropriate. After the encounter, staff may be trying to reconstruct an answer against a filing deadline. Prevention is usually simpler than recovery, but it requires disciplined capture rather than a hurried insurance-card upload.

Scheduling and registration

Use required fields and a defined evidence standard. Confirm the patient’s legal name, date of birth, address, contact preference, payer, member and group identifiers, subscriber relationship, ordering or referring provider where relevant, planned service, location and service date. Check for duplicate records before creating another chart or account. Record who changed material data and when.

Separate missing information from verified information. A blank field, patient-provided answer and payer-confirmed answer should not look identical. Route exceptions to a named owner before the encounter, with an escalation path for urgent care.

Eligibility and benefits

An electronic eligibility response is evidence for the time and transaction checked; it is not a promise of payment. Review active status and the service-specific details the workflow legitimately needs. Save the response or reference, check date, method and exception outcome. Recheck under the practice’s policy when the appointment is booked far in advance or coverage may have changed.

Build a queue for inactive coverage, mismatched member data, coordination-of-benefits questions and unavailable responses. The detailed operating design belongs in the guide to insurance verification support for healthcare, while insurance verification support covers the delivery option.

Prior authorisation

Determine requirements from a current payer or plan source for the actual service, member, provider and location. Track submission date, reference number, requested and approved service, units, dates, status, expiry and evidence. An authorisation is not a guarantee of payment, and the authorised details must match the eventual claim.

Clinical decisions and medical-necessity documentation remain with appropriately qualified clinical staff. Administrative support can check requirements, assemble authorised documents, submit, follow status and escalate. See prior authorisation support for that focused workflow.

The middle cycle turns the encounter into a claim

The middle cycle is where clinical documentation and administrative data meet. Coding and billing are related but different. Coding assigns supported codes according to current rules and documentation; billing constructs, submits and follows the financial transaction. A biller should not invent clinical facts to make a claim pass, and an automated edit cannot prove that documentation supports a code.

Charge capture needs reconciliation

Do not assume every completed encounter becomes a charge. Reconcile the schedule or service log to documented encounters, charge records, cancelled visits and known non-billable activity. Define what counts as complete, how late documentation is handled, who resolves a missing charge and how duplicates are prevented.

A practical control compares source encounters with charges each business day. Exceptions might include an encounter without a charge, a charge without a matching encounter, an unexpected quantity, a late entry or a provider/location combination that the billing setup does not recognise. Assign each exception; do not merely export it.

Claim edits, rejections and clean claims

A claim scrubber applies configured edits before transmission. A clearinghouse may then reject a file or claim that fails its acceptance rules. Payer acceptance only means the claim entered the adjudication process; it does not mean the payer has agreed to pay it.

For internal management, define a clean claim as a claim accepted by the initial payer without manual correction, rejection or avoidable resubmission under the organisation’s documented rules. State exclusions such as test claims, corrected claims, secondary claims or payer outages. The definition matters more than borrowing a headline benchmark.

Rejection work should be daily. Capture the edit or rejection source, reason, affected payer and correction owner. Repeated member-ID failures belong at registration; a recurring provider-enrolment issue may belong with credentialing; a format problem may require a configuration fix. The medical billing support services guide examines the submission workflow in more depth, and medical billing support services explains the commercial service.

The back end converts payer responses into resolved accounts

Payment posting should reproduce the remittance accurately enough for finance and follow-up teams to trust the balance. Post payments, contractual adjustments, patient responsibility and denial information to the correct claim line and account. Reconcile electronic funds transfer, electronic remittance advice, manual checks, deposits and the practice-management ledger. Separate a payer-approved adjustment from an unexplained write-off.

Build a denial inventory that supports action

Classify denials by standard internal reason, payer, plan, service, provider, location, dollar value, originating stage and preventability after review. Preserve the payer’s raw reason and remittance code; do not overwrite evidence with a broad label such as “billing error.” Then route each account to an action:

• correct and resubmit using the permitted claim type;
• appeal with the required evidence and approved argument;
• request clinical review from an authorised clinician;
• bill secondary coverage after primary processing;
• transfer valid patient responsibility under policy;
• adjust only with an approved contractual or policy basis; or
• escalate a payer, enrolment, configuration or systemic issue.

Timely-filing, corrected-claim, reconsideration and appeal windows are payer-, plan-, contract-, jurisdiction- and circumstance-specific. Record the applicable deadline from a current authoritative source on the work item. Prioritise by deadline, value, likelihood of resolution and patient impact—not by account age alone.

Age accounts from a clearly stated date, such as date of service or first claim submission, and keep the basis consistent. Segment 0–30, 31–60, 61–90, 91–120 and over-120-day balances, then drill into payer status and next action. A balance is not being worked merely because it appears in a report. The account should have an owner, last action, evidence, next action and due date. See the detailed AR follow-up workflow for medical billing or the operational AR follow-up support service.

Patient responsibility needs clarity, privacy and control

Patients should receive a clear explanation of what is known, what is estimated and what remains subject to payer adjudication. Use plain statements that identify the provider, date of service, amount billed, insurance activity, adjustments, payments, current balance and contact route. Train staff to explain the account without giving coverage or legal conclusions beyond the available evidence.

Apply one approved policy for point-of-service collection, deposits, payment plans, financial assistance, refunds, deceased patients, disputes, returned mail and external collection placement. Document exceptions and authority. Verify identity before discussing protected information and use communication channels and message content approved for privacy and consent.

If an external debt collector is used, determine with counsel and the vendor which federal and state rules apply. The CFPB states that Regulation F implements the FDCPA and governs debt collectors as defined by that law; it does not follow that every provider’s own billing team has the same status. The CFPB has also reminded covered debt collectors that false, deceptive or misleading representations and unfair means are prohibited when collecting medical debt. Obtain current legal advice for the organisation, jurisdiction, channel and account type.

Measure leakage with defined formulas

Choose a baseline period and publish the data source, population, exclusions, ageing basis and owner for every metric. Do not set a target from an external benchmark until definitions and case mix are comparable.

A rate should lead to a worklist. If denials rise, identify the reason, payer, service and originating stage. If old AR grows, separate accounts awaiting payer action from internal no-action accounts. If collections improve while complaints or refund volume rises, review the policy rather than celebrating one number.

Decide what to keep, outsource or phase

Keep clinical judgement, final coding authority where required, sensitive patient exceptions, payer-contract decisions, write-off approval, bank control and executive accountability with appropriately authorised practice personnel. Support partners can perform rule-based administrative work when the scope, access and escalation boundaries are explicit.

Suitable support scopes may include pre-registration checks, eligibility transactions, authorisation status follow-up, charge reconciliation queues, claim-status checks, remittance posting, denial inventory preparation, secondary-claim administration, AR worklists, patient-statement administration and reporting. Healthcare BPO services can combine several functions; a remote medical billing assistant may fit a narrower role.

Do not outsource a broken queue wholesale. Baseline volumes, accuracy, backlog, turnaround, payer mix, access and exception rate first. Pilot one bounded process with acceptance criteria and a control group where feasible. Run parallel reconciliation, inspect samples, measure rework and expand only after stable handoffs.

HIPAA controls must follow the work

A covered entity remains accountable for selecting and governing its business associates. HHS explains that a covered entity needs written satisfactory assurances through a contract, and a business associate must obtain equivalent assurances from a qualifying subcontractor. Map every organisation and system that may create, receive, maintain or transmit protected health information; execute the required agreements before access.

Apply the HIPAA minimum-necessary standard where it applies. Limit each role to the information and functions required for its task. HHS also requires a unique user identifier for workforce members using systems with electronic PHI; shared credentials are not an acceptable substitute for controlled provisioning.

Use an accurate and thorough risk assessment, named security responsibility, access approval and removal, authentication, activity review, device and workspace controls, workforce training, incident response, contingency planning and documented vendor oversight. HHS describes the Security Rule as requiring administrative, physical and technical safeguards. Encryption choices should follow the risk analysis and current requirements; HHS publishes methods by which encryption or destruction can render PHI unusable, unreadable or indecipherable.

Test suspected-incident escalation before production. The HHS Breach Notification Rule describes duties after breaches of unsecured PHI, including business-associate notice to the covered entity. Contract language, contact trees, preserved logs and prompt factual escalation should support—not delay—the covered entity’s assessment and notification duties.

Questions to ask a revenue-cycle support partner

• Which exact tasks, decisions and systems are included, and which remain with the practice?
• How are payer rules, filing limits, appeal instructions and worklists kept current?
• What accuracy, turnaround, reconciliation, productivity and escalation definitions will be reported?
• How will access be approved, restricted, logged, reviewed and removed?
• Which entities and subcontractors may handle PHI, and which agreements apply?
• How are coding questions, clinical evidence, patient complaints and legal issues escalated?
• Who controls write-offs, refunds, bank details, payer portal changes and bulk transactions?
• How will transition, continuity, data return and secure exit be tested?

A 90-day revenue-cycle improvement plan

1. Days 1–15: define and reconcile. Map the 11 stages, systems, owners and handoffs. Reconcile encounters, charges, claims, remittances, deposits and ledger totals for a baseline sample. Publish metric definitions and ageing basis.
2. Days 16–30: expose front-end exceptions. Measure missing registration fields, eligibility exceptions, unresolved authorisations and estimate or collection gaps. Create pre-service worklists with owners and service-date deadlines.
3. Days 31–45: control claim preparation. Install daily charge reconciliation, distinguish scrubber edits from clearinghouse rejections and payer denials, and assign recurring causes to their originating process.
4. Days 46–60: segment the back end. Classify denials and AR by payer, reason, value, age and filing or appeal deadline. Give each material account a documented last action, next action, owner and due date.
5. Days 61–70: secure the workflow. Confirm business-associate relationships, role access, unique users, logging, training, incident escalation, continuity and access-removal tests.
6. Days 71–80: pilot support. Transfer one defined queue with an approved procedure, sample review, daily reconciliation and escalation channel. Compare accepted output, rework, turnaround and backlog with baseline.
7. Days 81–90: decide and improve. Review cash, AR, clean claims, denials, patient issues, cost and control evidence. Fix upstream causes, adjust the scope and approve expansion only where the pilot is stable.

Next step

Choose one payer group or service line and bring 60–90 days of encounters, charges, claim acceptance, remittance, denial, AR and patient-balance data. A useful assessment should reconcile the flow, identify leakage by originating stage and produce a prioritised control plan—not only a larger collection worklist.