Most practices track denials. Denials are visible, they come with a reason code, and they land in a report that somebody eventually reads. Pends are the opposite: a claim that has been accepted, acknowledged, and then quietly stopped somewhere inside the payer’s system while it waits for information that may never have been requested from you. Nothing is rejected. Nothing is written off. It just sits there, until it ages past timely filing, at which point it becomes a denial you can no longer appeal.
What this covers
- A denial has been adjudicated. A pend is suspended and still payable.
- Pends rarely appear in denial reporting, so they are found late or not at all.
- A pend does not reset the timely filing clock, which runs from the date of service.
- Split the queue by reason: administrative pends to billing, clinical pends to a coder or clinician.
That asymmetry is the whole problem. A denied claim is a task. A pended claim is a trap, because the only thing distinguishing it from a claim that is about to pay is time.
The difference, precisely
| Denied | Pended | |
|---|---|---|
| Payer status | Adjudicated, a payment decision has been made | Adjudication suspended, decision pending |
| Money | Not payable as submitted | Still potentially payable |
| What you get | Remittance with a denial reason code | Often nothing, until someone asks |
| Appears in denial reports | Yes | Usually not |
| Risk if ignored | Appeal deadline missed | Timely filing missed, no appeal available |
| Who acts | Appeals and coding | Whoever notices |
The last row is the actual failure. Denials have a workflow because they announce themselves. Pends do not, so they get worked when somebody happens to run the right report, which, in a practice without a pend process, means when cash flow feels wrong and somebody starts digging.
Why pends exist at all
A payer pends a claim when it cannot complete adjudication with the information it has. That is a broad category, and the patterns repeat:
- Eligibility and coordination of benefits. The patient’s coverage changed, another payer is primary, or the member ID does not match the payer’s file. The claim is fine; the coverage picture is not.
- Authorisation mismatch. An authorisation number is present but does not match the dates, the units, the CPT codes, the rendering provider or the place of service.
- Medical necessity review. The claim has been routed for clinical review, which can take weeks and often depends on records nobody has sent.
- Coding edits. NCCI bundling, modifier requirements, units that look unusual for the code, or a diagnosis that does not support the service billed.
- Provider data problems. The rendering provider is not on the payer’s enrolment file, the group’s TIN/NPI relationship does not match, or a credentialing record is inactive.
- Requests for information. The payer has asked for records, sometimes by letter or portal notice, sometimes not at all, and the claim is waiting on a response you have not sent.
Note how many of these are front-end problems wearing a back-end costume. Eligibility, authorisation and provider enrolment are all decided before the claim goes out the door. A pend is usually the bill for a front-end gap.
Some pends are effectively denials in waiting, a claim pended for medical necessity that the payer intends to deny once records arrive. Working it as an administrative task wastes weeks. The test is whether the pend reason is factual (fix and resubmit) or clinical (needs records and possibly a peer-to-peer). Those are different work queues with different owners.
How to find claims you did not know were stuck
Pends are found by asking, not by waiting:
- 277CA acknowledgement reports. The front-end response confirms whether a claim was accepted or rejected by the payer’s clearinghouse gateway. It does not tell you what happens afterwards, so it is necessary but not sufficient.
- Claim status inquiries. 276/277 transactions or the payer’s portal, run on a schedule against open claims rather than in response to a hunch.
- A/R ageing by claim status rather than by dollars alone. A report showing which claims have been in adjudication more than 30 days is the single most useful pend tool, and most practice management systems can produce it.
- Payer portal work lists. Many payers expose pended claims awaiting information. If nobody logs in, those lists are where revenue quietly expires.
- Remittance code review. Some pends do generate a remittance line, commonly with a claim-suspended or additional-information-required adjustment code. If your posting team treats these as denials and files them in the appeal folder, they are being worked as the wrong thing.
A queue that works
A pend process needs three things: a trigger, an owner and a clock.
- Trigger. A weekly report of every claim in a pended status, refreshed on a fixed day, with the reason where the payer supplies one.
- Sort by age, not by value. The oldest claims are the ones closest to the timely filing line, so they go first regardless of dollars. A $90 claim resolved in week two beats a $900 claim resolved in week nine.
- Escalation thresholds. Anything pended beyond 14 days gets worked weekly. Anything beyond 30 days escalates to a named person with authority to call the payer. Nothing is allowed to reach day 45 silently.
- Owner per reason type. Administrative pends belong to billing, clinical pends to a clinician or coder who can produce records and argue medical necessity. Mixed queues are why pends stall, a billing specialist cannot resolve a medical necessity review.
- Feedback to the front end. Every eligibility and authorisation pend is evidence of a front-end failure. If the same reason appears twenty times a month, the fix is upstream, not another round of claim status checks.
A practice submitting $400,000 a month, with 6% of charges pended and an average 22 days to resolution, is carrying roughly $24,000 in unresolved adjudication at any moment. The $24,000 is not the loss, most of it eventually pays. The loss is the slice that crosses the timely filing line while it waits, plus the staff time spent reworking claims that a five-minute eligibility check would have prevented. Run that arithmetic with your own numbers before deciding pends are somebody else’s queue.
Where the pends actually come from
Across practices we review, pends concentrate in three root causes, and only one of them is a billing department problem:
- Front-end data. Coverage not verified or verified wrongly, authorisations captured without the details that matter (units, dates, rendering provider), demographic mismatches between the EMR and the payer.
- Unclear ownership. Pends split across billing, front desk and clinical staff with no single accountable queue, which means each party assumes someone else has it.
- Documentation lag. Payer requests for records that wait on clinical staff to produce notes, during which the claim ages. The request is not the problem; the turnaround is.
Fixing the first is a process change at scheduling and check-in. The second is a reporting and accountability change. The third is a service-level expectation inside the practice. None of them require new software, so they show up so rarely in “our new A/R platform” conversations.
Questions we get about pends
A denial has been adjudicated, the payer has made a payment decision and sent a remittance with a reason code. A pend has not: adjudication is suspended pending information. Practically, a denial appears in your denial report and a pend usually does not, so a claim status inquiry or an ageing-by-status report is the only reliable way to find them.
Until the payer’s timely filing deadline passes. Filing limits are typically 90 to 365 days from the date of service depending on payer and plan, and once that date passes the claim is not appealable on its merits. Because a pend does not reset that clock, the true deadline is fixed at the date of service, not at the date you discovered the pend.
Yes, and this is the common outcome when a pend is left alone. Once timely filing expires the claim converts to a denial that cannot be appealed on clinical grounds. That is why pends are more financially dangerous than denials despite looking less urgent.
Split by reason type. Administrative pends: eligibility, demographics, authorisation mismatches, provider data, belong with the billing team. Clinical pends such as medical necessity reviews need a coder or clinician who can produce records and argue the case. A queue where both land with the same person is where pends go to age.
Count and dollars pended by reason, the age of the oldest pended claim, and the average days in pend status. Tracked weekly, those three numbers tell you more about revenue risk than the total A/R figure, because they show money that is currently invisible to your denial reporting.
Yes. Pend resolution is part of our denial management process, a weekly status sweep across payers, escalation on age rather than dollars, and feedback to the front end when the same reason keeps recurring. It runs alongside coding because a meaningful share of pends are coding edits rather than administrative ones.
The bottom line
Track pends by age and reason rather than by dollar value. The oldest claims are the ones nearest the filing deadline, and a pend that crosses it stops being appealable on its merits.
What is sitting in adjudication in your practice right now?
Send us an ageing report by claim status for last month. We will separate the pends from the denials, tell you what is close to timely filing, and show you which of the two is actually costing you money.
Request a free A/R reviewFiling limits, pend handling and remittance codes vary by payer, plan and state. The arithmetic above is illustrative, substitute your own submission volume, pend rate and resolution days before drawing conclusions from it.
