Medical Billing Denial Management Software Process Guide

Medical billing denial management software routes each denied claim through root-cause categorization, appeal submission, and prevention, replacing the spreadsheets and shared inboxes your UR team runs today. This guide walks the full process step by step, then works through CO-50, CO-197, and CO-29 with the exact workflow action for each, inside Kipu or BestNotes.

What is denial management in medical billing?

Denial management is the process of categorizing rejected claims by code, correcting the root cause, appealing within the payor's window, and fixing the upstream workflow so the same denial does not recur. For a UR team, that means tracking whether a denial came from a missing concurrent review note, a late service request form, or a medical necessity dispute, then routing each one differently.

Behavioral health carries a heavier denial burden than most specialties. Treatment centers lose a meaningful share of potential revenue to preventable billing mistakes and claim denials (Pimsy), and much of that traces back to authorization and concurrency issues rather than coding errors. We break the full workflow down step by step in our guide to behavioral health denial management.

What are the stages of the medical billing denial management process?

Denial management runs through seven steps: capture, categorize, triage, work, appeal, track, and prevent. Grouped into five stages, each has a concrete software action you can run today inside Kipu or BestNotes plus a tracker.

Stage 1: Capture and log the denial

Pull the 835 remittance daily and log every CARC/RARC code, dollar amount, payor, and service date into a single tracker. If denials live in a shared inbox, they age past the appeal window before anyone sees them.

Stage 2: Categorize by root cause

Group denials into buckets: medical necessity, authorization or notification, timely filing, credentialing, and coding. The root cause determines who fixes it: UR for clinical denials, front office for eligibility ones.

Stage 3: Triage by dollar value and appeal deadline

Sort by appeal deadline first, dollar amount second. A $2,000 residential stay expiring in 10 days beats a $200 claim expiring in 60. Assign each denial an owner and a due date in the tracker.

Stage 4: Work the denial

For medical necessity and authorization denials, pull the chart, assemble the concurrent review notes and assessments, and build the appeal or request a peer-to-peer. Software like CriteriaIQ speeds this stage by matching chart documentation to payor medical necessity criteria before the P2P or appeal goes out (CriteriaIQ vs Kipu: UR and Denial Management).

Stage 5: Track, prevent, and feed back into UR

Record outcomes, denial rates by payor, and A/R aging. Feed recurring causes back into UR: earlier concurrent reviews, tighter authorization window tracking, and step-down documentation submitted before the payor asks.

How do you categorize and prioritize denials by denial code?

Sort every denial into one of four buckets: missing authorization, medical necessity, timely filing, or documentation quality. CARC and RARC codes on the remittance tell you which bucket applies. UR teams juggling dozens of concurrent cases across payors already track too much by spreadsheet and shared inbox, which is exactly where codes get misread and appeal windows slip.

CARC codes that matter most in behavioral health

The codes you will see most: CO-197 (no prior authorization), CO-50 (not medically necessary), CO-29 (timely filing), CO-16 with a RARC pointing to a missing service request form or note. Code definitions come from the X12 CARC code list, so train staff to read the RARC, not just the CARC.

Prioritizing by appeal deadline, not by arrival date

Work the queue by deadline and dollar impact:

CriteriaIQ maps CARC codes to the documentation gaps behind them, and our behavioral health documentation guide covers the note standards that prevent CO-50s in the first place.

Worked examples: CO-50, CO-197, and CO-29 from denial to resolution

CO-50: medical necessity not met

A payor denies a residential stay at day 14, saying ASAM 4th Edition criteria aren't met. In CriteriaIQ, pull the concurrent review timeline: the physician assessment supporting the last extension was signed two days after the authorization window closed, so the reviewer saw stale documentation. Fix the appeal by attaching the late-signed assessment, the ASAM dimension ratings, and the step-down plan showing why IOP was clinically inappropriate. Prevention: set a reminder two days before each authorization window ends so the note is signed, not just drafted, before the reviewer looks.

CO-197: no prior authorization

An IOP admission went in before the service request form cleared. Check whether the payor issued a retro-authorization; many will if the request was submitted within a defined period. If not, appeal with the intake packet and the P2P call notes proving the request was made. Prevention: block charge entry until the authorization number is attached in Kipu or BestNotes, so no claim goes out on an unapproved admission.

CO-29: timely filing limit expired

This is the hardest one. Locate proof of timely initial submission: a clearinghouse acceptance report or a corrected-claim receipt. If you have it, appeal with that documentation; payors routinely overturn CO-29 when the original filing is provable. If you don't, the denial is usually final, and the fix is upstream. Track payer-specific filing limits in one place, not a shared inbox. For more on building this kind of tracking into your UR workflow, see How RCM Software Reduces Denials.

CO-50 teaches the deeper lesson, and it's worth restating on its own: most medical necessity denials are documentation-timing failures, not clinical failures. The care was appropriate; the reviewer just never saw the evidence inside the authorization window. That means your denial management software doesn't need to write better appeals so much as it needs to make sure the right note is signed and visible before a concurrent review happens. A UR coordinator who treats every CO-50 as a chart-assembly problem, rather than a clinical dispute, will win more appeals faster and prevent the next one entirely.

