Free Medical Billing Audit

Guide

Why Are My Medical Claims Being Denied? Causes and Fixes

Medical claim denials happen when a payer processes a claim and refuses to pay all or part of it. The causes fall into a handful of groups: eligibility and registration errors, missing authorization, coding and modifier problems, missing or inconsistent information, medical necessity, duplicates, coordination of benefits, and filing deadlines. Each group has a different fix, so the first job is to read the denial correctly. This guide explains how to tell a rejection from a denial, how to read the codes on a remittance, and how to investigate, correct, and prevent each category.

Person holding printed paperwork
In this article
  1. Problem: what medical claim denials are and why they cost more than the claim
  2. Rejection versus denial
  3. Evidence to inspect
  4. Reading the remittance: group codes, CARCs, and RARCs
  5. Likely causes and denial categories
  6. Eligibility and registration
  7. Authorization and referral
  8. Coding and modifier problems
  9. Missing or inconsistent information
  10. Medical necessity
  11. Duplicate claims
  12. Coordination of benefits
  13. Timely filing
  14. Provider enrollment and credentialing
  15. Non-covered services and benefit limits
  16. Partial denials and underpayment
  17. Investigation steps
  18. Worked example (hypothetical)
  19. Corrective action
  20. Submission and follow-up
  21. Prevention
  22. Measurement
  23. Who does what: Mednex and the practice
  24. What cannot be promised
  25. Next steps
Flow diagram showing the difference between a claim rejection at the clearinghouse and a denial from the payer, and the next action for each.
Illustration only. Data shown is synthetic.

Problem: what medical claim denials are and why they cost more than the claim

A denial is a payer decision. The claim reached the payer, passed the basic checks, was adjudicated, and the payer decided not to pay some or all of it. The decision comes back on a remittance advice, often as an electronic 835 file or a paper explanation of payment.

Denials cost practices in several ways:

  • Delayed payment. Every denial restarts the clock. A claim that would have paid in a few weeks may take months once it needs correction or appeal.
  • Staff time. Working a denial takes longer than submitting a clean claim, and many denials are avoidable.
  • Lost revenue. Some denials are never worked, and deadlines pass. That amount becomes a write-off.
  • Patient friction. A denial can turn into a patient balance or a confusing statement.
  • Repeat cost. The same cause denies the next claim, and the one after that, until the process changes.

Denials affect every size of practice and every specialty, though the mix differs. A primary care office sees many eligibility and preventive-versus-problem coding issues. A specialty practice may see more authorization and medical necessity issues. Check your own denial report before assuming your pattern matches anyone else’s. The service side of this work is on the denial management page.

Rejection versus denial

People use the words interchangeably, but the difference changes what you do next.

Rejection Denial
Where it happens At the clearinghouse or the payer’s front-end edits, before adjudication. After the payer has processed the claim.
Typical causes Format errors, missing required fields, invalid payer ID, invalid member ID, invalid code or code format. Coverage, authorization, coding, necessity, duplicate, filing limit, bundling, and other policy reasons.
Where you see it Clearinghouse or payer acknowledgment reports. Remittance advice (835 or paper).
Usual fix Correct the error and resubmit as a new claim. Depending on cause: corrected claim, appeal, payment dispute, or acceptance of the adjustment.
Appeal rights Usually none, because the claim was not processed. Yes, under the payer’s appeal process and deadlines.
Risk if ignored Claim never gets paid and may not appear in aging as a denial. Appeal and filing deadlines pass.

A Medicare contractor’s appeals page illustrates the point. It says claims returned with message MA130 are unprocessable and cannot be appealed, and the provider must correct the information and submit a new claim. By contrast, a first-level Medicare appeal, called a redetermination, has a 120-day filing limit from the initial determination. Other payers use their own terms and windows, so confirm each payer’s rules.

Rejections hide easily. If no one reviews clearinghouse reports daily, rejected claims sit as open A/R and surface months later in the over 90 day report.

