The Pillars of Medical Billing: A Complete Guide for Independent Practices

Running an independent medical practice means owning every part of the revenue cycle. Unlike hospital systems with dedicated billing departments and enterprise software, independent practices often manage billing with small teams, fragmented tools, and hard-won institutional knowledge. The result is a process that works — until it doesn't.

Understanding the full billing lifecycle isn't just an operational concern. It's the difference between a practice that collects what it earns and one that leaves money on the table at every step.

This article breaks down the nine pillars of medical billing — the discrete stages that every claim passes through on its way from patient visit to collected revenue. Each one represents a point where efficiency is gained or lost, and where the right systems can make a meaningful difference.

1. Verification of Benefits

Before a patient is seen, someone at the practice needs to answer a simple question: is this patient eligible for the services they're about to receive, and what will they owe?

Verification of benefits (VOB) involves confirming active coverage, identifying the patient's copay, deductible, and coinsurance obligations, and flagging any coverage limitations that could affect reimbursement. For practices seeing 20-30 patients a day, this means logging into payer portals, navigating clearinghouse systems, or sitting on hold with insurance representatives — often spending 8 to 12 minutes per patient.

When VOB is done well, there are no surprises. The practice knows what it will be paid, the patient knows what they owe, and coverage gaps are caught before they become write-offs. When it's done poorly — or skipped — the consequences surface weeks later as denied claims and difficult patient balance conversations.

2. Claim Construction

Once a patient has been seen, the encounter needs to be translated into a claim. This is where clinical documentation becomes financial data.

There are two primary paths. If the practice uses superbills, the provider has already indicated the procedures performed and diagnoses treated — the billing team's job is to ingest that information, verify it, and assemble the claim. If the practice relies on chart-based workflows, the billing team (or the system they use) needs to review clinical documentation from the EHR and derive the appropriate CPT and ICD-10 codes.

Either way, the claim also needs accurate patient demographics and insurance information — subscriber ID, group number, payer ID, rendering provider details. This data typically lives in the EHR or on the superbill itself.

The output is a clean CMS-1500 or 837P transaction, ready for the next stage. The challenge is that claim construction involves pulling from multiple data sources and getting every field right. A single mismatched subscriber ID or missing modifier can derail the entire claim downstream.

3. Claim Scrubbing

Before a claim is submitted, it should be scrubbed — validated against the rules that will determine whether it gets paid.

This means checking that diagnosis codes are correctly mapped to procedure codes (Dx pointer setting), that the claim complies with payer-specific edit rules, and that it meets Medicare guidelines like CCI edits, MUE limits, and LCD/NCD coverage determinations. Many practices also benefit from scrubbing against their own submission history, catching patterns that have previously triggered denials.

The industry average first-pass denial rate sits between 15 and 20 percent. The vast majority of those denials are preventable with proper pre-submission validation. Practices that rely on manual review or basic third-party scrubbing tools are often working with incomplete rule sets and limited visibility into payer-specific requirements.

Effective scrubbing is the single highest-leverage activity in the billing cycle. Every claim caught before submission is a denial that never has to be worked.

4. Rejection Follow Up

A rejection occurs when a claim fails at the clearinghouse level — it never reaches the payer's adjudication stage. Common causes include invalid subscriber IDs, formatting errors, missing required fields, or mismatched provider information.

The manual process involves pulling rejection reports, interpreting error codes, correcting the underlying issue, and resubmitting. For practices handling rejections in batches, the turnaround can stretch from 24 to 72 hours — time during which the claim sits unpaid and the filing deadline clock keeps ticking.

Rejections are fundamentally different from denials. They're typically data quality issues with clear, deterministic fixes. The challenge isn't figuring out what went wrong — the error tells you — it's processing the volume quickly enough that nothing falls through the cracks, and resubmitting quickly enough that cash flow doesn't get interrupted.

5. Denial Follow Up

A denial is a claim that reached the payer and was adjudicated, but not paid. Unlike rejections, denials can stem from a wide range of more complex issues: medical necessity disputes, authorization failures, timely filing, coordination of benefits problems, or bundling edits the scrubbing process didn't catch.

