One Medicaid program, five managed care plans, five rulebooks: a working guide for behavioral health providers

Say a 40-person program in a state with four Medicaid managed care plans and a carved-out behavioral health plan for some services. On paper, that is one payer: Medicaid. In the billing office it is five. One plan wants IOP authorized by fax with its own form, another through a portal, a third does not require authorization for the first few visits at all. One plan finished credentialing your new LCSW in six weeks; another still shows her as pending, so every session she runs for its members is a claim you cannot send. A member switched plans on the first of the month, nobody noticed, and three weeks of residential days went to the wrong payer. None of this is unusual, and none of it is solved by working harder. It is solved by treating each plan as a separate payer with written rules, and by keeping those rules where intake, clinicians, utilization review and billing all see them.

Why one Medicaid program behaves like several payers

Most states deliver some or all Medicaid benefits through managed care. The state contracts with managed care organizations, and in some states with prepaid inpatient or ambulatory health plans, to cover a defined set of services for enrolled members. Federal rules for those arrangements sit in 42 CFR Part 438, which sets the floor: network adequacy, provider selection, coverage and authorization standards, grievance and appeal rights for members, and mental health parity requirements. Inside that floor, each state writes its own contracts, and each plan writes its own policies and provider manual.

For a behavioral health provider, the practical result is layered:

• The state defines the benefit, publishes a Medicaid billing manual or fee schedule, sets which services are covered, and enrolls providers.
• Each plan decides how it credentials, which services it authorizes and how, what its claims edits look like, how it pays and how it handles disputes, all within the state contract.
• Carve-outs may move some behavioral health or substance use services to a separate plan, a regional entity or fee-for-service Medicaid, while physical health stays with the member's main plan. Which services are carved out, and for whom, is a state decision and changes over time.
• Specialty arrangements such as plans for children in foster care, members with serious mental illness, or members eligible for both Medicare and Medicaid may follow different rules again.

The first operational job is to know exactly which of these layers apply to your programs in your state, for each level of care you deliver. The state Medicaid agency's provider pages and each plan's provider manual are where that answer lives. Confirm it in writing rather than from a colleague's memory of how it worked two contracts ago.

Build a payer profile for every plan before you need it

The single most useful document in a Medicaid-heavy billing office is a profile per plan. Not a tab in a spreadsheet that one person updates, but a structured record everyone works from. At minimum it should carry:

• Plan name, payer ID used by your clearinghouse, and the lines of business it covers in your state.
• Your contract status and effective date, the billing entities and locations covered, and the levels of care included in the contract.
• Which services require prior authorization, by level of care, and how requests are submitted: portal, fax, phone or electronic transaction.
• The medical necessity criteria the plan applies, and the documentation it expects with an initial request and with continued-stay review.
• Claim form by service, plan-specific coding or modifier requirements, rendering provider rules, and the timely filing limit stated in your contract.
• How corrected claims, reconsiderations and appeals are submitted, and the deadlines your contract sets for each.
• Provider relations, utilization management and claims contacts, with the date each was last confirmed.
• The contracted rate for each code or per-diem, so payments can be checked against it.

Every field should have a source: the contract page, the provider manual section, the bulletin date. When a plan changes a rule, the profile changes and the old version is kept with its effective dates. That history matters later, when you are defending a claim from eight months ago and the rule has since moved.

Enrollment: the state first, then each plan

Under federal managed care rules, the state must screen and enroll the network providers of its Medicaid managed care plans, and periodically revalidate them. In practice that usually means two separate processes: enrollment with the state Medicaid agency, and credentialing and contracting with each plan you want to see members from. How your state sequences them, and whether one enrollment feeds the other, varies. Confirm the order with the state agency and each plan before you start a new clinician or a new site.

What has to be enrolled

Behavioral health organizations get caught because enrollment is not one thing. Depending on the state and the plan, any of these may need its own enrollment or record:

• The organization as a billing entity, under its tax ID and organizational NPI.
• Each service location, particularly when levels of care are licensed by site.
• Each level of care or program type, which some states enroll separately.
• Each rendering clinician, linked to the billing entity and the locations where they work.
• Supervised or pre-licensed clinicians, whose billing rules may differ by plan and by state.
• EDI submission, electronic remittance and electronic funds transfer, often enrolled per plan through your clearinghouse.

