Payer contract

What a payer contract is

A payer contract is the legal and operational rulebook between your organization and a health plan. It defines reimbursement rates, covered and excluded services, prior authorization requirements, billing rules, and timelines for filing and payment. For behavioral health, this can include per-diem rates for residential or PHP/IOP, distinct rules for therapy codes, and special terms for state-funded or Medicaid-managed programs.

The contract is different from a benefits verification response. Eligibility tells you what the member has on paper, while the contract says what the payer will actually pay you for and under what conditions. When there is a conflict, the signed contract usually controls payment, which is why underpayments and many denials trace back to contract language.

Why payer contracts matter operationally

Every core RCM metric ties back to payer contracts: allowed amounts, contractual write-offs, denial patterns, and days in AR. If a per-diem rate, CPT fee, or revenue-code allowance is misconfigured relative to the contract, you either leave money on the table or create avoidable balance issues and rework.

Key operational points buried in payer contracts typically include:

• Reimbursement method (per diem, case rate, fee schedule, percent of charges)
• Required authorizations and concurrent review triggers
• Timely filing limits and appeal deadlines
• Documentation or modality rules for behavioral and telehealth services
• Carve-outs for substance use, residential, or other specialty programs

Ignoring these terms leads directly to CO-45 and CO-29 write-offs, CO-197 denials past the authorized units or days, and N130 remark codes when a service is not covered under the agreement. Over a year, that can mean hundreds of thousands in lost revenue or labor chasing money the payer is not obligated to pay.

How to read and use payer contracts day-to-day

Operationally, payer contracts should not live in a drawer. They need to be translated into concrete billing rules in your practice management or clearinghouse configuration, and into simple playbooks for front desk, UR, and billing teams.

When reviewing a contract, RCM and leadership should focus on:

• Rates and methodologies: Per-diem amounts by level of care, CPT/HCPCS fee schedules, and any bundled services.
• Authorization and utilization rules: When prior auth is required, what triggers concurrent review, and unit/day limits that create CO-197 denials.
• Coverage and exclusions: Residential, MAT, group therapy, telehealth, and any modality that has special conditions or is excluded.
• Filing and appeal timelines: Timely filing limits, reconsideration windows, and how to request underpayment corrections.

Once you extract those rules, configure them in your system: payer-specific fee schedules, place-of-service and revenue-code mappings, required modifiers, and alerts for auth limits. Then use the contract language when you appeal denials or underpayments. The more concrete your appeal is against the actual contract sections, the higher your success rate.

• Not loading the contracted per-diem rate for residential or PHP into your system, so you accept the payer's lower allowed amount on the 835 as correct instead of appealing underpayments tied to CO-45 adjustments.
• Ignoring behavioral health carve-outs in the contract and sending residential or SUD claims to the medical plan, which leads to repeated claim reroutes, N130 remark codes, and long AR while the carve-out vendor never receives a clean 837.
• Skimming over the prior authorization section and missing that IOP or residential requires concurrent review after a set number of days, so days 11+ deny as CO-197 even though the front desk confirmed eligibility.
• Treating per-diem contracts like fee-for-service and billing line-item CPT codes alongside the per-diem revenue code, which triggers NCCI edits or CO-97 bundling denials that look like payer error but are actually contract violations.
• Failing to update internal fee schedules and front-end checks when a contract is amended, so the team continues to quote outdated patient responsibility and appeal underpayments using obsolete rate tables.

Behavioral health payer contracts often carve SUD, residential, and intensive outpatient services away from the main medical plan into specialized vendors or state agencies. That means your front-end must know which entity is contractually responsible before you ever submit an 837, or you can lose 60 to 90 days bouncing between payers during which some timely filing clocks may be running.

Long episodes and per-diem structures are common in behavioral health contracts for residential, PHP, IOP, and withdrawal management. Contracts frequently include step-down requirements, daily or weekly unit caps, and concurrent review rules that cut off payment after a set number of days without updated clinicals. Clean claims can still deny for days 21 to 30 if UR misses a concurrent review requirement hidden in the utilization section.

State Medicaid and Medicaid managed care contracts add another layer. Behavioral carve-outs, separate rules for room-and-board components, and distinct revenue codes for detox versus residential can all live in separate exhibits. If you misinterpret which services are included in the per diem versus billable separately, your team can either underbill for legitimate therapy time or trigger CO-97 and CO-45 adjustments when payers apply their contract bundling logic.

For telehealth and hybrid care, behavioral contracts may have different rates, covered CPT codes, and modifier rules than in-person services. If your team follows generic telehealth guidance instead of the actual contract exhibits, you can see systemic underpayments or denials that look like policy problems but are really contract compliance issues.

AI can help with payer contracts by reading long, dense agreements and extracting the pieces that matter operationally: per-diem and fee-for-service rates, required modifiers, timely filing limits, and when prior auth or concurrent review is needed. Those extracted rules can feed directly into eligibility workflows, billing edits, and denial analytics so the team catches issues at scheduling or claim-scrub time instead of after the 835 arrives.

Supabill's agents can store payer-specific contract rules and apply them in real time: the benefits-verification agent can flag when a member's behavioral benefits sit with a carve-out vendor, and the claims-scrubbing agent can compare your claim structure to contracted requirements for place of service, revenue codes, and auth span. A denials agent can read every remittance, classify CO-45, CO-29, CO-197, and N130 adjustments against the contract, and surface patterns that justify renegotiation. Humans still need to interpret ambiguous language, negotiate rates, and decide when to escalate disputes beyond standard appeals, since those moves depend on strategy and payer relationships, not just text in the contract.

Is a payer contract the same as being in-network?

Being in-network usually means you have a signed payer contract and the plan lists you in its provider directory. The contract defines your reimbursement rates and obligations, while the in-network label is what members see and what drives lower patient cost sharing. Source

Do I need a payer contract to bill out-of-network?

No, you can bill out-of-network without a payer contract, but payment will follow the plan's out-of-network rules instead of a negotiated fee schedule. That typically means higher patient responsibility, more balance-billing issues, and less predictability in allowed amounts.

Who should have access to payer contracts in a behavioral health organization?

Leadership, RCM leads, utilization review staff, and anyone configuring billing systems should have access to current contracts and amendments. Front office and clinical teams do not need the full legal document, but they do need simple summaries of auth rules, covered services, and referral requirements.

How often should behavioral health payer contracts be reviewed?

At minimum, review contracts annually or any time you add new levels of care, new locations, or new service lines like telehealth IOP. You should also review them when denial patterns or underpayment trends show up in your reports, since those often point to misaligned configuration or outdated terms.

What should I do if a payer pays less than the contracted rate?

Compare the 835 allowed amount to your stored fee schedule and the contract language, then submit an underpayment inquiry or appeal that cites the specific contract section and expected rate. Include sample claims and remittances, and track responses to catch systemic underpayments that may justify a broader audit. Source

• CMS, Managed Care
• Healthcare.gov, Provider networks
• HFMA, Managed care contracting resources