Behavioral Health RCM Benchmarks: Clean Claims, AR, Denials

What a good clean claim rate, days in AR, and denial rate look like for a behavioral health practice, how each is defined, and what moves them.

Every behavioral health billing team tracks the same three numbers: how many claims go out clean, how long money sits in accounts receivable, and how many claims come back denied. What most teams lack is a shared definition of each one, a realistic target for a program that bills in units and carries authorizations, and a way to measure the numbers without rebuilding a spreadsheet every month. Ease is the unified CRM, EHR, and RCM where the metrics behavioral health billers track, clean claims, days in AR, and denials, are measured in the same system that produced the claims.

This guide defines the three metrics the way the revenue cycle profession defines them, gives the benchmarks billing teams commonly use, explains why behavioral health runs differently from a medical group, and shows what the federal payment rules mean for your floor.

The three numbers, defined the way payers and auditors define them

Benchmarks are only useful when everyone is counting the same thing. The Healthcare Financial Management Association publishes a standard set of revenue cycle indicators called MAP Keys, and three of them are the ones this guide is about.

• Clean claim rate (MAP Key CL-1). The number of claims that pass edits with no manual intervention, divided by the number of claims accepted into the claims processing tool for billing. Print-and-mail claims and claims held for edits are excluded, so this is a measure of electronic claims that went out without anyone touching them.
• Net days in accounts receivable (MAP Key FM-1). Net accounts receivable divided by average daily net patient service revenue, with the daily average taken over the most recent three months. HFMA describes it as a "trending indicator of overall A/R performance."
• Remittance denial rate (MAP Key AR-5). Total claims denied divided by total claims remitted, counted at the claim level from 835 remittances or paper remits. Only actionable denials count, which HFMA defines as those "that may be addressed and corrected within the organization." Patient-responsibility denials and duplicate-claim denials are excluded.

Two consequences follow. First, a denial rate that includes patient responsibility or duplicates will read high and tell you nothing. Second, a clean claim rate measured at the clearinghouse (accepted, not rejected) is a different number from one measured at the scrubber (no edits fired), and a team should know which one it is reporting.

What is a good clean claim rate for a behavioral health practice

The target billing teams commonly work toward is 95 percent or higher: at least 95 of every 100 claims accepted on first submission with no manual rework. Teams that reach it tend to run automated edits before submission, verify eligibility before the visit, and keep charge rules current so a code change does not silently break a claim type.

Behavioral health practices often start below that target, and the reasons are structural rather than sloppy:

• Unit billing. Time-based codes billed in 15-minute units fail edits when documented minutes and billed units disagree.
• Group codes. One group session becomes one claim line per participant, so a single scheduling error multiplies into several rejected claims.
• Authorizations. IOP, PHP, and residential care are commonly authorized in units or days, and a claim that overruns the authorization is rejected or denied before anyone reads the note.
• Level-of-care transitions. A client who steps down from residential to IOP mid-week generates two claim types with different bill types and revenue codes, and the boundary is where errors cluster. Our UB-04 billing guide walks through the codes that separate PHP from IOP on an institutional claim.

The practical answer to "what is a good rate" is therefore two numbers: the industry target of 95 percent, and your own baseline measured with the CL-1 definition. If you are at 82 percent, the next goal is 88, not 95, and the work is finding which edit fires most.

Days in AR: the number that tells you how long money sits

Net days in AR converts the balance sheet into a question a program director can act on: if we stopped billing today, how many days of revenue are still waiting to be paid? Billing teams commonly treat under 40 days as healthy, 30 to 40 as the normal range for a well-run outpatient or residential program, and under 30 as strong.

Three things push behavioral health programs above 40:

1. Medicaid and managed care mix. Medicaid plans pay on their own clocks, and a heavy Medicaid mix stretches the average even when every claim is clean.
2. Authorization gaps. Sessions delivered while a continued-stay request is pending sit unbilled or denied until the authorization is resolved.
3. Rework loops. A denied claim that is corrected and resubmitted after 30 days carries its full age back into AR.

Days in AR is also the metric most distorted by measurement shortcuts. Using gross charges instead of net patient service revenue in the denominator makes the number look better than it is, because gross charges include amounts no payer will ever pay. Use the FM-1 definition and keep the same one every month.

