Why do health plans need pharmacy payment integrity if they already audit their PBM?

Traditional PBM audits are usually retrospective, sample-based, and limited to narrow time windows, which means they can miss systematic configuration issues and emerging pricing problems. Pharmacy payment integrity adds a continuous oversight layer on top of the PBM relationship, so pricing errors, accumulator issues, coordination of benefits problems, and misapplied fees are identified and corrected earlier, before they compound into large and potentially unrecoverable spend.

How can a health plan tell if its PBM is pricing claims correctly?

The most reliable way for a health plan to tell if its PBM is pricing claims correctly is to independently reprice PBM-paid claims using the actual contract terms, benefit and plan design rules, accumulators, MAC and pricing files, and network configuration. By comparing what the PBM paid to what each claim should have cost, the plan can see whether ingredient cost, fees, member cost share, and network terms were applied as agreed in the contract.

Where do PBM overcharges and pricing errors typically hide?

PBM overcharges and pricing errors are most often found in a few predictable areas. These include MAC and other ingredient cost methodology issues, dispensing fees and per-claim adders, accumulator and benefit-phase configuration, coordination of benefits and retroactivity, network and pharmacy-type routing, and the details of spread pricing, pass-through terms, and guarantees. A focused pharmacy payment integrity program targets each of these domains with explicit rules, tests, and algorithms.

What are common ingredient cost methodology errors in PBM pricing?

Common ingredient cost methodology errors include using the wrong MAC list or effective dates, misclassifying brand and generic drugs in ways that affect discounts and guarantees, applying outdated AWP or WAC values, and failing to cap payments based on usual and customary requirements in the contract. Because each PBM maintains its own MAC lists and update cadence, these errors can be difficult to detect without independent verification and claim-level repricing.

What is a claims pricing specification and why is it important for PBM oversight?

A claims pricing specification, sometimes called a configuration matrix or benefit/pricing matrix, is an operational blueprint that translates PBM contract language into explicit, testable rules. It documents pricing formulas by channel, MAC hierarchy and update cadence, usual and customary definitions, fee tables, accumulator rules, utilization management logic, and coordination of benefits priorities. This specification is important because it becomes the reference point for configuring systems, repricing claims, and resolving disputes about how the contract should work in practice.

What should a health plan do when it finds PBM overcharges?

When a health plan finds PBM overcharges, it should document the relevant contract and claims pricing specification rules, present claim-level evidence comparing expected versus paid amounts, quantify the financial exposure across affected claims and time periods, identify the root cause, and agree with the PBM on remediation steps. Those steps usually include fixing the configuration going forward, addressing past claims through reprocessing or refunds, evaluating any member impact, and updating change-control and monitoring processes to prevent the issue from recurring.

What is Rivera and how does it support health plan PBM oversight?

Rivera is a pharmacy payment integrity platform built for health plans. It operates as an independent oversight layer alongside the PBM by continuously evaluating PBM-paid pharmacy claims against contract terms, benefit and plan design, and configuration rules. Rivera independently reprices claims, surfaces pricing and configuration discrepancies, and structures findings so pharmacy, finance, and compliance leaders can detect overpayments earlier, resolve issues with evidence, and strengthen ongoing PBM governance without replacing their PBM.

PBM oversight and pharmacy payment integrity: a practical playbook for health plan pharmacy leaders

Q: What is pharmacy payment integrity?

Pharmacy payment integrity is the practice of continuously checking whether every PBM-paid pharmacy claim matches the health plan's benefit and plan design, the PBM pricing contract, and the claims system configuration. Instead of relying only on occasional, sample-based PBM audits, pharmacy payment integrity uses claim-level repricing, configuration checks, and governance routines to detect and correct overcharges, configuration errors, and misapplied fees.

Q: How can health plans move from one-time PBM audits to continuous monitoring?

To move from one-time PBM audits to continuous monitoring, health plans need three capabilities: independent claim-level repricing of PBM-paid claims, stratification and prioritization so teams can focus on the highest-impact issues, and evidence preservation so findings can be defended with data. These capabilities work best when they are delivered by an independent pharmacy payment integrity platform that uses the plan's contract, benefit design, and configuration rules to monitor claims on an ongoing basis instead of testing only a small sample once a year.

Q: Which PBM contract terms support effective pharmacy payment integrity?

PBM contracts that support effective pharmacy payment integrity usually include robust audit rights to claim-level data and historical MAC lists, clear and consistent definitions for pass-through, spread, rebates, fees, usual and customary, specialty, and guarantees, requirements for notice and approval before configuration changes take effect, meaningful error-correction and lookback terms, documented configuration change control, detailed fee schedules, and network integrity clauses that address routing and pharmacy-type classification.