A clinician can be enrolled with the state, credentialed with three plans, pending with the fourth and never submitted to the carve-out entity. Each of those is a separate status with its own effective date. Track them separately, by plan, rather than as one global flag that says the clinician is credentialed. The existing post on proving eligibility on the date of service covers why the effective date matters more than the current status.

Effective dates decide which claims you can send

Ask every plan the same question in writing: from what date may this clinician render services to your members under our contract? Some plans will allow retroactive effective dates; others will not. Some backdate to the application, some to the approval. Your contract and the plan's policy decide, and the answer determines whether the sessions your new hire ran in her first month are billable or written off. Scheduling should know the answer before the session is booked, not after the claim rejects.

When clinicians join, move or leave

Build a checklist that fires on every staffing change, because each one touches Medicaid enrollment:

1. New hire: submit state enrollment if required, then each plan's credentialing, and record every submission date and reference number.
2. Added location or level of care: confirm whether each plan needs the clinician linked to the new site or program.
3. License change, such as a pre-licensed clinician becoming fully licensed: update the state and every plan, and confirm the new effective date for billing at the new credential.
4. Departure: notify the state and each plan as your contracts require, and keep the history so claims for past dates of service still trace to a valid enrollment.

Eligibility: which plan, on which day

For a commercial patient, eligibility asks whether coverage is active. For a Medicaid member, there is a second question that causes more trouble: which plan is responsible for this date of service. Members can change plans at enrollment windows, be reassigned by the state, lose and regain coverage, or have coverage applied retroactively. A member can also be in fee-for-service Medicaid for a period before plan enrollment takes effect, or have certain services carved out to a different entity.

Operationally, that means:

• Check eligibility at intake and record the plan, member ID and effective dates, not just an active flag.
• Re-check at a regular interval across the whole active census. Monthly is a common choice for long episodes because plan assignment often changes on the first of a month; set your own interval based on your state's rules and your payer mix.
• Re-check when the patient reports a new card, a change in household or income, or a letter from the state, and before every level-of-care transition.
• Confirm whether the service you are about to deliver is covered by the plan, carved out to another entity, or paid fee-for-service by the state.
• If the member also has Medicare or commercial coverage, establish the order of benefits before you bill. Medicaid is generally the payer of last resort, and plans will deny or recoup claims where other coverage should have paid first.

The verification of benefits post covers what an eligibility response can and cannot tell you. For Medicaid, add one rule: a plan change discovered after the fact is not just a billing problem. The new plan probably did not authorize the care you have been delivering.

Authorization rules that differ by plan

Federal rules require Medicaid managed care plans to have written policies for authorizing services, to apply review criteria consistently, to have decisions to deny or reduce a service made by someone with appropriate clinical expertise, and to give members notice of adverse decisions. Within those requirements, plans differ widely, and the differences are where days go unpaid.

What usually differs

• Which services need authorization at all. One plan may authorize outpatient therapy after an initial number of visits, another not at all, another from the first visit. Residential and PHP almost always need authorization, but the details vary.
• What the authorization counts. Days, units, visits, dollars or a date range, and whether units are counted per service, per day or per program week.
• Criteria. Many plans reference the ASAM Criteria for substance use services; others use proprietary or state-specified criteria. Which edition a plan uses matters when level numbers changed between editions.
• Submission method and forms. Portal, fax, phone or electronic transaction, and the specific clinical information the plan wants attached.
• Concurrent review cadence. How often continued stay must be reviewed for residential, PHP or IOP, and how much lead time the plan expects before the last authorized day.
• Level-of-care transitions. Whether a step-down from residential to PHP needs a new request, a modification or a fresh initial review.
• Retroactive authorization. Whether the plan will authorize after the fact for an urgent admission, and on what conditions.

State rules may also set standard and expedited decision timeframes, notice requirements and continuity-of-care obligations when a member transitions between plans. Confirm the timeframes that apply to you in your state contract and the plan's provider manual rather than assuming the federal floor or another state's practice.

Turn plan rules into rules on the record

The failure pattern is familiar: the utilization review coordinator knows that one plan needs IOP reviewed every two weeks and another every month. She goes on leave. Nobody else knows. The fix is to make each plan's authorization rules data, attached to the patient's coverage, so that when a member of a given plan is admitted to a given level of care, the system or the workflow knows:

1. Whether authorization is required before the first service.
2. What unit the authorization will be expressed in, so utilization is counted correctly as services are delivered.
3. When the next review is due, based on that plan's cadence and lead time, with an owner and a due date.
4. What documentation that plan expects for the review, so the clinical team can produce it before the call rather than during it.

The utilization review guide covers the review cycle itself. The point here is narrower: the rule that triggers the work should come from the plan profile, not from someone remembering it.

When the member changes plans mid-episode

Say a residential patient's Medicaid assignment moves from one plan to another on the first of the month, and your monthly eligibility run catches it on the third. Treat this as an authorization event, not a billing one. Contact the new plan, ask what continuity-of-care provisions apply to members in active treatment, request authorization for the remaining stay, and confirm whether your clinicians are credentialed with the new plan. Bill the days before the change to the old plan under its authorization, and the days after to the new plan under its own. Document every call with the date, the representative and the reference number. If the new plan will not cover a transition period, you want to know on the third, not on the remittance.

Claims: the same service, a different claim

Medicaid claims follow the same HIPAA standard transactions as every other payer, the 837P for professional services and the 837I for institutional services. What changes by state and plan is what goes inside them.

Where plan claims differ

• Codes and modifiers. States often specify HCPCS codes, modifiers or revenue codes for behavioral health services, including codes used only in that state's Medicaid program. Plans generally follow the state's coding, but some add their own requirements. Work from the state billing manual and each plan's billing guidance.
• Claim form by level of care. A service billed on a UB-04 by one plan may be billed on a CMS-1500 by another, depending on how the contract defines it.
• Rendering and supervising provider. Whether the individual clinician must appear on the claim, and how supervised clinicians are reported, varies by state and plan.
• Place of service and telehealth. Telehealth modifiers and place-of-service codes for Medicaid can differ from Medicare and commercial rules, and from plan to plan.
• Authorization number. Some plans require it on the claim; others match it on their side.
• Timely filing. The window is set by your contract and state rules, and it can differ between plans and between original and corrected claims.
• Corrected and replacement claims. Frequency codes, required original claim references and whether a correction must go through a portal rather than as an electronic replacement.

Scrub against plan rules, not generic rules

A generic claim scrubber catches format errors. The expensive Medicaid errors are relational: the clinician is not credentialed with this plan for this date, the authorization belongs to the previous plan, the modifier is the one the other plan wants, the service is carved out. Your pre-submission checks should read from the plan profile and the patient's coverage for that date. The claim scrubbing post walks through checks worth building; for Medicaid, add a plan-and-date check on every claim: does the plan on this claim match the plan responsible for this member on this date of service?

Remittances, denials and disputes, read by plan

Every plan sends an 835 with standard claim adjustment reason codes and remark codes, but plans use those codes differently. One plan's code for missing authorization might be another plan's code for a provider not on file. Read denials by plan before you decide on the fix.

Group denials by plan and reason

A denial report that only groups by reason code hides the pattern you need. Group by plan, then reason, then the upstream owner. If one plan keeps denying for provider not enrolled, the fix is in credentialing for that plan. If another keeps denying for authorization, check whether your plan profile has the right rule for that level of care. The five denial reasons post covers what each category is telling you; with Medicaid, the same category often points to a different workflow failure for each plan.

Know the difference between a member appeal and a provider dispute

Federal managed care rules give members a grievance and appeal process for adverse benefit determinations, such as a denial or reduction of a requested service. Provider claim disputes, reconsiderations and payment appeals are usually governed by your contract, the plan's provider manual and state rules. They have different forms, different deadlines and sometimes different addresses. Some states also offer providers an external review or state-level dispute route. Write each plan's process into its profile, including who in your organization files what, and calendar every deadline the day the denial posts.

Check payments against the contract

Medicaid rates are often set by fee schedule, but plan contracts can differ from the state schedule, rates change when the state updates its fee schedule, and plans do not always load the change on the same day. Compare every payment line to the contracted rate for that plan and code. A plan paying last year's rate after a fee schedule update shows up as a quiet underpayment across hundreds of claims. The contract rate variance post covers how to work them.

