Claim rejection: why a claim never reaches processing, and how it differs from a denial
A claim rejection happens when a payer's front-end edits stop a claim before it is processed, usually for a formatting error or a member ID, provider number, or code that does not match its records. A rejected claim carries no appeal rights, and Medicare does not treat it as received. A denial is a processed claim the payer refused to pay. Fix a rejection and send it again.
On this page
Rejection or denial: what changes for you
A rejection stops at the payer’s front door. A denial gets through the door, gets decided, and comes back unpaid. That one difference decides whether you can appeal, whether the claim counts as filed, and how you send it back.
| Rejected claim | Denied claim | |
|---|---|---|
| Where it stops | Front-end edits, before processing | After the payer adjudicates it |
| Where you see it | An acknowledgment, a rejection report, or a return notice | The remittance, with adjustment codes |
| Appeal rights | None | Yes, within the payer’s appeal window |
| Counts as filed | Medicare treats it as not received | Yes, the claim is on record |
| How to fix it | Correct the data and send it again | Corrected claim, appeal, or write-off |
CMS spells out the Medicare version in its claims processing manual. A claim returned as unprocessable “is not denied” and gets no appeal rights, and a rejected claim is “not considered as received” until it is resubmitted as a corrected, complete claim. Texas Medicaid works the same way in practice: a claim has to show as accepted on the batch’s Claim Response report before TMHP will look at paying it, and a rejected one must be fixed and sent again. The claim denials guide covers the other half.
What front-end edits catch
Payers screen electronic claims in layers, and each layer returns its own response. Medicare’s EDI rules lay the layers out clearly.
- File format. Translators check every file against the HIPAA standard. Syntax errors come back on a 999 implementation acknowledgment, and an unreadable envelope comes back on a TA1.
- Claim content. Claims that pass the syntax check go through code set edits, payer edits, and duplicate checks. Each accepted claim gets a claim control number on the 277CA claim acknowledgment, and the rest come back rejected with a reason.
- Member match. Texas puts a client mismatch first on its list of common rejection reasons for professional claims. The rider’s name, sex, date of birth, and nine-digit Medicaid number have to match the state’s eligibility record exactly, and Texas suggests running an eligibility check to get that exact match.
- Provider data. Texas warns that a claim without the enrolled taxonomy code may be rejected. It also rejects claims from a new provider until enrollment is complete. In Ohio managed care, claims from providers not enrolled with the state are rejected at the EDI front door.
Broker claims follow the same idea, with portal checks in place of acknowledgments. In Virginia, MTM Health turns down a claim when the electronic trip log lacks a required time or the member’s signature, or when the trip is not in completed status. The clean claim entry lists the details that let a payer settle a claim without asking you for more.
Where rejections show up
Many rejections never reach the remittance, so they are easy to miss. Check each of these after every submission:
- The 999. It confirms whether the file passed. Medicare contractors may purge an undownloaded 999 after five business days, so pull acknowledgments daily.
- The 277CA, or the payer’s own claim report. Texas considers a claim for payment only if it appears as accepted on the Claim Response report in the batch response file. Its separate Accepted and Rejected reports list the reasons.
- The remittance, for some payers. Medicare can return an unprocessable claim on the remittance with a CARC and a remark code such as MA130, which says no appeal rights apply and asks for a new claim. The remark codes entry explains how to read those pairs.
- The broker portal. Broker claims are handled inside each broker’s system. MTM Health, for one, takes appeals of denied trips through its online claims portal and gives providers 365 days to file them.
Fixing it and sending it again
Correct the source record first, then the claim. If the member ID was wrong in your trip record, fixing only the claim means the next claim for that rider rejects too. Then send a new original claim. A replacement needs an original claim on file, and a front-end rejection leaves nothing to replace. Our guide to corrected and voided claims covers the cases where a replacement is the right tool.
Watch the next acknowledgment to confirm the claim was accepted. A claim that rejects twice for the same reason often points to a setup problem, such as an unlinked provider number or a taxonomy code that differs from your enrollment.
The filing clock keeps running
A rejection does not pause the deadline. Under 42 CFR 447.45, each state must make providers file no more than 12 months after the trip, and many payers set shorter limits. Texas allows 95 days from each service date. WellTrans sets a 60-day invoice window and refuses anything sent after day 90. MTM Health allows Virginia providers six months from the trip for a clean claim.
Because Medicare counts a rejected claim as received only when it comes back clean, a claim rejected on day 80 and fixed on day 100 is a day 100 claim. Work rejections the day they arrive. Keep every rejection report as well: Texas accepts a TMHP rejection report as proof of meeting the 365-day federal deadline in specific appeals, such as claims sent while enrollment was pending. The timely filing limit entry lists the exceptions that can stretch the clock.
Frequently asked questions
- Rejected claims: is an appeal possible?
- No. CMS says a claim returned as unprocessable for incomplete or invalid information does not meet the criteria to be considered a claim, is not denied, and has no appeal rights. The only remedy is to correct the data and submit the claim again. Save the appeal process for claims that were processed and denied.
- Does a rejected claim stop the timely filing clock?
- Usually not. Medicare treats rejected claims as not received until they come back as corrected, complete claims, so the receipt date is the day you resubmit. Texas Medicaid pays a claim only if its Claim Response report lists it as accepted. Some programs accept a rejection report as evidence in an appeal, so keep every report.
- Is a rejected claim resent as a replacement or as a new original?
- Usually as a new original. A replacement needs an original claim on file, and a front-end rejection leaves nothing in the payer's system to replace. CMS allows a corrected or entirely new claim depending on whether the payer kept the original data, and remark code MA130 asks for a new claim carrying complete and correct data.
- Why would a broker reject a trip that was run correctly?
- Because the paperwork did not match its records. Brokers check the trip ID, times, mileage, and signature against the trip they assigned. In Virginia, MTM Health denies a claim when the trip log is missing a required data point or the trip is not in completed status. WellTrans accepts a resubmission once the missing details are added, but it disallows any invoice sent later than 90 days from the trip date.