A high number of touches can coexist with poor outcomes. Progress means the account moved closer to a clear financial disposition: information was obtained, a correction was accepted, an appeal was filed, payment was posted, responsibility was transferred appropriately or the account was otherwise resolved.
Why this question matters
A high number of touches can coexist with poor outcomes. Progress means the account moved closer to a clear financial disposition: information was obtained, a correction was accepted, an appeal was filed, payment was posted, responsibility was transferred appropriately or the account was otherwise resolved.
A/R analysis should explain why balances remain open, not merely how long they have been open. The best investigation connects age, status, payer behavior, operational history, financial value, deadlines and ownership.
A queue is more than a list
A work queue becomes accountable when each item has a clear reason for being there, a current owner, a required action, a due date, a history of meaningful activity and a defined path to closure. Without those controls, the queue may record work without controlling the outcome.
Minimum work-item structure
- Unique record or task identity.
- Business reason or issue type.
- Financial value where relevant.
- Current status.
- Assigned owner and team.
- Next required action.
- Due date or service level.
- Priority and the reason for it.
- Action history.
- Supporting documents or evidence.
- Escalation state.
- Closure reason and closure evidence.
Activity is not the same as progress
Notes such as “called payer” or “followed up” show activity, but they do not necessarily change the account state. Better records capture the outcome of the contact, what is now known, what must happen next and when the next action is due.
Escalation should be deliberate
- Escalate when a deadline is approaching.
- Escalate after repeated unsuccessful actions.
- Escalate unusually high-value or high-risk items.
- Escalate systemic payer or process issues to the team able to resolve the root cause.
- Record why the escalation occurred and who owns the escalated action.
Closure requires a disposition
An item should not close simply because a user stopped working it. Closure should state what happened: paid, adjusted, appealed and resolved, transferred, written off under approved policy, duplicate, not recoverable, corrected in source, or another controlled disposition. The closure evidence should match the reason.
A practical investigation sequence
- 01
Confirm the balance and source transactions.
- 02
Identify age, payer, facility, status, value and last meaningful activity.
- 03
Determine the reason the account remains open.
- 04
Check deadlines, escalation conditions and recoverability risk.
- 05
Assign a specific next action and due date.
- 06
Close only when the residual financial position is explained.
Questions to ask next
- What is causing the balance to remain open?
- What was the last meaningful action?
- Which deadline or recoverability risk is approaching?
- Is the delay internal, external or mixed?
- Who owns the next action and due date?
A practical example
For example, A/R over 90 days may rise by $900,000 in one quarter. The useful next step is not to label the entire increase “payer delay.” A closer review may show that most of the change sits with one payer, two facilities and a backlog of appeals that have had no meaningful action for 18 days.
Key takeaways
What to remember
- Age is a prioritization signal, not a diagnosis.
- Old A/R should be decomposed by cause, payer, facility, status, value and last meaningful action.
- Every material unresolved balance should have a current owner, next action, due date and explainable closure path.
Revenue-cycle conclusions should be tested against the organization’s actual contracts, payer rules, source data, workflows and financial records. The objective is to investigate consistently and preserve the evidence behind the conclusion.