Denial rate: what the payer data says and what to count

There is no single published denial benchmark for behavioral health, and the payer data that does exist shows how wide the range is. KFF's analysis of claims denials in ACA marketplace plans, built from federal transparency data, found that HealthCare.gov insurers denied 20 percent of in-network claims in 2023, and that the in-network denial rate "ranged from 1% to 54%" across insurers. The same analysis found consumers appealed fewer than 1 percent of denied in-network claims, and insurers upheld 56 percent of the denials that were appealed.

The underlying numbers come from the CMS Transparency in Coverage public use file, which reports issuer- and plan-level claims and appeals data for the Exchanges. It covers qualified health plans offered through the Exchanges, so treat it as a ceiling on what "normal" can mean rather than a target.

For a provider-side benchmark, most billing teams treat a remittance denial rate under 5 percent as the goal and anything approaching 10 percent as a sign that a process upstream is broken. The number to watch beside it is the appeal rate: a program that denies at 6 percent and appeals 80 percent of those denials is in better shape than one that denies at 4 percent and writes them off. Our claim denials guide covers the common denial reasons in mental health billing and the appeal timelines that go with them.

Why behavioral health runs different from a medical group

A medical group bills mostly visits. A behavioral health organization bills visits, units, days, groups, and programs, often for the same client in the same month, and each of those has its own failure mode.

• Eligibility changes mid-episode. A client in a 30-day residential stay can lose or change coverage during the stay. Programs that verify benefits at admission only find out at the remittance. See the verification of benefits workflow for how treatment centers run the 270/271 check and what to capture from it.
• Documentation drives billability. In most behavioral health programs a session is billable when the note is finalized and the attendance is recorded, so a documentation backlog is an AR problem, not only a clinical one.
• Institutional and professional claims coexist. PHP and IOP are billed on the institutional claim with revenue codes and condition codes, while outpatient therapy is billed on the professional claim with CPT codes. A billing team that reports one clean claim rate across both is averaging two different processes.
• Remittances carry the diagnosis. The 835 electronic remittance is where denial reasons live. Teams that post payments from the EOB PDF instead of parsing the ERA lose the reason codes they need to classify denials.

None of this means behavioral health benchmarks should be lower. It means the path to the benchmark runs through scheduling, documentation, and authorization tracking, not through the billing office alone.

The payment clocks that set your floor

Two federal rules define what a clean claim is and how fast it has to be paid, and they set the floor under any days-in-AR target.

For Medicaid, 42 CFR 447.45 defines a clean claim as "one that can be processed without obtaining additional information from the provider" or a third party. Under 42 CFR 447.45, a state Medicaid agency must pay 90 percent of clean claims from practitioners within 30 days of receipt and 99 percent within 90 days, and providers have 12 months from the date of service to submit. A program with a large Medicaid book should expect part of its AR to sit in the 31-to-90-day bucket by design, and should compare its Medicaid days in AR against those clocks rather than against a commercial target.

For Medicare, section 1842(c) of the Social Security Act defines a clean claim as one with "no defect or impropriety" that would prevent timely payment, sets a payment floor of 13 days after receipt for electronic claims, and requires interest to be paid on a clean claim that is not paid within 30 calendar days. The 13-day floor is why days in AR can never reach zero, and the 30-day ceiling is why a clean electronic Medicare claim aging past 30 days is a signal that something other than the payer's clock is at work.

Commercial and managed care contracts have their own prompt-pay terms, usually set by state insurance law, and they belong in the same table: for each payer, the contractual clock, the observed days to payment, and the gap between them.

How to measure these in-system instead of in a spreadsheet

The benchmarks above are easy to state and hard to sustain when the numbers are assembled by hand. A month-end spreadsheet that pulls a claims export from the clearinghouse, an aging report from the practice management system, and a denial log from someone's inbox will produce three numbers that cannot be reconciled with each other, because each came from a different system with a different definition of a claim.

What to look for in the system that generates the claims:

• Clean claim rate computed from the scrubber, so the numerator is claims that passed edits, not claims the clearinghouse accepted.
• Net days in AR from the same ledger that posts the remittances, with the three-month revenue average built in, so nobody chooses the denominator.
• Denial classification from the 835, with the adjustment reason and remark codes attached to the claim, so denial rate can be cut by payer, program, and code.
• Authorization units visible before submission, so a claim that would overrun an authorization is caught before it becomes a denial.
• Eligibility at intake and at the front desk, so coverage changes show up before the service, not after the remittance.