Q: How should health plans govern PBM oversight and pharmacy payment integrity?

Health plans can govern PBM oversight and pharmacy payment integrity by establishing a regular cadence of monthly, quarterly, and annual reviews and by assigning clear ownership across pharmacy, finance, legal, and internal audit. Many plans use a PBM performance or pharmacy payment integrity committee that reviews pricing variances and outliers monthly, conducts deeper repricing and configuration reviews quarterly, and uses claim-level data to support annual guarantee and rebate reconciliation and plan-year changes.

Nov 10, 2025

Health plans cannot assume that pharmacy benefit managers (PBMs) are pricing claims correctly just because a contract is in place. Pharmacy payment integrity gives pharmacy leaders a way to verify, at the claim level, that every dollar paid matches the contract and the plan design.

This playbook explains what pharmacy payment integrity is, why it matters now, and how health plans can move from retrospective PBM audits to continuous, claim-level monitoring. It outlines where PBM overcharges typically hide, how to translate complex contracts into testable rules, and which contract terms and governance structures support effective oversight. It also describes how an independent pharmacy payment integrity platform applies repricing, configuration monitoring, and structured workflows so health plans can detect overpayments early and resolve them with evidence.

For a deeper look at how audits and continuous monitoring work together, see Snapshots vs. streaming: why true pharmacy payment integrity needs both audits and continuous monitoring. For an analysis of how PBM legislation shapes oversight requirements, see Reform does not enforce itself: why PBM legislation demands continuous oversight.

What is pharmacy payment integrity and why does it matter now?

In plain terms, pharmacy payment integrity is the discipline of continuously checking whether every PBM-paid pharmacy claim matches three things:

The benefit and plan design
The PBM pricing contract
The claims system configuration

Instead of relying on occasional, sample-based PBM audits, pharmacy payment integrity uses claim-level repricing, configuration monitoring, and governance routines to detect and correct:

Overcharges and incorrect pricing
Configuration errors in accumulators, plan design, and coordination of benefits
Misapplied fees and network terms

PBM reform, rising specialty drug spend — projected at double-digit increases for 2026, the highest annual rate in more than a decade — and tighter margin pressure all increase the risk and impact of small errors compounding into large variances.

How can health plans verify that each PBM claim is priced correctly?

Most PBM disputes devolve into arguments about reports. The strongest PBM oversight programs instead organize around one core question:

What should this claim have cost, given our contract, plan design, and configuration?

For each paid claim, a health plan should be able to answer:

Did the member cost share match the benefit and plan design?
Did the ingredient cost, fees, and any adders follow the contract terms?
Did the claims system follow the right accumulators, COB rules, and edits?

Trend and utilization matter, but overcharging is fundamentally a claim-level pricing and configuration problem.

Where do PBM overcharges typically hide?

Overcharges and errors are not random. They tend to cluster in a few predictable areas. A practical pharmacy payment integrity program targets each of these with explicit checks and algorithms.

Ingredient cost methodology errors (MAC, AWP, WAC, NADAC, U&C)

Ingredient cost methodology errors, including MAC, AWP, WAC, NADAC, and U&C, are among the most consequential and least visible sources of PBM overcharges. Common failure points include:

MAC list application. No two PBM MAC lists are alike — every PBM applies different criteria for which drugs are included, at what price, and when lists are updated — making wrong list selection, wrong effective dates, or missed MAC application among the hardest pricing errors to detect without independent verification.
Brand vs. generic classification. Misclassification can trigger the wrong discount, guarantee bucket, or reimbursement basis.
AWP and WAC updates. Lags or mismatched effective dates can create systematic mispricing.
Usual and customary logic. The plan paying more than U&C or failing to cap based on U&C when the contract requires it.

What to verify:

The contracted pricing hierarchy is followed, such as “lesser of MAC, U&C, or AWP minus X percent plus fee.”
Effective dates for MAC, AWP, WAC, and NADAC align with contract language and file loads.
Drug identifier mapping (NDC, GPI, multi-source code) matches the contract and guarantee definitions.

Dispensing fees and per-claim adders

Small discrepancies in fees, applied across millions of claims, can add up quickly. Common issues include:

Wrong dispensing fee by network tier (retail 30, retail 90, mail, specialty)
Per-claim fees that are not in the contract, or that are stacked incorrectly
Specialty “service fees” or handling charges applied outside agreed terms

What to verify:

Fee schedules by channel and pharmacy type
Whether fees differ by brand vs. generic, 90-day vs. 30-day, or preferred vs. nonpreferred pharmacies

