Revenue cycle management for small practices: from eligibility to payment

A practice manager asks why a balance is still open. The front desk checked the insurance. The clinician finished the visit. Billing submitted the claim. Everyone completed a task, yet nobody can say what happens next.

Revenue cycle management, or RCM, is the work connecting those tasks: registration, eligibility, documentation, coding, claims, payer follow-up, payment posting and patient balances. In a small practice, several jobs may belong to the same person. That makes clear handoffs more useful, not less.

This guide proposes an operating model for independent U.S. medical practices submitting professional claims. Adapt it to your specialty, payer contracts and staffing. It is not a code-selection manual or a replacement for current payer instructions.

Download the weekly revenue-cycle review worksheet (CSV). Use it for aggregate measures and recurring issues. Keep patient and claim details in the approved billing system.

Start with one ordinary visit and trace it through the practice. At each step, identify who owns the work, what they need and how the next person knows it is ready. Assign a backup when the owner is absent.

A status should describe the work accurately. “Submitted” does not mean the payer has paid. “Needs review” is only helpful if somebody owns the review and knows why it is needed.

Collect patient and subscriber information carefully, confirm the intended payer and check coverage for the planned service date. Read the returned benefit detail rather than stopping at an active flag. Missing information needs investigation.

Eligibility, network participation, referrals and prior authorization answer different questions. Identify which apply to the expected service. If a requirement remains unresolved, record the question, its owner and the next follow-up. Our insurance eligibility verification checklist goes through this handoff in detail.

Give staff a practical way to discuss estimates with patients. Record the source and assumptions, distinguish an estimate from the final responsibility and explain what still needs confirmation. Do not treat an absent benefit field as a zero balance.

In a fictional orthopedic practice, an upcoming specialist visit may have active coverage but an unresolved referral requirement. Resolving that question before arrival gives the team options. Discovering it after submission creates a different and often more constrained problem. The example illustrates a workflow; it is not a rule for every orthopedic visit or plan.

A claim should follow the care documented. Make it easy for the clinician to see a request for clarification and for billing to see when that question is resolved. Avoid passing ambiguous instructions through several inboxes.

CMS’s E/M guidance calls for documentation supporting the codes reported. Your qualified reviewers should apply the rules for the encounter, including the appropriate code-set edition and relevant payer requirements.

AI can help propose codes or surface missing information, but the source matters. A suggestion should be traceable to the documentation, and missing clinical facts should remain a question for the clinician. Track edits and decisions through your normal review process.

Look at repeat queries. If a particular visit template regularly omits useful information, discuss the template with the clinical team. A targeted improvement can prevent the same clarification request from returning every afternoon. See the AI medical coding software checklist for a practical evaluation method.

Before submission, review required identifiers, service dates, documented codes and relevant claim fields. A claim scrubber can flag issues for staff to inspect. Passing its checks is useful, but it cannot promise coverage or payment.

After submission, inspect the acknowledgments and status responses. A transaction can pass one stage and still need attention at another. Retain the submission reference and the payer or clearinghouse response so staff can identify what actually happened.

For Medicare, CMS describes the 276 request and 277 response used to obtain claim status. A status response tells you about processing; it is not the remittance used to reconcile payment.

Set a review routine for missing acknowledgments and claims with no meaningful progress. Use the payer’s current procedures and deadlines to decide the action. Repeatedly resubmitting a claim without understanding its status can create duplicate work.

Operationally, a rejection usually means a submission failed an entry or processing check before the normal adjudication path. A denial generally reflects a payer decision on a claim or service. Read the actual response because terminology and handling vary. The distinction helps you choose the right next step.

A rejected identifier may require correction and resubmission through the appropriate process. A denial may call for corrected information, supporting documentation, reconsideration or an appeal. Do not assume that changing a field and sending the same claim again is the right answer.

• Keep the evidence: the response, relevant encounter documentation, submission history and any payer reference.
• Name the action: what must be checked, corrected, requested or submitted.
• Assign the owner: including a clinician when documentation clarification is required.
• Record the deadline: use the applicable payer or contract rule, with an internal follow-up date that leaves time to act.
• Review before sending: confirm that the proposed correction is supported and follows the required route.

When a claim is resolved, record the cause as well as the outcome. “Member identifier corrected” can point to a registration issue. “Documentation supplied” may reveal a missing handoff. A generic resolved flag loses that lesson.

An electronic remittance advice, commonly called an ERA or 835, explains the payer’s handling of claims and services. It includes payment and adjustment information. CMS explains the role of adjustment group, reason and remark codes, including adjustments at the provider level.

Posting the file is one step. Reconcile it with the corresponding payment, review amounts that do not match expectations and investigate unapplied money or provider-level adjustments. Confirm that entries land against the intended claim and account.

Review the remaining patient balance under the plan, contract and applicable rules before sending a statement. Do not assume every unpaid amount can be transferred to the patient. Give the team access to the explanation so they can answer a reasonable question about the bill.

Keep corrections, credits and refunds in a tracked process too. A growing credit balance is unfinished work even though it does not appear in an unpaid-claims queue.

Bring the oldest unresolved items, approaching deadlines and a few repeat causes to a weekly review. Keep a consistent definition for every metric. If the denominator changes from visits to claims halfway through the month, the trend stops being useful.

The downloadable worksheet includes a definition, review period, count or amount, owner, next action and review date. Start with the measures below. Use your own baseline before setting a target; there is no single healthy number that fits every specialty and payer mix.

For example, measure time from a completed encounter to first submission using the same definition of completed each week. Then separate the delay by cause: unsigned documentation, coding clarification, missing administrative information or a technical issue. That gives the team something they can change.

For denials, choose and document whether you count claim-level or service-line decisions. Keep first-pass denials separate from later resubmissions. Review payment delays alongside payer and service mix so a change in the mix does not get mistaken for a process improvement.

If an outside billing company is involved, include it in the map. Agree on who handles missing information, payer contact, patient questions and access to the underlying records. Software and outsourced labor are different purchases; compare their scope and total cost accordingly.

Moxcares RCM connects eligibility, professional 837P claims, claim review, payer responses, 835 ERA posting and denial work in the patient record. Your team retains responsibility for clinical decisions, coding review, corrections and submission. It is software for operating the revenue cycle, not an outsourced billing service.

In a demo, follow one encounter through the full path, including an exception. Ask where its owner sees the next task, what evidence is available and how the patient balance is explained. Those details will tell you more than a dashboard total.