How to Calculate Days in AR: Methods Compared

In this article▾

1. What exactly is "days in AR" in behavioral health?
2. What are the main ways people calculate days in AR?
3. How do the main days in AR methods compare?
4. How do setup and program type change the "right" days in AR method?
5. So which days in AR definition should you actually use?
6. How do you standardize days in AR across your organization?
7. How AI can help
8. FAQ
9. Sources

The CFO is staring at two dashboards. Finance says your days in AR are 41. Your billing vendor says 57. Same month, same programs, same payers.

Neither number is wrong. They are just not the same metric, and the difference is about to freeze hiring on a track no one defined the same way.

What this article covers:

• The main methods for calculating days in AR, with small numeric examples
• How choices about lookback window, gross vs net, and AR scope move the number
• Which definition to use for behavioral health programs, and when to deviate
• How to standardize your definition so every vendor and internal team is aligned

What exactly is "days in AR" in behavioral health?

Days in accounts receivable (AR), sometimes called DSO, tries to answer one question: on average, how many days of revenue are sitting in AR right now. In other words, if you stopped seeing patients today, how many days of recent revenue would it take to collect everything in your AR aging.

Formally, it links your AR balance at a point in time to how quickly charges are turning into cash. For definitions of AR itself, see our accounts receivable glossary entry.

Behavioral health and SUD centers have extra wrinkles: per-diem residential stays, Medicaid carve-outs, concurrent authorizations, long episodes of care, and high self-pay risk. That makes your days in AR very sensitive to how you define the numerator and denominator.

You can find the baseline definition of days in AR in our days in AR glossary, but in practice people compute it several different ways.

What are the main ways people calculate days in AR?

1. The averaging method: Total AR / average daily charges

This is the most common formula:

Days in AR = Total AR / Average daily charges

Where:

Average daily charges = Total charges over lookback period / Number of days in that period

Most practice management and EHR reports use a version of this.

Tiny example: 90-day vs 365-day lookback

Assume:

• AR today: 900,000 dollars
• Charges last 90 days: 1,800,000 dollars
• Charges last 365 days: 5,400,000 dollars

Using a 90-day lookback:

• Average daily charges = 1,800,000 / 90 = 20,000
• Days in AR = 900,000 / 20,000 = 45 days

Using a 365-day lookback:

• Average daily charges = 5,400,000 / 365 ≈ 14,795
• Days in AR = 900,000 / 14,795 ≈ 61 days

Same AR balance, same business, 45 vs 61 days in AR. The only change is the lookback window.

Why the lookback window matters more in behavioral health

A 365-day window smooths out seasonality. That sounds nice, but it can hide real change:

• Growing programs. If you added detox beds in the last quarter and doubled intensive outpatient volume, the last 90 days are a much better picture of current daily charges than last year's lower volume. A 365-day lookback will understate your true daily charges and overstate days in AR.
• Seasonal programs. School-based, collegiate, or winter-season residential programs see big swings. A 90-day window gives you faster feedback on operational issues, but it can bounce around.

For most behavioral health orgs, a 90-day rolling window is the right default. The key is consistency and clear labeling: "Days in AR (90-day lookback)."

2. Gross vs net days in AR: What do you do with credit balances?

Your total AR on the aging report often mixes:

• Debit balances: money payers or patients owe you
• Credit balances: overpayments you owe back

You can compute days in AR on:

• Gross AR: Debits + credits (credits as negative)
• Net AR: Debits only, with credit balances carved out

Tiny example: same AR, two answers

Assume:

• Debit AR: 1,000,000 dollars
• Credit balances: 100,000 dollars
• Net AR (debits only): 1,000,000
• Gross AR (debits minus credits): 900,000
• Average daily charges: 20,000 dollars

Gross days in AR:

• Days in AR = 900,000 / 20,000 = 45 days

Net days in AR:

• Days in AR = 1,000,000 / 20,000 = 50 days

Here, gross days in AR looks better because your unrefunded credits are masking real receivables. In other orgs, if credits are excluded from AR entirely, the opposite can happen.

Why it matters:

• If you are slow to resolve credit balances, gross days in AR can look artificially low. That hides refund risk and compliance exposure.
• Regulators and auditors expect you to track and resolve overpayments separately from open receivables, especially for Medicare and Medicaid plans source.

In most cases, net days in AR (credits removed) is the cleaner operator metric. Track credits and refunds as their own KPI.

3. Charge basis: Gross charges vs expected (net) revenue

The denominator of days in AR is often called "average daily charges." There are two meaningful ways to define this:

• Gross charges: Charges at your charge master rate
• Expected or net revenue: Charges reduced by expected contractuals and adjustments

Tiny example: inflated days because of a high charge master

Assume:

• AR (net of contractuals): 700,000 dollars
• Your charge master is set at 200 percent of typical contracted rates
• Last 90 days:
  • Gross charges: 3,600,000 dollars
  • Expected revenue (after contractuals): 1,800,000 dollars

Gross charge basis:

• Average daily charges = 3,600,000 / 90 = 40,000
• Days in AR = 700,000 / 40,000 = 17.5 days

Expected revenue basis:

• Average daily expected revenue = 1,800,000 / 90 = 20,000
• Days in AR = 700,000 / 20,000 = 35 days

Did your performance change? No. You just changed the denominator. Gross charges can make days in AR look artificially low when your charge master is far above realistic reimbursement.

For behavioral health:

• Many commercial contracts pay per diem or per session at flat rates. Your gross charges may be 250 percent of those.
• State Medicaid often pays a fixed fee schedule that ignores your posted charge entirely source.

If you have a reliable contract modeling engine, expected revenue as the denominator is more accurate. If you do not, gross charges are acceptable, but you must recognize they bias the number.

4. The DSO "countback" method

Finance teams sometimes use a "countback" or "count back" DSO method instead of the averaging formula. This is more common in corporate finance, less common in medical billing systems.

Conceptually:

1. Start with your AR balance on the report date.
2. Look at your recent daily (or weekly) revenue.
3. "Count back" days of revenue until the sum equals your AR.
4. The number of days counted is your days in AR.

This method assumes the dollars in AR today came from the most recent stretch of revenue, which is closer to reality when revenue is uneven.

Tiny example: uneven revenue, same AR

Assume:

• AR today: 220,000 dollars
• Last four days of revenue:
  • Day 4 (today): 50,000
  • Day 3: 70,000
  • Day 2: 80,000
  • Day 1: 100,000

Average daily revenue over 4 days = 300,000 / 4 = 75,000. If we used the averaging method, days in AR = 220,000 / 75,000 ≈ 2.9 days.

Now use the countback method:

• Start with AR = 220,000.
• Subtract day 4 revenue: 220,000 − 50,000 = 170,000 (1 full day).
• Subtract day 3 revenue: 170,000 − 70,000 = 100,000 (2 full days).
• Subtract day 2 revenue: 100,000 − 80,000 = 20,000 (3 full days).
• Day 1 revenue is 100,000. You need only 20,000 of it: 20,000 / 100,000 = 0.2 of a day.

Total = 3.2 days in AR.

With very uneven daily or weekly revenue, the countback method is more precise. The downside: it is harder to compute inside most EHRs and billing systems.

5. What is included in "AR" in the numerator?

This is the source of many "why are our numbers different" arguments.

You must decide which buckets belong in "AR" for this metric:

• Insurance AR only
• Insurance + patient responsibility (self pay)
• Excluding bad debt (sent to collections)
• Including or excluding unbilled ("DNFB" or charge lag)
• Including small balance write-off candidates

Tiny example: same org, three different numerators

Assume, as of today:

• Insurance AR: 800,000 dollars
• Patient AR (active, not in collections): 150,000 dollars
• Bad debt (in collections): 50,000 dollars
• Unbilled but authorized and rendered services: 100,000 dollars
• Average daily charges: 25,000 dollars

Possible definitions:

1. Payer-only AR: 800,000 / 25,000 = 32 days
2. Payer + patient AR (no bad debt): (800,000 + 150,000) / 25,000 = 950,000 / 25,000 = 38 days
3. All AR + unbilled: (800,000 + 150,000 + 50,000 + 100,000) / 25,000 = 1,100,000 / 25,000 = 44 days

