Consider a familiar renewal decision, using a fictional example: your largest commercial payer offers a 4% increase. Managed care needs to decide whether it is enough. Finance needs to know what belongs in next year's plan. Revenue cycle is still trying to collect what the current agreement already owes.
Now imagine the payer report says the relationship is performing well overall. Days to payment improved. Total collections rose. The contract's average rate looks competitive. Would you sign?
I would want to know what those averages are hiding. Which service lines drive the increase? Are all facilities being paid under the right terms? Is faster payment coming with more denials or more work?
A payer performance scorecard should help answer those questions before the negotiation, not explain them after the budget is set. Its value is not a more polished payer grade. It is a better decision about where to negotiate, where to enforce the existing agreement, and where to fix an internal process.
A payer performance scorecard needs four separate views
A payer performance scorecard is a decision tool that connects market position, contract execution, payment performance, and operational friction for a defined payer relationship. It shows the evidence behind each finding, its financial meaning, and the next action, without hiding different problems inside a single overall score.
I would organize it around four questions. Each should lead to a different decision:
- Market position: Are the rates competitive for the services and peers that actually belong in the comparison?
- Contract execution: Is the payer applying the reimbursement terms we agreed to?
- Payment performance: What has been paid, what remains unresolved, and how long does payment take?
- Operational friction: What work is required to get the right payment?
These views belong together because they describe the same relationship. They should stay separate because they call for different actions.
A market gap is a reason to develop a negotiation position. A validated underpayment is a reason to enforce an existing term. Neither should disappear because another measure turns green.
That distinction also changes the payer conversation. “We need a better increase” is a different request from “These claims were paid against the wrong fee schedule.”
Make the enterprise view a roll-up, not a blur
Consider a fictional health system with three hospitals, an employed physician group, and two surgery centers. The same payer name appears across the system, but a single average should not be the starting point for deciding what to do.
Build the underlying view by payer product, agreement, entity, service line, and payment method. Then summarize it for the enterprise.
Suppose one hospital has a rate opportunity, a second has a payment configuration problem, and the physician group has an authorization-related workflow issue. The systemwide response is not simply to “escalate payer performance.” It is three specific workstreams, with different evidence and different owners.
For the executive page, I would show:
- Economic significance: The payer's share of net patient service revenue, with the largest affected entities and service lines identified.
- Decision window: Renewal timing and the actual notice, amendment, and dispute deadlines in the relevant agreements.
- Material exceptions: The few findings that could change the financial plan or the negotiation position.
- Decision requested: What leadership needs to approve, resolve, or assign.
Keep the detail behind that page. Aggregate rates using a consistent service basket, combine ratios from their underlying numerators and denominators, and show coverage gaps instead of averaging unlike measures.
An enterprise summary should make the important exceptions easier to see. It should not make them disappear.
Follow one agreement from rate opportunity to payment
Here is a fictional example for one hospital's outpatient service line under one commercial PPO agreement. The service cohort covers a fixed 90-day period, with a stated reporting cutoff; the staff-work measure uses a separate four-week log.
All figures are illustrative. They are not customer results, industry benchmarks, or promised recoveries.
The market comparison reprices the same units. Before using it, check product, geography, provider type, site of care, billing basis, and payment method, and identify services without a credible peer reference.
The paid-claim review is a subset of the service cohort, not proof of performance across every claim. Its $200,000 variance assumes the team has reconciled patient responsibility, coordination of benefits, reversals, recoupments, and the governing terms; overpayments should remain visible rather than being hidden in a net total.
The table gives managed care and finance a shared starting point. It does not pretend that every finding means the same thing.
Separate earnings opportunity, cash timing, and capacity
The wrong headline for that example is “$1.04 million in recoverable revenue.” Adding $800,000, $200,000, and $40,000 produces a precise number with no coherent financial meaning.
The $800,000 is prospective. It describes a negotiation scenario on a defined service basket, not an amount owed today. Finance should decide what, if anything, enters the plan after testing achievable rates, effective dates, volume, mix, and implementation timing.
The $200,000 is retrospective. It is a validated payment variance, but it is not collected cash. It also should not automatically be called incremental revenue: finance needs to determine how the balance is already reflected in receivables, revenue estimates, and reserves.
The unresolved claims describe exposure and timing. Some balances may be collectible, some disputed, and some require adjustment. A count alone does not establish the dollars at risk or an expected loss.
The $40,000 is an allocation of staff cost. Reducing that work could free capacity, reduce overtime, or avoid a future hire. It does not automatically reduce expense by $40,000.
Keep these categories separate in the leadership discussion. They answer different questions: What could improve future economics? What should already have been paid? What is delaying cash? What work could be removed?
The strongest business case is not the one with the largest total. It is the one finance can reconcile.
Turn the scorecard into a better renewal position
Return to the fictional 4% renewal offer. Assume, solely for illustration, that it applies uniformly to every rate in the $10.0 million basket, with unchanged terms and mix.
That would add $400,000 on the same basket, bringing it to $10.4 million. It would still sit $400,000 below the $10.8 million peer-reference scenario.
That is not proof the payer should agree to 8%. It tells the team where to investigate and how to evaluate the offer beyond its headline.
I would take three separate requests into the payer discussion:
- A targeted rate proposal: Show the services driving the gap and the evidence for the proposed changes, rather than asking for an unsupported across-the-board percentage.
- A payment-correction workstream: Bring the $200,000 reconciliation, the relevant contract terms, and a request for correction and resolution timing. Do not treat payment already owed as a concession in exchange for future rates.
- An operational resolution plan: Identify the recurring causes of unresolved claims and rework, distinguish payer issues from provider issues, and assign a specific fix to each.
Finance can then compare the proposal with the payer's counteroffer using the same service basket and implementation assumptions. Managed care can see what is a negotiable improvement and what is an existing contractual obligation.
The scorecard has done its job when it changes the request, not merely the presentation.
Make the next monthly review about what changed
A denial rate without a definition can generate more argument than insight. HFMA's MAP Keys distinguish remittance denial rate from denial write-offs and specify the inclusions, exclusions, and data sources behind each measure (HFMA MAP Keys).
Use a published definition where it fits. Label narrower internal measures explicitly, and put the cohort, cutoff, calculation, and evidence coverage next to each number.
In the example, 1,500 unresolved claims represent 15% of the 10,000-claim service cohort. That is not a denial rate. The 800 hours describe four weeks of work, not a full-quarter cost.
For each material finding, close the review with a named individual, a deliverable, a due date tied to the actual decision window, and evidence that will establish completion.
At the next review, keep the original cohort visible. How much of the $200,000 has been corrected and collected? What remains unresolved? Did the proposed workflow change reduce repeat work? Has the rate proposal changed the expected economics of the renewal?
Introduce the next cohort separately. Otherwise, a change in service mix or claim maturity can look like improvement when the original problem is still open.
Start with one payer relationship and the next decision that matters. Assemble the relevant agreements, a deidentified claim and remittance sample, the market comparison, and a short log of the work required to resolve exceptions.
If you are preparing for that review, bring those inputs and your specific payer question to a working session with Trek Health. We will start with the decision the scorecard needs to support.
The goal is not to prove that a payer is good or bad. It is to know what to negotiate, what to collect, what to fix, and what belongs in the financial plan.



