Reading a 271 response line by line

Most practice systems hide the raw X12 271 behind a green checkmark and a few benefit rows. That is fine—until a denial lands and nobody can explain what eligibility actually said on the date of service. This post is a desk-level tour of what to look for in a 271 (or the portal screen your clearinghouse builds from one), in the same order a careful registrar should read it.

ClinicOffice is educational content. We are not your clearinghouse and we do not see your payer contracts.

Remind me: 270 vs 271

270 — Eligibility, Coverage, or Benefit Inquiry (you ask).
271 — Eligibility, Coverage, or Benefit Response (the payer answers).

Those transaction names come from the X12 standards for eligibility inquiry/response (x12.org, confirmed 2026-07-21). CAQH CORE operating rules shape how many systems behave in production (caqh.org, confirmed 2026-07-21). You do not need to read loop IDs to run a good desk; you need a habit of reading the meaning of the response.

Line 1 — Did the inquiry even match a member?

Before benefits, confirm identity:

Member ID accepted or rejected
Name / date of birth match
Relationship (self vs dependent)

If the 271 says the member was not found, stop. Do not check the patient in as “probably fine.” Fix the ID, the spelling, or the payer selection and re-run. Bad identity match is how you get confident wrong answers.

Line 2 — Active or inactive for the service date?

Look for plan status on the date of service you submitted, not “last month.”

Active → continue
Inactive / terminated → call the patient before the visit; update intake if they have a new card
“Active” with a weird plan name → read the network and product type (HMO, PPO, Medicare Advantage, etc.)

Terminated coverage that still sits in your PMS is a classic path to CO-27-class denials (expenses after coverage terminated) on the public CARC list (x12.org/codes, confirmed 2026-07-21).

Line 3 — What kind of plan is this?

Product type changes front-desk behavior:

Signal	Desk action
HMO / gated network	Ask about PCP and referrals early
High-deductible	Expect larger POS conversation; verify deductible remaining
Medicare Advantage	Do not assume traditional Medicare rules
Medicaid managed care	Re-check often; enrollment can move

Green “eligible” is not a dollar amount. Find, when the payer returns them:

Copay for office / specialty / telehealth as applicable
Coinsurance percentage
Deductible remaining
Out-of-pocket remaining

Copy those numbers into the place your POS collection scripts will read from. If the 271 does not return a copay, do not invent one—use portal detail or the plan’s published schedule and document the gap.

Line 5 — Auth, referral, and limitation flags

Many 271 responses carry indicators that a service may need authorization or referral. Treat “unknown” as needs human follow-up, not as clearance. Hand off to your prior auth workflow before the patient is in the chair for an auth-prone service.

Line 6 — Other coverage / COB hints

If the response mentions additional coverage, COB, or “bill other payer,” open the secondary-insurance questions the same day. Eligibility hints do not replace the full COB intake. Missing secondaries show up later as CO-22 / CO-23 style denials on remits.

Line 7 — Reference data you will need for appeals

Save:

Date and time of the check
Service date queried
Transaction or trace ID if shown
Staff user who ran it
Screenshot/PDF policy per your compliance rules

When billing appeals an eligibility denial, this is the difference between evidence and a shrug.

A 60-second desk script while reading the screen

Match patient identity.
Confirm active for DOS.
Write copay / deductible remaining on the encounter.
Flag auth/referral.
Ask “any other coverage?” if not already documented.
File the result where billing can find it.

If any step fails, fix it before rooming—not after the claim drops.

What a 271 will not do

It will not guarantee adjudication weeks later if the employer drops coverage mid-month.
It will not replace medical necessity or coding.
It will not tell you the patient’s mood about paying the copay—that is still a human conversation at the window.

Go deeper

Full process: Eligibility and benefits playbook
Collect the amount you just verified: POS scripts
One-page SOP: Request the front-desk SOP or /#lead

When the portal and the 271 disagree

It happens: clearinghouse screen says active; payer portal says inactive—or copays differ.

Prefer the source you will defend in an appeal (document both).
Call the payer or use the portal’s benefit detail for dollars if the 271 is thin.
Tell the patient you are confirming benefits, not guessing.
Do not check them in as “probably fine” while two systems conflict.

Escalate same-day to billing when dollars at the window would change. A wrong $40 ask is recoverable; a wrong “you’re fully covered” promise is not.

Tie-in to end-of-day close

Eligibility work is not finished at check-in. End-of-day should confirm every kept appointment had a documented check (or a documented exception). Gaps become tomorrow’s denials. That habit belongs next to charge capture in your front-office close, not only in the billing department.

Sources (confirmed 2026-07-21)

X12 — 270/271 eligibility inquiry and response: x12.org
CAQH CORE — Eligibility & Benefits operating rules: caqh.org
X12/WPC — Claim Adjustment Reason Codes: x12.org/codes