AR Follow-Up Support for Medical Billing

The ageing report nobody has time to work

The pattern is familiar. Current charges are going out, payments are posting and patient calls keep arriving. Meanwhile, accounts receivable over 90 days grows quietly each month. Staff pull a few large balances, call for status and add a note. Then somebody discovers a group of claims whose filing or appeal opportunity has expired.

That is not merely delayed cash. If no valid correction, reconsideration or appeal path remains, it may be permanently lost revenue. The loss began earlier than the write-off: when the team did not surface the deadline, obtain the missing evidence or assign a next action while the claim was still recoverable.

A raw ageing report hides those decisions. It groups dollars by elapsed time but does not show why the payer has not paid, what evidence exists, what deadline remains or how many minutes the next useful action will take. A 120-day claim with a documented appeal route may deserve attention before a 35-day clean claim that is still inside normal adjudication. An old balance with no contractual path may deserve a documented close instead of a sixth status call.

Work by recoverability, not by age

Start by stratifying the ageing file. At minimum, segment by payer, denial or non-payment reason, dollar band, service date, claim status, last meaningful action and days remaining before the relevant filing, reconsideration or appeal deadline. Add responsible owner and missing evidence. Do not publish one universal deadline in the worklist; verify the current payer-specific rule and record its source and effective date.

Then rank the intersection, not a single column. A useful prioritisation model considers:

• Recoverability: Is there a valid correction, documentation, reconsideration or appeal path?
• Deadline pressure: How much verified time remains to preserve that path?
• Expected value: What is the allowed amount or realistic collectible balance, not merely the charge?
• Evidence readiness: Is the required eligibility record, authorisation, referral, coding review or clinical documentation available?
• Effort: Can the next action be completed now, or will it require several internal handoffs?

The goal is expected recovery per unit of effort, adjusted for deadline risk. This is a management model, not a prediction that a claim will pay. A supervisor should review the rules, exceptions and closed balances rather than allowing a spreadsheet score to make final determinations.

The claims worth deprioritising

Some balances cost more to pursue than they are likely to return. That conclusion should be governed, not reached through neglect. Define a threshold using expected allowed amount, contractual and legal obligations, patient-impact considerations, reason, remaining rights and estimated work. Require approval for categories that may involve a systemic defect, even when individual balances are small.

Keep the distinction between “low priority” and “closed.” Low priority means the claim still has a documented next-review date. Closed means an authorised disposition, reason and supporting record. This prevents small recurring denials from disappearing when, in aggregate, they reveal a front-end problem.

Denials by reason category, and what each one needs

Reason codes begin the investigation; they do not always explain the operational cause. Read the electronic remittance advice, payer message and claim history together. Map payer wording into controlled internal categories without erasing the original code or text.

Eligibility and coverage

Confirm the member, service date, plan, coverage status and submitted identifiers against contemporaneous evidence. The front desk or eligibility team may need to supply the verification record. For a focused upstream method, see insurance verification support.

Authorisation and referral

Locate the authorisation or referral, covered dates, service scope and reference details. Compare them with the billed service and payer response. Route clinical questions and exceptions to authorised practice personnel; do not have a follow-up specialist invent or alter clinical support.

Coding and medical necessity

Preserve the denial detail and assemble the requested documentation, but send coding and clinical determinations to qualified internal or contracted professionals. The AR team controls the case and deadline; it does not exceed its competence.

Timely filing

Verify the current limit and any exception or proof-of-submission route in the applicable payer source. Locate clearinghouse acceptance, prior claim identifiers and correspondence. Never assume that another payer’s window or last year’s rule applies.

Coordination of benefits

Identify the coverage-order issue and the party permitted to correct it. Record what the payer needs, communicate within authorised boundaries and keep the claim active until a documented outcome replaces “patient to update.”

Duplicate, bundling or claim edits

Compare the submitted claim, adjustments, related services and remittance. Determine whether the next step is a corrected claim, an appeal, internal review or no further action. Do not resubmit blindly; that can create another duplicate response without resolving the cause.

This post owns post-submission recovery. For the broader operating system, read how the healthcare revenue cycle works. For charge and claim accuracy, see accurate medical billing.

The follow-up sequence that gets a claim to a decision

A productive touch changes the state of the claim. Before calling, review the remittance, payer portal, clearinghouse response, previous notes and relevant manual. Form a specific question: whether the claim is on file, which edit is unresolved, what exact document is missing, which review path applies or when the next decision is due.

1. Validate the record. Confirm patient, payer, service date, claim identifier and status using authorised systems.
2. Identify the blocking reason. Capture the payer’s wording and translate it into the controlled work category without overwriting source detail.
3. Choose one next action. Correct, submit evidence, request reconsideration, initiate the verified appeal route, wait until a justified follow-up date or close with approval.
4. Document evidence. Record portal result or call date, channel, representative and reference number when provided, documents discussed, stated outcome and source location.
5. Set ownership and time. Assign the named person or queue, due date and escalation trigger. A claim without a next-action date is not under control.
6. Resolve deliberately. Close only with payment, adjustment, transfer to another authorised workflow or approved final disposition.