Tracking it all without a spreadsheet per payer

The spreadsheet-per-payer approach fails for a predictable reason: each spreadsheet holds part of the truth, and no single screen holds the combination that decides whether a service is billable. Whether a session on Tuesday can be billed depends on the member's plan that day, that plan's authorization for that level of care, the clinician's enrollment with that plan, and that plan's claim rules. Four spreadsheets, four owners, one claim.

Whatever system you use, aim for these properties:

• One record per patient that carries coverage history with plan and effective dates, so every service date maps to a responsible payer.
• Authorizations attached to coverage, with the unit type, remaining utilization and expiry visible where scheduling happens, not only in billing.
• Provider enrollment by plan, location and effective date, checked when a session is booked and again before the claim is built.
• Plan rules stored once and used by intake, utilization review and billing alike, with version history.
• One work queue for denials, expiring authorizations, pending enrollments and eligibility changes, each item carrying a plan, a deadline and a named owner.
• Reporting by plan: first-pass acceptance, denial reasons, days in accounts receivable and authorization lapses for each plan, so you can see which relationship needs attention. The revenue cycle KPIs article covers how to count them consistently.

A worked example, from inquiry to remittance

Take a hypothetical IOP in a state with three Medicaid plans, labeled here A, B and C. A referral comes in on a Monday.

1. Intake. Eligibility returns active Medicaid with Plan B, effective the first of the month. Intake records the plan, member ID and dates on the record, not on a sticky note.
2. Plan rules. Plan B's profile says IOP requires authorization before the first day, expressed in program days, with continued-stay review due before the last authorized day and a stated lead time in its manual. Utilization review submits the initial request through Plan B's portal and logs the reference number.
3. Staffing. The group facilitator for Thursdays is credentialed with Plans A and C but pending with B. Scheduling sees the conflict and moves the patient to a group run by a clinician enrolled with B, rather than discovering it on a rejection three weeks later.
4. Service and documentation. Attendance and notes are completed per the program's documentation rules. Each attended day counts against the authorization.
5. Review. The continued-stay review is created automatically from Plan B's cadence, with an owner and a due date ahead of the last authorized day.
6. Monthly eligibility run. On the first of the next month, the member shows as moved to Plan C. Utilization review contacts Plan C the same day about continuity of care and a new authorization, and confirms the patient's clinicians are enrolled with C.
7. Claims. Days before the change bill to Plan B with B's codes and authorization; days after bill to Plan C with C's. Pre-submission checks confirm plan, date, authorization and rendering provider match.
8. Remittance. Plan C pays two days below contract. The variance is flagged against C's rate, and the denial-and-variance queue assigns it to the billing lead with C's dispute deadline attached.

Nothing in that sequence is clever. It works because every decision reads from the same plan profile and the same patient record.

A maintenance routine that keeps the profiles honest

Plan rules drift. A short routine keeps your profiles accurate without turning into a project.

Weekly

• Read each plan's provider bulletins and portal announcements, and update the affected profiles with the effective date.
• Review pending enrollments by plan and follow up on any that have not moved since the last check.
• Work the queue of authorizations approaching their last day or unit.

Monthly

• Run eligibility across the active census and act on every plan change the same day.
• Review denials by plan and reason, and assign each recurring pattern to an upstream owner with a fix and a date.
• Compare payments to contract rates by plan and total the variance.

Quarterly and at renewal

• Reconfirm contacts, payer IDs and submission addresses for each plan.
• Re-read each plan's provider manual sections on authorization, claims and disputes, and reconcile them against your profile.
• Check revalidation and recredentialing dates with the state and each plan, for the organization and every clinician.
• Before adding a level of care or site, confirm what each plan needs; the new level of care checklist covers the rest of that work.

Where software fits

None of the above requires a particular product. It requires that plan rules, coverage history, provider enrollment and authorizations live where everyone can see them together. If you want that on one record, Unisona Health tracks authorized visits, units, dollars and expiry on the patient's coverage through prior authorizations, and tracks licenses and payer enrollments with escalation before they lapse through credentials and licensure. Whatever you use, start this week by building the profile for your largest Medicaid plan, and see how many of its fields your team can fill in from a source rather than from memory.

Frequently asked questions