NPI Portal NPI Lookup & Verification

Denials playbook

How to reduce claim denials

Most of the denials in our denial code index (missing information, eligibility, timely filing, bundling) are preventable front-end failures, not payer judgment calls. This page covers the prevention workflow that stops them, the numbers to track, and when it's worth paying for software to do the checking for you.

Disclosure: some links in the tools section are affiliate links; if you sign up through them we may earn a commission at no extra cost to you. That doesn't change what we recommend, and no vendor influences how denial codes on this site are explained.

Why claims actually get denied

Read enough remittance advices and a pattern emerges: the codes that dominate denial queues are administrative, not clinical. CO 16 means the claim arrived with something missing or invalid. CO 29 means it arrived too late. Eligibility denials mean nobody confirmed coverage before the visit. Duplicates, bundling, and missing-authorization denials round out most queues. None of these are the payer deciding care wasn't warranted; they're the payer saying the paperwork failed before adjudication ever started.

That's good news, because paperwork failures have locations. A denial is the last visible symptom of a broken step earlier in the revenue cycle: an intake form that doesn't capture the referring provider, an eligibility check that never runs, a code set that didn't get its quarterly update. Fix the step and the denial category disappears; work denials one at a time and the queue refills forever.

The prevention workflow

  1. Verify eligibility at scheduling, not at billing. Coverage, plan type, and whether the payer on file is actually primary. Eligibility denials found at billing are weeks old; found at scheduling they cost a phone call.
  2. Validate identifiers before submission. Ordering and referring provider NPIs against the NPPES registry, and the rendering NPI against the payer's enrollment record. Mistyped or unenrolled NPIs are classic CO 16 fuel (remark codes N265 and N276).
  3. Keep code sets current. CPT and HCPCS change annually, payer edits quarterly. A claim scrubber is only as good as its last update: a retired procedure code sails through a stale scrubber and dies at the payer.
  4. Confirm authorization and referral requirements per plan. The same service can need prior auth on one plan and not another from the same payer. Capture the auth number at scheduling and carry it to the claim.
  5. Submit promptly and track what comes back. The timely filing clock (CO 29) runs while claims sit in queues: for Medicare the limit is 12 months from the date of service, and many commercial plans allow far less. Unprocessable claims returned for correction don't pause the clock.

Measure it: three numbers that matter

You can't tell whether prevention is working without a baseline. Three metrics, pulled monthly from your remittance data, are enough:

  • Initial denial rate is denied claims as a share of claims submitted. This is the headline number; watch the trend, not the absolute value.
  • Top remark codes by volume are the diagnostic detail. If one remark code dominates (say N265, missing ordering-provider information), you don't have a denial problem, you have a single broken intake step wearing a denial costume.
  • First-pass resolution is the share of claims paid without any rework. This is the number that actually correlates with cost, because every touched claim costs staff time whether or not it eventually pays.

A month of this reporting usually points at one or two upstream fixes. Make them, watch the remark-code report shift, repeat.

When software is worth it (and when it isn't)

If your remark-code report shows denials concentrated on one or two causes, fix the process (no purchase required). Software earns its subscription when the failure mode is breadth: denials spread across many causes, eligibility checks that don't happen because they're manual, code sets nobody owns updating, or a denial queue growing faster than staff can work it. The common thread in the tools below is that they move the checking to before submission, where a rejected claim costs seconds instead of weeks.

Tools that catch denials before submission

Picked for the denial-prevention problems above rather than feature breadth. Links marked with the disclosure at the top of this page.

Tebra Independent practices

Practice management, EHR, and billing in one system, built from the Kareo and PatientPop merger. Claims are scrubbed and eligibility is checked before submission rather than after the remittance comes back.

Strongest fit when denials trace to disconnected front-end systems: scheduling, eligibility, and claims living in different tools.

See Tebra →

CollaborateMD Billing companies & billing teams

Billing software built by billers, designed for teams working claims across many practices at once: claim-level scrubbing, denial worklists, and batch eligibility.

Strongest fit when the problem is denial-queue throughput: lots of CO 16s and CO 29s aging in a work queue.

See CollaborateMD →

AdvancedMD Larger groups

A broader billing, EHR, and patient-experience suite for multi-provider groups, with claim scrubbing and denial management built into the revenue cycle tools.

Strongest fit when a group needs denial reporting across providers and locations, not just claim-by-claim fixes.

See AdvancedMD →

CCO coding courses Individual billers & coders

Certification prep and continuing education for medical coders and billers. If denials trace to coding gaps rather than tooling (wrong modifiers, retired codes, missed remark codes), training is the cheaper fix.

Strongest fit when one biller or coder owns the denial queue and the same coding mistakes keep recurring.

Browse courses →

Frequently asked questions

What denial rate should a practice aim for?
Track your own trend rather than chasing a universal number: measure initial denial rate (denied claims ÷ submitted claims) monthly, and treat any month-over-month rise as a front-end process failure to locate. Well-run billing operations keep initial denials in the low single digits.
Should I work denials or prevent them first?
Both, but prevention pays more. A worked denial recovers one claim; a fixed intake step stops every future denial from that cause. Use your remark-code report to find the biggest recurring cause, fix that step, then work the backlog.
Do I need new software to reduce denials?
Not always. If your denials concentrate on one or two remark codes, a process fix (verifying eligibility at scheduling, validating NPIs before submission) may be enough. Software earns its cost when denials are spread across many causes or the volume is too high to work manually.

Denial explanations on this site are original plain-English summaries; consult your payer's remittance advice and policy for authoritative guidance. Tool listings reflect our editorial assessment and are not endorsements by any payer. Updated 2026-07-11.