What Is A/R Follow-Up, and How Often Should a Claim Be Touched?

A/R follow-up is the process of moving unpaid claims toward payment or another final resolution. The appropriate timing for each follow-up depends on the claim’s status, the payer’s processing timeline, the balance involved, and any filing or appeal deadlines—not on a universal 7-, 14-, or 30-day schedule.

A rejected claim may need attention today. A claim that is accepted and still within the payer’s normal processing window may not.

The goal is not to touch every claim on a fixed schedule. It is to identify which claim needs action next.

What exactly is A/R follow-up?

Accounts receivable follow-up begins after a claim has been submitted but remains unresolved. The billing team tracks its status, determines what is preventing payment, and takes the appropriate next step.

That may mean correcting a rejection, supplying requested information, working a denial, escalating a stalled claim, pursuing an underpayment, or following up on secondary coverage.

Status checks are part of that process, but they do not always require manual work. CMS recommends the electronic 276/277 claim-status process because providers can automatically generate 276 status requests and receive 277 responses, reducing individual data entry and calls to Medicare contractors. CMS also notes that systems can automatically post 277 responses to patient accounts when they support it.

That distinction matters when deciding how often staff should actually touch an account.

How often should an A/R claim be touched?

There’s no single follow-up interval that fits every unpaid claim. Instead, set the next follow-up date based on the claim’s current status and the next action it needs.

A/R touch triggers
Claim statusWhen to follow upNext action
Accepted and processingAt the next meaningful payer status pointMonitor status
DeniedOnce the denial is identifiedDetermine cause and correct or appeal
High-balance claim stalledWhen expected processing time has passedEscalate with payer
Records requestedBefore the payer’s response deadlineSubmit records and confirm receipt
RejectedAs soon as identifiedCorrect and resubmit
Secondary or tertiary claimAfter prior payer adjudicationConfirm crossover or submit
Timely filing or appeal deadline approachingBefore rights are at riskEscalate immediately
UnderpaidAfter expected payment is reconciledValidate and pursue the variance

Two claims can be the same age and require completely different treatment

Consider two $2,000 claims that are both 21 days old. One has been accepted and is moving through adjudication. The other was rejected because subscriber information did not match. Following up on both simply because they reached day 21 creates unnecessary work on the first while delaying action on the second.

Why shouldn’t every claim follow the same schedule?

Electronic claim-status tools make routine manual checking less necessary.

The 276 transaction is an electronic request for claim status, while the 277 is the health plan’s response. CMS identifies ASC X12N 276/277 Version 5010 as the adopted standard for claim-status transactions. Federal operating rules also require applicable health plans to provide real-time online access to claims-status information.

For Medicare specifically, CMS says providers can use the 276/277 process to check individual claims or batches. Its guidance notes that a 277 response may take up to 24 hours.

If a system can obtain routine status information electronically, staff do not need to open every account simply to find out whether anything has changed.

Reserve manual follow-up for claims that require a decision or action.

When should claim age affect A/R follow-up?

Age matters most when delays put reimbursement at risk.

For Medicare Fee-for-Service, claims generally must be filed within 12 months, or one calendar year, after the date of service. CMS notes that claims filed outside the timely filing period are denied unless an applicable exception applies.

Commercial payer, Medicaid, corrected-claim, reconsideration, and appeal deadlines vary. A/R worklists therefore need payer-specific deadlines rather than relying on aging buckets alone.

A useful priority order is:

  1. Deadline risk: Is a filing or appeal deadline approaching?
  2. Financial value: How much collectible revenue is at stake?
  3. Claim status: Is the claim rejected, denied, underpaid, stalled, or still processing?
  4. Age: How long has the balance remained unresolved?

A 60-day claim is not automatically more urgent than a 30-day claim. The younger claim may carry a larger balance and an appeal deadline next week.

What counts as an A/R touch?

A meaningful touch should move the claim forward or establish a specific next action.

Opening an account, finding the same status, adding “follow up in 14 days,” and closing it creates activity. It does not necessarily create progress.

A productive touch might:

  • Correct and resubmit a rejected claim
  • Escalate a stalled high-balance claim
  • Identify and pursue an underpayment
  • Submit requested documentation
  • Work or escalate a denial
  • Confirm secondary or tertiary billing
  • Document a payer commitment and next-action date

This distinction also matters when evaluating collector productivity. Raw touch counts can reward repeated handling of the same unresolved accounts.

Track movement instead: dollars recovered, high-value balances resolved, filing losses prevented, underpayments collected, and claims moved out of older A/R.

What can unresolved A/R tell you about the revenue cycle?

A/R follow-up should identify more than which claims remain unpaid. It should show why they reached A/R in the first place.

Repeated eligibility problems may point to front-end verification. Authorization-related balances may indicate a workflow gap before service. Recurring coding-related denials may require documentation or coding review. A pattern of stalled claims with one payer may call for a payer-specific escalation process.

Segment unresolved A/R by:

  • Age
  • Balance
  • Claim type
  • Denial or rejection reason
  • Payer and plan
  • Provider
  • Specialty

The purpose is to separate isolated accounts from repeatable revenue-cycle problems.

How do you know whether A/R follow-up is working?

A/R performance should improve when claims move toward resolution with fewer unnecessary touches.

Look beyond the number of accounts worked. Monitor movement between aging buckets, resolution of high-balance claims, denial and underpayment recovery, timely-filing losses, recurring payer issues, and unresolved accounts without a defined next action.

The strongest worklist is not necessarily the one with the most touches. It is the one that consistently puts staff on claims where intervention can change the outcome.

A/R follow-up should create movement, not touches

There is no reason to manually touch every unpaid claim every 7, 14, or 30 days.

Set the next action according to claim status, payer processing time, financial value, and deadline risk. Automate routine status monitoring where payer infrastructure allows it, and direct staff attention toward exceptions that require intervention.

Integrity One Group includes accounts receivable follow-up within its revenue cycle management services, with A/R aging analysis, worklists prioritized by value and timeliness, high-balance resolution, payer escalation, underpayment recovery, secondary and tertiary follow-up, and timely-filing deadline monitoring.

The question for an A/R team should not be, “When did we last touch this claim?”

It should be, “What needs to happen next to get it resolved?”

About the author

FAQs
What is A/R follow-up in medical billing?
assurix-blue-arrow

A/R follow-up is the process of monitoring unpaid claims, determining what is delaying payment, and taking the next action required to resolve the balance.

How often should an unpaid claim be followed up?
assurix-blue-arrow

There is no universal follow-up interval. Timing should depend on claim status, payer processing time, financial value, and filing or appeal deadlines. Claims progressing normally may be monitored electronically while staff focus on exceptions.

What is a 276/277 claim-status transaction?
assurix-blue-arrow

A 276 is an electronic claim-status request, and a 277 is the response. CMS recommends the electronic process because status inquiries and responses can be automated, reducing manual queries.

Should A/R teams work the oldest claims first?
assurix-blue-arrow

Not automatically. Age is one priority factor. Deadline risk, balance, and claim status should also determine which account is worked first.

How long do you have to file a Medicare claim?
assurix-blue-arrow

Medicare Fee-for-Service claims generally must be filed within 12 months, or one calendar year, after the date of service, subject to limited exceptions.