Denial Management in Medical Billing: A Complete Guide

Denial management is the process of identifying, classifying, correcting, appealing, tracking, and preventing claims that a payer did not pay as expected.

The best denial management programs do more than recover individual claims. They answer two questions at the same time:

1. What is the next action needed to collect this account?
2. What upstream process allowed this denial to happen?

Without the first question, revenue remains unpaid. Without the second, staff keeps solving the same problem one claim at a time.

Rejection, Denial, and Underpayment Are Different

These terms should not share one generic “billing issue” queue.

Claim rejection

A rejected claim did not pass a front-end edit and generally did not enter adjudication. The clearinghouse or payer may reject it because required data is missing, the format is invalid, or an identifier fails validation.

The usual next action is to correct and resubmit—not appeal.

Claim denial

A denied claim entered adjudication, and the payer determined that all or part of it would not be paid under the information and rules applied. The next step may be a corrected claim, documentation response, reconsideration, appeal, patient-responsibility review, contractual adjustment, or write-off.

Underpayment

An underpaid claim received payment, but the amount may be below the contracted or otherwise expected allowance. It will not necessarily appear on a denial report. Payment variance review is therefore a separate control.

Routing these three outcomes correctly is the beginning of denial management.

How to Read a Denial

Start with the remittance advice, not a free-text label in the billing system.

Electronic remittance advice uses the X12 835 transaction. Claim Adjustment Reason Codes (CARCs) explain why an amount was adjusted, while Remittance Advice Remark Codes (RARCs) provide additional information. Group codes indicate the general financial category, such as contractual obligation or patient responsibility.

CMS maintains payment and remittance guidance, while X12 publishes the current code lists. (CMS remittance advice guidance)

Never interpret a CARC in isolation when the remittance requires a remark code. For example, CO-16 is a broad missing-or-invalid-information code. The accompanying RARC should identify the actual problem. CO-97, by contrast, indicates that the service's benefit is included in payment for another adjudicated service and usually calls for a bundling or distinct-service review.

Use the denial code library to understand common codes, then verify the actual remittance and payer policy before acting.

The Eight-Step Denial Management Process

1. Capture the denial completely

Record:

• Claim and service line
• Patient and payer
• Date of service
• Billed, allowed, paid, and adjusted amounts
• Group code, CARC, and RARC
• Payer explanation and policy reference
• Receipt date
• Filing, correction, reconsideration, and appeal deadlines
• Current owner and next action

A denial without a deadline and owner is already aging.

2. Normalize the reason

Payers can use different messages for similar problems. Map the remittance into an internal category without discarding the original codes.

Useful categories include:

• Registration or demographic error
• Eligibility or coordination of benefits
• Authorization or referral
• Coding or modifier
• Documentation or missing information
• Medical necessity or coverage
• Duplicate or bundling
• Timely filing
• Provider enrollment or network
• Payer processing error
• Patient responsibility
• Underpayment or contract variance

The original code supports claim-level action. The normalized category supports trend analysis.

3. Decide the correct action path

Not every denial should be appealed.

• Correct and resubmit when the original claim contained a correctable billing error and the payer allows a corrected claim.
• Send requested information when the payer needs a specified document or data element.
• Request reconsideration or appeal when the original claim was correct or the dispute depends on coverage, medical necessity, contract terms, or payer processing.
• Transfer to patient responsibility only when the remittance, contract, notice requirements, and financial policy support it.
• Adjust or write off only under an approved policy with a documented reason.

Submitting an appeal when the payer expects a corrected claim wastes time. Rebilling a true appeal can create duplicates and consume the deadline.

Once the case is classified and an appeal is the correct path, use the free appeal letter for insurance denial generator to organize the denial language, argument, supporting facts, requested resolution, and enclosure list into an editable draft.

4. Build the case before touching the portal

Gather the original claim, remittance, payer policy, authorization record, eligibility response, clinical documentation, order, referral, contract provision, submission proof, prior correspondence, and timeline.

The response should make one clear argument supported by the documents the payer needs. A large chart dump can obscure the relevant evidence.

5. Submit through the correct channel

Confirm the payer's required form, portal, fax, address, claim frequency code, attachment method, and filing level. Capture proof of receipt and the payer reference number.

6. Monitor until final resolution

“Appeal sent” is not a terminal status. Track acknowledgment, review deadline, requests for information, decision, payment, posting, and any next appeal level.

7. Validate the financial result

If the payer overturns the denial, confirm that the correct amount was paid and posted. Do not close the case based only on an approval notice.

8. Feed the cause upstream

When the claim is resolved, record the root cause and prevention owner. A recovered authorization denial may still reveal a scheduling failure. A corrected CO-16 denial may show that provider enrollment data is outdated.

A Practical Denial Work Queue