“Called payer, pending” is a wasted note because it tells the next specialist almost nothing. Pending until when? For what decision? Which evidence was acknowledged? What will happen if no response arrives? Good notes reduce duplicate work and allow quality review.

Build a payer playbook that is maintained, not remembered

The payer playbook is the operational asset that shortens research and preserves knowledge. Maintain a controlled entry for portal capabilities, authentication and access owner, contact routes, correction process, reconsideration versus formal appeal, submission location and format, documentation expectations, escalation path and known response patterns.

For every time-sensitive rule, store the official provider-manual or contract reference, effective date, date checked and reviewer. Set a refresh cadence and an immediate-review trigger when a payer notice or portal change appears. Old screenshots and copied deadlines are clues, not authority.

Add practice-specific learning: which internal team owns a missing referral, where proof of timely submission is stored and who approves a coding review. Restrict the playbook to process facts; do not turn anecdote about a representative into a policy. Supervisors should sample claims against the current source to detect drift.

Where the AR problem actually starts

A follow-up team treats symptoms if the front end keeps generating avoidable denials. Feed recurring root causes back to eligibility, registration, authorisation, charge entry, coding review and claim submission. Report causes in operational terms: missing subscriber detail, inactive coverage not escalated, authorisation mismatch, incomplete demographic field, charge held past a control date or claim rejected before payer acceptance.

Assign each recurring cause an owner, corrective action and review date. Measure whether new incidence declines while the AR team works the existing inventory. Our guides to prior authorisation support and insurance verification for healthcare address two upstream controls without turning this article into a full revenue-cycle overview.

Staffing and supervision for follow-up work

Assigning by payer or coherent payer group lets specialists learn portals, terminology and escalation routes. Cross-train for coverage so knowledge does not become a single-person dependency. Large or complex inventories may also need category specialists, but every handoff should preserve one accountable claim owner.

Do not manage solely to a call target. Count documented outcomes: corrected and accepted claim, evidence submitted through the verified route, appeal initiated, payment located and reconciled, justified next action, or approved closure. Review touches per resolved claim alongside quality, because high activity with repeated vague notes is not productivity.

Sample notes and source evidence. Check that the action matched the denial, deadlines came from current materials, patient information was handled appropriately and promised follow-up occurred. Expect training time for systems, payer mix, policies and escalation. A specialist can learn the mechanics quickly while still needing supervised exposure before independent judgement is reliable. A remote medical billing assistant may fit a supervised role; a managed AR service carries a different scope and accountability.

Security, access and the compliance baseline

Outsourcing is not inherently incompatible with HIPAA, but the relationship and controls must match the work. HHS explains that covered entities may disclose protected health information to a business associate when they obtain satisfactory assurances through a business associate agreement. Its current business-associate guidance describes required limits and safeguards; the exact arrangement should be reviewed by qualified counsel and privacy or security personnel.

For electronic protected health information, HHS’s current Security Rule summary describes administrative, physical and technical safeguards, including appropriate role-based authorisation, workstation controls, access control, authentication, audit controls and transmission security. It also notes that the page summarises the rule currently in effect while proposed modifications are tracked separately.

Translate that baseline into the workflow: named accounts rather than shared credentials; access aligned to assigned duties; approved devices and workspace rules; controlled exports and printing; logging and review; security-incident reporting; termination and access-removal steps; and subcontractor governance where applicable. Follow the covered entity’s minimum-necessary policies and confirm which systems, fields and records each role genuinely needs. A BAA is not a substitute for operational controls.

The metrics that show whether recovery is real

Cash collected matters, but it can rise while old receivables deteriorate or while a strong current month masks a neglected backlog. Review a balanced set using consistently defined numerators, denominators, time periods and exclusions:

• Days in AR: document the organisation’s calculation and trend it consistently.
• AR over 90 and 120 days: show both dollars and percentage of total receivables, segmented by payer and reason.
• First-submission denial rate: separate denials from front-end rejections and define the claim unit.
• Appeal overturn rate: use only cases that reached a decision, while also reporting open and withdrawn cases.
• Net collection rate: document adjustments and calculation rules so teams are comparing like with like.
• Touches per resolved claim: pair efficiency with note quality and outcome; fewer touches are not better if cases are closed incorrectly.

Do not import a generic benchmark without a named, current and comparable source. The practice’s payer mix, speciality, contract terms, balance distribution and calculation method can make headline comparisons misleading. Baseline the same definitions before and after a process change and explain other factors that could affect the result.