Eligibility
Answers questions such as:
- Is the policy currently active?
- What is the coverage period?
- Who is the subscriber?
- What payer information is available?
One platform
Intake, clinical, billing, and workforce — without four vendors and three logins.
Everything below runs on the same patient record, the same permissions, and the same audit log.
See the audit packet builder →Clinical
Revenue cycle
Audit & compliance
Level of care
A 40-bed detox and a two-clinician practice don't need the same software — or the same invoice.
Pick your level of care and see what changes: workflows, modules, and price.
Compare by level of care →By level of care
By role
Who builds this
We came from audit defense and billing, not from a generic EHR.
Why we built ProbityCare →Revenue Cycle Management
Behavioral health billing does not begin when someone creates a claim. It begins before the patient receives care.
Insurance eligibility, benefits, authorization requirements, provider credentials, documentation, coding, claim preparation, payer responses, denials, and contracted reimbursement can all affect whether — and how much — an organization ultimately gets paid.
For behavioral health organizations, especially those operating structured or higher levels of care, revenue cycle management works best when these stages are treated as one connected process.
This guide walks through that process from the beginning.
This is general education, not legal, coding, or patient-specific billing advice. Payer requirements differ; always confirm the current rules that apply to your organization, payers, and contracts.
Definition
Behavioral health billing is the process of converting covered behavioral health services into claims, submitting those claims to the appropriate payer, processing payer responses, collecting reimbursement, resolving exceptions, and managing patient financial responsibility.
Depending on the organization, this can involve:
Behavioral health billing is part of the broader revenue cycle. The revenue cycle starts before a claim exists and continues after payment is received.
Context
Behavioral health organizations often manage several dependencies at the same time.
Is the patient’s coverage active?
Does the plan cover the service?
Does the service require approval?
Is the rendering provider appropriately configured for the payer and service?
What service and level of care was delivered?
Does the record support the billed service?
Are the appropriate codes, modifiers, and claim information being used?
Was the claim prepared correctly?
Was the claim accepted, rejected, denied, or paid?
Was reimbursement consistent with the organization’s agreement?
What amount remains the patient’s responsibility?
An eligibility gap surfaces as a denial weeks later; an unsigned note holds a claim that was otherwise ready. That is why it helps to evaluate the whole cycle rather than any one step on its own.
The Big Picture
Instead of treating billing as an isolated back-office function, behavioral health organizations can evaluate each stage as part of a connected revenue cycle. Select a stage to jump to it.
Before care
During care
The claim
After adjudication
Before Care
Before delivering insurance-funded services, organizations generally need to understand the patient's current coverage and applicable benefits. Eligibility and benefits are related but not identical concepts.
Eligibility
Answers questions such as:
Benefits
May help answer:
Electronic eligibility inquiries and responses commonly use the HIPAA-adopted X12 270/271 transaction.1 How much behavioral health benefit detail a response carries varies by payer, so some details may still need a portal lookup or a call.
Final reimbursement depends on payer adjudication, plan terms, medical necessity requirements, authorization, documentation, coding, and other applicable requirements.
Inactive coverage, incorrect payer information, demographic mismatches, or misunderstood benefits rarely stop care from happening. They tend to surface later, as a rejected claim, a denial, or an unexpected patient balance, after the service has already been delivered and when the fix is harder. Re-checking coverage when a patient moves to a new level of care, or at the start of a new plan year, catches some of these earlier.
Before Care
Some behavioral health services require payer authorization before or during treatment. This can become especially important for structured services and higher levels of care.
Authorization information may include:
If authorization information is visible only after billing receives the claim, the organization may discover the problem too late. Scheduling, utilization management, clinical teams, and billing may all need visibility into authorization status, so that a concurrent review is requested before visits run out, not after.
Electronic authorization requests can use the HIPAA-adopted X12 278 transaction,2 though many payers also rely on portals, fax, or phone. For certain payers, including Medicare Advantage organizations and state Medicaid and CHIP programs, CMS's Interoperability and Prior Authorization final rule (CMS-0057-F) phases in process and API requirements, with some provisions starting January 1, 2026 and most API requirements due by January 1, 2027.3 It does not apply to every plan.
An approved authorization means the payer agreed the service may be covered as requested. The claim still has to meet the plan's other terms, documentation, and coding requirements.
Further reading: The authorization expired yesterday. Who was supposed to know?
During Care
The clinical record and the financial record are connected. Billing teams may need to know whether required documentation has been completed before a claim is considered ready for submission.
Depending on the service and payer requirements, documentation may include:
Documentation requirements vary by payer, program, jurisdiction, contract, service, and level of care. Organizations should follow applicable payer requirements, contracts, laws, regulations, and clinical standards.
Payers decide whether a service was medically necessary using their own criteria. The record is how an organization shows, in terms a reviewer can evaluate, why this service at this level of care was appropriate for this patient on this date. Notes that repeat the same language visit after visit make that harder to show. For substance use disorder records, confidentiality rules under 42 CFR Part 24 can also shape how documentation is shared.
Related workflows: charting & forms, treatment plans, group notes, and the documentation clock.
Further reading: Cloned notes and medical necessity: what separates a template from a copy
Translating Care
Behavioral health claims may involve different code sets and billing formats depending on the provider, service, payer, and level of care. At a high level, coding can involve:
Diagnoses are reported with ICD-10-CM.7 Services are generally reported with HCPCS, whose Level I is the CPT code set and whose Level II covers other items and services.6 Both are HIPAA-adopted medical data code sets.5 Professional claims also carry a place-of-service code,8 while institutional claims use revenue codes maintained by the National Uniform Billing Committee.9
Professional claims
CMS-1500 / 837P. Commonly used for practitioner services, with CPT or HCPCS codes, modifiers, units, and a place-of-service code.
Institutional claims
UB-04 / 837I. Commonly used by facilities, with revenue codes, and HCPCS codes where the payer requires them, plus admission and discharge information.
Which format applies depends on the organization, payer, and service. The same level of care can be billed on an institutional claim by one program and a professional claim by another, and code and modifier requirements vary by payer.
Never select a billing code solely because it produces higher reimbursement. Coding should accurately represent the service provided and comply with applicable payer and regulatory requirements.
The Claim
Once the service and supporting documentation are ready, claim information must be assembled accurately. Common claim data can include:
Requirements differ based on payer and claim type. Electronic claims use the HIPAA-adopted X12 837 standard, in professional (837P) and institutional (837I) versions.10 Providers are identified by a National Provider Identifier issued through NPPES,11 and a taxonomy code, from the code set maintained by the National Uniform Claim Committee, describes the provider's type and specialty.12 Which provider appears in which field (rendering, billing, supervising) depends on the payer, the claim type, and how each provider is enrolled.
The Claim
Claim scrubbing means checking claim information for potential problems before the claim is sent to the payer. For behavioral health organizations, useful validation may extend beyond whether required electronic fields are populated.
Does the service align with available authorization information?
Is the provider information appropriate for the claim?
Are code and modifier combinations consistent with configured requirements?
Does the billed service align with the patient’s program?
Is the required documentation state complete?
Is patient and subscriber information complete?
Is payer information configured correctly?
Some edits come from public sources. Medicare, for example, publishes National Correct Coding Initiative edits for code pairs and units of service.13 Others come from individual payer policies and from rules an organization configures for its own programs and contracts.
Finding a problem before submission is generally easier than resolving it after a payer response.
Further reading: Seven claim problems you can catch before the payer sees them
The Claim
Claims may be transmitted electronically through a clearinghouse or other payer-connected workflow. HHS adopts the transaction standards and operating rules that govern these exchanges.14
Claim creationThe billing system assembles the claim from the encounter, provider, payer, and coding data.
Electronic transmissionThe claim is sent as an electronic transaction, usually to a clearinghouse.
Clearinghouse validationThe clearinghouse checks format and payer-specific front-end edits before forwarding.
Payer acceptanceThe payer confirms whether it can accept the claim for processing.
Payer adjudicationThe payer applies coverage, benefits, policy, and contract terms to decide payment.
A claim being accepted for processing does not mean the payer has approved it for payment.
Two Different Things
These terms are often used together but represent different stages of the claim lifecycle.
Rejection
Generally occurs before full payer adjudication, when a claim cannot be accepted for processing because of an issue such as missing, invalid, or improperly formatted information.
Denial
Generally occurs after the payer has processed or adjudicated the claim and determined that payment will not be made for all or part of the claim.
Path A — rejected before adjudication
or
Path B — accepted and adjudicated
Many clearinghouses and payers report acceptance or rejection through acknowledgment transactions, commonly the X12 999 and 277CA. A rejected claim generally has to be corrected and resubmitted, and because a rejected claim may not count as received, an unworked rejection can turn into a timely filing problem. A denied claim may call for a corrected claim, an appeal, or other follow-up, depending on the reason and the payer's rules.
Exact terminology and workflows may vary by payer and clearinghouse.
After Adjudication
After adjudication, payer remittance information explains how the claim was processed. The Electronic Remittance Advice (ERA) is the HIPAA-adopted X12 835 transaction.15
An ERA commonly provides information related to:
Adjustments on an 835 are explained with Claim Adjustment Reason Codes (CARCs),17 placed in groups such as CO (contractual obligation) and PR (patient responsibility), and are often supplemented by Remittance Advice Remark Codes (RARCs).18 Payment itself may arrive separately, commonly by electronic funds transfer, and has to be matched back to the remittance.16 Posting is where denials, underpayments, and patient responsibility first become visible, so it works best when each line is tied back to the original claim.
After Adjudication
Denials should become work items rather than disappearing into reports.
A denial workflow may include:
Identify
Categorize
Assign
Investigate
Correct
Appeal or resubmit where appropriate
Track
Resolve
Analyze root cause
Appeal deadlines and procedures are set by the payer, plan, or program. Track them from the date on the remittance or denial notice so the option to appeal doesn't lapse while the item sits unassigned.
Organizations should also analyze why denials occur. Patterns may reveal problems involving:
Further reading: The five denial reasons behind most behavioral health write-offs
After Adjudication
Receiving payment does not necessarily mean the claim was reimbursed according to the organization's expectations. Organizations with negotiated payer agreements may need to compare actual reimbursement against contracted rates.
If a billing workflow considers a claim resolved as soon as money is received, reimbursement variances can be difficult to identify. Connecting contract rates with remittance information can help surface payments that require additional review.
A variance is a question, not a conclusion. Before treating a payment as short, account for patient responsibility, the patient's benefits, and any contract terms (such as multiple-service rules or carve-outs) that legitimately change the expected amount.
When the contract itself is the problem: Using outcomes in a rate negotiation
After Adjudication
Payer adjudication may assign a portion of the financial responsibility to the patient.
Depending on the patient's coverage and payer determination, this may include:
Patient financial workflows should clearly distinguish payer responsibility from patient responsibility, and statements should reflect what the remittance actually assigned to the patient rather than an estimate made at intake.
For uninsured or self-pay patients, the federal No Surprises Act generally requires providers to give a good faith estimate of expected charges.1920 State rules may add their own requirements.
It Depends on the Service
Billing workflows can vary significantly depending on the service being delivered.
Outpatient
Typical considerations:
PHP & IOP
Typical considerations:
Residential & Detox
Typical considerations:
MAT & OTP
Typical considerations:
Opioid treatment programs are also subject to federal rules at 42 CFR Part 8, administered by SAMHSA,21 in addition to payer billing requirements.
For IOP programs: What has to be true before an IOP day is actually billable
For residential programs: Per-diem and case-rate billing for residential programs
Specific billing requirements vary by payer, contract, jurisdiction, provider type, and service. Always verify current requirements applicable to your organization.
What Goes Wrong
Most billing problems trace back to something earlier in the cycle. These are among the most common.
The plan was not active on the date of service, so the payer will generally not pay for that care.
A demographic or subscriber mismatch keeps the payer from matching the claim to the member.
A service that required approval was delivered without an authorization on file.
Care continued past the approved visits, units, days, or dates.
The rendering or billing provider is not configured the way the payer expects.
The record does not yet support the billed service, or it is unsigned.
The submitted codes do not accurately represent the service delivered.
A required modifier is missing, or one is added that is inconsistent with the code.
The units billed do not match the documented service time or day of care.
The billed service does not match the patient’s program or authorization.
The claim reached the payer after its filing deadline. Deadlines vary by payer; Medicare, for example, generally requires claims within one calendar year of the date of service.22
The same service was submitted more than once, often after an unconfirmed resubmission.
The claim could not be accepted for processing and has to be corrected and resubmitted.
The payer adjudicated the claim and declined some or all of the payment.
The payment posted below the contracted or expected amount.
Patient responsibility remains outstanding with no statement or follow-up.
Software can help surface and organize many of these, but not every problem is preventable by software. Staffing, training, process, and payer behavior all play a role.
What to Monitor
These metrics help show where the cycle is slowing down or leaking. They are described in plain terms below, without universal “good” benchmarks: different organizations, payers, services, and levels of care can produce materially different numbers. Trend each against your own history, and keep definitions consistent.
Claims
The share of claims that pass pre-submission checks without manual correction. Organizations define “clean” differently, so write down the definition you use.
The share of claims accepted for processing on the first submission, without being rejected and resubmitted.
The share of submitted claims returned before adjudication because they could not be accepted for processing.
The share of adjudicated claims, or claim lines, that the payer denies in full or in part.
Speed & receivables
The time from date of service to claim submission. Long lags often point to documentation or charge-capture delays.
The time from claim submission to payment posting.
Roughly how many days of charges remain unpaid, usually calculated from the A/R balance and average daily charges.
How outstanding balances spread across age buckets such as 0–30, 31–60, 61–90, and 90+ days.
Authorization & documentation
How much of an approved authorization (visits, units, days, or dollars) has been used.
Scheduled or ongoing services at risk because an authorization is expiring or nearly used up.
The share of delivered services with completed, signed documentation that supports billing.
Delivered services that have not yet become claims, measured by count, dollars, or age.
Payment
Payments collected as a share of what the organization was entitled to collect after contractual adjustments.
The difference between expected contractual reimbursement and what the payer actually paid.
How long patient-responsibility balances have been outstanding.
Evaluating Vendors
Instead of asking whether software “does billing,” ask vendors to demonstrate the complete workflow. For a broader framework, see our behavioral health EHR buyer's guide or compare platforms side by side.
Can eligibility be verified?
Can benefits information be recorded?
Can prior authorizations be tracked?
Can utilization be monitored?
Can documentation affect claim readiness?
Can claims be validated before submission?
Can electronic claims be transmitted?
Can payer responses be posted?
Can rejections be worked?
Can denials be assigned and tracked?
Can payer contracts and rates be stored?
Can payments be compared against expected rates?
Can patient balances be managed?
Can leadership see revenue cycle performance?
Can workflows differ by level of care?
Can the system support multiple locations and programs?
Bring a Scenario
During a software demonstration, do not ask the vendor to simply show you the billing screen. Give them a scenario.
Scenario
Watch who sees the expiring authorization, whether the incomplete note holds the claim, where the claim issue is caught, and how the underpayment is surfaced, and how many screens and people it takes.
Weighing cost as well? ProbityCare publishes its per-seat pricing.
Use This With Your Team
A working checklist for the revenue cycle, grouped by stage. Tick what applies, then print it or save it as a PDF. Nothing is submitted and no email is required.
Nothing here is submitted or emailed. Tick the steps that apply to your organization, then print or save the list as a PDF for your team. Requirements vary by payer, contract, and level of care.
How ProbityCare Helps
ProbityCare is designed around the relationship between care delivery and reimbursement. Instead of treating clinical activity, authorization, billing, and payment as unrelated workflows, ProbityCare connects the information across the patient journey.
Revenue cycle
Record coverage and benefit information before services are delivered.
Explore Eligibility & Benefits →Revenue cycle
Track approved visits, units, days, dollars, utilization, and expiration.
Explore Prior Authorizations →Revenue cycle
Validate claim information against configured requirements before submission.
Explore Claim Scrubbing →Revenue cycle
Connect payer responses back to the original claim.
Explore Remittance Posting →Revenue cycle
Turn denials and unresolved claims into assigned, trackable work items.
Explore Denials Queue →Revenue cycle
Compare actual payment against expected contractual reimbursement.
Explore Contracts & Rates →Revenue cycle
Keep patient financial responsibility connected to the broader account.
Explore Patient Balances →Common Questions
Behavioral health billing is the process of translating behavioral health services into claims and financial transactions so organizations can seek reimbursement from payers and collect applicable patient responsibility. The broader revenue cycle also includes eligibility, benefits, authorization, documentation, claim preparation, payer responses, denials, remittance, and payment review.
Behavioral health billing can involve payer-specific requirements, prior authorization, different provider types, multiple levels of care, clinical documentation requirements, coding rules, utilization limits, claim edits, denials, and contracted reimbursement arrangements. The exact complexity varies by organization and payer.
The behavioral health revenue cycle includes the financial and operational processes associated with getting paid for services. It can begin with patient registration and insurance verification and continue through authorization, service delivery, documentation, claim preparation, submission, payer adjudication, remittance, denial management, patient responsibility, and payment review.
Claim scrubbing is the process of checking claim information for potential errors or inconsistencies before submission. Depending on the system, validation may include patient information, payer data, provider information, coding, modifiers, authorization, and other claim requirements.
A rejected claim generally fails before full adjudication because the claim cannot be accepted for processing. A denied claim generally reaches adjudication but the payer determines that some or all of the claim will not be paid. Exact terminology and workflows can vary by payer and clearinghouse.
An Electronic Remittance Advice, or ERA, is an electronic explanation of how a payer processed healthcare claims. It can contain payment, adjustment, denial, and patient-responsibility information and is commonly associated with the HIPAA 835 transaction.
Prior authorization is a payer process that may require approval before certain services are provided or continued. Depending on the payer and service, authorization may specify approved visits, units, days, dollars, dates, or levels of care.
Organizations can improve billing workflows by verifying insurance information, understanding authorization requirements, maintaining complete documentation, validating claims before submission, monitoring payer responses, systematically working denials, and reviewing reimbursement against applicable payer agreements.
Evaluate the entire revenue cycle rather than claim submission alone. Consider eligibility, benefits, prior authorization, utilization, documentation readiness, claim validation, electronic submission, remittance, rejection and denial workflows, payer contracts, patient balances, reporting, integrations, and support for your organization’s levels of care.
Connect the Revenue Cycle
Bring ProbityCare one of the revenue-cycle workflows creating friction inside your organization: an expiring authorization, incomplete documentation, a rejected claim, a denial, or a payer underpayment. We'll show you how the workflow can move across clinical, utilization, billing, and financial operations inside ProbityCare.
Thirty minutes, your workflows, no slides.