Why the annual PBM audit is no longer enough

The annual pharmacy benefit audit — a retrospective, sample-based review of PBM-adjudicated claims — has been the primary oversight mechanism for health plan pharmacy departments for decades. It is no longer sufficient on its own. Benefit designs change continuously, PBM contract terms evolve throughout the year, and claim errors introduced mid-cycle accumulate for months before a periodic review can surface them. According to Rivera's primary research with pharmacy executives across commercial, Medicare, and Medicaid health plans, audit findings frequently lag adjudication activity by 12 to 24 months, and engagement fees often approach or exceed the amounts recovered.

This article explains why the structure of the annual audit creates gaps that are difficult to close within the audit model, what continuous pharmacy claims monitoring does differently, and what pharmacy leaders are doing to address oversight risk in an environment where the traditional tools are narrowing.

What is a pharmacy benefit audit and why does it fall short?

A pharmacy benefit audit is a retrospective review of pharmacy claims conducted by an independent firm to verify that a health plan's pharmacy benefit manager (PBM) is adjudicating claims according to the plan's contract terms, benefit design, and regulatory requirements. Audit firms sample claims from a defined historical window, apply a contract interpretation, and produce a findings report that the health plan uses as the basis for recovery discussions with the PBM.

The limitation is structural, not operational. The annual audit is built to review what happened, not what is happening. Three features of its design create persistent oversight gaps:

Lag. Audit reviews typically cover claims adjudicated 12 to 24 months prior. Errors introduced when a plan year is built, when a PBM implements a new clinical program, or when a formulary change is made have already accumulated across thousands of claims by the time they appear in audit findings.

Scope. Audits review a sample of claims, not all of them. Systemic errors affecting a narrow drug class, a specific network tier, or a particular member segment can sit below the detection threshold of a sample-based methodology. Plans often do not know what they are not finding.

Dispute dynamics. PBMs have substantial experience responding to audit findings. Settlements frequently come in below projected recovery amounts, and the dispute process consumes internal resources across multiple quarters. Rivera's primary research found that pharmacy leaders consistently describe audit engagement fees as approaching or exceeding recovered amounts.

What is the difference between a PBM audit and continuous pharmacy claims monitoring?

The core distinction is coverage and timing. A pharmacy benefit audit reviews a sample of historical claims periodically. Continuous pharmacy claims monitoring reviews every adjudicated claim on an ongoing basis.

Both have a role. The annual audit establishes a documented record and tests specific contract guarantees. Continuous monitoring closes the gap between audits and addresses the category of errors that a periodic, sample-based review is structurally unable to catch.

Why is continuous pharmacy oversight more important now than it was five years ago?

Three converging pressures have made the oversight gap more consequential.

Benefit and contract change has accelerated. Federal PBM reforms, state regulatory requirements, and annual plan design cycles mean that the terms governing pharmacy adjudication are changing more frequently. Each change has to be correctly translated into the PBM's adjudication system. When that translation is imperfect, errors begin accumulating immediately.

Savings pressure is at a historic high. According to Rivera's primary research, pharmacy departments are operating under more financial scrutiny than at any prior point — from CFOs, regulators, ASO clients, and state Medicaid programs simultaneously. Traditional savings levers, including PBM contract renewals and specialty management programs, are narrowing. The gap between what was negotiated and what is being paid is a source of recoverable value that is structurally separate from those levers.

Stakeholder expectations have changed. Plan leadership, large employer clients, and regulators are no longer satisfied with "we conduct an annual PBM audit." They want evidence of active oversight — trend data, documented findings, corrective actions, and financial impact. The annual audit produces a periodic report. Continuous monitoring produces an ongoing record.

What is configuration drift and why does it matter for pharmacy oversight?

Configuration drift is what occurs when a change to a health plan's benefit design, PBM contract, or regulatory framework is not accurately reflected in how the PBM adjudicates claims. It is one of the most consequential and least visible sources of overpayment exposure in pharmacy benefits.

Every plan year build, mid-year formulary change, clinical program update, or contract amendment creates an opportunity for the adjudication configuration to diverge from what was intended. A misconfigured accumulator adjustment program, a prior authorization rule that did not survive a system update, or a specialty pricing term that was amended at contract renewal but not reflected in the fee schedule — each of these runs through adjudication silently until someone tests the claim output against the current rule.

