Payment Integrity vs. Prospective Rate Benchmarking: What's the Difference?

"We already have a payment integrity and network benchmarking solution." It's one of the most common reasons a benefits benchmarking conversation stalls, especially at a broker that just got absorbed into a larger consultancy with its own enterprise analytics stack. It's also usually based on a real but incomplete picture: payment integrity and prospective rate benchmarking solve two different problems, and having one doesn't mean you have the other.

Here's the distinction, because "we already have that" is worth testing before it ends a conversation.

The proof: these tools answer different questions, at different points in time

Payment integrity is retrospective. It looks at claims that have already been paid and asks whether they were paid correctly: pre-pay edits, post-pay audits, duplicate billing detection, coordination-of-benefits checks, fraud detection. The action it produces is denying, adjusting, or clawing back a specific incorrect payment. It's essential, and it's a real capability an enterprise parent's actuary team is likely to have in-house, because it runs on the parent's own claims data.

Prospective rate benchmarking is forward-looking. It answers a different question entirely: before you sign anything, what should this plan cost, based on what real carriers are actually negotiating for these procedures at these hospitals, for comparable employers? It has nothing to do with whether a claim was processed correctly. It has to do with whether the underlying contracted rate was ever competitive in the first place.

A concrete way to see why this distinction matters: pull the negotiated-rate distribution for a single, common procedure code across hospitals that publish their actual rates under CMS's price transparency rule. For total knee arthroplasty (CPT 27447) across 324 hospitals reporting that code, the median negotiated rate is roughly $21,700, with the middle 50% of hospitals ranging from about $12,200 to $33,700. That's not claims fraud or a processing error, every one of those rates was paid exactly as billed. It's a 3x spread in what "correct" looks like, baked into the contract before a single claim is ever submitted. Payment integrity has no lever here: there's nothing to catch, because nothing was paid wrong. Prospective benchmarking is the only way to know, before renewal, whether your client landed on the $12,200 end of that range or the $33,700 end.

Why a "clean" payment integrity record doesn't mean a competitive contract

There's a structural reason "we already have that" comes up so often, and it isn't that payment integrity vendors are bad at their jobs. Most are good at exactly what they're built for. The issue is how they're paid. Most payment integrity vendors work on a shared-savings or contingency fee: a cut of whatever they claw back. That's a reasonable incentive for finding duplicate claims and coding errors. It's a weak incentive for telling a client the real problem isn't claims accuracy, it's that the contract itself was priced 20% above market before the first claim was ever filed. A vendor paid on recoveries has no reason to volunteer that the bigger fix is a renegotiation, not another audit rule. Rate benchmarking doesn't carry that conflict, because the report doesn't change based on what it finds, so there's no incentive to keep the recoveries narrative going instead of surfacing the structural problem underneath it.

A pattern we see often in this exact "we already have that" moment (illustrative, not a specific engagement): a broker's book gets folded into a larger consultancy, the enterprise payment integrity platform comes along as a value-add, and everyone assumes network benchmarking is now covered. A few renewal cycles pass. The payment integrity dashboard looks great, claims adjudicated correctly, error rates low, recoveries trending down, which reads as the plan running cleanly. Nobody runs an independent, negotiated-rate check until a new broker or the client's own CFO finally asks for one. When they do, the plan turns out to be sitting well above the market median against comparable employers in that same market. Years of a technically clean payment integrity record sat on top of a contract that was overpriced from day one, and nothing in that dashboard was ever built to say so.

What this looks like for a benefits broker specifically

Medlyze's own benchmarking, built on CMS Transparency in Coverage machine-readable files, shows clients sitting at a specific rate percentile against 100+ comparable group plans in their market, typically 15–25% above the market median when a plan hasn't been re-benchmarked recently. That percentile isn't a payment error. It's a contracting outcome, visible before renewal, that a claims-accuracy audit will never surface because every one of those claims paid out exactly as the (uncompetitive) contract specified.

This is also why the two tools aren't competitive with each other; they're complementary, and most enterprise analytics teams already treat them that way once someone lays out the distinction. Payment integrity findings, patterns of coding or billing behavior, feed into which contract terms are worth renegotiating. Rate benchmarks, in turn, give payment integrity rules a defensible, market-based baseline instead of an arbitrary internal threshold. Neither replaces the other.

What to ask before assuming "we already have that" closes the conversation

• Does the existing tool use the parent's own claims data, or independent negotiated-rate filings? If it's claims-based, it's payment integrity, even if it's marketed as "network benchmarking."
• Does it answer questions before a renewal is signed, or after a claim is paid? Before-the-fact and after-the-fact are different products solving different problems.
• Does the output go to a CFO in a renewal conversation, or to a claims-recovery team? If it's the latter, it's not doing the job a rate benchmark does.
• Is the vendor paid on what it recovers, or on the report itself? A contingency-fee payment integrity vendor is built to find billing errors, not to tell a client the contract was priced badly. That's not a knock on the vendor, it's just not the job.

See where a client actually sits

Medlyze's Benefits Analytics delivers CFO-ready benchmarking reports built on public CMS Transparency in Coverage data, showing exactly how a client's plan compares to 100+ market peers by payer, procedure, and hospital, before the renewal conversation, not after a claim gets flagged.

View a sample report →