All guides

271 AAA error codes: why an eligibility check is rejected

When an electronic eligibility check comes back with an “AAA” segment, the payer is flagging a problem instead of returning normal coverage details. The code in that segment, called AAA03, tells you what kind. When the segment sits in the subscriber or patient part of the response, codes 72 and 73 point to the member ID or the name, 71 points to the date of birth, and 75 means the subscriber was not found. Fix the data you sent, then send the check again. Other AAA codes flag payer, provider or system problems, and those call for a different response.

What is an AAA segment in a 271 response?

The 270 is the eligibility inquiry your system sends. The 271 is the payer’s answer. X12 describes the pair as the way to find out whether an insurer has a subscriber or dependent on file. CMS lists the 270/271 version 5010 as the adopted HIPAA standard.

When the payer cannot give you a normal answer, it can return an AAA segment instead. According to the CAQH CORE 259 rule, the segment carries three things that matter to you:

  • AAA01, a valid request indicator. The rule has plans return “N” (no).
  • AAA03, the reject reason code. This is the number you look up.
  • AAA04, a follow-up action code. The rule has plans return “C”, which in X12 practice means please correct and resubmit.

The CORE rule covers only the patient and subscriber identification elements. For those, an AAA means the question could not be matched or was missing required data, so correct something and ask again. AAA segments can also appear for other reasons. CMS’s Medicare companion guide, for example, lists codes for provider identifiers, the request date range and a system that is unable to respond. A system problem calls for a retry later, not a data fix.

What do the common AAA03 codes mean?

These patient identification codes come from the CAQH CORE 259 document. The rule’s own required table uses 58, 65, 71, 72, 73 and 76 (duplicate subscriber ID). The rest (64, 67, 75, 77, 78) appear in its 2006 study table, so a given payer may or may not return them. Wording is paraphrased.

Code Meaning
58 Invalid or missing date of birth
64 Invalid or missing patient ID
65 Invalid or missing patient name
67 Patient not found
71 Patient birth date does not match the one in the payer’s database
72 Invalid or missing subscriber (insured) ID
73 Invalid or missing subscriber (insured) name
75 Subscriber (insured) not found
76 Duplicate subscriber (insured) ID number
77 Subscriber found, patient not found
78 Subscriber not in the group or plan identified

The same table also counts rejections for non-eligibility reasons, such as a system timeout. Those are not about your patient’s data, so retrying later can be the right move. Payers may add their own detail, so read each payer’s companion guide. CMS, for example, publishes a companion guide for its Medicare eligibility transactions.

What does the CAQH CORE rule require?

The rule exists because, as CAQH CORE put it, plans used AAA codes in inconsistent ways, and providers need specific feedback to know what to correct. Its main points:

  • When a plan rejects a request for one of the listed identification problems, it must return an AAA segment for each error it detects. Two problems can produce two segments, one for the name and one for the member ID.
  • The software that sent the 270 must show the end user text that describes the specific error. The wording is the vendor’s choice, but the meaning must stay the same.
  • The rule does not require a plan to validate IDs or dates of birth, and it does not tell plans how to search for a person.

The version linked here is from March 2011 and covers identification errors only. Do not treat it as a full list of every reason a payer might reject a check.

How often do these rejections happen?

The CORE document includes a patient ID study from 2006, with a very small sample: 7 providers, 9 health plans and 3 clearinghouses. In that study, providers reported a valid answer on the first try 82.5 percent of the time, and health plans reported 77.9 percent. The most common identification rejection for providers was “patient not found” at 9.2 percent.

That is old data from a small group, so do not use it as a benchmark for your clinic. It does show one useful pattern: the vague codes were used most, and the specific ones were rare. Your own rejection log will tell you more. Count a month of rejected checks by code, and you will see which data entry step causes most of them.

How do you fix each type of rejection?

Start with what the front desk can check in a minute.

  1. 72 or 64 (ID problems). Compare the ID to the front and back of the card. Look for a swapped digit, a letter read as a number, or a missing prefix. Check the payer’s companion guide for the ID format it expects.
  2. 73, 65 (name problems). The CORE rule treats a name as invalid only when it does not match the name in the plan’s system. Check spelling, hyphens, suffixes and whether the card shows a legal name or a nickname.
  3. 71 or 58 (date of birth). Confirm the date with the patient and check for a day and month typed the wrong way round.
  4. 75, 67, 77 (not found). Make sure you used the subscriber’s ID, not the dependent’s, and chose the right payer. A card from a new plan year may have a new ID.
  5. 78 (not in the plan). Check the group number and the plan on the card, then ask the patient if coverage changed.

If the second try fails, call the payer or use its portal. A 271 reflects coverage only at the moment it was sent, and CMS says a response is not a guarantee of payment, so record what you checked and when. Our insurance verification checklist covers what else to confirm, and our guide to 270/271 transactions explains the format.

Where Clinicrung fits

Clinicrung is being built to run routine eligibility checks and flag the ones that come back rejected, so a person can fix the data and resubmit. It is not built yet, and early access is delivered in small groups, partly by hand. Join the waitlist to follow its progress.

This post is general information about eligibility transactions, not legal, billing or compliance advice. Payer rules vary, so check each payer’s current guide and ask a qualified professional about your situation.