Prioritize denials with a consistent rule. A simple score can consider:

• Days remaining before the deadline
• Dollar value
• Probability of recovery
• Patient or service impact
• Ease of correction
• Repeat frequency
• Strategic payer or contract issue

Then assign a status that communicates the next action:

• New—needs classification
• Waiting for internal documentation
• Ready to correct
• Ready to appeal
• Submitted—awaiting acknowledgment
• Payer review in progress
• Additional information requested
• Approved—payment pending
• Upheld—next-level review
• Closed—paid, adjusted, transferred, or written off

Avoid statuses like “working” or “pending” without a named dependency and due date.

The Denial Metrics That Matter

Initial denial rate

Initial denial rate = claims denied on initial adjudication ÷ total claims adjudicated

Track count and dollar value. A high-volume, low-dollar code may consume more staff time than a smaller number of large denials.

Preventable denial rate

Preventable denial rate = denials caused by controllable workflow failures ÷ total denials

Define “preventable” in writing. Authorization missed before service and incomplete claim data may be preventable; a novel coverage dispute may not be.

Appeal or correction rate

What percentage of actionable denials did the practice actually pursue before the deadline?

Overturn rate

Overturn rate = appealed denials reversed ÷ appealed denials decided

A high overturn rate can mean strong appeal work—or a payer frequently denied valid claims initially. Review it by payer and denial category.

Recovery yield

Recovery yield = dollars recovered ÷ dollars pursued

Also calculate recovered dollars per staff hour. A workflow can recover money while still being inefficient.

Time to resolution

Measure from remittance receipt to final payment or approved closure. Segment it by payer, category, and action type.

Repeat-denial rate

How often does the same normalized cause recur after a prevention change? This tells you whether the fix worked.

These measures belong in the larger revenue cycle management dashboard.

How to Prevent the Most Common Denial Categories

Eligibility and coordination of benefits

• Verify active coverage and benefits before the visit
• Confirm member data against the card and payer response
• Ask about other coverage and accident or employment-related claims
• Recheck when the appointment moves or coverage changes

Use the eligibility verification guide to design the pre-visit workflow.

Prior authorization and referral

• Check requirements when the service is ordered
• Match the request to code, provider, site, quantity, and date
• Store the authorization where billing can see it
• Monitor pending requests and expiration dates

Authorization does not guarantee payment, but an incomplete authorization record makes a preventable denial more likely. See how long prior authorization takes and the payer requirement guides.

Missing or invalid information

• Use pre-submission validation
• Review the RARC paired with CO-16
• Maintain provider enrollment, NPI, taxonomy, and location data
• Confirm required claim attachments and service-specific fields

Coding and bundling

• Review code combinations, modifiers, units, and payer edits
• Confirm documentation supports distinct services
• Update coding references and educate staff when payer policy changes
• Do not add a modifier solely to bypass an edit

Medical necessity and coverage

• Identify the applicable policy before service when possible
• Document the criteria in the clinical record
• Connect the appeal to the exact coverage language
• Keep clinical judgment with qualified professionals

Timely filing

• Track rejected claims separately from accepted claims
• Monitor claims with no payer acknowledgment
• Store proof of original filing
• Create internal deadlines earlier than the payer's limit

Medicare generally denies fee-for-service claims received more than 12 months after the date of service, subject to limited exceptions. Commercial and Medicaid limits vary and may be much shorter. (Medicare Claims Processing Manual)

The Monthly Denial Review

A useful monthly meeting is short and specific. Review:

1. Top denial categories by count and dollars
2. Oldest and highest-value actionable cases
3. Deadlines in the next 30 days
4. Overturn and recovery results
5. New payer patterns
6. Recurring causes that were supposed to be fixed
7. One upstream change with a named owner and measurement date

Do not spend the meeting reading individual account notes. Work the claims in the queue; use the meeting to change the system.

Compliance Still Applies When Revenue Is at Risk

Denial pressure is not a reason to code beyond the documentation, add unsupported modifiers, change dates, omit material information, or appeal with a statement the record cannot support.

HHS-OIG recommends internal monitoring, written standards, training, corrective action, communication, and accountability as foundations of a physician-practice compliance program. Those controls should extend to outsourced billing partners and automated workflows as well as employees. (HHS-OIG compliance programs for physicians)

The Bottom Line

Denial management is both a recovery function and a process-improvement function. The claim-level workflow protects revenue today. Root-cause analysis prevents the same work tomorrow.

Start by separating rejections, denials, and underpayments; capture the original remittance codes; assign every case an owner and deadline; and make one upstream fix each month.

Greenlight Medical helps private practices turn payer responses into organized queues, assemble the information staff needs, and surface repeat patterns before they become old A/R. Book a free practice operations audit to map the denial workflow that is consuming your team's time.