Free PDF · Medical Billing

Eligibility & Verification Workflow

Eligibility errors are the single largest source of preventable denials in the revenue cycle. A coverage check that's stale, skipped, or misread at registration becomes a CARC 27 denial weeks later — after the visit, after the bill, when the patient is hardest to collect from. This workflow standardizes the 270/271 process so coverage, benefits, and patient responsibility are nailed down before the patient is seen.

✓ Why verify before the visit, not after
✓ The verification workflow
✓ What to read off the 271 response
✓ Process control questions

★★★★★Trusted by 3,000+ buyers· built from 23 medical billing software tools· independent

PDF · FreeEligibility & Verification Workflow

Where should we send it? Free · arrives in seconds · no spam.

We email it to you — one-click unsubscribe anytime.

1Tell us where to send it
Your name and work email — nothing more.
2Check your inbox
Your guide arrives in seconds, not days.
3Use it with your team
Editable and ready to share — make it your own.

A peek inside

See exactly what you're getting

Free PDF

Spotsaas · 2026

Eligibility & Verification Workflow

✓ Why verify before the visit, not after

✓ The verification workflow

✓ What to read off the 271 response

✓ Process control questions

Get the guide →

What it is

The Eligibility & Verification Workflow is a downloadable PDF that standardizes how a practice confirms a patient's coverage, benefits, and financial responsibility before the visit — using the 270 eligibility inquiry and its 271 response. It exists because eligibility errors are the single largest source of preventable denials in the revenue cycle: a coverage check that's stale, skipped, or misread at registration becomes a CARC 27 denial weeks later, after the visit, after the bill, when the patient is hardest to collect from. The workflow moves verification to where it belongs — before the patient is seen — so coverage, benefits, and patient responsibility are nailed down in advance.

The workflow runs in four phases. Pre-visit (2-3 days out) runs a batch 270/271 inquiry for the upcoming schedule, confirms each plan is active for the scheduled date of service, captures plan type and network status, and flags any patient whose 271 returns inactive or 'not found' for outreach. Benefit detail capture records copay, coinsurance, deductible status, and out-of-pocket maximum, and identifies whether the planned CPT needs prior auth or a referral. Authorization & referral submits and records any required authorization and confirms PCP referrals for HMO/POS plans. Patient financial clearance calculates the estimated responsibility, communicates it, and collects at or before check-in.

The PDF also includes a reference table for reading the 271 response — what each data element (eligibility status, effective/term dates, copay/coinsurance/deductible, service-type benefits, prior-auth indicator, COB) tells you and what to do if it's wrong or missing — plus process-control questions about eligibility-denial rate, recurring-patient re-checks, and tying point-of-service collections to the verified estimate. Its core operating principle: automate the batch 270 the night before each clinic day and exception-route only the patients whose 271 comes back inactive or 'not found,' so the front desk spends its time on the handful that need a human.

What it's used for

Practices use the workflow to convert eligibility from a reactive, error-prone step at check-in into a proactive, batched process that runs before patients arrive. It is the single highest-leverage way to prevent the largest category of denials while improving point-of-service collections.

✓ Running a batch 270/271 eligibility inquiry 2-3 days ahead of each clinic day so coverage is confirmed for the scheduled date of service before the patient arrives.
✓ Confirming the plan is active within its effective and termination dates and capturing plan type (HMO/PPO/EPO/POS), network status, and primary vs. secondary order.
✓ Capturing benefit detail — copay, coinsurance percentage, individual and family deductible met versus remaining, and out-of-pocket maximum — to drive an accurate patient estimate.
✓ Identifying service-level requirements, such as whether the planned CPT needs prior authorization or a PCP referral, and submitting and recording any required auth.
✓ Calculating and communicating the patient's estimated responsibility so copay and deductible can be collected at or before check-in, where collection rates are far higher.
✓ Reading the 271 response correctly — eligibility status, coverage window, benefits, prior-auth indicator, and COB order — and routing any inactive or 'not found' result to outreach.
✓ Re-verifying eligibility for recurring or series patients each visit, since coverage can terminate mid-series and let later visits deny if checked only once at the start.

Who uses it

The workflow is owned primarily by the front office but its results matter to billers and managers downstream. It connects scheduling, registration, and patient financial counseling into one pre-visit verification routine.

Front-desk and registration staffThey capture and confirm coverage at the point of contact and use the workflow to exception-route only the patients whose 271 returns inactive or 'not found,' rather than re-keying coverage that hasn't changed.

Eligibility / verification specialistsThey run the batch 270/271 inquiries, read the 271 responses, and manage the prior-auth and referral steps that determine whether a service will be covered.

Patient financial counselorsThey turn the captured benefit detail into an estimate, communicate it, and set up payment plans or financial-assistance screening, capturing more at the point of service.

Billers and A/R staffThey feel the downstream effect directly — accurate pre-visit verification is what prevents the CARC 27 and COB denials that otherwise land in their work queues weeks later.

Revenue cycle managersThey track the share of denials that are eligibility-related and use the workflow's process-control questions to confirm verification is being run at the right time and on every recurring visit.

Context & good to know