Evidence to inspect

Good denial work is evidence-driven. Before deciding how to respond, gather these items.

  • The remittance advice for the claim, including claim-level and line-level adjustments.
  • The original claim as submitted: CMS-1500 or 837P data, including codes, modifiers, diagnoses, place of service, rendering and billing provider, and dates.
  • Clearinghouse acknowledgments to confirm what was accepted.
  • Eligibility record from the date of service, with the payer, plan, and any other coverage.
  • Authorization or referral record, with number, dates, and approved services.
  • Encounter note and orders for coding and medical necessity review. Handle these under your privacy procedures.
  • Payer policy: the provider manual, the coverage policy, and the contract terms.
  • Previous communications with the payer, with dates and reference numbers.
Protected information

Denial work can require clinical records. Those should move only through secure workflows under a signed business associate agreement. Never send patient details through website forms or ordinary email.

Reading the remittance: group codes, CARCs, and RARCs

Remittance advice describes payment changes with standardized codes. The X12 organization, which maintains the claim adjustment reason code (CARC) list, describes a CARC as explaining why a claim or service line was paid differently than billed. Three pieces appear together:

  • Group code. A two-letter code that generally assigns responsibility for the adjustment amount. The X12 page lists CO (contractual obligation), PR (patient responsibility), OA (other adjustment), PI (payer initiated reductions), and CR (corrections and reversal, which is not used with version 005010 and later). A CO adjustment generally means the provider cannot bill the patient for that amount, while PR means the amount is the patient’s responsibility. Confirm the rules for your payer and contract before billing a patient.
  • CARC. A numeric reason code. Some CARCs are limited to certain group codes, and some must be accompanied by a remark code. Codes carry start and stop dates, so use the current list rather than an old printout.
  • Remittance advice remark code (RARC). A supplemental code that adds detail or tells you what is needed, such as missing information. Some CARCs require at least one RARC.

Treat the code as a pointer, not a verdict. The same CARC can come from different underlying problems, and payers add their own text. Always read the payer’s explanation, then verify against the claim and your records. This article does not list specific code numbers as universal causes, because the correct reading depends on the current code list and the payer’s usage.

Likely causes and denial categories

Most denials fit into one of the categories below. The “claim edits” that payers and clearinghouses run, which are automated checks on codes, modifiers, diagnoses, and combinations, produce many of the coding and bundling denials.

Eligibility and registration

Coverage was inactive on the date of service, the patient changed plans, the subscriber information was wrong, the name or date of birth did not match the payer record, or another payer was primary. These are largely front-end problems. Prevention is verification before the visit and accurate registration.

Authorization and referral

The service required prior approval or a referral and none was on file, the authorization was for different codes or dates, or it expired. See prior authorization services for how this work is managed. Correction may include a retro-authorization request where the payer allows it, or an appeal with supporting records.

Coding and modifier problems

The code does not match the documentation, a required modifier is missing, a modifier is not supported by the note, a diagnosis does not support the procedure, or two codes are bundled under payer edits. Modifier 25 on an E/M service performed with another service is a frequent example in outpatient practices. Coding corrections must follow the clinical record, and clinicians own that record. The change should never be made just to avoid a denial.

Missing or inconsistent information

Required fields were blank or did not match payer records. Examples include rendering provider identifiers, referring provider data, place of service, or dates. These often respond to a corrected claim.

Medical necessity

The payer decided the service was not supported under its coverage policy for the diagnosis given. Causes include an incomplete diagnosis, a policy limit, a frequency limit, or documentation that does not show why the service was needed. Response depends on the record. If documentation supports the service, an appeal with the relevant policy and records may be appropriate. If not, the practice should review its documentation process rather than rely on appeals.

Duplicate claims

