Claim Rejection vs. Denial in Medical Billing: A Rejected Claim Was Never Filed, and the Clock Keeps Running

Does a rejected claim stop the timely-filing clock?

No. For Medicare, 42 CFR 424.44 says a claim must be filed “no later than the close of the period ending 1 calendar year after the date of service,” and the claims manual counts that period from the date of service, the line-item “From” date on a professional claim. What stops the clock is a filed claim, and the manual sets three conditions for one: sent to the right Medicare contractor, on the prescribed form, and in accordance with CMS instructions. A submission that misses them “will not be accepted into Medicare’s electronic claims processing system and will not be considered filed for purposes of determining timely filing.” The receipt date that counts is the day an accepted submission arrives.

So a rejection buys no time. It is sometimes said that rejections do not count against timely filing, and that is true only in the sense that a rejected claim was never filed at all. Every day a rejection spends in a queue comes out of the same year.

The end of the clock is hard. When Medicare denies a claim as filed late, the manual says the denial “does not constitute an ‘initial determination’,” so it is not subject to appeal, and 42 CFR 405.926(n) lists late-filing determinations among actions that are not initial determinations. Where the provider is responsible for the late claim, the manual adds that the provider may not charge the beneficiary for the services, except the deductible and coinsurance that would have applied. The money does not move to the patient; it is gone. On the remittance it shows as CARC 29: “The time limit for filing has expired.”

Medicare Advantage, Medicaid and commercial plans set their own filing limits in the provider contract, the provider manual or state rules, and the limit can differ from Medicare’s year. Each payer’s limit belongs on the rejection report next to the claim, because the limit is what turns an old rejection into a write-off.

Where rejected claims hide

Rejections arrive in more places than denials, and none of them is the remittance a biller already reads every day. Five places to look:

• The clearinghouse rejection report: claims stopped by the clearinghouse’s own edits before they reach any payer, such as a missing subscriber ID, an invalid NPI or a payer ID that does not match.
• Payer acknowledgments: claims the clearinghouse passed on and the payer’s front end turned back, reported claim by claim. A claim can show as accepted by the clearinghouse and still be rejected here.
• Returns on the remittance itself. Medicare’s manual allows a contractor to return an unprocessable claim through the remittance, as long as the error codes are shown. X12’s remark code MA130 reads: “Your claim contains incomplete and/or invalid information, and no appeal rights are afforded because the claim is unprocessable. Please submit a new claim with the complete/correct information.” It looks like a denial on the screen and behaves like a rejection: there is nothing to appeal, and the fix is a new claim.
• Paper returns: where paper claims are still used, an incomplete one comes back by mail with a form explaining the errors, to whoever opens the mail that day.
• Claims that were never created: a visit with no claim is in no queue at all. It shows up only when someone compares the schedule with the charges entered, which is why charge lag and unsigned notes belong in the same review.

The common thread: a rejection is a message to the practice, not a decision by the payer, and messages get lost when nobody owns the inbox they land in.

Two queues, worked two different ways

Rejections and denials need different reports, different skills and different fixes. Keeping them on one “problem claims” list is how a rejection gets treated like a denial, saved for appeal day, and found when the filing year is over.

• The rejection queue is worked every day, oldest date of service first. Each item is fixed where the error started — the patient’s insurance record, the provider record or the payer table in the PM — so the next claim goes out right. Then the claim is sent again, and the next acknowledgment is checked. A rejection is closed by an acceptance, not by a resubmission.
• The denial queue is worked by reason code and payer. Each line gets a route — a corrected claim, a reopening, an appeal, a bill to the patient where the plan assigns the amount to the patient, or a write-off with a stated reason — inside that payer’s deadline.
• Each queue has one named owner. If billing is outsourced, the billing company owns the work and the practice owns the report: both queues, sent on a fixed day.

One habit belongs to the rejection queue alone: fix the source record, not only the claim. A subscriber ID corrected on one claim but not on the patient’s insurance record produces the same rejection on the next visit, and the one after that.

A daily rejection age report

The report that keeps rejections from aging into write-offs is short. It runs every working day, and every rejected claim stays on it until an acceptance comes back:

• Claim number, payer and date of service, with days since the date of service, not days since the rejection.
• The payer’s filing limit and the days left before it.
• The rejection reason as the clearinghouse or payer stated it, and the source record it points to.
• Times rejected: a claim rejected twice for the same reason means the source record was never fixed.
• Owner, date resubmitted and date accepted.

Illustrative example: a practice’s report shows 30 open rejections worth about $9,000. Twenty-two are under a week old; six were rejected for the same payer ID after a plan changed its routing; two have been rejected three times and have dates of service ten months back. The six are one fix in the payer table. The two are the urgent line, because against Medicare’s one-year limit they have about two months left, and against a shorter contract limit they may have none.

When a rejection comes back as a denial

Some denials on the remittance are rejections that were not worked in time, or front-end problems that got through. The X12 list names them plainly. CARC 29, “The time limit for filing has expired,” is the end of a rejection that aged out, or of a claim that was never created. CARC 31, “Patient cannot be identified as our insured,” and CARC 140, “Patient/Insured health identification number and name do not match,” point at the same registration data that front-end rejections flag. CARC 18, “Exact duplicate claim/service,” can follow a claim sent again without checking whether the first one had been accepted after all.

Read together, these codes show where the fix belongs: registration and insurance capture, the payer table, and the habit of confirming acceptance. None of them is an appeal problem. The other front-end source, a service billed without a required approval, has its own code, CARC 197, and its own tracker.

When to fix it in-house, and when not to buy anything

If one person reads the clearinghouse report every morning, every rejection has an owner and an acceptance date, and CARC 29 does not turn up on the remittances, the practice has this covered; outside help would repeat work already done. If billing is outsourced, asking the billing company for the daily rejection age report and a monthly count of CARC 29 by payer costs nothing and tells the owner more than a collections summary.

An outside look earns its fee when nobody can say how many rejections are open or how old they are, when the same rejection repeats month after month, or when timely-filing write-offs are posted without anyone tracing where each claim stalled. The Revenue Review counts this under the visit-to-claim and claim-to-payment hand-offs and takes two weeks; its first pass reads aggregate exports — rejection and denial reports, adjustments by code, aging — not patient names, and it ends with a written report that prices each finding and a 90-day plan. It makes no coding or compliance judgment. A free 20-minute call is enough to tell whether it fits.