PILLAR GUIDE
What is a PBM contract audit?
An independent read of the contract language that decides what your self-funded plan actually pays for pharmacy. This guide explains what a PBM contract audit examines, why it differs from a claims review, and how a plan sponsor starts one.
GC
By Ginny Crisp, PharmD · Reviews hundreds of PBM contracts a year
Published July 2026 · Updated July 2026
A PBM contract audit is an independent review of a pharmacy benefit manager contract that reads the pricing methodology, rebate definitions, audit rights, termination terms, and specialty routing to find where a self-funded plan is overpaying or carrying unprotected risk. It examines the language that governs the spend, not the spend itself, because the contract sets the ceiling on everything the PBM is allowed to charge.
Most plan sponsors negotiate a pharmacy benefit manager contract once, sign it, and never read the pricing exhibits again until renewal. The problem is that the avoidable cost lives in those exhibits. A favorable headline discount can sit beside a rebate definition that excludes most of the rebate dollars, an audit-rights clause that gives you no real access to the data, and a pricing model that quietly permits the PBM to keep a margin on every claim. An audit surfaces those terms before they cost another year of spend.
What does a PBM contract audit actually examine?
A complete audit reads the contract section by section against what protective language looks like. The pricing-methodology section comes first, because it decides whether the plan is on a pass-through model or an aggregate model. Under spread pricing, the PBM can charge the plan more for a drug than it pays the pharmacy and keep the difference; aggregate pricing guarantees often permit it, and pass-through guarantees prohibit it. The audit confirms which model the contract actually creates, regardless of how the cover summary describes it.
From there, an audit examines five areas where contract language routinely leaks money:
-
Pricing guarantees and effective rates. The GER (Generic Effective Rate) and its brand counterpart state the minimum discount off AWP the PBM must hit, measured in aggregate. The audit checks whether the contract carries true-up and remediation language, so a missed guarantee actually gets paid back, and whether the rates are specified at the channel level rather than blended across retail, mail, and specialty.
-
Rebate definitions. The headline rebate passthrough percentage means nothing without the definition of eligible rebate revenue underneath it. Many contracts exclude administrative fees, market-share payments, and manufacturer compensation collected by a rebate aggregator before the passthrough is even calculated. The audit reads the definition, not the percentage.
-
Audit rights. The clause that decides whether the plan can ever verify the pricing is itself a contract term. The audit checks for the right to inspect claims at the line level, reasonable notice and frequency, access to MAC lists and rebate documentation, and the absence of fees or restrictions that make the right unusable.
-
Termination and transition. The audit examines whether the plan can actually leave, including notice periods, cause definitions, runout-claims handling, and data-return obligations. A contract you cannot exit on reasonable terms removes your leverage at every future renewal.
-
Specialty routing. Specialty drugs drive a disproportionate share of plan spend, and most contracts route those claims to a PBM-owned specialty pharmacy. The audit checks whether the plan has visibility into specialty pricing and whether the routing language locks the plan into a single affiliated channel.
How is a contract audit different from a claims review?
A contract audit reads the rules. A claims review checks whether the PBM followed them. The distinction matters because the two answer different questions, and the order is not interchangeable.
A claims review takes a period of actual paid claims and tests them against the contracted guarantees: did the PBM hit the promised AWP discounts, did rebates flow at the stated percentage, were dispensing fees charged as specified. It is a compliance test against the language. A contract audit asks the prior question: is the language itself protective. If the rebate definition excludes most rebate dollars, a claims review will find the PBM perfectly compliant while the plan still leaves money on the table, because the contract permitted it. Weak language makes weak claims compliant by definition.
That is why the contract audit comes first. The audit tells you what to renegotiate; the claims review then tells you whether the PBM is honoring what you did negotiate. Plan sponsors who run only a claims review can confirm the PBM is following the contract and still be overpaying every month, because the leak is in the terms, not the execution.
Why does a self-funded plan need one?
A self-funded plan carries pharmacy spend directly. There is no insurer absorbing the difference between a good contract and a weak one; every dollar the contract language fails to protect comes off the plan's own budget. Pharmacy is frequently the fastest-growing line in that budget, driven by specialty drugs and rebate dynamics that the contract either controls or lets run.
There is also a fiduciary dimension. Under ERISA, the plan sponsor that controls plan decisions is a fiduciary held to a prudent-expert standard, and PBM selection and oversight are fiduciary acts. Reviewing the contract that governs a major plan expense, and documenting that review, is part of the prudent process the duty requires. An independent audit produces exactly that documentation: what was reviewed, what was found, and what the plan decided to do about it.
Independence is the operative word. An audit run by a party with a revenue tie to the PBM, a broker taking PBM-side compensation, or the PBM's own reporting team, is not a check on the contract. Across the hundreds of PBM contracts Prescription Benefit Solutions reviews a year, the same protective terms are missing again and again, and they are missing because the only people who read the contract closely were the ones who benefit from the language staying vague. Our Standards for Independent PBM Review define what independence requires.
How do you start a PBM contract audit?
Start by gathering the complete executed contract. That means every exhibit, every pricing schedule, every amendment, and any side letters, not just the master agreement. The pricing and rebate terms almost always live in the exhibits, and an audit of the master agreement alone misses the part that decides the spend.
Next, have an independent reviewer read the document against protective-language benchmarks rather than against the PBM's own summary. The output of a good audit is concrete: a section-by-section list of the specific clauses that are weak, the protective version of each, and a priority order tied to your renewal timeline. The renewal or RFP window is the point of real leverage, so the audit is most valuable when it runs several months ahead of it.
To see the difference between weak and protective wording before you start, the PBM Contract Language Library puts the vague version next to the language to ask for, clause by clause. The free toolkit library turns the same provisions into audit worksheets you can run against your own contract, and the Plan Sponsor FAQ answers what working with an independent reviewer looks like. For the underlying terms, the PBM glossary defines each one in plain English.
If spread pricing is the term you most want to understand first, the companion guide on what spread pricing is in a PBM contract covers how it hides and how to detect it.
Frequently asked questions
What is a PBM contract audit?
A PBM contract audit is an independent review of a pharmacy benefit manager contract that examines its pricing methodology, rebate definitions, audit rights, termination terms, and specialty routing to find where a self-funded plan is overpaying or carrying unprotected risk.
How is a PBM contract audit different from a claims review?
A contract audit reads the rules that govern your spend, the language that decides what the PBM can charge. A claims review checks whether the PBM followed those rules on actual claims. The contract sets the ceiling; the claims test whether the PBM hit it. You need both, and the contract audit comes first because weak language makes the claims compliant by definition.
Does my self-funded plan need a PBM contract audit?
If your plan is self-funded, you carry the pharmacy spend directly and the PBM's contract language decides how much of it is avoidable. Plan sponsors are ERISA fiduciaries, and reviewing the contract that governs a major plan expense is part of the documented, prudent process that duty requires.
How do you start a PBM contract audit?
Start by gathering the full executed contract with every exhibit, amendment, and pricing schedule, then have an independent reviewer with no PBM revenue tie read the pricing methodology, rebate definitions, audit-rights, and termination sections against what protective language looks like. The output is a list of specific terms to renegotiate before renewal.
How often should a PBM contract be audited?
Review the contract at least once a year and always before a renewal or RFP. Pricing guarantees, rebate definitions, and formulary authority drift over the contract term, and the renewal window is the only point of real leverage to fix the language.