Eligibility and benefits playbook for the front desk

Eligibility is the highest-leverage denial-prevention step a front desk owns. When coverage, plan order, or cost-sharing is wrong at registration, the claim is already on a path to denial—before coding, before the note is signed, and long before billing opens the remittance.

ClinicOffice is a content property of AdvancedCare USA Inc. These playbooks are educational. We do not run your eligibility stack, connect to payers, or manage your front desk.

Why eligibility is a front-desk job

A large share of denials start with registration and insurance data, not with the coder. Industry revenue-cycle reporting (including HFMA and similar RCM benchmarks, as of 2026-07) consistently flags eligibility, demographics, and coordination of benefits as top root causes. Treat that as directional—your own denial log is the scorecard that matters.

Denials the desk can prevent by getting eligibility right include (names from the Washington Publishing Company CARC list, as of 2026-07-21):

CARC	Common name / meaning (short)
CO-22	May be covered by another payer (coordination of benefits)
CO-23	Impact of prior payer adjudication (COB residual issues)
CO-27	Expenses incurred after coverage terminated

Link each of those codes to a concrete desk habit: wrong primary, missing secondary, or a terminated plan that was never re-checked.

The 270/271 transaction in plain language

In HIPAA electronic transactions, X12 270 is the eligibility, coverage, or benefit inquiry. X12 271 is the response. Together they are how clearinghouses and practice systems ask a payer “is this member covered, and what are the benefits?” and get a structured answer back. See the X12 standards overview for Eligibility, Coverage or Benefit Inquiry/Response (x12.org, confirmed 2026-07-21).

You do not need to speak EDI to run a good process. You do need to know:

• The 270 is only as good as the identifiers you send (member ID, name, date of birth, relationship, date of service, provider identifiers).
• The 271 is a snapshot for a service date—not a promise that adjudication will match if the plan changes later the same month.
• CAQH CORE publishes operating rules that govern how eligibility inquiries and responses behave in production systems (caqh.org, CORE Eligibility & Benefits operating rules, confirmed 2026-07-21). Your vendor may already implement them; the desk still owns the human steps around the tool.

For traditional Medicare, eligibility also runs through CMS channels such as HETS (HIPAA Eligibility Transaction System). Confirm current access paths in CMS materials for providers (cms.gov, confirmed 2026-07-21).

Day-before and day-of cadence

At scheduling (or as soon as the appointment is on the book):

1. Capture card images (front and back) or an electronic equivalent.
2. Confirm subscriber vs patient, plan name, and whether a referral or auth flag is obvious on the card or portal.
3. Run eligibility if the visit is within a few days; otherwise queue it for the day-before batch.

Day before (T-1):

1. Batch-run 270/271 (or portal checks) for the next day’s schedule.
2. Flag: inactive coverage, plan change, high deductible remaining, missing referral/auth, secondary payer present, or “other coverage” indicators.
3. Call patients whose coverage is inactive or unclear before they arrive. A five-minute call beats a lobby argument and a denied claim.

Day of:

1. Re-check same-day adds, walk-ins, and anyone flagged overnight.
2. For commercial plans that change mid-month, day-of is cheap insurance. For stable traditional Medicare, a monthly rhythm is often enough—still document what you checked and when.

What to capture into the chart from the 271

Do not stop at “eligible: yes.” Record enough that billing can defend the claim and the desk can collect correctly at the door:

• Active / inactive status and plan type (HMO, PPO, Medicare Advantage, etc.)
• Deductible remaining and out-of-pocket remaining (when returned)
• Copay and coinsurance for the visit type you are seeing
• Prior authorization or referral indicators when present
• Other coverage / COB order hints (then complete the intake COB flow)
• Date/time of the check, who ran it, and the transaction or reference ID if your system provides one

That documentation is what turns a later denial into an appeal with proof instead of a he-said-she-said with the payer.

Commercial vs Medicare cadence

Payer type	Practical cadence	Notes
Commercial / employer	Day-before + day-of for changes	Coverage can end with a job change without notice to you
Medicare Advantage / managed	Day-before at minimum	Plan rules and networks vary; do not assume fee-for-service habits
Traditional Medicare	Monthly for established, day-before for new or long-gap patients	Use HETS / approved eligibility channels
Medicaid / managed Medicaid	Day-before + day-of when enrollment is volatile	State plans vary; treat “active last month” as insufficient

Documenting the 271 so denials can be appealed

When a claim comes back with CO-22, CO-23, CO-27, or a related eligibility reason:

1. Pull the stored 271 (or portal screenshot policy your compliance team allows) for the date of service.
2. Show active coverage and benefit data as of that check.
3. If the payer’s file later disagreed, you still prove front-desk diligence—and you know whether the fix is COB, a corrected claim, or patient billing.

Store results where billing and the desk both can find them. A sticky note is not an appeal packet.

Front-desk eligibility checklist

• Card (or electronic ID) on file for this plan year / this visit
• Subscriber relationship and spelling match the payer file
• 270/271 or portal check completed for the service date
• Copay / deductible / coinsurance noted for POS collection (scripts)
• Auth / referral flags reviewed; auth incomplete visits not rendered blindly (prior auth workflow)
• Secondary / accident / MSP questions completed when indicated (COB intake)
• Result documented with timestamp

What this playbook is not

It is not a clearinghouse product, a payer contract, or legal advice. Plan rules differ. When a 271 and a portal disagree, escalate to billing or your payer representative before the patient is in the chair with the wrong expectation.

Next steps

• Point-of-service collection scripts — collect what eligibility just told you is due.
• Intake that prevents COB denials — finish the registration questions eligibility alone cannot answer.
• Request the one-page front-desk SOP — eligibility script + copay script + COB intake in one page.
• Or use the form at the bottom of this page / homepage lead form.

Sources (confirmed 2026-07-21)

• X12 — Eligibility, Coverage or Benefit Inquiry (270) and Response (271): x12.org
• CAQH CORE — Eligibility & Benefits operating rules: caqh.org
• Washington Publishing Company / X12 code lists — Claim Adjustment Reason Codes (including CO-22, CO-23, CO-27): x12.org/codes
• CMS — Medicare eligibility / provider resources (including HETS context): cms.gov
• Industry RCM literature (HFMA and peer benchmarks) — registration/eligibility as a major denial root cause; treat percentages as directional, not a guarantee for your specialty

---