Author: Knicole C. Emanuel Esq. | October 1, 2026
Every provider that bills Medicare has felt the sting of a denied claim. Some denials are one-off mistakes: a transposed digit, a missed modifier. But others show up with frustrating regularity, draining revenue, consuming staff hours, and delaying payment for care that was unquestionably needed and delivered. Understanding the most common denial patterns is the first step toward preventing them.
CO-50: Medical Necessity — The Big One
No denial code haunts providers quite like CO-50: “these are non-covered services because this is not deemed a ‘medical necessity’ by the payer.” This denial means the Medicare Administrative Contractor (MAC) has determined that the documentation submitted does not support the clinical need for the service billed. It does not necessarily mean that the care was inappropriate; it means the record, as presented, did not make the case.
The fix starts before the claim is ever submitted. Ensure that clinical documentation clearly connects the diagnosis to the service, references applicable Local Coverage Determinations (LCDs), if necessary, and explains why alternative treatments were insufficient, if necessary. When CO-50 denials occur, providers should pursue a redetermination under 42 CFR § 405.904, supported by strengthened documentation.
CO-4: The Procedure Code Does Not Match the Diagnosis
CO-4 flags a mismatch between the procedure code and the diagnosis code on the claim. This is often a coding error, rather than a clinical one: the service was appropriate, but the claim told a contradictory story. Common culprits include outdated ICD-10 mappings, unspecified diagnosis codes when a more specific code was available, and copy-forward errors in the electronic health record (EHR).
Prevention requires routine audits of code pairing logic and close collaboration between clinical and billing teams. A coder who understands the clinical rationale – and a clinician who understands coding requirements – can catch these mismatches before submission.
CO-29: The Filing Deadline Has Passed
CO-29 – “the time limit for filing has expired” – is one of the most preventable and least forgivable denials. Medicare generally requires claims to be filed within one calendar year from the date of service. Miss that window, and you have no appeal right; the revenue is simply gone.
This denial typically results from workflow bottlenecks: delayed charge capture, unresolved claim edits sitting in a work queue, or rebilling after a prior rejection without tracking the original timely filing date. Automated deadline alerts and aging reports are essential safeguards.
CO-16 and CO-18: Missing or Invalid Information
CO-16 (“claim/service lacks information or has submission/billing error(s)”) and CO-18 (“exact duplicate claim/service”) are high-volume, low-complexity denials that point to front-end process failures. CO-16 often traces back to missing referring provider information, incomplete patient demographics, or absent prior authorization numbers. CO-18 results from inadvertent resubmission of a claim that was already adjudicated.
Both are preventable with clean claim scrubbing software and staff training on resubmission protocols. The goal is to catch these before the claim leaves your system.
PR-96: Non-Covered Charges Under the Patient’s Plan
PR-96 denials indicate that the billed service is not covered under the patient’s specific Medicare benefit category. This frequently arises with screening services, certain preventive procedures, or services subject to frequency limitations. Providers should verify coverage eligibility and benefit-specific restrictions at the point of scheduling, not after the claim is returned.
The Bigger Picture
The common thread across these denials is that most are preventable at the point of documentation or submission, not at the point of care. Providers rarely deliver unnecessary services, but they routinely fail to document the necessity in the language Medicare requires, code the claim in a way that tells a coherent clinical story, or submit it within the rules that govern the process.
Building a denial management program that tracks patterns, identifies root causes, and feeds corrections back into the front end is not optional; it is the difference between a revenue cycle that functions and one that hemorrhages.
Every denied claim is a lesson. The question is whether your organization is learning from them.
This article was originally published on RACmonitor.