The payer saw an earlier claim for the same service. Sometimes the original is still processing or was paid, and the denial is correct. Sometimes a corrected claim was submitted with the wrong frequency code or without the original claim reference. Check before resubmitting, because repeat submissions can create more duplicates.

Coordination of benefits

The payer believes another plan is primary, or the claim lacked other-insurance information. Correction involves confirming the order of benefits with the patient or payer and sending the claim in the right order.

Timely filing

The claim arrived after the payer’s filing limit. Limits differ by payer and contract. If the claim is late because of a practice delay, recovery chances are slim. If it was filed on time and the payer lost it, proof of timely filing, such as clearinghouse acceptance reports, matters. Keep those reports.

Provider enrollment and credentialing

The rendering or billing provider was not enrolled or effective with the plan on the date of service. Fixing this involves enrollment status and payer rules on effective dates. See medical credentialing services.

Non-covered services and benefit limits

The plan does not cover the service, or a benefit limit was reached. Some of these are correct denials that become patient responsibility, subject to the patient’s plan and any notice requirements. Others reflect a coding or diagnosis problem that changes coverage. Review carefully before billing the patient.

Partial denials and underpayment

One line of a multi-line claim denies, or the payer reduces payment under bundling or fee schedule rules. Compare the payment to the expected contracted amount to see whether the adjustment is correct.

Investigation steps

  1. Confirm the claim reached adjudication. Check the clearinghouse and payer acknowledgments. If it was rejected, correct and resubmit. Skip the appeal route.
  2. Read the remittance in full. Note the group code, reason code, remark code, adjustment amount, and any payer message, for the claim and for each line.
  3. Compare the claim to the record. Check demographics, coverage, authorization, codes, modifiers, diagnoses, and dates against source documents.
  4. Classify the denial. Put it into one of the categories above. When the code and the facts disagree, trust the facts and ask the payer.
  5. Check the payer policy. Look for coverage rules, bundling edits, frequency limits, and documentation requirements that apply to this service.
  6. Check deadlines. Find the corrected-claim and appeal windows in the payer manual or contract. Do not assume one window applies to all payers.
  7. Decide the path: accept (the denial is correct), correct and resubmit, appeal, dispute, or bill the patient where permitted.
  8. Trace the root cause. Ask which step upstream allowed the error, whether registration, scheduling, authorization, coding, charge entry, or submission.
  9. Record everything. Log the category, cause, action, dates, and outcome so trends can be counted.

Worked example (hypothetical)

Hypothetical example

The numbers below are round illustrations created to show the method. They do not come from a real practice and do not predict any result.

A practice reviews one month of denials and finds 100 denied claims. The billing lead sorts them by category:

Category Denied claims (illustration) Likely fix path
Eligibility and registration 30 Verify coverage for the date of service, correct and resubmit
Missing or inconsistent information 20 Corrected claim
Authorization or referral 15 Retro-authorization request or appeal if allowed
Coding or modifier 15 Coding review against the note, then correct or accept
Duplicate 10 Check original claim status before any resubmission
Medical necessity 10 Review documentation and policy, appeal if supported
Total 100

The lead notices that 30 percent of denials are eligibility related. Looking at the 30 claims, most belong to patients whose visits were booked well in advance. Eligibility was checked at booking, and not again before the visit. In the illustration, some patients changed plans in between.

The lead takes three actions:

  1. Work the existing 30 claims. Verify the correct coverage for each date of service, then resubmit to the right payer inside its filing window.
  2. Change the front-end process. Add an eligibility recheck shortly before each visit for appointments booked in advance.
  3. Add a measure. Track eligibility denials monthly as a share of all denials.

The 20 missing-information denials show a different pattern: they cluster with one referring provider field that the registration screen does not require. The fix is a required field and a pre-submission check. For the 15 coding claims, a coder reviews notes and sends two clear questions to the clinician. The clinician confirms the documentation in some cases and amends in others, according to what was actually done.

