Your A/R days are creeping up. Here’s where to look first.

A/R days is one of those healthcare metrics everyone knows they should watch every month. But what do you do when it starts moving in the wrong direction?

Is 35 days good? Is 50 concerning? Why did one payer suddenly jump to 70? And if your overall number looks fine, could a problem still be hiding underneath it?

For medical practices, days in accounts receivable can reveal a lot about how efficiently care is turning into collected revenue. The number becomes much more useful once you stop treating it as a score and start treating it as a clue.

First, what are A/R days in healthcare?

A/R days measure roughly how long it takes a practice to collect the money it is owed. In simple terms:

That does not mean every claim takes exactly 50 days to get paid. Some claims may be paid quickly while others sit unresolved for months. The metric gives you a high-level view of how quickly revenue is moving through the practice.

So, what are “good” A/R days?

There is no magic number that applies to every medical practice. Specialty, payer mix, claim complexity, reimbursement structure, and patient responsibility all affect how quickly money comes in. A practice with complicated surgical claims may reasonably look different from one billing mostly straightforward office visits.

As a directional benchmark, many practices aim to keep overall A/R below roughly 30 to 40 days, while 50 or more days warrants a closer look. But even a healthy-looking average can hide a large number of balances sitting in 90-, 120-, or 180-day buckets.

The more useful question is: What is keeping our money in A/R?

A/R problems usually start before something reaches A/R

When A/R days climb, the instinct is often to focus on collections: call the payer, resubmit the denial, contact the patient. Those steps are often necessary, but sometimes they are too little, too late.

Imagine a claim that sits unpaid because the patient’s insurance information was incorrect. The A/R team can eventually fix it, but the real issue happened during intake. Or perhaps a payer denies a procedure because the documentation did not support the submitted code. Again, the A/R team sees the problem, but its source was upstream in the chart.

That is why reducing A/R days in medical billing requires looking beyond the balance itself.

Start with the claims that never should have been delayed

Some of the most frustrating A/R is preventable. A patient’s coverage changed but was not verified before the visit. A required modifier is missing. A payer-specific rule gets overlooked.

A small mistake repeated across hundreds or thousands of encounters can create a very large A/R balance. Real-time eligibility verification and pre-submission claim validation can catch many of these issues while they are still relatively easy to fix—leaving fewer preventable problems to chase later.

Then look at A/R by payer, provider, and procedure

An overall A/R number can hide its most useful information: the patterns underneath it.

A practice might average a fairly healthy 38 A/R days. Dig deeper, however, and you may discover that most commercial payers are paying in 25 to 30 days while one payer averages 65. One procedure may consistently sit in A/R longer than others. Claims from one location may have an unusually high rate of demographic rejections.

This is where healthcare revenue analytics becomes more useful than a monthly total. Break the number apart until it points to something the team can act on.

Denials should teach you something

Denial management software is often designed to help teams resolve denials faster. But there is another opportunity: use denials to prevent the next denial.

If a payer repeatedly rejects the same CPT code for the same reason, that information should not live exclusively in a denial queue. It should make its way back upstream. Maybe documentation needs to capture something differently. Maybe a modifier should be reviewed before submission. Maybe eligibility needs to be checked differently for a particular plan.

Once you can connect the denied claim back to intake, documentation, and coding, A/R becomes feedback—not just a list of balances to collect.

This is where AI can actually be useful

There is plenty of talk about AI in revenue cycle management. Reducing A/R days does not require anything magical. It often requires doing many small things earlier and more consistently—which is exactly where AI can help.

Beam can verify eligibility before the visit, validate patient and insurance information, connect structured clinical documentation to coding, scrub claims before submission, track outstanding balances, and surface patterns in denials and payer behavior.

If one payer begins denying a particular service more frequently, Beam can help identify the pattern and trace it back to the documentation, coding, or eligibility information associated with those claims. Instead of simply asking the A/R team to work denials faster, the practice can ask why they keep happening.

Do not just work A/R. Learn from it.

The goal is not zero A/R. There will always be accounts receivable in healthcare. Payers have processing timelines, patients have balances, and some claims genuinely require additional review.

The goal is to make sure claims are not sitting there for reasons you could have prevented. Watch your overall A/R days, but do not stop there. Look at aging buckets. Compare payers. Find procedures that behave differently. Track denial reasons. Then follow those problems back to where they started.

Sometimes the best way to get a claim out of A/R faster is to make sure it never gets stuck there in the first place.