US Medical Billing
A/R & Follow-Up

No Response From the Payer

A balance is open, the payer has said nothing, and the queue says to follow up. But no response is not one state — it is at least four, and they look identical from the practice's side. The claim may never have arrived; it may have been rejected before adjudication ever began; it may be genuinely pending; or it may have been decided by a response the practice never received. Three of those are invisible to calling and asking again, which is why the first move is to establish which one is true rather than to apply pressure to all four.

Updated 8 min read

On this page

Key takeaways

Four failures that look the same

What silence can actually mean, and what each case calls for.
What silence can actually mean, and what each case calls for.
The stateHow it is confirmedWhat it calls for
It never arrivedThe submission trail — the acknowledgment for that claim, not for the batch it traveled in.Resubmission, plus the evidence of the original attempt if a filing window is now at risk.
It was rejected before adjudicationA claim rejection sits upstream of the payer's decision system and may never have reached the practice's.Correction and resubmission. There is nothing to appeal, because nothing was decided.
It is genuinely pendingA status response saying so, ideally with what it is waiting on.Wait, with a date — and act only if it is waiting on something the practice holds.
It was decided and the response never arrivedA status response showing finalization, with no matching remittance in the practice's records.Obtain the remittance and post it. Then check what the missing time cost against the appeal window.

The second and fourth rows are the ones that persist, because neither produces anything in the practice's system to contradict the assumption that the claim is simply slow.

Establish the state, rather than asking about it

The distinction that matters is between an answer that is a record and an answer that is an assertion. A representative saying a claim is in process has produced neither a decision nor evidence; a status response is a document.

  • Ask the transaction first. The 276/277 claim status transaction answers at scale and returns a claim status that can be stored against the claim, which is what makes it usable months later.
  • Check your own acknowledgments before blaming the payer. Acceptance of a batch is not acceptance of a claim. A claim rejected at the front door produces a record that is easy not to work and easy to mistake for silence.
  • Reconcile finalized-but-unposted separately. A claim the payer considers finished and the practice considers open is a posting or delivery failure, not a follow-up problem, and it is found by comparing status against what was received rather than by calling.
  • Escalate only once the state is known. Provider representative escalation is worth a great deal when the question is specific and very little when it is "why has this not paid".
  • Record what a call produced. Where the answer did come by phone, documenting a follow-up call covers why the note is the only durable part of it.

When the plan simply will not decide

There is a case the four states above do not cover: the claim arrived, adjudication is owed, and the plan is not deciding. Practices generally treat that as a queue to keep working. For a plan governed by ERISA it is also a legal state.

Silence can satisfy exhaustion rather than block it

The same three limits that apply to every ERISA route

What keeps running while nothing happens

The reason silence is expensive is not the delay. It is that the deadlines which end the practice's options are not paused by the payer's failure to respond.

  • Filing windows keep running. A claim that never arrived is aging against a timely filing limit that does not care why. This is why the evidence of the original submission is worth more than the resubmission itself.
  • Appeal windows may already have started. Where the claim was decided and the response never arrived, the clock has been running against a decision nobody saw — the case for reconciling finalized-but-unposted claims on a schedule rather than on suspicion.
  • A promise to reprocess pauses nothing. More is lost by holding an appeal during a promising conversation than by filing one that turns out to have been unnecessary.
  • Silence generalizes. If one claim went missing at a payer, the mechanism that lost it is still operating. A/R by payer analysis is how a repeated silence stops being a series of claims and becomes one finding.

The rule that keeps this from becoming a queue

Common questions

The payer says it has no record of our claim. Now what?

First establish whether that is true from your side, because a payer's system saying it has no record and the claim never having arrived are not the same finding. The claim-level acknowledgment is the evidence — acceptance of the batch it traveled in does not establish acceptance of the claim. Where the original submission can be evidenced, that evidence is worth more than the resubmission, because it is the argument available if a filing window has since closed. Where it cannot be, resubmit immediately and treat the gap in the acknowledgment trail as the finding, since a claim that vanished without a trace means the trail is not being kept in a usable way.

How do we tell a pending claim from one that was never adjudicated?

By asking the status transaction rather than a person. A 276/277 exchange returns a status that can be stored against the claim, which distinguishes accepted-and-pending from never-received and from finalized, and does it in bulk rather than one call at a time. The distinction matters because the actions are opposite: a pending claim needs a date and possibly whatever it is waiting on, while an unreceived one needs resubmission today. A representative's account of what a screen shows is genuinely useful context and is not a record, which is the practical reason to lead with the transaction.

Does a payer failing to respond give us any rights?

For a plan governed by ERISA, yes, and it is worth knowing. Under 29 CFR 2560.503-1(l)(1), where a plan fails to establish or follow claims procedures consistent with the regulation's requirements, the claimant is deemed to have exhausted the administrative remedies available under the plan and is entitled to pursue available remedies under section 502(a) on the basis that the plan failed to provide a reasonable claims procedure that would yield a decision on the merits. Three limits apply: it is ERISA, so not every plan; the right belongs to the claimant, so a provider reaches it by assignment and an anti-assignment clause can defeat that; and it establishes that the administrative route is finished rather than that the claim is payable. Whether to use it is a question for counsel — knowing it exists changes what a practice accepts as an answer.

Should we keep calling while we wait?

Only with a specific question, and only once the state is known. Repeated calls asking why a claim has not paid produce assertions rather than records and consume the time the genuinely stuck claims need. The higher-value activities are establishing status electronically, reconciling claims the payer considers finalized against what was actually received, and preserving the evidence that protects the filing and appeal windows — none of which is a phone call. Escalation to a named contact is worth a great deal, and it is worth it when the question is specific.

Does a payer's delay extend our deadlines?

Not as a general rule, and assuming otherwise is where the real losses happen. Filing and appeal windows are terms of the agreement or of the applicable program, and they are not paused by the payer being slow, by an open inquiry, or by a representative's assurance that something is being reprocessed. That asymmetry is the argument for treating silence as a diagnosis with a deadline attached rather than as a queue to keep working: the actions that protect the claim — evidencing the original submission, obtaining the remittance, filing to preserve an appeal — all have to happen while the answer is still unknown.

Authoritative sources

  • 29 CFR § 2560.503-1(l) — Failure to establish and follow reasonable claims procedures (opens in a new tab)

    Provides that, except as otherwise specified for disability claims, in the case of the failure of a plan to establish or follow claims procedures consistent with the requirements of the section, a claimant shall be deemed to have exhausted the administrative remedies available under the plan and shall be entitled to pursue any available remedies under section 502(a) of ERISA on the basis that the plan has failed to provide a reasonable claims procedure that would yield a decision on the merits of the claim. The section separately establishes the timeframes within which a plan must notify a claimant of a benefit determination.

Ready to improve your revenue cycle?

Tell us about your practice and we’ll tell you where we would start.