The economics of denial management are stark. Industry data suggests that roughly 65 percent of denied claims are never worked — the billing team either lacks the bandwidth, the expertise, or the tracking systems to follow up. Yet when denials are worked, recovery rates typically fall between 50 and 70 percent.

Resolution isn't one-size-fits-all. Depending on the denial reason and payer, the appropriate path might be a corrected claim resubmission, an upload of supporting documentation, an appeal letter, etc. Each has its own requirements, deadlines, and likelihood of success. The practices that recover the most are the ones that systematically work every denial and match the right resolution strategy to each case.

6. Claim Status

Between submission and payment, claims enter a gray zone. They're out of the practice's hands but not yet resolved. Without active monitoring, aging claims can quietly miss filing deadlines or stall in payer adjudication queues.

Checking claim status manually means logging into payer portals or calling representatives. Most practices don't have the bandwidth to check proactively, so they operate reactively, only investigating when a claim has been outstanding long enough to raise concern.

Electronic 276/277 transactions offer a standardized way to query claim status, but many practices don't use them effectively. The practices with the healthiest A/R are the ones that monitor claim status continuously, flag aging claims early, and escalate before deadlines pass.

7. Payment Posting

When a payer processes a claim, the practice receives payment along with an explanation of how the amount was calculated. This arrives either as an Electronic Remittance Advice (ERA, or 835 file) or as a paper Explanation of Benefits (EOB).

Payment posting means matching each payment line to the corresponding claim, recording the allowed amount, the paid amount, and any adjustment reason codes. For paper EOBs, this also means manually extracting data from scanned documents.

Accurate posting is essential for two reasons. First, it's how the practice identifies underpayments — cases where the payer paid less than the contracted rate. Second, it triggers downstream actions: transferring the balance to the patient, generating secondary claims when a patient has multiple insurance plans, or flagging discrepancies for follow-up.

8. Patient Collection

After insurance has paid its portion, the remaining balance falls to the patient. For many practices, patient A/R is the most difficult money to collect — not because patients are unwilling to pay, but because the process of communicating what they owe is often unclear, slow, and manual.

The traditional approach involves generating individual statements, printing and mailing them, and following up with phone calls. Practices that modernize this process — offering digital statements, online payment options, and automated reminder cadences — consistently see higher collection rates and faster payment cycles.

Clarity matters as much as convenience. Medical bills are notoriously confusing. A statement that clearly explains what was billed, what insurance covered, and what the patient owes removes the friction that causes patients to set a bill aside rather than pay it.

9. Prior Authorization

Prior authorization sits at the front of the revenue cycle, before the patient is even seen. Certain procedures, medications, and referrals require advance approval from the payer, and the burden of obtaining that approval falls on the practice.

The process is manual, time-intensive, and often involves navigating payer-specific submission requirements, compiling clinical documentation, and following up repeatedly. Industry surveys consistently identify prior auth as one of the top administrative burdens in healthcare, with practices reporting an average of 45 minutes per authorization.

As payer requirements expand, prior auth is becoming an increasingly critical piece of the billing puzzle — and an increasingly attractive target for automation.

How It All Connects

These nine pillars aren't independent tasks. They're a pipeline. A missed VOB leads to a denied claim. A poorly constructed claim fails scrubbing. A rejection that isn't worked quickly enough misses its filing window. An underpayment that isn't caught at posting is revenue permanently lost.

The practices that run this pipeline well share a few characteristics: they treat billing as a system rather than a collection of tasks, they catch errors early rather than chasing them late, and they have visibility across the full lifecycle of every claim.

In the articles that follow, we'll go deeper into each pillar — how it works, where practices most commonly lose time and revenue, and how the right tools can turn each stage from a manual bottleneck into an automated workflow.

Quill is an autonomous practice management system that handles the full revenue cycle. To learn more about how Quill automates each of these pillars, explore the deep-dive articles linked below or request a demo.