AR Optimization Services

What AR Optimization Covers

AR optimization is broader than day-to-day follow-up. It means restructuring how balances are prioritized, aged, escalated and written off — so days in AR trends down permanently, not just for one collections push.

• Aging-bucket triage — balances prioritized by dollar value and age, not worked in submission order
• Underpayment identification — contracted-rate variance flagged automatically, not caught by accident
• Payer-specific follow-up cadence — timelines matched to each payer’s actual response patterns
• Timely-filing protection — claims tracked against filing deadlines before they become unrecoverable
• Write-off governance — every adjustment reviewed and approved, so collectible balances aren’t written off in error

Insurance AR and Patient AR

Insurance and patient balances age differently and need different playbooks. Our Insurance AR Follow-up team pursues payer balances with systematic escalation; our Patient AR & Collections team handles patient-responsibility balances with a process built for patient retention, not just recovery.

Where AR Optimization Fits

AR reduction is one output of our broader Revenue Cycle Optimization work, alongside denial prevention and clean-claim improvement. Most practices start with a free RCM Audit to see exactly which aging buckets and payers are driving the problem before committing to an optimization engagement.

Aging Buckets and What Each One Means

AR aging reports group open insurance balances by how long they have been outstanding, usually from the date of service or, more usefully for follow-up, from the claim submission date. The bucket tells the analyst what the likely problem is and what action is due.

Because insurance payment usually arrives well before the patient portion is billed, the aging report should be split into insurance and patient responsibility so that a secondary payer or a patient statement does not hide a claim that still needs payer follow-up. Bucket percentages and days in AR are meaningful only when the report is calculated the same way every month.

Prioritization Logic: Which Claims Get Worked First

Working oldest-first sounds fair, but it wastes effort on small balances while valuable claims run out of time. A priority model scores each open claim and sorts the work queue accordingly:

1. Deadline riskDays remaining until the payer's timely filing, corrected claim or appeal limit are computed for every account. Anything within a defined window moves to the top regardless of balance.
2. Dollar valueWithin the same risk tier, higher expected collectible balances are worked first. Expected value is billed amount adjusted for the likely contracted rate, not the gross charge.
3. Payer behaviorPayers with slow processing, a history of pended claims or recurring underpayments get earlier touches. Payers that reliably pay in a known window are checked only after that window.
4. Status and last actionAccounts with a promised payment date are held until that date; accounts with no touch since the last follow-up interval re-enter the queue automatically.
5. Low-value handlingVery small balances are batch-worked by payer through portal tools or bulk status requests rather than individual calls.

Claim Status: 276/277, Portals and Phone Calls

The 276 is the HIPAA claim status request and the 277 is the response. Used in bulk, they replace many calls. The 277 returns a status category code and status code that indicate whether a claim is acknowledged (category A), pending (P), finalized (F), in need of additional information (R) or in error (E), and the status codes explain why. Not all payers return the same level of detail, so portals and phone calls remain part of the toolbox:

• Batch 276/277: best for claims past the payer's usual processing time and for confirming receipt. A finalized-with-denial response is routed to the denial queue.
• Payer portal: used when the 277 is limited. Screens often show the remittance, the denial reason or a pending letter that a 277 does not.
• Phone: reserved for claims where electronic status is vague, for pended claims, or for escalations. The analyst has the claim number, billed amount, date of service, NPI and tax ID ready.

Common Stall Reasons and the Action for Each

• No record of the claim: check the 277CA or clearinghouse acceptance report, then resubmit within the filing limit and keep proof.
• Pended for medical records: send records the same day using the method the payer specifies and note the control or attachment number.
• Pended for COB or eligibility: confirm active coverage and other insurance with the patient, update the account and let the payer know.
• Processed but not paid: check whether payment went to the patient, to a different address or tax ID, or to a virtual card not yet matched.
• Paid at the wrong rate: route to underpayment dispute with the contract rate calculation.
• Denied: move to the denial workflow with the CARC/RARC, rather than repeating status checks.

Payer Escalation Ladder

When the standard channel stalls, escalation follows a defined path and records every step so the history is usable.

1. Second call or portal messageA different representative or the payer's claims-research channel is tried with the previous reference number cited.
2. Supervisor or claims-research teamRequest a supervisor with the facts, the dates, the previous call numbers and the specific action required.
3. Provider relations or network managementFor contracted payers, a provider relations representative can often open a project ticket, correct systemic issues such as misloaded fee schedules and speed reprocessing of batches of claims.
4. Formal written disputeA written reconsideration or contractual dispute is filed with documentation. Contract dispute clauses may include arbitration.
5. Prompt-pay interest and regulatory complaintMany states have prompt-pay laws that require payers to pay clean claims within a set number of days or pay interest. Where payers continue to fail to meet these obligations, a complaint to the state department of insurance (for fully insured plans) or other applicable regulator is an option. Self-funded plans are generally governed by federal law instead, so the right route depends on plan type.

Timely Filing Risk

Timely filing limits are set by the payer and the contract, not by a universal rule, and several clocks can apply to one claim. Commonly seen limits include:

The practical defense is evidence. Clearinghouse acceptance reports, payer acknowledgments (277CA), portal confirmations and call reference numbers are filed at the claim level so that a timely filing denial (CO-29) can be overturned when the original claim was received in time. A timely filing tracker also shows which payers have the shortest limits and which accounts are inside a 30-day warning window.

Secondary Billing and Coordination of Benefits

Secondary follow-up is its own queue because the claim cannot move until the primary has adjudicated. After the primary 835 posts, the secondary claim is built with the primary's payments and adjustments reported in the claim (CAS and AMT segments on the 837), or generated through payer crossover where available. Typical checks are:

• Confirm the correct primary and secondary order using the COB rules and the payer's own records (birthday rule for dependent children, active coverage for Medicare Secondary Payer situations, and similar).
• Attach the primary EOB when the secondary payer requires paper or image documentation.
• Watch the secondary filing limit from the primary remittance date.
• Bill the patient only the amount left after both payers have processed.
• Where a crossover did not occur after the expected window, submit the secondary claim directly rather than waiting.