A fee schedule is the plan’s answer to “what do we pay for this code,” decided in advance instead of negotiated claim by claim. It’s a table: procedure code (CPT, HCPCS) mapped to a dollar rate, built either from a network contract the provider signed, a plan-defined rate the sponsor set unilaterally, or a public benchmark like a Medicare fee schedule percentage used as the pricing basis. When a claim comes in for a code that’s on the applicable fee schedule, that rate — not the amount billed — is what the claim prices against.
How it prices a claim
At adjudication, pricing runs as a lookup: match the billed code (and often the provider or provider’s network) against the fee schedule that applies to this claim, and if there’s a match, that rate becomes the allowed amount cost-sharing calculates from. A $300 billed charge against a $180 contracted rate prices at $180 — the $120 difference is the network write-off, not something the member owes, because the provider agreed to that rate as a condition of being in-network. The fee schedule is what makes that write-off possible in the first place; without a contracted rate on file, there’s nothing to write off against.
A worked example
A provider bills CPT 99213 (an established-patient office visit) at $180. Two different claims, two different fee schedule situations:
- In-network claim: the provider’s contracted fee schedule rate for 99213 is $95. The claim prices at $95. The $85 gap between billed and contracted is the provider’s write-off. Cost-sharing applies to the $95.
- Same code, no fee schedule match: an out-of-network provider bills the identical code, but has no contracted rate on file with this plan. There’s nothing to look up — the claim falls through to a usual-and-customary benchmark instead, and the pricing (and the balance-billing exposure that comes with it) follows a different path entirely. See usual and customary for how that fallback pricing actually works.
Per-client fee schedules in a TPA context
A single-plan operation typically runs one fee schedule, maybe a few for different networks. A TPA doesn’t have that luxury: every client group on the book can carry its own negotiated rates, its own network, and its own plan-defined pricing for codes outside any network contract — and those schedules have to stay fully isolated from each other. A rate negotiated for Client A’s network has no business pricing a claim for Client B, even if both clients’ claims run through the same adjudication engine on the same platform. Getting this wrong isn’t a cosmetic bug; it means a client either overpays because the system reached for the wrong rate, or a provider gets underpaid against a contract they actually hold.
Why this matters operationally
The fee schedule is upstream of almost every dollar figure that follows it — the allowed amount, the write-off, the member’s cost-share, the EOB line items. A claims adjudication engine that prices against the correct fee schedule first, with usual-and-customary as a defined fallback only when no schedule applies, is what keeps pricing consistent and auditable claim to claim. For a TPA running multiple client books, per-client fee schedule isolation is one of the concrete features that separates multi-client-capable software from single-plan software with client folders bolted on.