All three numbers are "days in AR," but they answer different questions and have very different operator implications.

For behavioral health, unbilled driven by authorization delays, incomplete documentation, or slow note signing is often as big a cash drag as billed AR. Many centers track it separately as charge lag.

6. The companion metric: Percent of AR over 90 days

Average days in AR can look fine while a chunk of your AR is rotting in the tail.

The standard companion metric:

Percent of AR over 90 days = AR aged 91+ days / Total AR

Example:

• Total AR: 1,000,000 dollars
• AR aged 0-90 days: 700,000 dollars
• AR aged over 90 days: 300,000 dollars

Metrics:

• Days in AR (say) = 35 days
• Percent of AR over 90 days = 300,000 / 1,000,000 = 30 percent

A 35-day average looks healthy. Thirty percent over 90 days is a problem, especially in Medicaid and commercial where timely filing and appeal windows matter source.

For behavioral health, always pair days in AR with percent over 90 days, segmented by payer type.

How do the main days in AR methods compare?

How do setup and program type change the "right" days in AR method?

Outpatient clinics: Short claims, steadier volume

For standard outpatient therapy or psychiatry:

• Encounters are short.
• Volumes are more stable week to week.
• Authorizations may be session-based, but claims are often per visit.

Here, the average method with a 90-day lookback and net AR is usually appropriate. Gross vs expected revenue matters less because contract variance on a 45-minute therapy session is often smaller in dollar terms.

Key nuances:

• Payer-only vs all AR: If your patient responsibility is significant (high deductibles, out of network, cash-pay IOP), consider tracking days in AR with and without patient balances.
• Telehealth: Make sure your telehealth modifiers and place of service codes are correctly modeled in expected revenue if you use net revenue as your denominator source.

Residential / PHP / IOP: Per-diem timing can distort the picture

Residential, PHP, and IOP per-diem models create structural differences:

• Charges post daily over long episodes.
• Authorizations and concurrent reviews lag behind admission.
• Medicaid MCOs and carve-outs have slower, more manual adjudication cycles source.

Common pattern: A pure gross days in AR view shows 50-60 days in AR at the facility level. Leadership panics. When you segment:

• Detox and short-stay units might be at 30 days.
• Long-stay residential and some state Medicaid contracts naturally sit around 60 days because of authorization cycles and payment timing.

To manage this:

• Use net days in AR, 90-day lookback.
• Segment by level of care and payer.
• Pair with percent over 90 days and a view that excludes open but not yet billable per diems (authorization pending, documentation incomplete).

This is where getting clear about what is included in "AR" versus charge lag really matters.

Growing vs steady programs: The lookback window can lie

If you have:

• Opened new locations or levels of care in the last 6 months
• Shifted payer mix, such as moving toward more commercial or more Medicaid
• Expanded telehealth or school-based programs

Then a 365-day lookback is going to lag reality. It bakes in your smaller past.

In a growth scenario:

• A 365-day lookback overstates days in AR, since average daily charges look lower than current reality.
• A 90-day lookback is closer to your current run rate and is what you want for decision-making.

In a shrinking or seasonally declining scenario, the reverse is true. The main rule: pick one window, label it, and avoid mixing them in trend lines.

In-house vs outsourced billing: AR definitions drift

If you work with an outsourced billing vendor, they may:

• Exclude self-pay from their AR metrics, focusing only on payer performance.
• Exclude certain aged buckets, like bad debt or legacy balances.
• Use their default aging categories, which may differ from finance.
• Include or exclude DNFB / unbilled balances.

Common real scenario:

• Vendor reports "days in AR = 34" based on payer AR only.
• Finance reports "days in AR = 49" including self-pay, bad debt, and unbilled.
• The board sees a 15-day gap and concludes either finance or the vendor is wrong.

Both numbers are often correct given their inputs. The fix is to define which buckets belong in "enterprise days in AR" and make vendors compute to that standard or send raw aging.

So which days in AR definition should you actually use?

