Reducing Days in A/R: Proven Strategies for Faster Payments | StafGo Health

Days in accounts receivable is the single most revealing number in a practice's financial reporting. It is also the most misread. A practice sees the figure climb from 34 to 47 and responds by pushing the billing team to chase aged claims harder, which addresses the symptom and leaves the cause untouched.

The days accumulated somewhere. Usually not in the follow up queue. More often at registration, in a coding decision, or in a denial that was never worked because nobody owned it.

Why Days in A/R Is the Measure That Reveals Everything

Days in A/R is a downstream indicator. Every upstream failure eventually shows up in it. An eligibility check skipped at the front desk becomes a denial three weeks later, which becomes an appeal, which becomes a balance sitting at 90 days. The number tells you something is wrong. It does not tell you where.

That is why the useful work is diagnostic rather than corrective. Practices that reduce days in A/R durably do it by finding where the delay originates. Practices that attack the aged bucket get a temporary improvement and watch the number climb back.

Calculating It Correctly, and the Measure That Matters More

Days in A/R is total accounts receivable divided by average daily charges, where average daily charges are gross charges over a period divided by the days in that period. Use a rolling 90 or 120 day window rather than a single month, because charge volume varies and a single month will distort the result.

Where the Days Actually Accumulate

Read that table as a sequence rather than a list. Days introduced at registration cannot be recovered at follow up. They can only be worked around at greater cost.

Front End: Preventing the Delay Before It Starts

The highest return work in reducing days in A/R happens before the patient is seen. A claim that goes out clean the first time collects in a fraction of the time of one that denies, is reworked and resubmitted.

• Verify eligibility before every visit, not at registration. Coverage changes, plans terminate and benefits reset. Verification 48 to 72 hours ahead leaves time to resolve a problem before the patient arrives. This is what insurance verification and eligibility checking is for.
• Capture complete demographic and subscriber detail. A large share of preventable denials trace to a wrong policy number, a missing group number or an incorrect date of birth.
• Confirm authorisation is obtained and documented before the service is rendered. Prior authorisation management is one of the few places where a process failure creates a denial that is close to unappealable.
• Establish patient financial responsibility up front and collect at the time of service where possible. Every dollar not collected at the desk enters the slowest and least collectable part of the ledger.
• Check coordination of benefits where secondary coverage exists, since incorrect primary and secondary ordering is a recurring and entirely avoidable denial.

Mid Cycle: Coding and Clean Claim Submission

Clean claim rate is the operational lever most directly tied to days in A/R. A practice submitting at 85 percent clean is reworking roughly one claim in seven, and each rework adds weeks.

• Submit daily. Batching claims weekly adds days to every claim in the batch for no operational benefit.
• Work clearinghouse rejections the same day. A rejection is not a denial. It never reached the payer, and it is the cheapest possible fix at the earliest possible point.
• Run claim scrubbing before submission so coding and format errors are caught before the claim leaves.
• Keep coding current. Code sets and payer policies change. Medical coding and billing accuracy is upstream of most avoidable denials, and specialty practices carry more exposure here than primary care.
• Track clean claim rate by payer and by provider. The aggregate hides the pattern. One provider or one payer usually accounts for a disproportionate share.

Back End: Follow Up, Denials and Appeals

Back end work cannot fix upstream problems, but poor back end work will compound them.

Follow up needs a queue, not availability

Claims should enter a follow up queue on a defined schedule, typically at 21 to 30 days for commercial payers, and be worked in priority order by value and by proximity to timely filing limits. Follow up that happens when someone has spare time does not happen.

Denials need root cause analysis, not just rework

Reworking a denial recovers one claim. Identifying why it denied prevents the next fifty. Categorise every denial by reason code, group by payer and by originating stage, and act on the categories that recur. A/R and denial management delivers most of its value here rather than in the individual appeal.

Appeal selectively and promptly

Not every denial is worth appealing. Appeal where the denial is incorrect and the documentation supports reversal, and do it inside the payer's appeal window. Track appeal outcomes by payer and reason so effort concentrates where it succeeds.

The Patient Responsibility Problem

Patient balances age longer and collect worse than any payer balance, and the share of revenue sitting in patient responsibility has grown steadily as deductibles have risen. A practice that has reduced payer A/R while patient A/R climbs has moved the problem rather than solved it.

• Provide a cost estimate before service wherever the procedure and coverage allow it
• Collect copays and known patient portions at the time of service
• Run a structured statement cycle with defined intervals rather than ad hoc billing
• Offer multiple payment methods, including online and mobile, since friction reduces collection
• Offer payment plans on larger balances rather than letting them age to uncollectable

This is the area where patient billing and support most directly affects the aging report, and it is frequently the least resourced function in a practice.

Automation and Where It Genuinely Helps

Automation compresses the cycle where the work is rules based and high volume. It does not resolve a payer dispute or fix a documentation gap. Practices that expect it to do so end up with faster processing of the same errors. Automation in medical RCM is most effective when applied to a process that already works.

The Dashboard Worth Building

Segment every one of these by payer. Aggregate figures conceal the payer that is responsible for most of the problem, and payer specific patterns are where corrective action actually lands. For a fuller treatment of collection performance, see our guide on improving net collection rate.

Frequently Asked Questions