Percent-of-Charge Contracts: Why Some Rates Resist Benchmarking

Most conversations about rates assume a rate is a number — a fixed amount you can line up against another fixed amount. Percent-of-charge contracts break that assumption, and they break it in a way that quietly corrupts naive benchmarking. If you've ever tried to compare a percent-of-charge arrangement to a per diem and felt like you were comparing things that don't belong on the same axis, you were right. This post explains why. (For the full set of contract structures, start with the billing grammar of behavioral health.)

What percent-of-charge means

Under most contract structures, the negotiated rate is a fixed amount: a per diem pays a set amount per day, a case rate pays a set amount per episode. A percent-of-charge contract works differently. It defines payment as a percentage of the facility's billed charges rather than as a fixed negotiated figure.

The consequence is subtle but important: the "rate" isn't a standalone number you can read off a file. It's a ratio. The actual dollars only exist once you also know the charge it's applied to. Two facilities on the same percent-of-charge terms can be paid very differently, because their billed charges differ.

Why it exists

Percent-of-charge arrangements persist for practical reasons. They're simple to state, they flex automatically as charges change, and in some situations they're the structure the parties land on rather than negotiating a fixed schedule line by line. They're a normal part of the contracting landscape — one of the structures a behavioral health facility contract can take, alongside per diems, case rates, bundled arrangements, and fee-for-service.

The point here isn't that percent-of-charge is good or bad. It's that it's structurally different — and that difference is exactly what a naive rate comparison ignores.

The benchmarking problem

Here's where it bites. Suppose you pull what looks like a peer's rate and it's a percent-of-charge figure. You want to compare it to your per diem. You can't — at least not directly. A percentage of billed charges and a fixed amount per day aren't the same kind of quantity. Lining them up as if they were is a category error: you'd be comparing a ratio to a dollar figure and treating the result as meaningful.

This is the same trap that makes a raw rate lookup misleading in general. The billing code can be identical; the structure underneath is not. A percent-of-charge rate, a per diem, and a case rate can all sit in the same column of the same file and describe fundamentally different economics. Without the structure — and, for percent-of-charge specifically, without the charge context — the number tells you less than you think.

Why honest rate intelligence treats these differently

The wrong response to this is to force everything into one number so the comparison looks clean. That's how you get benchmarks that are tidy and wrong. The honest response is to recognize that not every rate reduces to the same unit, and to treat structurally different rates as structurally different.

This is one of the reasons rate data has to be confidence-scored rather than taken at face value. Part of scoring how much to trust a number is recognizing when a number can't be directly compared to another — when a percent-of-charge figure shouldn't be silently averaged in with per diems as though they were interchangeable. A rate you can defend is one that's been read in its own structure, not flattened into a false common denominator.

The rates stay real — actual negotiated terms, never modeled estimates. What good intelligence adds is the honesty to say "this one is a percent-of-charge arrangement and doesn't line up cleanly with those per diems," rather than pretending the mess resolves itself. The Coverage & Methodology page lays out that read-in-context approach.

The takeaway

If a rate resists comparison, that's often information, not a defect. Percent-of-charge contracts resist naive benchmarking by design — they're ratios, not fixed amounts, and they only become dollars once a charge is attached. Treat them as their own thing, and you avoid the category error that quietly undermines a lot of do-it-yourself rate analysis.

See your rates read in context

Benchmarking that respects structure — including the rates that don't reduce to a single number — is what TierBench is built for. See which payers we hold rate data on, read the rate-data FAQ, or book a 20-minute call to talk through your contracts.

---

← Back to all posts