CO-31 Denial Code: Patient Cannot Be Identified as Insured, Explained

CO-31 means "Patient cannot be identified as our insured." The payer searched its member file using the demographic data on your claim and came up empty. No match, no payment. This is one of the most fixable denials in the queue because the patient almost always does have coverage. The problem is a mismatch between what your front desk recorded and what the payer has on file.

What CO-31 means

• CO stands for Contractual Obligation. The adjusted amount cannot be billed to the patient while the denial stands unresolved.
• 31 means the payer ran your submitted demographics (member ID, name, date of birth) against its enrollment database and found no matching covered member.

A simple example: your claim goes out with member ID XYZ123, the name "Smith, John," and a date of birth. The payer finds no record matching that combination and returns CO-31. The claim is not denied for clinical reasons; the adjudication system simply could not locate the member.

Why CO-31 fires

Five causes account for most CO-31 volume:

• Wrong member ID at registration. The patient brought a spouse's old card, copied the number down incorrectly, or the front-desk team transposed two digits.
• Name mismatch. A hyphenated surname submitted as a single surname, a maiden name on the ID card versus a married name in the payer system, or a nickname on the schedule instead of the legal name on the enrollment record.
• Date-of-birth error. Month and day are commonly flipped during intake data entry. One transposition is enough to break the member match.
• Newly enrolled member. The patient just started this plan and the employer's roster update has not yet processed. The patient is genuinely covered, but the payer's system does not know it yet. Calling provider relations confirms whether enrollment is pending.
• Dependent billing under the wrong ID. Some payers issue separate member IDs per family member. Others use the subscriber's ID for the whole family. If a dependent's claim goes out under the subscriber's ID with the dependent's name, or the reverse, the match fails.

How to fix a CO-31 denial

Work through this in order. Each step either confirms the correct data or narrows what is wrong.

• Run a real-time eligibility check for the date of service. Use the patient's full legal name, group number from the card, and (where the payer accepts it) the last four of the SSN to widen the match. The response either confirms coverage and returns the correct member ID, or tells you there is no active record for this individual.
• Contact the patient if the eligibility check returns nothing. Ask them to call the member services number on the back of their card to confirm their member ID, spelling, and effective date. Patients who have recently changed employers or got married are the most likely to hand you outdated information.
• Call provider relations if your data looks correct. Bring the member ID, the patient's name and DOB, and the date of service. The payer representative can look up the account on their side and identify whether the enrollment system has a discrepancy or a pending update.
• Submit a corrected claim once the data is confirmed. Use the corrected-claim process (frequency code 7 on the 837P, or the "Corrected" flag in your billing system) with the original claim number and the corrected demographic fields. Do not submit as a new claim; a second claim with the original data produces a CO-18 duplicate denial on top of the existing CO-31.

CO-31, CO-27, and CO-28: the differences

These three codes all show up on eligibility-related denials and are easy to confuse.

• CO-27 means expenses were incurred after the patient's coverage ended. The patient was covered at some point, but the policy terminated before the date of service. The question shifts to patient liability or retroactive-continuation claims.
• CO-28 means the payer has no active coverage record for the date of service. It is similar to CO-31 but typically implies coverage existed at some point and was not active at the time of the claim, rather than a flat member-match failure.
• CO-31 is specifically a member-identification failure: the payer cannot locate anyone matching your submitted demographics in its enrollment database at all. The root cause is almost always a data entry or enrollment processing error, not a genuine absence of coverage.

The distinction matters for how you respond. CO-27 usually leads to a patient-balance question. CO-28 often points to an enrollment lag or early-termination dispute. CO-31 almost always has a correctable data error at its root.

Preventing CO-31 denials at the front desk

CO-31 is one of the few denial types where prevention is cheaper than recovery. Three registration habits eliminate most of the volume:

• Verify member ID at every visit. Member IDs change when employers renew plans, when patients switch plans during open enrollment, and when a spouse changes jobs. A card scanned a year ago may no longer reflect the active member ID.
• Run eligibility before the appointment, not after the denial. Most clearinghouses support batch eligibility queries the day before scheduled appointments. A CO-31 caught at 4 PM the day before the visit can be resolved with a phone call. One caught after claim submission takes a corrected-claim cycle and delays payment by weeks.
• Confirm the legal name, not the preferred name. The name on a patient's insurance enrollment is their legal name at the time they enrolled. A recently married patient, a patient who uses a middle name, or a patient with a hyphenated surname that varies across systems is a CO-31 risk on the first claim after the change. Ask for the name as it appears on the insurance card, capture it verbatim, and note any discrepancy between the card and the chart.

For practices with high CO-31 volume from a single payer, the likely cause is a system-level issue rather than random errors: a clearinghouse format that truncates names, an enrollment data feed that loads member IDs inconsistently, or a specific employer group whose roster updates run late. Identifying the pattern is the first step toward a fix that affects every claim, not just the ones already denied. See the denial management guide for how to build that kind of pattern analysis into your regular AR review.