For behavioral health and SUD centers, a practical standard looks like this:

1. Numerator: Net AR, credits removed.

   • Include: insurance AR and active patient AR (not yet in bad debt).
   • Exclude: credit balances, resolved zero balances, and assigned bad debt in collections.
   • Track credits and refunds as their own KPI and compliance risk.

2. Denominator: Average daily charges over the last 90 days.

   • If you do not have reliable contract modeling: use gross charges, and note that this will slightly understate days in AR when your charge master is high.
   • If you have a trustworthy contract modeling system: use expected revenue as the denominator and label the metric as "net days in AR (expected revenue basis)."

3. Lookback window: A rolling 90 days.

   • Better for growing or changing programs.
   • Aligns more closely with current payer mix and volume.

4. Scope: Compute at multiple levels.

   • Enterprise-wide days in AR (for board and CFO).
   • By payer category: Medicaid, Medicaid MCOs, commercial, Medicare, self-pay.
   • By program or level of care: outpatient, IOP, PHP, residential, detox.

5. Companion metric: Percent of AR over 90 days.

   • Always show it next to days in AR, at least at payer and program level.

You will still see differences between gross-basis and expected-revenue-basis days in AR. That is fine. The problem is not that they differ. The problem happens when they are not clearly labeled.

How do you standardize days in AR across your organization?

Step 1: Write one clear definition

In plain language, document:

• Numerator: Which AR buckets are in, which are out
  • Example: "Include payer and active self-pay AR aged 0-365 days. Exclude credits, bad debt, legacy write-offs, and unbilled."
• Denominator:
  • Charges or expected revenue
  • Lookback period (90 days, rolling)
• Timing:
  • As of what date (end of calendar month)
  • Which posting date to use (transaction date vs service date)

Publish this in a simple one-pager and in your internal days in AR glossary entry.

Step 2: Put it in a metrics catalog

Create a shared "metrics catalog" that includes:

• Metric name and aliases (Days in AR / AR days / DSO)
• Formal definition
• Data source systems (EHR, billing, general ledger)
• Calculation logic at a high level
• Owner (person)
• Where it appears: board pack, executive dashboard, vendor SLA report

Include related metrics like net collection rate, accounts receivable, and charge lag with equally clear definitions.

Step 3: Name an owner and a cadence

Assign ownership, typically:

• Finance leader or RCM director owns the metric definition.
• IT or analytics owns the implementation in dashboards.
• Vendor managers ensure external partners comply.

Set a monthly reconciliation cadence:

• Once per month, compare days in AR from:
  • Finance
  • Internal RCM / billing
  • External vendors (if any)
• Require each to show:
  • Their numerator AR by bucket
  • Their denominator and lookback window
  • Their AR scope (payer only, all AR, unbilled or not)

If any definition drifts, fix it before it hits leadership.

Step 4: Force vendors to align or send raw aging

Every RCM or billing vendor should either:

• Compute days in AR according to your definition, or
• Provide raw aging and charge data so you can compute it yourself.

Minimum vendor requirements:

• Full AR aging by payer, patient, age bucket, and program / facility.
• Clear separation of credits and debits.
• Identification of bad debt, legacy, and any excluded categories.
• Exportable charge and posting data within the defined 90-day window.

Make this part of the contract and the SLA review, not an informal request.

How AI can help

AI is well suited to the repetitive, data-consistent work that days in AR requires: pulling aging data from multiple systems, categorizing AR correctly, and applying one shared formula every time.

A well-configured AI agent can:

• Ingest AR aging from different EHRs and billing systems, normalize payer and program mappings, and flag buckets that do not align with your definition.
• Compute net AR, separate credits, and calculate days in AR and percent over 90 days at enterprise, payer, and program levels in near real time.
• Spot outliers, such as one Medicaid MCO whose AR over 90 days suddenly jumps, and push those into workqueues for human follow-up.

This is where Supabill goes further than a fixed report. Supabill can compute days in AR every way described here, side by side, so you can see which method most honestly represents your programs. Its agents recommend a definition based on what you are actually looking at: a residential book with long per-diem episodes gets different guidance than a steady outpatient panel, and they flag when a vendor's number diverges from your standard and show exactly why.

