A rejected claim never reached the payer’s adjudication system, so nobody is going to pay it, deny it, or call you about it. It just sits in a report until someone fixes it. That’s what makes rejections dangerous: they’re usually easy to fix, but if no one works them, the claim ages quietly toward its timely filing limit. This guide explains the reports you’ll see, the most common rejection reasons, and a daily routine that keeps them from turning into write-offs.
Rejection vs denial: why the difference matters
- Rejection: the claim failed a format or data check at the clearinghouse or at the payer’s front end. It was never accepted into the payer’s claims system, so there’s no claim number and no remittance. You fix the data and resubmit the claim as if it were new.
- Denial: the payer accepted and processed the claim, then decided not to pay all or part of it. You’ll see a claim number and a denial code on the ERA or EOB, and the fix is a corrected claim or an appeal. See our guide to claim denial codes.
The key point: a rejected claim generally doesn’t count as filed. If you rely on the original send date of a claim that was rejected, you may find the payer has no record of it at all when you call months later. Our timely filing guide explains why clearinghouse acceptance reports, not send dates, are your proof.
The reports that tell you a claim was rejected
Electronic professional claims go out as 837P transactions. Several acknowledgment reports come back, and each one answers a different question:
- Clearinghouse edit report: your clearinghouse checks claims against its own edits before forwarding them. Claims that fail never leave the clearinghouse. Names vary by vendor (Office Ally, Availity, Waystar, Trizetto and others each have their own screens), but every clearinghouse has a rejected or “needs attention” queue.
- 999 (implementation acknowledgment): confirms whether the file was syntactically valid. A rejected 999 usually means a structural or formatting problem with the batch rather than one patient’s data.
- 277CA (claim acknowledgment): the payer’s front-end response for each claim, showing whether it was accepted for processing or rejected, with status category and status codes explaining why.
- Payer portal status: once accepted, the claim should appear in the payer’s portal or claim-status response (276/277). If a claim shows as accepted at the clearinghouse but the payer has no record of it, call or check the portal before assuming it’s in process.
The most common rejection reasons and how to fix them
Patient and subscriber data
- Member ID not found or invalid: often a typo, an old card, or a missing prefix or suffix. Re-verify eligibility and copy the ID exactly as the payer shows it.
- Name or date of birth doesn’t match: nicknames, hyphenated last names, and swapped month/day fields cause many of these. Match the payer’s eligibility response, not the patient’s preferred name.
- Subscriber vs patient mix-up: when the patient is a dependent, the subscriber’s details and the relationship code must be right. Billing a child under their own name as the subscriber is a classic cause.
- Wrong payer ID: the same insurer can have different payer IDs for different products, especially Medicare Advantage and Medicaid managed care plans. Check the card and your clearinghouse’s payer list.
Most of these are prevented at check-in. See our eligibility verification checklist.
Provider data
- Invalid or inactive NPI: confirm the rendering and billing NPIs in the NPPES registry and make sure the right NPI is in the right field.
- Taxonomy problems: some payers require the taxonomy code, and it must match how the provider is enrolled with that payer.
- Billing provider address: the billing provider address generally must be a physical location, not a PO box. Use the pay-to address fields for a PO box or lockbox.
- Provider not set up with the payer: some front-end edits reject claims for providers who aren’t enrolled or linked to the group. See our credentialing and enrollment guide.
Codes and claim details
- Invalid or non-billable ICD-10-CM code: a code that isn’t valid for the date of service, or a category code that needs more characters. Check codes in our ICD-10 code search, which flags whether a code is billable.
- Missing or invalid diagnosis pointer: every service line needs a pointer to a diagnosis that exists on the claim.
- Invalid place of service, or POS that doesn’t fit the code: see our place of service codes guide.
- Missing referring or ordering provider: required for services like labs, imaging, and some therapy and DME claims.
- Dates that don’t make sense: service dates in the future, or after the claim date, or outside the patient’s coverage period.
- Duplicate submission: some clearinghouses and payers reject an exact duplicate of a claim already accepted. If you’re fixing a processed claim, send a corrected claim instead. See our corrected claims guide.
Fix the cause, not just the claim
A daily rejection workflow
- Check every report, every day. Look at the clearinghouse rejection queue and the 277CA responses each morning. Rejections older than a day or two are where timely filing problems start.
- Sort by type. Group rejections into patient data, provider data, and coding or claim-detail problems. Patient data issues may need the front desk; provider issues may need credentialing or system setup.
- Correct in the source system. Fix the data in your practice management system, not only in the clearinghouse, or the same error will go out again on the next claim.
- Resubmit and confirm acceptance. Don’t mark a rejection as done when you resend it. Mark it done when the 277CA shows the claim was accepted.
- Track repeat offenders. Keep a simple log of rejection reasons by payer and by cause. Review it weekly and fix the setup issues behind the top items.
Clearinghouse edits vs payer edits
Clearinghouse edits check format and common data problems, and many clearinghouses add payer-specific rules. They don’t know everything the payer will check. A claim can pass the clearinghouse and still be rejected by the payer’s front end, or be accepted and later denied for coding or coverage reasons. Running claims through a pre-submission check, such as our free claim scrubber for modifier, unit, and diagnosis pointer issues, catches a different set of problems than the clearinghouse does.
How to prevent rejections
- Registration accuracy: scan both sides of the insurance card, verify eligibility before the visit, and copy names and IDs exactly as the payer returns them.
- Clean provider setup: keep NPIs, taxonomy codes, tax IDs, and addresses in the PM system consistent with each payer’s enrollment records.
- Up-to-date code sets: load annual ICD-10-CM updates before October 1 and CPT/HCPCS updates before January 1. See our ICD-10-CM update guide.
- Payer list maintenance: review payer IDs when plans change, especially in January.
- Ownership: make one person responsible for the rejection queue each day, with a backup, so nothing sits unworked.
Frequently asked questions
Does a rejected claim count toward timely filing?
Generally no. A rejected claim was never accepted by the payer, so most payers treat it as not filed. Fix and resubmit quickly, and keep the acceptance report as proof once the claim goes through.
Should I resubmit a rejected claim as a corrected claim?
No. Because the payer never accepted it, a rejected claim is usually resubmitted as an original claim with the error fixed. Corrected claims (frequency code 7) are for claims the payer already processed.
Why was my claim accepted by the clearinghouse but the payer has no record of it?
The clearinghouse may have accepted the file, but the payer’s front end rejected the claim, or the claim went to the wrong payer ID. Check the 277CA and the payer portal, and call the payer if it still doesn’t appear.
How often should rejection reports be worked?
Daily. Rejections are usually quick to fix, and working them every day keeps them from aging toward timely filing limits.
This guide is general information. Report names, edits, and rejection codes vary by clearinghouse and payer; follow your clearinghouse’s documentation and the payer’s companion guide.