If the system that documents the session, tracks the authorization, and generates the claim is the same system that reports on all three, the benchmarks stop being a reporting project and become a dashboard.

How Ease measures clean claims, days in AR, and denials

Ease was built from the ground up as one behavioral health platform, with CRM, EHR, and RCM in a single product with one login and one patient record rather than three tools connected by integrations. That is the design this guide argues for, and it is what makes the three benchmarks measurable in place.

• Reporting from intake to billing. Ease reporting covers the path from referral to remittance, with Power BI dashboards and real-time custom reports, so clean claim rate, days in AR, and denial rate are measured in-system rather than reconstructed from exports.
• Claims generated from the record. Claims are auto-generated with customizable rules and worked from a claims worklist, with ERA parsing and electronic remittances posted next to the clinical record, so denial follow-up happens where the documentation lives.
• Institutional claims for programs. Ease generates 837I institutional claims and the paper UB-04 for residential, PHP, IOP, and detox, with revenue-code-based service lines and the condition codes that separate PHP from IOP.
• Eligibility in the same system. Real-time eligibility runs through Availity's 270/271 check on CRM leads before admission and on patients afterward, in the same system as admissions and billing.
• Authorizations before the claim. Ease shows remaining authorized units against the total on the patient's insurance record, before a claim is ever submitted.
• Attendance feeds the worklist. Group sessions capture attendance per attendee, with a planned-absence reason for anyone who did not attend, and that attendance feeds the billing worklist alongside note and appointment-status evidence.

What Ease does not do: it does not publish a customer benchmark of its own, and it does not promise a specific clean claim rate or days-in-AR figure. Those numbers belong to your program, your payer mix, and your front desk, and the platform's job is to measure them honestly. If you are comparing systems, the RCM product page covers billing and the group practice revenue cycle resource covers the operating rhythm behind these metrics.

Questions to bring to a demo

• Show me clean claim rate for last month. Is the numerator claims that passed edits, or claims the clearinghouse accepted?
• Show me net days in AR. What is the denominator, and over how many months is it averaged?
• Take one denied claim from a remittance. Where do the reason codes land, and can I cut denial rate by payer and by program?
• A client steps down from residential to IOP on a Wednesday. What do the two claims look like, and where would an error show up?
• Show me an authorization with two units left. Where does the biller see it before the next claim goes out?

The teams that hit 95 percent clean, under 40 days in AR, and under 5 percent denied are not the ones with the best spreadsheet. They are the ones whose system measured the numbers the same way every month and put the fix one click from the claim.

Frequently Asked Questions

What is a good clean claim rate for a behavioral health practice?

The target most billing teams work toward is 95 percent or higher of claims accepted on first submission with no manual rework. Behavioral health programs that bill in 15-minute units, run group codes, and carry authorizations tend to start lower, so the useful first step is measuring your own rate the way HFMA defines it and then closing the gap edit by edit.

How is clean claim rate calculated?

Under HFMA's MAP Key CL-1, clean claim rate is the number of claims that pass edits with no manual intervention divided by the number of claims accepted into the claims processing tool for billing. Print-and-mail claims and claims held for edits are excluded from the numerator.

What is a good days in AR number?

Billing teams commonly aim for net days in AR under 40, with 30 to 40 treated as healthy and under 30 as strong. HFMA's MAP Key FM-1 calculates it as net accounts receivable divided by average daily net patient service revenue over the most recent three months.

What denial rate should a behavioral health program expect?

There is no single published behavioral health figure. KFF's analysis of CMS transparency data found HealthCare.gov marketplace insurers denied 20 percent of in-network claims in 2023, with individual insurers ranging from 1 percent to 54 percent. Most practices treat a remittance denial rate under 5 percent as the goal and anything near 10 percent as a process problem.

Does Ease report clean claim rate, days in AR, and denial rate?

Yes. Ease is one platform for CRM, EHR, and RCM, and its reporting covers intake to billing, so clean claim rate, days in AR, and denial rate are measured in the same system that produced the claims, alongside Power BI dashboards and custom reports.