Pick the reason on your denial. You get what it means, the steps to fix the claim, and how to prevent the next one.
Timely filing
A timely filing denial means the payer received the claim after its deadline for that date of service. Medicare generally allows 12 months from the date of service; commercial plans set their own limits in your contract, often much shorter.
Fix this claim
Find proof the claim was sent on time: the clearinghouse acceptance report or the payer’s acknowledgment with its date.
If you have that proof, send a reconsideration or appeal with it attached; payers usually reverse the denial when the original submission was within the limit.
If the delay came from another payer (for example, waiting on a primary payer’s decision), send that payer’s remittance showing the date it was decided.
If there is no proof and no valid reason, the charge usually has to be written off; the patient generally cannot be billed for your late filing.
Stop the next one
Keep a list of every payer’s filing limit and track each open claim against it.
Work clearinghouse rejections every day; a rejected claim is not a filed claim.
Make unsigned notes and unbilled visits visible daily, so no visit waits weeks for a charge.
Confirm the primary payer at check-in so the first claim goes to the right place.
A duplicate claim denial means the payer believes it already received, or already processed, a claim for the same patient, date of service and service. Most are caused by resending a claim instead of checking its status or sending a properly marked corrected claim.
Fix this claim
Check the status of the original claim first; it may already be paid or in process.
If the original was paid correctly, the duplicate denial needs no action.
If you needed to change the original, send a corrected (replacement) claim that references the original claim number, not a new claim.
If two distinct services were really performed, resend with the documentation and the detail that shows they were separate.
Stop the next one
Check claim status before any resubmission.
Use the corrected-claim process for changes, never a fresh claim.
A prior authorization denial means the payer required approval before the service and the claim did not carry a valid authorization: none was obtained, it had expired, or it did not cover the service, dates or number of visits billed.
Fix this claim
Check whether an authorization exists and was simply missing from the claim; if so, send a corrected claim with it.
If none was obtained, ask the payer whether it accepts retroactive authorization for this service; some do within a short window.
Otherwise appeal with the clinical documentation showing the service was necessary and urgent if it was.
Record the outcome so the same service is flagged next time.
Stop the next one
Check authorization requirements when the service is ordered, by payer and plan.
Track every approval with its number, dates and remaining visits, and warn before scheduling outside them.
Carry the authorization onto the claim automatically.
An eligibility denial means the payer could not match the patient to active coverage on the date of service: the plan had ended, the member ID or name did not match, or the service was billed to the wrong plan.
Fix this claim
Run a new eligibility check for the date of service to see the coverage the payer has on file.
If demographics were wrong, correct them and resubmit.
If the patient has a different plan, bill that plan, watching its filing limit.
If there was no coverage, follow your self-pay policy with the patient.
Stop the next one
Verify eligibility before every visit, not only at registration.
Ask about insurance changes at every check-in and scan the current card.
A medical necessity denial means the payer decided the service was not reasonable and necessary for the diagnosis and documentation on the claim, often because the diagnosis did not support the service or the payer’s coverage policy was not met.
Fix this claim
Read the payer’s coverage policy for the service and compare it with the note.
If the documentation supports the service, appeal with the relevant note, results and the policy criteria it meets.
If the diagnosis was coded incompletely, correct it if the record supports a more specific code, and resubmit.
For Medicare, if a valid ABN was signed, the patient can be billed; without one, usually not.
Stop the next one
Document the reason for each service in the note, not only the diagnosis.
Check the payer’s coverage policy for frequently denied services.
Give Medicare patients an Advance Beneficiary Notice before services Medicare may not cover.
A missing-information denial (or a front-end rejection) means a required field on the claim was empty or invalid: patient details, the billing or rendering provider’s number, the place of service, a referring provider or another required element.
Fix this claim
Read the exact field named in the rejection or denial reason.
Correct the field from the source record (the insurance card, the provider’s enrollment details).
If it was rejected (never accepted), simply resubmit; if it was denied after processing, send a corrected claim.
Stop the next one
Capture demographics from the insurance card at registration and verify them with eligibility.
Keep provider enrollment details in one place and pull them onto claims automatically.
Check every claim for required fields before it is sent.
A coordination of benefits denial means the payer believes another plan should pay first, or it needs updated information from the patient about other coverage before it will pay.
Fix this claim
Confirm which plan is primary for the date of service.
Bill the primary first; then send the secondary claim with the primary’s remittance.
If the payer needs updated coverage information, ask the patient to contact the plan, then resubmit.
Stop the next one
Ask about all coverage at check-in, including spouse or parent plans and Medicare.
For Medicare patients, use the Medicare Secondary Payer questionnaire at intake.
Record the order of benefits on the patient record so every claim follows it.
A bundling denial means the payer considers the service part of another service billed for the same patient on the same day, so it pays only for the main service.
Fix this claim
Check whether the services are truly bundled under the payer’s or national correct coding edits.
If they were separate (a different site, session or problem), document that and resubmit with the appropriate modifier.
If they were not separate, accept the bundled payment; appealing will not change the edit.
Stop the next one
Check correct coding edits before the claim is sent.
Use modifiers only when the note shows the services were distinct.
A non-covered denial means the patient’s plan does not include the service as a benefit at all, regardless of medical necessity, for example many cosmetic, screening or routine services under some plans.
Fix this claim
Confirm the exclusion in the benefits returned by the eligibility check or the plan documents.
If the service is covered under another plan, bill that plan.
If it is truly excluded, bill the patient according to your agreement with them and the payer contract.
Stop the next one
Check benefits for services that plans often exclude, before the visit.
Tell patients in writing when a service may not be covered and get their agreement to pay (for Medicare, use the ABN where it applies).
A diagnosis coding denial means a diagnosis code on the claim was invalid for the date of service (for example, deleted in the yearly update), not coded to its full length, or did not support the service billed.
Fix this claim
Check the code against the ICD-10-CM version in effect on the date of service.
Replace it with the complete, specific code the documentation supports.
Make sure each service line points to the diagnosis that justifies it, then resubmit.
Stop the next one
Update your code set every October and review your most used codes for changes.
Code to the highest specificity the note supports.
Hi! I'm the XEHR Concierge — ask me anything about XEHR (pricing, features, demos, comparisons, support):
Platform features
Pricing plans
HIPAA compliance
Schedule a demo
Thinking
Powered by XEHR
Your privacyIf you accept, the chat remembers you between visits and we count site visits with a web analytics service (never what you type into forms). Decline and everything still works. Privacy Policy