Because it is agentic, you can talk to it. Ask why days in AR moved this month, compare gross vs net or a 90 vs 365 day lookback on the spot, then pin the view you trust as a dashboard and start tracking it. You still own the definition. Supabill makes choosing the right one, and holding everyone to it, the easy path.

One honest limit: AI cannot fix missing or incorrect data in source systems. If charges are posted late, authorizations are not recorded correctly, or contracts are not modeled accurately, the math on top will still mislead. Human operators still need to set the definitions, validate mappings, and decide which exceptions matter.

FAQ

Q: Is there a universal "good" days in AR target for behavioral health?

A: No. Targets vary by payer mix, state Medicaid rules, and level of care. Many finance groups discuss benchmarks in the 30-60 day range for medical practices, but behavioral health with heavy per-diem residential and Medicaid carve-outs often runs higher without indicating failure source. Focus on trend over time, payer segmentation, and percent over 90 days, not a single magic number.

Q: Should days in AR include self-pay and patient responsibility balances?

A: For enterprise cash planning, yes. Patient responsibility is real cash risk, especially with high-deductible plans. For vendor performance and payer comparison, it can be useful to look at payer-only days in AR as a separate metric. The key is to define which you are using and avoid mixing them in the same trend line.

Q: Do unbilled services (DNFB) belong in days in AR?

A: Strictly speaking, unbilled services are not yet receivables, so traditional finance metrics exclude them source. Operationally, in behavioral health, DNFB and charge lag can be as damaging as slow collections. Many centers track a separate "days in unbilled" metric and a combined "days in AR plus unbilled" for total cash risk. Just label each clearly.

Q: How do credit balances and refunds fit into AR metrics?

A: Credit balances represent money you owe back, not money owed to you. They should not reduce your open AR in a way that makes days in AR look better. Best practice is to track credit balances, refund timeliness, and unresolved credits separately, for compliance and audit reasons source. For operator days in AR, use net AR with credits removed from the numerator.

Q: Is the DSO countback method better than the averaging method for behavioral health?

A: It is more precise mathematically when revenue is highly uneven, such as programs with big one-time grants or lump-sum payments. In practice, most behavioral health EHRs and billing systems do not support it natively, and the operational decisions you need to make do not require that level of precision. A well-defined average method with a 90-day lookback is usually sufficient.

Q: How often should we recalculate days in AR?

A: Monthly is the standard for finance reporting and board communication source. For operational management, many RCM teams refresh days in AR and percent over 90 days weekly by payer and program, especially when working through denial backlogs or authorization issues. Daily updates are rarely necessary unless you are in acute cash crisis.

Q: How do Medicaid carve-outs and MCOs affect days in AR?

A: Carve-outs and Medicaid MCOs often have slower adjudication cycles, more manual concurrent review, and more frequent retroactive eligibility changes source. This naturally pushes days in AR higher for those payers, even with good billing practices. Segment your metrics so Medicaid carve-out performance does not hide or distort commercial or Medicare performance.

Q: What is the relationship between days in AR and net collection rate?

A: Days in AR measures speed of collection. Net collection rate measures completeness of collection against expected reimbursement. You can have low days in AR but poor net collection if claims are promptly denied and written off. You can also have high net collection but high days in AR if payers pay accurately but very slowly. You need both metrics to understand performance source.

Q: Can we rely on our EHR's "days in AR" report as-is?

A: Only after you confirm how it is defined. Many built-in reports use system defaults for AR buckets, include or exclude credits, and mix payer and patient balances in ways that do not match your finance definitions. Review the report logic with your EHR vendor, compare it to your metrics catalog, and adjust either the report or your expectations.

Sources

• HFMA: Revenue Cycle (MAP Keys)
• MGMA: Revenue cycle resources
• CMS: Internet-Only Manuals (IOMs)
• X12: Claim Adjustment Reason Codes (CARC)
• CAQH: CAQH Index
• KFF: Private insurance research
• HealthCare.gov: Appeal an insurance company decision
• HHS: HIPAA