This example says nothing about how much would be recovered. That depends on each payer’s rules, the records, and the deadlines. Its point is that categories and root causes tell you where to spend effort.

Corrective action

Category Typical corrective action Typical owner
Eligibility and registration Verify coverage on the date of service, update demographics, resubmit to the correct payer Billing team, front desk for prevention
Authorization and referral Request retro-authorization if available, appeal with records, or accept and review front-end process Practice and billing team
Coding and modifier Review code against note, query the clinician, correct only what the record supports Coder and clinician
Missing information Add the missing data and submit a corrected claim Billing team
Medical necessity Review policy and documentation, appeal if supported Clinician and practice
Duplicate Locate the original claim and its status, resubmit only if appropriate Billing team
Coordination of benefits Confirm order of benefits, resubmit to primary, then secondary Billing team and front desk
Timely filing Provide proof of timely filing if it exists, otherwise follow practice write-off policy Billing team and practice manager
Enrollment and credentialing Confirm effective dates, request retroactive consideration where the payer allows it Credentialing owner

Two principles apply across categories. Correct a claim only to reflect what was done and documented. And decide early whether an appeal is worth the effort, since each one costs staff time.

Submission and follow-up

  1. Use the right route. Corrected claims, appeals, and payment disputes may go to different places. Use the payer’s current instructions.
  2. Write a clear appeal. State the claim, the denial reason, what you are asking, and why the record supports it. Attach the remittance, the relevant policy, and supporting records. Keep the letter short and factual.
  3. Keep proof. Save submission confirmations, dates, and reference numbers.
  4. Set a follow-up date. Check status at the payer’s stated processing time, or at a short interval you set.
  5. Escalate when stuck. After repeated no-response follow-ups, contact the payer’s provider relations or a named representative, and note the call.
  6. Know the next levels. If the first appeal fails, check second-level options and deadlines. Decide whether the claim value justifies continuing.
  7. Close the claim. Post payment, review any variance from expected, or record the final outcome and write-off decision.

Claims that stay unresolved eventually appear in aging reports. The method for working them is in how to reduce A/R over 90 days.

Prevention

Most denial prevention happens before the claim is submitted.

  • Verify eligibility before the visit, and again if the appointment was booked well ahead.
  • Capture complete registration data, including all coverage and a copy of the card where policy allows.
  • Check authorization needs by payer and service, and store the approval details where billing can see them.
  • Review coding on a schedule, with a sample of claims checked against the note, especially for modifiers and high-use codes.
  • Run claim edits before submission. A scrubber that checks required fields, code pairs, and payer-specific rules catches many errors early.
  • Review rejections daily and correct them the same day.
  • Keep a payer rules table with filing windows, appeal windows, and special requirements, and update it from payer bulletins.
  • Train front desk and clinicians on the specific errors your denial report shows, rather than generic topics.
  • Review enrollment status when a new clinician joins or a payer changes a provider ID.
  • Hold a monthly denial review with an owner for each root cause.

Small practices sometimes ask whether to keep this work in-house or hand it off. The tradeoffs are in outsourcing versus in-house medical billing.

Measurement

Track medical claim denials by cause, not only by count, so that each fix has a number attached.

Measure What it shows
Denial rate (denied claims divided by claims submitted), by payer Where denials concentrate. Define it the same way each month.
Denials by category and reason code Which root causes to fix first.
Rejection rate and time to correct How well front-end edits and daily review work.
Share of denials worked within your target window Whether denials have owners.
Appeal volume and outcome Which denial types are worth appealing.
Write-offs by reason Whether losses are avoidable, such as timely filing or authorization.
Repeat denials for the same cause Whether corrections stick.

Use your own baseline and compare month to month. A figure from another practice is not a fair target, since specialty, payer mix, and systems differ. Allow time for corrected claims and appeals to finish before judging results.

Who does what: Mednex and the practice

