Most-favored-nation clause

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

The comparison rule lives in the contract

The FTC's competition guidance describes an MFN generally as a promise to treat one party at least as well as others. In a payer agreement, the clause may compare reimbursement, discounts, payment terms, product participation, value-based terms, or another negotiated benefit.

Read the full definition. A clause may apply to one code, a service category, all covered services, one product, affiliated plans, government programs, commercial payers, self-pay, or a named geographic market. It may compare gross rates, effective rates after incentives, or a package of terms.

The NAIC state insurance department directory helps locate the relevant regulator. It does not interpret a contract or compile every state restriction. Counsel should check current insurance, provider-contract, antitrust, Medicaid, and other applicable authority.

Seven questions reveal practical scope

For each clause, record:

1. Protected party: Which payer, affiliate, network, or product receives the promise?
2. Comparator: Which other payer, buyer, product, region, or class is compared?
3. Term: Does it cover rates, discounts, timing, bundles, incentives, or nonprice terms?
4. Trigger: Is comparison based on an offer, signed agreement, effective rate, paid claim, or another event?
5. Exceptions: Are Medicaid, Medicare, grants, pilots, self-pay, value-based arrangements, or distressed contracts excluded?
6. Action: Must the provider notify, offer an amendment, reduce a rate, repay money, or permit termination?
7. Period: When does the promise start, end, survive, or reset?

Do not compare headline fee-schedule numbers alone. Different codes, unit conventions, modifiers, timely-filing rules, utilization terms, patient mix, and administrative burden can change economic value.

MFNs can have different competitive effects

The FTC says MFNs often reduce contracting risk, while some circumstances can limit targeted discounts or create a de facto price floor. In a 1996 pharmacy-network matter, the agency challenged a clause that it alleged discouraged pharmacies from accepting lower reimbursement elsewhere in a highly concentrated network. The settlement did not declare every MFN unlawful.

Market share, bargaining power, clause design, competitors, state law, and actual effect matter. An ABA practice should avoid exchanging current or future payer rates with competing providers. Route competition questions to qualified counsel using the exact clause and market facts.

A fictional contract review

North Valley ABA reviews four reimbursement arrangements before offering a lower rate for a new pilot. Its MFN matrix finds two agreements inside the defined comparator group, one government program expressly excluded, and one clause whose affiliate definition is unclear.

The team reports 2 of 4 included, 1 of 4 excluded, and 1 of 4 escalated. It does not call the pilot safe based on a 50% inclusion rate. Counsel resolves the fourth contract, the payer-contracting owner calculates comparable economics, and an authorized executive decides whether to proceed.

If the new rate triggers notice under an included agreement, the practice follows the clause's timing and delivery method. It preserves the proposed terms, comparison analysis, legal advice, approval, notice evidence, payer response, and any amendment.

Build an MFN register

Use one row per payer, product, entity, state, and contract version. Capture the clause text, defined terms, comparison method, exclusions, effective dates, survival, notice address, owner, counsel interpretation, and next review trigger.

Connect the register to contract intake and amendment review. A new fee schedule, single-case agreement, prompt-pay discount, value-based incentive, or self-pay change can create a review event. Software may surface potential conflicts; authorized contracting and legal roles decide meaning and action.

Test a proposed change against a small scenario grid before approval. Vary payer, product, entity, code, geography, effective date, discount type, and total economics. Record whether the scenario is included, excluded, ambiguous, or requires notice. Escalate ambiguity before the new rate becomes effective.

Protect the register as confidential contracting information. Use internal need-to-know access and avoid sharing one payer's rates or strategy with competing providers. Aggregate board reporting where practical and retain the underlying contract evidence for the authorized review team.

Useful measures include active agreements screened for MFN language divided by active agreements; potential triggers reviewed before effective date divided by triggers due; and required notices delivered with evidence by deadline divided by notices due. Report unresolved contracts and dollars at risk separately.

Negotiation points deserve plain language

Ask whether the clause can be removed, narrowed to comparable products, limited to named codes, based on signed effective arrangements, or paired with clear exclusions and a cure process. Seek a practical end date and exclude rates imposed by law or government programs where appropriate.

Price is only one term. Review audit, recoupment, termination, amendment, confidentiality, data, dispute, and assignment provisions together. A favorable fee schedule can lose value when another clause expands the comparison or remedy.