Tracking a Claim: Status, Aging, and Follow-Up
A claim the payer accepted and has not decided is in a strange position: it is not a problem, not a payment, and not a denial. It is simply quiet — and quiet claims are the only ones in the revenue cycle that will never ask for your attention, because there is nothing about them to notice.
Updated 7 min read
On this page
Key takeaways
- A claim can be accepted and still not be decided. That state belongs to no process: submission ended at acceptance, and denial work has not begun.
- Status is a question you ask, not a signal you receive. The 276/277 transaction exists precisely because payers do not narrate progress.
- Aging measures how long claims have been waiting, not how long they should wait. It is a lens on your own A/R, not a verdict on a payer.
- Follow-up is triage, not chasing. Its job is to find the claims that are stuck for a reason, before the filing and appeal clocks run out on them.
The gap between two processes
The two operational processes on this site meet at adjudication and do not overlap. The Claim Submission Process ends the moment a payer accepts a claim. The Denial Appeal Process begins after a payer has adjudicated one and refused it. Between them is a stretch that belongs to neither: the claim is with the payer, and nothing has come back.
Most of those claims are fine. They are being processed, and they will be paid on the payer's own timetable. But some are not fine, and the two look identical from the outside — because the outside is silence in both cases. Follow-up is the discipline of telling them apart before it matters.
Silence is the default, not a signal
Asking for status
There is a standard transaction for exactly this question. A 276 asks a payer for the status of a claim; a 277 is the payer's answer. It exists because the alternative is manual: calling, or logging into a portal, one claim and one payer at a time.
What a status response gives you is where the claim is in the payer's process, which is not the same as what the payer will decide. It can tell you that a claim is in process, that it has been finalized, or that the payer has no record of it at all — and that last answer is the one worth the whole exercise, because a claim the payer has no record of is not being processed slowly. It is not there.
“No record” means the clock is still running
What aging tells you, and what it does not
The standard way to find quiet claims is to sort by age: how long has each been outstanding? Aging buckets are the usual shape of this, and they are genuinely useful — with one important caveat about what they are measuring.
Aging measures elapsed time against your own expectations, not against a rule. There is no universal number of days after which a payer is late; payers process at different speeds, plans differ, and a claim that is old is not necessarily a claim that is stuck. A bucket is a prompt to look, not a finding — and treating age alone as a problem generates a lot of calls about claims that were always going to be paid on time.
The aggregate version of this is days in A/R, which measures how long money takes to arrive after billing across the whole book. It is the trailing bookend to charge lag: one measures how long you take to bill, the other how long you wait to be paid. A practice can be excellent at one and poor at the other, and the two are fixed in completely different places.
Sort by reason to work, by age to find
Follow-up is triage
The word “follow-up” makes this sound like chasing, and chasing is the least useful version of it. The work is triage: sorting quiet claims into the ones that are fine and the ones that are not, and doing it while there is still time to act on the answer.
- Progressing normally
- The payer has it, it is in process. Nothing to do. Most quiet claims are here, and calling about them costs staff time and changes nothing.
- Not received
- The payer has no record. The claim stopped at a gate and the acknowledgment was missed. Resubmit — and go and find out why the report was not worked, because this claim will not be the only one.
- Waiting on something
- The payer has it and needs information — records, a response to a development request. This is a soft denial in all but name, and it is on you, not them. It resolves when the thing is supplied.
- Finalized, and you did not know
- A decision was made and the remittance was not posted, or was posted and the denial on one line was missed among the paid ones. The claim is not quiet at all; the answer arrived and nobody read it.
Only two of those four are follow-up problems, and each of the other two points somewhere else — at the acknowledgment step, or at posting. That is the recurring shape of this whole subject: a claim that appears stuck is usually a report that was not read, one step earlier.
The clocks do not pause while a claim is quiet
Common questions
How long should I wait before following up on a claim?
There is no universal number, and we do not publish one. Payers process at different speeds and plans differ, so an age that indicates a problem at one payer is unremarkable at another. What is more useful than a fixed interval is a fixed habit: use aging to surface candidates, then ask for status rather than assuming — because the answer that matters ("we have no record of this claim") is not a function of how long you waited.
What is a 276/277?
It is the standard claim status transaction: a 276 asks a payer for the status of a claim, and a 277 is the payer's answer. It exists because payers do not narrate progress — silence is the default state, not a signal — and because the alternative is asking manually, one claim and one payer at a time. Note that a status response tells you where a claim is in the payer's process, not what the payer will eventually decide.
The payer says it has no record of a claim we submitted. What now?
Resubmit it — and then go and find out why nobody knew. A claim the payer has no record of stopped at a gate before adjudication, and an acknowledgment report said so at the time. That report was not worked, which means this claim is unlikely to be the only one, and the filing window has been running the whole time on all of them. The resubmission fixes one claim; the acknowledgment habit fixes the cause.
Isn't aging enough to manage follow-up?
Aging is good for finding candidates and poor for prioritizing them, because age says nothing about why a claim is sitting. Two claims of identical age can be one progressing perfectly normally and one the payer never received — and only the second is a problem. Use age to build the list and status to decide what is actually on it; otherwise most follow-up effort goes into calling about claims that were always going to be paid.
Key terms in this article
Defined once, on their own pages.
Continue learning
Where to go next.
Days in A/R
The aggregate measure of how long money takes to arrive after billing.
Denials & Appeals
What to do once a quiet claim turns out to have been decided against you.
Days in A/R calculator
Calculate how long your outstanding balance represents in days of charges.
Submitting Claims
The acknowledgment step that catches most of these problems before follow-up ever has to.
Authoritative sources
- X12 — EDI standards (opens in a new tab)
Maintains the 276/277 claim status transactions and the acknowledgment transactions referenced here.
- Centers for Medicare & Medicaid Services (CMS) (opens in a new tab)
Publishes Medicare claim status and claims-processing guidance for providers.
- Healthcare Financial Management Association (HFMA) (opens in a new tab)
Publishes standard definitions for revenue-cycle metrics, including days in A/R.