Eligibility is where the revenue cycle is won or lost before any care is even rendered. Roughly a quarter of all denials trace back to eligibility and registration problems — inactive plans, wrong payer, expired coverage, or unmet prior-auth requirements — and every one of those is knowable before the encounter through a real-time 270/271 inquiry. Verifying after the fact only tells you why the claim will be denied; verifying before the visit lets you fix the problem while it's still fixable, by contacting the patient, rescheduling, or initiating an authorization.

Verification also drives the patient side of collections, which matters more every year as high-deductible plans push cost onto patients. When you know the copay, coinsurance, deductible status, and out-of-pocket maximum before the patient arrives, you can collect at check-in — where collection rates are far higher than chasing a balance after adjudication. The workflow's goal of zero surprises serves the patient, the front desk, and the biller simultaneously, and it shrinks patient A/R by capturing dollars before they ever enter aging.

On Spotsaas, real-time 270/271 eligibility, auto-batched verification, and patient-estimate tooling are among the features that most clearly separate billing platforms. The ability to run the night-before batch automatically and exception-route only the problem cases is exactly what makes this workflow scalable. The eligibility workflow pairs directly with the Clean-Claim Submission Checklist and the Patient Statement & Collections Workflow, and practices comparing software on Spotsaas should weigh how seamlessly each vendor automates batch eligibility and surfaces patient estimates at registration.

✓ Independent · vendors can't pay to rank

Built on verified data, not vendor spin

Every Spotsaas resource draws on the Spotsaas Score — a blend of verified review ratings, review volume, and feature depth across 23 medical billing software tools. Refreshed regularly; data as of June 2026.

FAQ

Questions, answered

What is a 270/271 eligibility transaction?

The 270 is the standardized electronic inquiry a provider sends to a payer to check a patient's coverage and benefits; the 271 is the payer's response. The 271 reports eligibility status, plan effective and termination dates, copay/coinsurance/deductible, service-level benefits, prior-auth requirements, and coordination-of-benefits information. Running a 270/271 before the visit is the foundation of preventing eligibility-related denials.

Why verify eligibility before the visit instead of after?

Because before the visit the problem is still fixable. About a quarter of denials trace to eligibility issues, all of which are knowable in advance via the 270/271. Verifying after the encounter only confirms why the claim will deny — too late to contact the patient, reschedule, or get an authorization. Pre-visit verification also lets you collect the patient's portion at check-in, where collection rates are much higher.

What information should I capture from the 271 response?

Read eligibility status (active/inactive), plan effective and termination dates, copay/coinsurance/deductible (met vs. remaining), out-of-pocket maximum, service-type benefits for the planned CPT, the prior-auth indicator, and any coordination-of-benefits/other-coverage detail. Each element drives an action: confirm the date of service falls in the active window, build the patient estimate, initiate any required auth, and set the correct primary/secondary billing order.

How far in advance should eligibility be verified?

The workflow recommends running a batch 270/271 inquiry 2-3 days before each clinic day. That's far enough ahead to act on problems — reach a patient whose plan is inactive, initiate an authorization, or confirm a referral — but close enough that coverage is unlikely to change before the visit. For same-day adds and walk-ins, run the inquiry at registration.

Why re-verify eligibility for recurring or series patients?

Coverage can terminate mid-series — between therapy sessions, infusion visits, or a course of treatment. A one-time eligibility check at the start of the series will let later visits deny if coverage lapses. The workflow's process-control questions specifically ask whether eligibility is re-checked each visit for recurring patients, because this is a common and avoidable source of denials.

How does eligibility verification improve patient collections?

When you've captured copay, coinsurance, deductible status, and out-of-pocket max before the visit, you can calculate and communicate the patient's estimated responsibility and collect it at or before check-in. Point-of-service collection rates are far higher than back-end statement collections, and dollars collected at check-in never enter A/R aging — so verification directly shrinks patient A/R and reduces bad debt.

What is a CARC 27 denial and how does this workflow prevent it?

CARC 27 means coverage was expired or not in effect on the date of service. It's a classic eligibility denial that appears weeks after the visit. The workflow prevents it by confirming, via the 271, that the plan is active and the date of service falls within the effective and termination dates before the patient is seen — so a coverage problem is caught and resolved in advance rather than denied later.

Should eligibility verification be automated?

Yes, for efficiency and accuracy. The workflow recommends automating the batch 270 the night before each clinic day and exception-routing only the patients whose 271 comes back inactive or 'not found.' That way the front desk spends its time on the handful of cases that need human attention instead of manually re-keying coverage that hasn't changed. Real-time, auto-batched eligibility is a key feature to compare when selecting billing software.

How do I handle coordination of benefits in eligibility?

When a patient has more than one plan, the 271's COB/other-coverage element tells you the primary versus secondary order. Setting the correct billing order before submission prevents COB denials, where a claim is rejected because it was sent to the wrong payer first. The workflow captures primary/secondary order during the pre-visit and benefit-detail phases so the claim is routed correctly from the start.

What share of denials should be eligibility-related?

It should be low — a few percent at most. If eligibility denials (CARC 27, 26, 31) run higher than that, the workflow's process-control question points to the likely cause: verification is being skipped, or it's being run too early so coverage changes between the check and the visit. Tracking this share is the cleanest way to know whether the verification process is actually working.

Keep exploring