General operational information only. Payer, state, contractual and regulatory requirements vary. Confirm current requirements with the applicable payer or agency.
Quick answer
What practice leaders need to know
An aging report should drive action, not simply display balances. Segment insurance A/R by payer, age, amount, claim state, filing or appeal deadline, root cause and next action. Prioritize recoverable balances with approaching deadlines or repeated payer failures.
Turn the aging report into an operating inventory
An aging report groups unresolved balances by time, but age alone does not explain the claim's current state, deadline or probability of recovery. Establish a consistent aging basis—such as date of service or claim submission—and document it so reports can be compared. Reconcile encounters, charges, claim acknowledgements, remittances and deposits to identify items that never entered the expected workflow. Each insurance balance should be connected to a payer, provider, service, location, financial amount, current claim state and next action. The report becomes useful when it directs work and supports accountability, not when it merely proves that old balances exist.
Identify the current claim state
Classify accounts as unsubmitted, rejected, accepted and pending, denied, underpaid, awaiting documentation, affected by enrollment, waiting on coordination of benefits, no response or another controlled status. Use electronic acknowledgements, payer portals, remittances, correspondence and documented calls as evidence. Do not label every unpaid claim denied or pending. The state determines whether staff should submit, correct, appeal, provide information, contact the patient, escalate enrollment or monitor normal processing. Require a last-verified date because an accurate status from six weeks ago may no longer support today's work decision.
Protect filing and appeal deadlines first
Create urgent queues for claims approaching payer submission, corrected-claim, reconsideration or appeal limits. Calculate deadlines from the authoritative payer rule and the event that starts the period, and retain the source and date reviewed. Contract terms, government program rules and payer policies vary, so avoid one universal threshold. Escalate missing documentation or enrollment dependencies early enough for the responsible team to act. If a deadline has passed, determine whether an exception or available recovery route applies before closing the account. Record avoidable deadline losses separately so leadership can correct the process that created them.
Combine value with recoverability
High-dollar balances deserve visibility, but the largest account is not always the most recoverable. Consider documentation availability, payer status, deadline, contract terms, root cause and the effort required. Create thresholds that trigger senior review while preserving work on smaller, repeatable claims that collectively represent material revenue. Group claims affected by the same configuration or payer behavior so one escalation can address the full exposure. Use expected allowed amounts rather than gross charges when feasible and consistently defined, because charge amounts can distort the true financial opportunity.
Create purpose-built work queues
Separate normal payer processing from exceptions that require action. Useful queues may include no acknowledgement, clearinghouse rejection, payer no-response, additional information request, authorization denial, enrollment or affiliation issue, coding review, underpayment, coordination of benefits, credit balance and appeal follow-up. Define entry and exit criteria, assigned role, service standard and escalation route for each queue. Avoid allowing staff to place difficult accounts into a generic research status with no due date. Queue design should mirror the actual claim lifecycle and make the next action obvious to a trained user.
Distinguish rejections, denials and underpayments
A rejection occurs before adjudication when the transaction or claim is not accepted, while a denial or adjustment appears after payer processing. An underpayment requires comparison with the applicable allowed amount or contract expectation. CMS remittance guidance and CARC/RARC information help interpret Medicare and standardized remittance details, but staff must still apply the correct payer rules and contract. Keeping these states separate improves routing and reporting. A rejected claim may need corrected identifiers; a denied claim may require documentation or appeal; an underpayment may need contract analysis. Combining them into unpaid A/R hides the appropriate recovery path.
Use a standard account work note
Every note should identify the evidence reviewed, action taken, result, next action, owner and follow-up date. Include payer reference information when available without copying unnecessary sensitive data. A note that says called payer or checked portal does not show whether the claim moved. Use controlled status values for reporting and a concise narrative for facts that do not fit the status. Preserve prior notes rather than overwriting them so another staff member can reconstruct the recovery history. Standard notes reduce duplicate calls, improve escalations and support quality review.
Escalate repeated payer and configuration patterns
When multiple claims share a payer response, provider mismatch, missing affiliation, claim edit or remittance problem, identify the full affected population. Resolve individual deadlines while opening a system-level issue with an accountable owner. Provide submission evidence, claim examples, provider and group identifiers, payer references and the requested correction. Track the exposure and validate the payer or configuration change before closing the issue. Repeated one-by-one follow-up consumes staff time and may allow new claims to enter the same failure. Pattern work is both recovery and prevention.
Manage payer no-response claims deliberately
A claim that remains pending beyond the payer's expected processing window needs verified status. Confirm acceptance, receipt date and payer control number, then ask whether information, recoupment, coordination or another review is holding the claim. Record the representative or portal evidence and the payer's next expected action. Escalate according to the contract, program and available provider-relations path when repeated follow-up produces no movement. Avoid daily calls that add notes without changing the outcome. Set a meaningful follow-up date tied to the payer's response and preserve proof of timely submission.
Measure inventory movement and quality
Track dollars and claim counts entering, resolving and aging within each state. Useful measures include days in A/R, aging distribution, no-response volume, deadline losses, underpayments, denial resolution and accounts without a next action. Define formulas and exclusions and compare trends by payer, provider, location and service. A falling aging balance can reflect collections, write-offs or transfers, so leadership should see the components. Measure whether corrective actions reduce repeated causes and whether staff notes meet the operating standard. Productivity based only on touches can reward activity without resolution.
Run weekly operational and monthly leadership reviews
The weekly review should focus on urgent deadlines, high-value recoverable balances, blocked queues, payer patterns and items without accountable next steps. The monthly review should connect aging movement with collections, adjustments, denials, underpayments and prevention work. Assign decisions and due dates and revisit prior actions. Separate third-party payer delays from internal dependencies so leadership understands what can be controlled. Aging reduction is not achieved through a one-time cleanup; it requires a maintained inventory, reliable work standards and upstream changes that prevent new claims from entering the same backlog.
Reconcile A/R with remittances and deposits
An aging balance can be wrong because a remittance was not received, a payment was not posted, an EFT was unmatched or an adjustment was applied incorrectly. Reconcile payer remittances, bank deposits and posting batches before sending staff to pursue a claim that has already paid. Investigate remittance without funds, funds without remittance, duplicate posting, unapplied cash and provider-level adjustments. Use trace information and preserve the resolution. Accurate A/R recovery depends on an accurate ledger; otherwise work queues waste time and patient balances may be transferred incorrectly.
Segment legacy A/R from current production
When a practice begins a cleanup or changes billing partners, define which organization owns balances before and after the cutover date. Reconcile the inventory, preserve claim notes and deadlines and prevent both teams from working or ignoring the same account. Legacy A/R may need different prioritization because documentation, access or filing options are limited. Report recovered cash, valid closures and unrecoverable causes separately from current-cycle performance. A cleanup can improve the balance temporarily, but leadership should also verify that new claims are not recreating the same backlog.
Use patient contact only after payer responsibility is clear
Before moving an amount to patient responsibility, confirm the payer adjudication, coordination of benefits, contract adjustment and posting. Follow the practice's approved financial policy and applicable notice requirements. Give patients a clear route to question a balance, and route payer disputes back to insurance follow-up instead of repeatedly issuing statements. Track complaints and returned statements because they may reveal upstream posting or eligibility problems. Insurance A/R and patient A/R are connected, but transferring a balance does not resolve an uncertain payer obligation.
Working reference
Insurance A/R prioritization matrix
Use documented criteria to place balances in the right work queue.
| Priority group | Typical signal | Action |
|---|---|---|
| Deadline risk | Filing or appeal limit is approaching | Work or escalate immediately |
| High-value recoverable | Material balance with a clear correction path | Assign focused follow-up |
| Repeated payer pattern | Same unresolved cause across claims | Resolve accounts and address the root cause |
| Normal payer processing | Claim is pending within an expected window | Monitor until the next status date |
| Invalid or nonrecoverable | Documented contractual or exhausted balance | Approve and record valid closure |
Common questions
Questions practice teams ask
Which aging bucket should receive attention first?
The bucket with the greatest deadline and recovery risk, not automatically the oldest one.
When does claim aging begin?
Practices should choose and document a consistent basis, such as date of service or claim submission, so reports can be compared.
Should staff always work the oldest claims first?
No. Include deadlines, value, payer status, cause and recoverability in the priority decision.
What information should every worked account contain?
A current status, evidence, owner, next action and follow-up date.
What should leadership review?
Review aging by payer and claim state, cash movement, deadline losses, repeated causes and accounts without a next action.
Primary references
Sources and further reading
Requirements can change. Use these primary sources to confirm the current rule that applies to the payer, service and date of care.
Ready to turn this guidance into action?
Tell us what is happening in your practice, and we will help you identify the most useful next step.