Prior Authorization Denied: The 10 Most Common Reasons and How to Prevent Each One
Most prior authorization denials are predictable. Across thousands of submissions, the same handful of failure modes account for the majority of denied cases. This guide walks through the 10 most common reasons prior authorizations get denied, the typical fix for each one, and how submission automation prevents the denial before it happens.
Loading audio...
Most prior authorization denials are predictable. Across thousands of submissions, the same handful of failure modes account for the majority of denied cases. The denial codes change, the payers change, the procedures change, but the root causes stay remarkably stable.
This guide walks through the 10 most common reasons prior authorizations get denied, the typical fix for each one, and how submission automation prevents the denial before it happens. It is written for practice managers, billing teams, and prior auth coordinators who want to drive their first-pass approval rate above 90%.
Why do prior auth denials matter?
Each denied prior authorization triggers a chain of downstream costs.
Per-denial labor. $25 to $80 in coordinator time to investigate the denial, gather missing information, and resubmit or appeal.
Patient impact. A denial that adds 3 to 7 days to the authorization timeline often triggers a patient cancellation. Patients who can't wait often disappear from the practice entirely.
Provider satisfaction. Each P2P review pulls a clinician away from clinical work for 15 to 45 minutes. Practices that run high P2P volumes report it as one of the top burnout drivers among physicians.
Revenue impact. A denied case that gets resolved 7 days later means billing happens 7 days later. At enterprise volume, that translates into measurable working capital cost.
The math is straightforward. A practice running 200 PAs per week with a 12% denial rate has 24 denials per week and an annualized denial labor cost of $50,000 to $100,000 before counting downstream effects. Finance leaders mapping the broader picture should pair this with the fully loaded cost of a manual prior authorization.
What are the 10 most common reasons prior authorizations get denied?
Listed in approximate order of frequency.
1. Missing or incomplete clinical documentation
The most common denial reason across nearly every payer. Clinical notes, imaging results, lab values, or treatment history that the payer's medical necessity criteria require but that the submission didn't include.
The fix: Build a documentation checklist by procedure type. The checklist should map to the specific medical necessity criteria the payer publishes for each CPT.
How automation prevents it: A platform that pulls clinical documentation directly from the EHR using the procedure CPT and the payer's medical necessity rules eliminates the manual gathering step. The submission goes out complete the first time.
2. Service not covered under the patient's plan
The procedure or medication is not a covered benefit on this patient's specific plan, even if it is covered on other plans from the same payer.
The fix: Check coverage at the moment of order entry, not at submission. Coverage rules vary across plans within the same payer, and what was covered last year may not be covered this year.
How automation prevents it: Real-time eligibility verification flags coverage exclusions before the PA even gets initiated.
3. Wrong CPT or diagnosis code combination
The CPT code submitted does not match the diagnosis code submitted, or the diagnosis does not support medical necessity for the requested service.
The fix: Coding validation at the order entry step. The diagnosis-procedure pair needs to align with the payer's medical policy.
How automation prevents it: Code validation engines catch invalid combinations before submission. The system flags the issue and routes back to the ordering provider for correction.
4. Step therapy requirement not met
The payer requires the patient to try a less expensive alternative before approving the requested service. The submission did not document the step therapy attempt.
The fix: Track step therapy requirements by payer and drug class. Document attempts and failures in a structured field, not narrative notes.
How automation prevents it: A platform that knows the payer's step therapy rules can pre-check the patient's medication history in the EHR and surface the requirement to the prescriber before submission.
5. Authorization requested after the service was rendered
The provider rendered the service before authorization was obtained. Most payers won't retroactively approve.
The fix: Hard-stop workflow controls that prevent service rendering until authorization is documented. Education for clinical staff on which services require auth.
How automation prevents it: The system flags PA requirements at the point of order entry and blocks scheduling until approval is logged.
6. Incorrect provider information (NPI, taxonomy)
The submission references a provider NPI or taxonomy code that doesn't match the payer's records or doesn't have credentialing for the service.
The fix: Maintain a current provider credentialing roster mapped to each payer. Check rendering provider eligibility before submission.
How automation prevents it: Provider databases auto-validate NPI and taxonomy against payer-specific credentialing rules.
7. Patient eligibility lapsed
The patient's coverage terminated between scheduling and the authorization request, or the patient changed plans without notifying the practice.
The fix: Re-verify eligibility within 24 hours of submission. Many practices verify at scheduling and assume coverage holds, which it often doesn't for Medicaid populations with frequent eligibility events.
How automation prevents it: Continuous eligibility monitoring catches coverage changes and flags the case before the PA is submitted against an inactive plan.
8. Quantity or frequency limits exceeded
The requested service exceeds payer-defined frequency or quantity limits (e.g., physical therapy visits beyond the per-year cap).
The fix: Track utilization by patient against payer-defined limits. Surface the limit to the ordering provider when a new request would exceed it.
How automation prevents it: Utilization tracking at the patient level. The system surfaces the limit at order entry, with the option to submit a medical necessity exception request if appropriate.
9. Site of service mismatch
The payer requires the service to be performed at a specific site of care (outpatient vs. inpatient vs. ASC) and the submission specified the wrong site.
The fix: Site-of-service rules tracked by payer. Coordinator workflow that validates site against payer policy before submission.
How automation prevents it: Site-of-service rules embedded in the platform. The system flags mismatches at order entry.
10. Medical necessity criteria not documented
The clinical documentation in the submission does not explicitly meet the payer's medical necessity criteria, even though the underlying clinical situation might justify the service.
The fix: Train clinical staff on payer-specific medical necessity language. The note needs to use the right terminology and check the right boxes.
How automation prevents it: Some platforms surface the payer's medical necessity criteria during the documentation step, prompting the clinician to address each criterion explicitly.
The denial pattern most teams miss: soft denials and pends
Beyond outright denials, practices lose significant labor to “pends” and “soft denials.” These show up as requests for additional information rather than full denials, but they consume the same labor and delay the same revenue.
The pattern is consistent. The submission goes in. Three days later, the payer returns a request for additional documentation. The coordinator gathers it and resubmits. Two days later, the payer requests another piece. The coordinator gathers that and resubmits again. By the time approval happens, the case has been touched 4 to 6 times.
Pends and soft denials are often the largest drain on coordinator productivity, and they don't show up in standard denial rate metrics because they aren't technically denials.
How is automation actually changing the denial landscape?
Three changes are visible in practices that have deployed prior auth automation.
| Metric | Before automation | After automation |
|---|---|---|
| First-pass approval rate | 75% to 85% | 90% to 95% |
| Soft denial rate | 15% to 25% | 5% to 10% |
| Coordinator time per PA | 25 to 35 min | 5 to 10 min |
| Authorization turnaround | 3 to 7 days | 1 to 3 days |
| Appeal volume | 8% to 12% | 3% to 5% |
The improvement on first-pass approval comes primarily from completeness. Submissions go out with complete documentation, correct codes, validated provider information, and current eligibility. Most denials happen because of submission quality, not because of clinical merit. Practices already mapping payer turnaround should also read why payers now operate at machine speed.
“Before Linear Health, I was managing five different systems just to get a patient from referral to appointment. Now I have one screen. Our team went from chasing spreadsheets and voicemails to actually coordinating care. The difference is night and day.”
Practices running more than 50 PAs per week typically see denial rate drop 5 to 10 percentage points within 60 days of automation deployment. Book a 15-minute demo to see how this maps to your specific payer mix.
Where PA automation works (and where it doesn't)
Best fit:
- Specialty practices with PA volume above 50 per week
- Practices on Medicare Advantage-heavy panels with high denial exposure
- Multi-payer practices where payer rule complexity drives manual error
- Organizations with chronic coordinator vacancy
Less ideal fit:
- Primary care practices with low PA volume
- Practices on commercial PPO panels with minimal PA requirements
- Organizations without basic EHR integration capability
Teams shopping for vendors should also review the best prior authorization software and the operational details in the prior authorization cheat sheet.
A prevention checklist to run before every submission
Use this checklist for every manual submission until automation is in place.
- Eligibility verified within 24 hours of submission
- Coverage confirmed for this specific procedure on this specific plan
- CPT and ICD-10 combination validated against payer policy
- Clinical documentation complete per payer medical necessity criteria
- Step therapy history documented (where applicable)
- Rendering provider NPI and taxonomy validated for this service
- Site of service matches payer rules
- Frequency and quantity limits checked against patient utilization history
When should you appeal versus resubmit?
The decision tree.
Resubmit when: the denial reason is correctable through additional documentation, code correction, or eligibility update. Resubmission is faster and cleaner than appeal.
Appeal when: the denial is on medical necessity grounds and the submission was complete and correct. Appeal data shows roughly 80% approval rate when appeals are filed correctly with strong clinical documentation. Use the templated language in the prior auth appeal letter templates for the most common appeal scenarios.
Initiate peer-to-peer when: the appeal is rejected and the clinical case is strong enough to warrant physician-to-physician discussion. P2P approval rates run 50% to 70% for prepared physicians.
Frequently asked questions
What percentage of prior authorizations are denied?
Denial rates vary widely by payer and procedure but typically run 7 to 15% across most commercial and Medicare Advantage plans. Some MA plans have denial rates above 20% on certain procedures.
How long does prior authorization take?
Standard authorization runs 3 to 7 days for manual submissions, 1 to 3 days for automated submissions, and within 72 hours for expedited (urgent) cases under the new CMS 2026 rules.
Can a prior authorization be denied after it was already approved?
Yes, in some cases. Payers can retract approval if information was misrepresented or if eligibility lapsed between approval and service rendering. Approval is not the same as a payment guarantee.
What is the difference between a denial and a pend?
A denial is a final negative decision. A pend (or soft denial) is a request for additional information. Pends are not technically denials but they consume similar labor and delay the same revenue.
Should I always appeal a denied prior authorization?
No. Appeal when the denial is on medical necessity grounds and your submission was complete and correct. Resubmit (don't appeal) when the issue is missing documentation, coding error, or eligibility lapse. Resubmission is faster.
Sami scaled Simple Online Healthcare to $150M and built a multi-specialty telehealth clinic across 20 specialties and all 50 states. Connect on LinkedIn.
