Rank unpaid claim work by due-date risk, claim status, balance, and next step. Age alone is not enough. Balance alone is not enough. The best queue shows why an item needs work now.
Accounts receivable, or AR, means money still open on an account. An AR queue does not predict payment. It helps staff choose a safe work order. The order should change when new facts arrive.
Why are claim age and balance not enough?
They do not show if a due date is near. They also do not show if the claim can move today. A large old claim may be in a valid payer review. A small new claim may face a near filing limit.
Age can hide the claim's true stage. A payer may have received one claim. Another claim may have failed before receipt. Both can look open in the local system.
The dental AR guide explains the full work cycle. A rank method adds order to that cycle. It does not replace a claim review.
Do not send a repeat claim just because it is old. Check the claim status first. A repeat may make the trail harder to read.
What facts belong in the AR queue?
Keep the due-date source, claim status, balance, and next step. Also keep proof of claim receipt. Name the person who owns the work.
CMS lists more than one way to check claim status. These can include set data tools, a portal, and a phone call. See the CMS claim status page.
A claim status is only one fact. It does not prove coverage or payment. It does not prove authorization or network terms. It also does not set the patient balance.
Each queue row should show:
- The patient and claim reference.
- The payer and plan.
- The first send and receipt proof.
- The latest checked status and its date.
- The due-date source and start event.
- The open balance.
- The last step taken.
- The next step and owner.
- Any fact that is still unknown.
Do not write only “pending.” State where that status came from. Add the date and payer reference when one exists.
How should due-date risk change the order?
Move a claim up when a checked due date is near. This applies when a valid next step can still be taken. Use the real source for that due date.
The source may be a payer rule or plan term. It may be a contract, program guide, or written notice. Do not use one set time for all payers.
The type of task also matters. A first claim may have one limit. A fixed claim or appeal may have another. A reply to a record request may follow its notice.
Write down the date source and start event. Note who checked the math. If the rule is not clear, make that gap a top task.
The timely filing guide shows why claim facts matter. It does not give one due date for all claims.
How should staff weigh status, balance, and next steps?
Use repeatable priority bands instead of one score. Apply the bands in order. Then use the practice's written tie-break rule within each band.
| Band | Put these claims here | Tie-break inside the band |
|---|---|---|
| A. Due-date risk | A checked limit is near and a valid step remains. | Work the earliest verified limit first. |
| B. Actionable exception | The claim was rejected, lacks receipt, or needs a supported reply. | Work the clearest valid next step first. |
| C. Balance | Risk and action are alike, but balances differ. | Apply the written balance rule. |
| D. Repeat-pattern risk | The same fault may affect more claims. | Start with the issue that has the widest checked spread. |
| E. Monitored wait | A recent source shows a payer or outside step is pending. | Review at the next source-based event. |
Unknown due-date facts go to a fact-check queue. Do not place them in a low band. A small claim can lead when its verified deadline is near. A large waiting claim should remain visible in Band E.
Do not turn these bands into a recovery promise. They only guide staff time. Review the order when new evidence arrives.
How should owners and repeat work be tracked?
Give each claim one owner and one clear next step. The next check should link to a real event. It should not come from a made-up wait time.
A next step may be simple. Staff may need to check receipt. They may need to find a remit. They may fix a true data error. They may ask the payer for a written reply.
Clinical questions go to the treating provider. Billing staff must not change care facts. They must not add a new reason for care.
Track why each claim was touched. A note that says only “followed up” is weak. A good note shows the source, result, and next step.
Repeat work may show a larger flaw. It may start in intake, benefits, records, claim send, or payment posts. Send that pattern to the right work owner.
What does a hypothetical rank choice look like?
Hypothetical scenario: Two open claims compete for staff time. One is old and has a large balance. Its payer gave a recent valid pending status. The other is new and has a lower balance. It lacks claim receipt near a checked filing limit.
The team works the new claim first. It checks the send trail and finds a rejection. Staff fix only the true data error. They then save the new receipt.
The old claim stays in the queue. It has an owner and a review point. That point comes from the latest payer facts.
This case does not promise payment for either claim. It shows why risk and next steps can beat age alone.
Frequently asked questions
These answers show how to use the queue.
Should the largest balance always come first?
No. Balance matters, but so do due dates and status. A small claim may need faster action. Use a written policy for the choice.
Can a pending claim leave the queue?
Not for good. Keep the source and date of the status. Set a review point from real payer facts. Pending is not a payment result.
This guide is general administrative information, not legal, medical, clinical, dental, coding, documentation, privacy, security, contract, accounting, financial, patient-billing, or coverage advice, and not a statement that any workflow, record, request, response, claim, payment, adjustment, deadline, decision, or outcome is accurate, complete, compliant, authorized, covered, or payable. Requirements and outcomes vary by payer, program, plan, patient, provider, service, record, agreement, system, jurisdiction, and date.