Plan design and accumulator configuration

Benefit and accumulator configuration is one of the most frequent and preventable causes of both member and plan overpayment. Typical issues include:

Deductible applied when it should not be or not applied when it should
Out-of-pocket maximum not triggering correctly
Family and individual accumulators misconfigured
Copay vs. coinsurance inversions; minimum and maximum amounts misapplied
Preventive drug lists or zero-cost-share policies missing or misconfigured

What to verify:

A “golden” set of test claims that exercises each benefit scenario and phase
Accumulator logic across deductible, initial coverage, and any applicable coverage gap or catastrophic phases

Coordination of benefits (COB) and reprocessing

COB and retroactivity issues often sit at the intersection of PBM configuration and plan operations. Problems include:

Secondary payer rules incorrectly set, causing the plan to pay primary amounts
Claims not reversed or rebilled after other insurance is discovered
Retro eligibility changes that are not reprocessed in a timely way

What to verify:

COB configuration and audit trails in PBM and plan systems
Timeliness standards and performance for reversals and reprocessing
Overpayment recovery workflow and reporting, including root-cause tracking

Pharmacy network and contracted rates not applied

Network routing and pharmacy type designation directly affect pricing and guarantees. Common failure modes:

Claims adjudicating under the wrong network (for example, standard instead of preferred)
Incorrect pharmacy type designation, such as specialty vs. retail
Misconfigured pharmacy IDs leading to application of the wrong fee or rate

What to verify:

Network participation files, pharmacy IDs, and effective dates
Pharmacy type and channel flags used in pricing logic and reporting

Spread pricing, “pass-through” models, and guarantees

Even in "pass-through" arrangements, details matter. The FTC's 2025 interim report found the Big 3 PBMs generated an estimated $1.4 billion from spread pricing on specialty generics alone, while simultaneously billing plan sponsors more than they reimbursed pharmacies. Common gaps include:

“Pass-through” may apply to ingredient cost, not to admin or service fees
Direct and indirect remuneration and post-adjudication adjustments may not be clearly credited
Definitions of “rebate,” “discount,” “remuneration,” and “specialty” may not match how claims are processed and reported

What to verify:

Precise definitions in the contract for what is passed through, when, and how it is documented
How post-adjudication financial adjustments flow back to the plan and how they interact with guarantees

How do you translate a PBM contract into testable rules?

One of the biggest gaps in PBM oversight is the translation step between a legal contract and the rules engines that drive claim adjudication. Health plans need a clear, operational view of how their contract is meant to work in practice.

A practical tool for this is a claims pricing specification (sometimes called a configuration matrix or benefit/pricing matrix). It should convert legal language into explicit, testable logic.

A strong claims pricing specification includes:

Pricing formulas by channel (retail 30, retail 90, mail, specialty)
MAC list sources, hierarchy, and update cadence
U&C definitions and any caps
Dispensing fee tables by network, channel, and product type
DAW penalties or rules, if applicable
Compound logic and ingredient-level pricing rules
Vaccine and medical-benefit carve logic
Exclusions, formulary tiers, and UM rules (PA, step therapy, quantity limits)
Accumulator, deductible, and benefit-phase logic
COB priority rules and exception handling

Pharmacy leaders should:

Require PBM sign-off that the specification matches the contract
Retain it as an auditable artifact and as the baseline for future change control

An independent pharmacy payment integrity partner should build or validate this specification and maintain it as a living document as the contract and plan design evolve.

How can health plans move from one-time PBM audits to continuous monitoring?

Traditional PBM audits are often retrospective, sample-based, and limited to narrow time windows. They can be useful, but they cannot provide the level of assurance or speed that modern pharmacy spend demands.

A continuous pharmacy payment integrity program includes three core capabilities. These capabilities work best when delivered independently of the PBM because relying on PBM-provided reporting to verify PBM performance is an inherent conflict of interest.

Independent, claim-level repricing

To know whether a PBM is pricing claims correctly, health plans need an independent calculation of what each claim should have cost.

Effective repricing uses:

Contracted rate tables and fee schedules
MAC lists, including historical versions by effective date
Plan design rules and accumulators
Drug reference files and classification logic
Network and pharmacy type mappings

By comparing what the PBM paid to what the model calculates, health plans can identify:

Systematic configuration errors that affect many claims
Specific NDCs, pharmacies, and time periods with recurring issues
Discrepancies in fees, ingredient cost, and member cost share

The key is that this happens on every claim, not on a small sample once a year. Understanding how these findings translate into measurable financial value requires looking beyond recovery alone.

Targeted stratification and prioritization

