CO-16 Denial Code: Claim Lacks Information (Meaning and Fix)

Jupiter RCM article cover: CO-16 Denial Code: Claim Lacks Information (Meaning and Fix)

CO-16 means the payer could not finish processing the claim because information is missing or wrong. The provider is responsible for the adjustment (group code CO), but it is rarely a final “no.” Find the remark code sent with it, correct the specific field it names, and resubmit the claim.

What does CO-16 mean?

CO is the group code for Contractual Obligation, and CARC 16 is officially described as “Claim/service lacks information or has submission/billing error(s).” Its usage note requires at least one Remittance Advice Remark Code (RARC) with it. The wording is published in the X12 Claim Adjustment Reason Code list (opens in a new tab).

That usage note is the key to working CO-16. The CARC only says that something is wrong; the RARC says what. Common pairings include M51 (missing, incomplete or invalid procedure code) and, on Medicare claims, MA130, which marks the claim as unprocessable with no appeal rights: you fix it and send it again as a new claim. RARC wording is published in the X12 Remittance Advice Remark Code list (opens in a new tab).

Common causes of CO-16

CauseWhere to look
Missing or invalid patient or subscriber data (name, date of birth, member ID)Registration record and the eligibility response
Missing or invalid provider identifiers (NPI, taxonomy, referring provider)Provider master file and the NPPES NPI Registry
Invalid or incomplete procedure or diagnosis codesCharge entry and coding
Missing dates, units or place of serviceCharge entry
Information the payer requested earlier was never sentCorrespondence and payer portal

How to fix a CO-16 denial

  1. Open the ERA or EOB and write down every RARC listed with CARC 16.
  2. Look up each RARC and match it to the field on the claim.
  3. Correct the data at its source, such as the registration record or provider file, not just on this claim.
  4. Resubmit. For Medicare claims marked unprocessable (MA130), send a new claim rather than an appeal. For other payers, follow their corrected-claim rules, which often means frequency code 7 with the original claim number.
  5. Keep the timely filing deadline in view. A claim returned as unprocessable does not stop the clock.

Correct or appeal a CO-16 denial?

Almost always correct. CO-16 says the claim was incomplete, not that the service was rejected on its merits, so an appeal usually adds weeks without changing anything. Appeal only if you can show the information was on the original claim and the payer missed it.

How to prevent CO-16

  • Run eligibility checks before each visit and copy member details exactly as the payer returns them.
  • Keep NPIs, taxonomy codes and addresses in one maintained provider file.
  • Use a claim scrubber that checks required fields before submission.
  • Track CO-16 by RARC each month. Repeat remark codes point to one broken step in your workflow.

Frequently asked questions

Can I bill the patient for a CO-16 denial?

No. Group code CO places the amount on the provider. Fix and resubmit the claim instead.

What if no remark code came with CO-16?

The usage note requires one, so ask the payer or your clearinghouse for the full 835 detail before changing anything. Without the RARC you are guessing.

Is CO-16 a rejection or a denial?

It is reported on the remittance as a denial, but it behaves like a rejection: the claim needs correcting, not arguing.

Related denial code guides

Code descriptions are quoted from X12 at the time of writing and are revised from time to time. Payer policies and your contracts decide what is billable and appealable.

Seeing CO-16 every week?

We can review your recent CO-16 denials by remark code and show you which front-end step is causing them.

About this article

This article was published by the Jupiter RCM editorial team for general information about medical billing and revenue cycle management. It is not legal, compliance or coding advice for your specific situation. Payer policies and code sets change, so always check the current requirements.

Let’s take a closer look at your revenue cycle

Tell us what’s getting stuck. Denials, old A/R, credentialing, reports nobody reads? We’ll look at how you work now and tell you straight what we’d change, and why.