In an annual audit cycle, that silence can last a year or longer. Continuous pharmacy monitoring tests each claim against the plan's current benefit and contract rules as adjudication occurs. Configuration errors are identified in the cycle they are introduced, not at the next scheduled review.

What do pharmacy leaders say about their current audit approach?

Rivera's primary research with pharmacy executives across commercial, Medicare, and Medicaid health plans produced several consistent findings:

• Annual PBM audits are described as compliance exercises, not savings tools — conducted primarily to satisfy a contractual or regulatory expectation.

• Audit firms are characterized as operating 12 to 24 months behind current adjudication activity.

• Multiple pharmacy leaders acknowledged they do not have visibility into 100% of claims in real time and described this as a known, accepted limitation.

• When a PBM implements a new clinical program mid-year, it can break prior configuration fixes — and there is currently no mechanism to catch this between audit cycles.

The consistent thread is not dissatisfaction with audit quality. It is recognition that the audit model cannot answer the question pharmacy leaders are increasingly being asked: what is happening in our pharmacy claims right now?

How does continuous pharmacy monitoring work in practice?

Continuous pharmacy claims monitoring applies a library of proprietary algorithms — encoded from plan design documents, PBM contract terms, and applicable regulatory requirements — to adjudicated claims on an ongoing basis. Each claim is tested against the rules that should govern it. Discrepancies are flagged, documented, and quantified so the health plan can pursue resolution with the PBM.

Rivera's monitoring is independent of the PBM — the algorithms reflect what the plan negotiated and designed, not how the PBM interprets its own contract. It is retrospective, operating after adjudication, not as an intervention at the point of claim. And it is continuous, not periodic: the library runs against every claim in every adjudication cycle, not a sample in an annual review.

Recoveries identified are dollars the plan should already be receiving under its existing contract and benefit design. They are not clawbacks from pharmacies, members, or providers. The recovery process runs between the health plan and the PBM, and the neutral-event framing matters operationally: plans often face internal resistance to savings mechanisms that impose costs on providers or pharmacies. Continuous monitoring findings do not have that characteristic.

FAQ

What is a pharmacy benefit audit? A pharmacy benefit audit is a retrospective, sample-based review of pharmacy claims conducted by an independent firm to verify that a health plan's PBM is adjudicating claims in accordance with the plan's contract terms, benefit design, and applicable regulatory requirements. Audit findings are used as the basis for recovery discussions with the PBM. Annual pharmacy benefit audits review historical claims on a defined cycle and do not provide visibility into current adjudication activity.

Why are pharmacy benefit audits described as compliance exercises rather than savings tools? Pharmacy benefit audits review historical claims with a lag of 12 to 24 months, apply a sample-based methodology that can miss systemic errors affecting narrow claim populations, and produce findings that must survive a PBM dispute process before any recovery is realized. According to Rivera's primary research with health plan pharmacy leaders, engagement fees frequently approach or exceed recovered amounts. For most health plans, the annual audit satisfies a contractual or regulatory expectation more than it functions as an active savings mechanism.

What does continuous pharmacy claims monitoring do that an audit does not? Continuous pharmacy claims monitoring reviews every adjudicated claim on an ongoing basis against the plan's current benefit design rules, contract terms, and regulatory requirements. It identifies configuration errors, pricing discrepancies, and benefit design drift as they occur rather than after they have accumulated across a full plan year or audit cycle. Mid-year changes — PBM program updates, formulary revisions, benefit amendments — are tested in real time rather than discovered retrospectively at the next scheduled review.

What is configuration drift in pharmacy benefits? Configuration drift occurs when a change to a health plan's benefit design, PBM contract, or regulatory framework is not accurately reflected in how the PBM adjudicates claims. In an annual audit cycle, configuration drift can accumulate undetected for 12 months or more. Continuous monitoring applies the plan's current rules to each claim as it is adjudicated, flagging discrepancies in the cycle they are introduced rather than at the next audit review.

Are continuous monitoring recoveries the same as audit recoveries? Continuous monitoring identifies dollars the health plan should already be receiving under its existing PBM contract and benefit design — not amounts owed by pharmacies, members, or providers. The recovery process runs between the health plan and the PBM. Unlike savings mechanisms that impose costs on providers or pharmacies, continuous monitoring recoveries represent a correction to adjudication alignment, which simplifies internal approval and reduces organizational resistance.