Even with full-population repricing, health plans need a way to focus on what matters most.

Useful stratifications include:

Highest spend drugs and therapeutic classes
Specialty and high-cost channels
Ninety-day and mail-order fills
Outliers in unit cost and dispensing fees
DAW 1 claims
Claims limited by U&C
Reversals, rebills, and transition fills

Evidence preservation and audit readiness

Continuous oversight only works if findings can be defended and acted upon.

Plans should ensure they can access and retain:

Full paid claim detail, including all relevant pricing fields
Reversal and reprocessing history
Network and pharmacy identifiers
Drug file extracts or reference keys
MAC list versions with dates
Post-adjudication adjustments and guarantee calculations

What PBM contract terms support effective pharmacy payment integrity?

Contract language either enables or limits what pharmacy leaders can see and do. With sweeping new federal PBM transparency and oversight requirements now taking effect in 2026 — including requirements for PBMs to provide health plans with detailed semi-annual data on drug spending, rebates, spread pricing, and affiliated pharmacy use — what health plans require in their PBM contracts is no longer just a negotiating preference. It is increasingly shaped by federal standards that affect every PBM relationship. To support meaningful oversight, PBM contracts should include:

Robust audit rights. Access to claim-level fields, MAC lists (including historical versions), network rate tables, and configuration artifacts.
Clear definitions. Consistent, specific definitions for pass-through, spread, remuneration, rebates, fees, U&C, specialty, and guarantees.
Effective-date discipline. Requirements for notice, documentation, and approval before configuration or pricing changes take effect.
Error correction terms. Obligations to refund overpayments with interest or penalties, with a lookback period that is long enough to be meaningful and a clear dispute process and timeline.
Configuration change control. Documented testing, sign-off, and traceability for benefit and pricing configuration changes.
Fee transparency. Detailed schedules for administrative, clinical, data, platform, and implementation fees, with limits on “miscellaneous” or “other” categories.
Network integrity clauses. Requirements to route claims to correct networks and pharmacy types, with remedies if misrouting occurs.

How should health plans govern PBM oversight and pharmacy payment integrity?

Even the best analytics and algorithms will not drive change without clear governance. A practical model is to operate on three time horizons.

Monthly: rapid detection and response

Pricing variance dashboards by channel, drug, and pharmacy
Outlier reports for unit cost, fees, and cost share
COB exceptions, reversals, and reprocessing performance

Quarterly: focused deep dives

Stratified claim repricing reviews on priority areas
Network tier validation for preferred vs. nonpreferred pharmacies
Accumulator and benefit design test suite reruns
Trend analysis for recurring configuration issues

Annually: true-up and future-year readiness

Guarantee and rebate reconciliation, anchored in claim-level data
Configuration baseline review for upcoming plan year changes
Assessment of PBM performance relative to oversight standards

Many plans use a standing PBM performance and compliance committee that includes pharmacy, finance, legal, and internal audit. An independent pharmacy payment integrity platform should plug into this cadence so leaders get consistent, decision-ready insight rather than sporadic audit reports.

What should health plans do when they find PBM overcharges?

When discrepancies surface, PBM oversight can quickly devolve into “report wars.” A structured approach keeps the discussion grounded in facts.

When an issue is identified:

Document the rule. Cite the relevant contract language and the corresponding claims pricing specification rule.
Show the claim-level evidence. Demonstrate how the PBM-paid amount differs from the expected amount for representative claims.
Quantify exposure. Estimate affected claim counts, time periods, and financial impact ranges.
Identify root cause. Determine whether the issue stems from configuration, file loads, drug mapping, network routing, or other operational drivers.
Define remediation. Agree on how to fix the issue going forward and how to address past claims, including reprocessing or refunds and any member impacts.
Lock in controls. Update configuration documentation, change-control processes, and monitoring rules to prevent recurrence.

A closing standard for PBM oversight

PBMs manage real complexity at scale, and errors are inevitable. Health plans cannot eliminate every discrepancy, but they can decide whether they catch issues early and systematically or only after they have compounded into unrecoverable spend.

A modern PBM oversight standard looks like this:

Every claim can be independently repriced against contract and plan design
Configuration changes are documented, tested, and monitored
Overcharges, errors, and misconfigurations are detected quickly and resolved with evidence
Guarantees and rebates are validated on top of accurate claim-level pricing, not instead of it

That is what pharmacy payment integrity delivers. Rivera was built to help health plans meet that standard by turning PBM oversight from a periodic event into an ongoing discipline, using independent claim-level repricing, configuration monitoring, and structured workflows that integrate with existing PBM relationships rather than replacing them.