Reference-based pricing is a different answer to the same question a fee schedule answers: what does the plan pay for this code? A fee schedule gets that number from a negotiated network contract. RBP gets it from a public benchmark instead — most commonly a defined multiple applied to what a government program would pay for the same procedure code, applied uniformly across providers regardless of whether any of them have agreed to it. There’s no network in the traditional sense; the plan is telling every provider, in advance, what it will pay, rather than negotiating that number contract by contract.
The plan-defined table that sets that multiple — a rate per code, built off a Medicare-percentage benchmark instead of a network contract — is, mechanically, a fee schedule; a fee schedule can itself be built from a public benchmark rather than a negotiated rate. What makes RBP a distinct pricing model isn’t the table, it’s what’s missing behind it: no negotiated network agreement, and no provider who signed anything agreeing to accept that rate as payment in full. That absence — not the existence of a rate table — is the real difference between RBP and a fee schedule, and it’s what drives the balance-billing exposure below.
How it changes the pricing path
Under a fee schedule model, the allowed amount comes from a contract the provider signed — the provider agreed to accept that rate, and the gap between billed and allowed becomes a write-off they’re contractually bound to absorb. Under RBP, the plan sets the allowed amount unilaterally from the benchmark, and the provider never agreed to accept it as payment in full. That’s the structural difference that matters: RBP can produce real savings against inflated billed charges, but because the provider isn’t contractually bound the way an in-network provider is, the gap between billed and allowed under RBP behaves like an out-of-network gap even when the plan intends the provider relationship to function like an in-network one.
A worked example
A plan runs RBP at 160% of the applicable government benchmark rate for inpatient procedures. A hospital bills $40,000 for a procedure where the reference benchmark is $9,000 — the RBP allowed amount comes out to $14,400 (160% of $9,000). The member’s coinsurance is 20% after deductible.
| Amount | |
|---|---|
| Billed | $40,000 |
| RBP allowed amount (160% of benchmark) | $14,400 |
| Plan pays (80% of allowed) | $11,520 |
| Member coinsurance (20% of allowed) | $2,880 |
| Gap between billed and allowed | $25,600 |
The plan’s cost-sharing math is clean — $2,880 in coinsurance, calculated the same way it would be against any allowed amount. But because the hospital never contracted to accept $14,400 as payment in full, that $25,600 gap is exposure the member could see billed directly, the same mechanic as any other balance billing situation — RBP doesn’t eliminate that risk, it just changes where the allowed amount comes from.
Why this matters operationally
RBP plans generally pair the pricing model with member-advocacy or provider-negotiation support specifically because the balance-billing exposure is real and needs active management — a plan running RBP with no downstream support for members who get balance billed is exporting a savings win on paper into a member relations problem in practice. For a self-funded employer plan evaluating RBP against a traditional network, the tradeoff is lower and more predictable plan-side costs against a pricing model that requires more active handling of the gap it creates. A claims adjudication engine that can price against a configured RBP benchmark as its own defined pricing source — distinct from a fee schedule and from U&C — keeps that allowed amount consistent and traceable claim to claim, which matters when a member or provider disputes how the number was derived.