Task Mednex Practice
Denial categorization Sorts denials by cause and payer from remittance and claim data Provides denial and remittance reports and payer information
Corrected claims and appeals Prepares and submits, tracks deadlines Provides records and clinician statements
Eligibility and authorization Verifies benefits and works authorization requests as scoped Supplies accurate scheduling and registration data
Coding review Flags mismatches and sends queries Clinicians decide documentation and final coding
Root cause reporting Reports trends and recommends fixes Changes front-end and clinical workflows

Protected health information is shared only through a secure workflow under a signed business associate agreement. Mednex does not give legal advice and does not decide clinical documentation.

What cannot be promised

Nobody can promise that a denied claim will be overturned. Payers decide, and some denials are correct. A good process can reduce avoidable denials, make sure every denial has an owner and a deadline, and document outcomes. It cannot change a payer’s coverage policy or revive a claim that is past its limits.

Next steps

Pull your last three months of denials and sort them into the categories above. The largest group, and the cause behind it, is where to start. If you would like a review of your denial and rejection patterns, request a free medical billing audit and send report exports instead of patient records. For general billing support, see medical billing or use the contact page.

General information only

This guide is educational. It is not legal, coding, compliance or clinical advice. Rules differ by payer, plan, state and contract, so confirm against the payer's current policy before acting.

Frequently asked questions

What is the difference between a rejected claim and a denied claim?

A rejected claim fails front-end edits at the clearinghouse or payer and is never processed, so it is corrected and resubmitted. A denied claim was processed and refused payment in whole or part, and can be corrected, appealed, or accepted. Medicare contractors state unprocessable claims cannot be appealed.

What are the most common reasons for medical claim denials?

Common groups are eligibility and registration errors, missing authorization or referral, coding and modifier problems, missing or inconsistent information, medical necessity, duplicate claims, coordination of benefits, timely filing, and provider enrollment. Your own denial report shows which groups matter most for your payers.

What is a CARC and what is a RARC?

A claim adjustment reason code (CARC) explains why a claim or line was paid differently than billed. A remittance advice remark code (RARC) adds detail or tells you what is needed. Both appear on the remittance with a group code. Read the payer's own explanation as well.

What do the group codes CO and PR mean on a remittance?

Group codes generally assign responsibility for an adjustment. CO means contractual obligation and PR means patient responsibility, with OA, PI, and CR also in use. Rules for billing patients depend on the payer and contract, so confirm before sending a patient statement.

Should every denied claim be appealed?

No. Some denials are correct, and some are fixed faster with a corrected claim. Classify the denial first, check the record and payer policy, and note the deadline. Appeal when the documentation supports payment and the value justifies the effort.

How long do I have to appeal a denial?

It depends on the payer and contract. A Medicare contractor page states a first-level redetermination must be filed within 120 days of the initial determination. Commercial and Medicaid plans set their own windows. Read each payer's manual or agreement and track the deadline per claim.

How can a practice reduce prior authorization denials?

Check which services need approval for each payer, record the authorization number, dates, and approved codes where billing can see them, and verify they match the claim. Track expirations. When approval was missed, ask whether the payer allows a retro-authorization request.

What are claim edits in medical billing?

Claim edits are automated checks run by clearinghouses and payers on required fields, code combinations, modifiers, diagnoses, and payer rules. Some edits reject a claim before processing, and others lead to a denial or reduced payment. Running edits before submission catches many errors.

Can a billing service stop my claims from being denied?

No service can stop all denials, because payers decide coverage. A billing service can reduce avoidable ones by checking eligibility and authorization, reviewing coding, scrubbing claims, working rejections daily, and tracking denial causes. It cannot guarantee any claim will be paid.

Sources

Want this reviewed against your own claims?

The free medical billing audit looks at a sample of your recent claims, denial reasons and A/R aging. You get a written summary and a walkthrough call.

Do not include patient names, insurance IDs or clinical details. If records are needed later, we set up a secure way to share them.