What does denial management software actually automate vs. what still needs human review?

What software does well

Software handles the tracking layer: authorization windows, concurrent review due dates, document assembly for service request forms, and matching denial codes to the right workflow. A CO-29 (timely filing) denial needs a different response than a CO-197 (no prior authorization), and the X12 CARC code list defines these categories so software can route them consistently. This replaces the spreadsheets and shared inboxes most UR teams currently run on.

What still needs an RN or licensed clinician

Medical necessity arguments cannot be automated. When a payor questions ASAM 4th Edition level-of-care fit or a step-down timing decision, a clinician must build the argument from the chart and defend it on the P2P call. Software can assemble the supporting notes; it cannot make the case.

Where CriteriaIQ falls short

CriteriaIQ automates criteria mapping and deadline tracking on Kipu and BestNotes, including Milliman MCG workflows (Milliman MCG Behavioral Health Software). It does not replace your reviewers: the clinical judgment behind a medical necessity appeal, and the peer-to-peer conversation itself, stay with your RN.

How do you write an effective appeal for medical necessity and authorization denials?

Structure every appeal the same way: denial code and date, the criteria set you're arguing from (ASAM 4th Edition for SUD levels of care), then a documentation map that ties each criterion to a named note, assessment, or lab result with its date, so a reviewer never hunts through the chart to find your evidence. For medical necessity denials (CO-50), quote the payor's own criteria language, then match it to clinical facts: current ASAM dimension ratings, step-down rationale, and length-of-stay justification tied to documented risk, not convenience. For authorization denials (CO-197, CO-29), lead with proof the service request was submitted inside the authorization window, including timestamps and any payor correspondence. State your requested action explicitly: overturn, retro-authorize, or reprocess, with the dates of service listed. Keep P2P call notes in the same letter file, since the peer's verbal statements often become your strongest written evidence.

Honest limitation: CriteriaIQ RCM organizes the documentation mapping and deadline tracking inside Kipu and BestNotes, but the clinical argument is yours to write. No software replaces a UR nurse's judgment about which notes prove medical necessity.

What metrics measure denial management success?

Track five numbers monthly. Denial rate: denials divided by claims submitted, with behavioral health facilities often running well above the low single digits payors expect. First-pass resolution rate: the share of denials overturned on the initial appeal without escalation. Overturn rate by CARC code: if CO-50 appeals fail but CO-29 appeals succeed, your medical necessity documentation is the problem, not your timeliness.

Days to resolution matters because appeal windows are short. Medicare redetermination deadlines run 120 days from the remittance date, and state Medicaid timelines are frequently tighter (Medicare appeals). Miss one and the denial becomes write-off.

Finally, watch A/R aging by payor. Claims sitting past 90 days usually mean an authorization window closed or a service request form was never resubmitted. CriteriaIQ surfaces these timelines per case so a UR nurse managing dozens of concurrent reviews can see which authorizations expire this week before they become denials.

What interview questions reveal whether a candidate understands denial management workflows?

Skip "tell me about yourself." Ask these instead.

1. "Walk me through a CO-29 denial from the remittance to resolution." Tests whether they check the timely filing limit, locate the payer's appeal window, and document before the deadline.
2. "A concurrent review gets pended for a missing nursing note. What do you do in the next hour?" Tests chart triage and escalation, not just paperwork.
3. "How do you prepare a peer-to-peer in the 24 hours before the call?" Look for ASAM level-of-care framing and a summary sheet, not improvisation.
4. "Which CARC codes would make you appeal, and which would make you rebill?" Tests the appeal-versus-corrected-claim decision.

A strong candidate answers with specific codes, timelines, and payer behavior. A weak one answers in generalities about "following up."

FAQ

Can denial management software work without replacing my Kipu EMR?

Yes. Tools like CriteriaIQ layer on top of Kipu or BestNotes rather than replacing them: they map CARC codes to documentation gaps, track authorization windows, and assemble appeal packets while your EMR stays the system of record. Your reviewers keep working in the same charts and workflows they already use, with denial tracking added alongside.

How long do I have to appeal a behavioral health denial?

It varies by payor and level. Medicare redeterminations run 120 days from the remittance date, and state Medicaid timelines are often tighter. Commercial payors set their own windows, sometimes 30 to 180 days. Log the deadline for every denial at capture time and triage by deadline first, since a missed window turns an appealable claim into a write-off.

What is the difference between a hard denial and a soft denial?

A soft denial is a request for more information, like a CO-16 pointing to a missing note, and you can fix and resubmit without a formal appeal. A hard denial, such as CO-50 or CO-29, requires an appeal or peer-to-peer to overturn. Read the RARC on the remittance to tell which one you are holding before deciding the response.

Should a UR nurse or a billing specialist handle appeals?

Split it by root cause. Clinical denials, meaning medical necessity and level-of-care disputes, belong to a UR nurse or licensed clinician who can build the argument from the chart and defend it on a P2P call. Authorization, timely filing, and credentialing denials fit a billing specialist. Route each bucket to a named owner in your tracker.