How to Work an Insurance A/R Aging Report

An insurance accounts-receivable aging report is not just a list of old balances. Used well, it is a work queue that tells the billing team which claim needs attention, why it is unpaid, who owns the next step, and which deadline creates the most risk. The goal is to move each balance toward payment, correction, appeal, contractual adjustment, patient responsibility, or documented closure.

Start with a reliable report

Run the report by insurance balance and age from the appropriate starting point, such as date of service or claim submission. State which aging basis the report uses. Include payer, plan, patient account, claim number, dates of service, billed and outstanding amount, last submission date, last payer response, current status, assigned owner, next action, and filing or appeal deadline when known.

Reconcile totals with the practice-management system or general reporting source. Remove or separately flag credit balances, unapplied cash, patient balances, and accounts already resolved but not closed. Otherwise, the queue can overstate collectible insurance A/R.

Do not work strictly from oldest to newest

Age matters, but deadline and collectibility matter more. A useful priority order is:

Claims approaching a filing, reconsideration, appeal, or documentation deadline
High-value claims with no confirmed payer receipt or status
Denied or underpaid claims with a supported next action
Claims stalled for information from the patient, clinician, or payer
Lower-value routine follow-up that can be handled efficiently in batches

For Original Medicare, claims generally must reach the correct Medicare Administrative Contractor no later than one calendar year after the date of service, with limited exceptions. Other payers and contracts use different deadlines. Store the actual source and deadline rather than applying Medicare’s rule to every account.

Segment the report into actionable queues

No claim on file or no acceptance. Confirm submission, acknowledgment, payer routing, and identifiers.
Pending adjudication. Check the payer’s normal processing timeframe and claim status.
Rejected or returned. Correct the front-end issue and resubmit through the proper process.
Denied. Read the remittance and payer notice, then determine correction, appeal, or other resolution.
Underpaid. Compare the allowed amount and payment with the contract and claim details.
Patient or clinical information needed. Assign the outreach and deadline.
Secondary payer pending. Confirm primary adjudication and crossover or secondary submission status.
Credit or posting issue. Route to payment-posting or credit-balance review.

Use electronic claim status where available

CMS explains that Medicare providers can obtain status through a contractor portal, interactive voice response, direct data entry, or the electronic 276 request and 277 response. CMS recommends the electronic process where supported because it can reduce manual queries and allow status information to post back to accounts. Similar HIPAA claim-status transactions apply more broadly to covered entities.

A status such as pending is not a completed follow-up note. Record the date, source, payer status, reason, expected next event, and scheduled follow-up date.

Read the remittance before contacting the payer

For Medicare, the electronic or standard paper remittance reports claim or line adjudication details and uses group codes, Claim Adjustment Reason Codes, and Remittance Advice Remark Codes to explain adjustments. Use the complete code combination and payer-specific notice rather than relying on a short description stored in the billing system.

Document one clear next action

Every worked account should end with an owner, action, and date. Examples include submit corrected claim by a specific date, obtain records from a named team, file appeal through the payer portal, confirm secondary receipt, or recheck payer status after the stated processing interval. Avoid notes such as “called payer” that do not explain the outcome.

Escalate patterns, not only individual claims

When the same payer, service, provider, or denial reason appears repeatedly, quantify it and move the issue to a root-cause review. A configuration problem, enrollment gap, missing authorization handoff, or coding error will continue to refill the aging report until the upstream process changes.

Measure the queue

Review total insurance A/R, aging distribution, days since last action, balances approaching deadlines, denial and underpayment inventory, dollars resolved, and accounts without an owner. Pair dollars with claim counts so that one large account does not hide a widespread operational problem.

FlowClaim supports practices with insurance A/R follow-up, old A/R recovery, and payment posting. Request a free billing audit to identify stalled balances and repeat workflow failures.

Frequently asked questions

Should the oldest claim always be worked first?

Age matters, but a newer claim near a deadline may need earlier action. Combine age with the actual deadline, status, financial impact, and supported recovery opportunity.

What makes an A/R note useful?

Record the evidence reviewed, current status, action taken, next action, responsible person, and next review date. Another biller should be able to continue without repeating the investigation.

When is a balance resolved?

Use a documented outcome, such as correct payment or an approved adjustment, rather than treating a phone call or resubmission as resolution.

Sources

Editorial note: Filing, correction, appeal, and payer-response deadlines vary. Confirm the current payer rule and provider contract for each claim.

← Back to all articles