Denial Management
Physical Therapy Claim Denials: A Practical Root-Cause Guide
A denial code identifies the payer-reported reason, but effective denial management requires reviewing the claim and determining the underlying operational cause. The same message can arise from different facts, and the appropriate response depends on the payer instructions, claim history, documentation, authorization, eligibility, provider information, and date of service. This guide focuses on a practical review process rather than a universal code dictionary.
01
Rejected Claim vs Denied Claim
A rejected claim generally fails an early submission or acceptance edit and may not enter the payer's adjudication workflow. Examples can include missing or invalid claim information, formatting issues, or an incorrect payer route. The team normally needs to identify the rejection source, correct the information when appropriate, and submit according to the applicable process.
A denied claim has generally reached payer adjudication and received an unfavorable determination or zero-payment outcome. It may require a corrected claim, requested information, reconsideration, appeal, or another action. Terminology and workflows vary, so use the clearinghouse and payer response—not a label alone—to confirm status. See Billing & Claims for the broader submission workflow.
02
Common PT Denial Categories
Physical therapy denials may relate to authorization, eligibility, claim information, coding or modifiers, documentation, medical-necessity determinations, duplication, timely filing, or payer payment policy. These categories are starting points for investigation. They are not interchangeable, and a single category may contain multiple operational causes.
A useful denial inventory groups claims by payer, reported reason, age, amount, service type, provider where appropriate, authorization status, eligibility issue, and claim-submission history. This makes repeated patterns easier to see without assuming that every claim in a category requires the same response.
03
Why Authorization Denials Happen
Authorization-related denials may involve a missing authorization, expired approval, date-range mismatch, visits or units beyond an approved amount, services outside the available approval, delayed reauthorization, or information that did not transfer correctly to the claim. The actual issue must be confirmed against the approval record and payer response.
A patient may have active coverage and still require authorization. An authorization may also exist while another claim requirement remains unresolved. Review the authorization or reference number, dates, visits, units where applicable, services, payer or utilization-management vendor, and claim data. The prior authorization guide explains a tracking workflow.
04
Why Eligibility Denials Happen
Eligibility-related denials can follow inactive coverage, an incorrect payer or member identifier, coordination-of-benefits issues, a plan change, or a mismatch between the patient information used at verification and the claim. Verification is a point-in-time administrative review and does not guarantee payment.
Research should compare available eligibility information with the date of service, claim, payer response, and any later coverage information. Repeated eligibility-related denials may justify a review of front-end collection and verification practices. Learn more about Eligibility & Benefits workflows.
05
Modifier and Coding-Related Denials
A payer response may reference a modifier, procedure combination, edit, unit, or other claim detail. That message should lead to claim-specific review rather than an automatic correction. Determine what was billed, what documentation supports, what the payer reports, and which instructions apply to the actual service and date.
Coding and modifier requirements vary by payer, plan, service, provider, setting, and date of service. Administrative staff should not change coding merely to obtain payment. Coding decisions should reflect the service, documentation, applicable requirements, and the practice's established clinical and compliance responsibilities.
06
Documentation-Related Denials
Payers may request records or deny based on missing, incomplete, late, or insufficient documentation under the applicable review criteria. Administrative denial work can identify the request, deadline, submission channel, and claim status, then coordinate with the practice. Clinical documentation remains the responsibility of the treating provider.
The response should use the documentation that accurately reflects the care delivered. Revenue-cycle staff can track what was requested, what was supplied, proof of submission, and the payer's next response. They should not create clinical content or represent that documentation guarantees a particular determination.
07
Timely-Filing Denials
A timely-filing denial requires review of the payer-reported limit, applicable plan or contract information, original submission date, acceptance evidence, rejection history, corrected-claim history, and any circumstances recognized by the payer. There is no universal filing or appeal timeframe across payers and plans.
Do not assume the date printed on a claim proves timely receipt. Clearinghouse acceptance, payer acknowledgment, prior correspondence, or other records may be relevant. The correct response can differ when a claim was never accepted, was sent to the wrong payer, or was resubmitted after an earlier rejection.
08
Why Repeated Denials Matter
One denial is a claim problem. Repeated denials may be a workflow problem. A pattern by payer, category, provider, service, authorization status, or submission source can reveal where additional investigation or process correction may be useful. It can also show that a payer change or a particular account group needs focused review.
Patterns should still be interpreted cautiously. An increase in denial count may reflect higher claim volume, one concentrated payer event, or a changed classification method. Compare counts, dollars, claim volume, dates, and operational context before concluding that one process failed.
Management reporting becomes more useful when it separates new denials, unresolved denials, corrected claims, responses awaiting payer action, and accounts awaiting practice action. This prevents a growing inventory from being interpreted as one undifferentiated problem. It also helps leaders see whether staff are only identifying denials or moving them through defined response and escalation stages. Available reporting depends on the system, remittance detail, claim history, and consistency of the team's status documentation. Comparing later reports can then show whether a category is improving, stable, or continuing to add unresolved accounts after a workflow change.
09
Corrected Claim, Reconsideration or Appeal?
A corrected claim generally updates claim information through the payer's defined process. Reconsideration may ask the payer to re-review an outcome, while an appeal commonly presents a formal challenge supported by applicable information. Payers may use different names, forms, portals, addresses, or sequences for these actions.
Not every denial should be appealed. The appropriate next step depends on whether information was incorrect, documentation is requested, the payer made a processing determination, the practice disputes the decision, and a response remains available. Follow the payer's current instructions and preserve submission evidence and deadlines relevant to the claim.
10
Denial Root-Cause Workflow
Identify the payer response
Capture the claim, line, amount, reported reason, remittance information, and date.
Categorize the denial
Group the issue for operational analysis without treating the category as a final root-cause conclusion.
Investigate the underlying facts
Review claim history, eligibility, authorization, documentation, submission, payment, and provider information as relevant.
Select the appropriate action
Determine whether correction, information submission, reconsideration, appeal, other follow-up, or practice review fits the circumstances.
Follow through and document
Record the action, confirmation or reference information, deadline, owner, and next-action date.
Feed recurring problems upstream
Use supported patterns to review front-end, authorization, billing, documentation-coordination, enrollment, or posting workflows.
11
Practical Denial Review Checklist
A consistent checklist prevents the denial code from becoming the end of the analysis. Use only the fields relevant and available for the claim.
- Payer and plan
- Reported reason and remittance details
- Denied amount and claim age
- Authorization status and approval record
- Eligibility information for the date of service
- Original and corrected claim history
- Applicable filing or appeal deadline
- Documentation requested and available
- Payer instructions and submission channel
- Last meaningful action
- Owner and next-action date
12
Frequently Asked Questions
What is the difference between a rejected and denied claim?
A rejection commonly occurs before payer adjudication because a submission or acceptance edit was not satisfied. A denial generally follows adjudication. Confirm the actual status from clearinghouse and payer responses because terminology and workflows vary.
Should every physical therapy denial be appealed?
No. A corrected claim, requested information, reconsideration, appeal, or another action may be appropriate depending on the payer response and claim facts. Some denials may not have an available or supportable challenge.
Does a denial code prove the root cause?
No. It reports the payer's stated reason. Claim history and relevant eligibility, authorization, documentation, billing, provider, and payment information may be needed to understand the underlying operational cause.
Can authorization denials be prevented?
Some authorization-related problems may be reduced through requirement review and tracking, but not every denial is preventable. Payer rules, plan information, clinical determinations, claim circumstances, and changes can affect outcomes.
Why track denial patterns?
Patterns can show concentrations by payer, category, service, amount, or workflow and help management decide where investigation may be most useful. A pattern is a signal for review, not automatic proof of one cause.