What to expect from an independent pharmacy payment integrity program

A pharmacy payment integrity program is an independent, ongoing review of pharmacy claims to verify that a health plan’s benefit design and pharmacy benefit manager (PBM) contract terms are being applied correctly at the claim level. Unlike a periodic audit, which reviews a sample of claims after the plan year closes, a continuous monitoring program evaluates 100% of claims on an ongoing basis,  identifies overpayments, and addresses root causes so errors do not recur.

If your health plan is evaluating whether to invest in this kind of program, the questions you are probably weighing are practical ones: what does implementation actually involve, how quickly do results materialize, and what does the value trajectory look like beyond year one? This article walks through what health plans should expect at each stage, from initial engagement through compounding long-term value.

What typically brings health plans to the conversation

Health plans invest significant time and resources negotiating PBM contract terms and designing benefit structures but have limited ability to verify that the hard work is being reflected accurately at the claim level. The PBM processes claims, applies pricing, and reports its own performance. The plan sees the aggregate but not the detail, creating a meaningful gap in visibility.

This gap typically starts raising alarms when a plan has a PBM contract renewal and wants independent data to inform negotiations, an audit surfaces enough findings to suggest the issues were not isolated, a leadership transition brings fresh scrutiny to pharmacy operations, or stakeholders start asking harder questions about pharmacy spend that internal teams cannot fully answer with the data available to them.

Whatever the catalyst, the underlying question is the same: are we getting what we negotiated?

What happens during onboarding

The onboarding process for a pharmacy payment integrity program is data-driven and plan-specific. It is not a generic compliance scan applied out of the box.

The program begins with a review of the plan’s benefit design documents, PBM contract, formulary structure, and any relevant regulatory requirements. This is the foundation: the program needs to understand what the plan intended before it can evaluate whether that intent is being executed correctly.

From there, the oversight provider configures its proprietary algorithms to reflect the plan’s specific logic. At Rivera, this involves building from a library of 750+ algorithms, each tied to a specific question about how the benefit should work. These are not generic checks. They encode the unique pricing terms, copay structures, coordination of benefits rules, formulary tier assignments, and clinical program requirements that define how each claim should be adjudicated for that plan. The algorithm library compounds over time: learnings from one client’s findings inform the checks applied across all clients, which means the system gets more precise as it scales.

Once configured, the provider ingests the plan’s claims data and begins running the full set of algorithms against every claim. There is no sampling. Every transaction is evaluated, which means the program has a complete picture from the start rather than extrapolating from a subset.

What findings typically surface first

Initial findings vary by plan, but certain categories tend to appear early because they affect large volumes of claims or involve pricing logic that is frequently misconfigured.

Pricing discrepancies are among the most common. These include contracted rates that are not being applied correctly, ingredient cost calculations that diverge from the agreed-upon methodology, or dispensing fees that do not match the contract schedule. Because pricing affects every claim in a given category, even small per-claim variances produce significant aggregate impact.

Coordination of benefits errors appear frequently in plans with dual-eligible or multi-coverage populations. When a member has more than one source of coverage, the sequencing of which plan pays primary and how the secondary plan adjusts its payment is governed by specific rules. Errors in this logic tend to be systemic, meaning they affect every claim for every affected member, not just an occasional transaction.

Member cost-share misapplications, where copay or coinsurance amounts do not align with the plan’s benefit design for a given tier or drug category, are another early finding. So is configuration drift: the gradual divergence between the plan’s current benefit design and the PBM’s adjudication logic, which often occurs after mid-year formulary updates, benefit changes, or contract amendments that are not fully implemented in the PBM’s system.

None of these findings require the PBM to have acted in bad faith. Pharmacy benefit administration is complex, and the volume of rules governing adjudication creates real surface area for implementation errors. What matters is whether the plan has a mechanism to detect them.

How value compounds beyond recovery

The most visible output of a pharmacy payment integrity program is dollar recovery. Claims that were paid incorrectly are identified and documented with the detail the health plan needs to pursue recovery from the PBM. For most health plans, the recovered dollars in the first year alone exceed the cost of the program, which is why the ROI conversation often starts there.

Recovery is the starting point, not the ceiling. The deeper value is in what happens after a finding is documented and the root cause gets corrected. Fix the underlying configuration, pricing logic, or contract interpretation, and that correction applies to every subsequent claim in the affected category for the life of the contract.

But corrections don't always hold — formularies change, new plan year builds don't always translate cleanly into adjudication, a PBM rolls out a clinical program and something shifts, an issue that was resolved in Q2 can resurface by Q4 under different conditions. That's not a failure of the oversight program. It's the nature of pharmacy benefit administration, and it's precisely why the oversight has to keep running.

This is what second-year and third-year value actually looks like. Some of the systemic issues from year one stay fixed, others come back in a different form, and new ones emerge that didn't exist before. The program's job is to catch all three: what was corrected and broke again, and what's wrong now for the first time. Recovery volumes may decline as the largest structural problems get resolved, but the ongoing work of keeping the benefit running as designed doesn't stop.

The third dimension is contract leverage. A health plan entering a PBM contract renewal with twelve months of independently validated, claim-level performance data is in a materially different negotiating position than one relying on PBM-supplied reports or a single retrospective audit. The data documents exactly where execution deviated from the contract, how much it cost, and whether the corrections held. That specificity is something a PBM-provided report cannot replicate, because the PBM is not going to produce a document that works against its own negotiating position.

How to know whether your program is working

A pharmacy payment integrity program that is performing well should show a recognizable pattern over time. Recovery volumes should be highest in the first year and decline in subsequent years as systemic issues are corrected. If recoveries stay flat or increase year over year, that's likely a signal that root causes are not being addressed.

Error recurrence rates should decline in categories where corrections have been implemented. If pricing errors on a specific drug category were identified and corrected in Q2, the same errors should not appear in Q3 and Q4 claims. Tracking recurrence by error category is the clearest measure of whether the program is producing structural improvement or just generating reports.

The program should also be producing usable contract leverage data well in advance of PBM renewal cycles. If the renewal is in Q1, the plan should have a full year of claim-level findings organized by contract term and error type, ready to bring into negotiations. An oversight program that delivers findings on a lag or in a format that requires significant reprocessing before it is useful in a negotiation is leaving value on the table.

Finally, the relationship should feel like a partnership, not a reporting function. The oversight provider should be proactive about flagging issues, transparent about what the data shows, and engaged in the operational follow-through required to get errors corrected. Recovery without resolution is only half the job.

Questions to ask before selecting a partner

Health plans evaluating pharmacy payment integrity providers should focus on five areas.

Independence. Is the provider affiliated with any PBM? Do they have revenue-sharing arrangements or operational dependencies that could affect objectivity? Independence is the foundation. Without it, findings are structurally compromised.

Coverage. Does the program review 100% of claims or a sample? Sample-based programs miss errors that fall outside the sample frame, particularly low-volume specialty claims or mid-year configuration changes.

Specificity. Are the algorithms built from your plan’s actual benefit design and contract terms, or are they generic compliance checks? Specificity determines whether findings are actionable enough to diagnose a root cause and prescribe a fix.

Follow-through. Does the provider stop at identification and recovery, or do they work through root-cause correction with the plan and PBM to prevent recurrence? Recovery without prevention means you are paying to find the same problems repeatedly.

ROI accountability. How does the provider structure its engagement? Programs backed by a guarantee, with fees structured on a per-member-per-month (PMPM) basis, align both sides around the same outcome: findings that are real, documented, and recoverable. The plan isn't paying more when errors are high and less when they aren't. The provider isn't chasing volume to justify its fees. A PMPM structure with a guarantee creates a straightforward relationship: the provider stands behind the value of the program, and the plan has cost predictability from day one.

Frequently asked questions

How long does it take to implement a pharmacy payment integrity program?

Implementation timelines vary by plan complexity, but most programs are fully operational within 60 to 90 days of engagement. The onboarding period involves reviewing benefit design and contract documents, configuring the algorithm library to reflect the plan’s specific terms, ingesting claims data, and running the initial review. Plans typically see their first findings within that window.

What does pharmacy payment integrity cost?

Engagement structures vary, but the model matters as much as the number. Rivera operates on a per-member-per-month fee backed by a guarantee, which means the plan has cost predictability from day one and the provider has a clear obligation to perform. Plans should ask any prospective provider how their fees are structured, whether they stand behind the program with a guarantee, and how they define and measure return. A program that cannot answer those questions directly is worth scrutinizing before you sign.

Does the health plan need to change its PBM to benefit from pharmacy payment integrity?

No. Pharmacy payment integrity programs operate independently of the PBM. The program reviews claims data and identifies errors regardless of which PBM the plan uses. In fact, the data a program produces often strengthens the plan’s position within the existing PBM relationship by providing documented, claim-level evidence of where execution diverged from the contract.

How is this different from what our PBM already reports?

PBM reporting reflects the PBM’s own adjudication logic and is produced by the same system that processed the claims. Independent pharmacy payment integrity applies a separate set of algorithms built from your plan’s benefit design and contract terms to independently verify whether the PBM’s execution matches the plan’s intent. It is the difference between self-reported performance and independently validated performance.

What happens when the program finds an error?

When an error is identified, the finding is documented with claim-level detail and the overpayment is calculated, giving the health plan the evidence needed to pursue recovery with the PBM. Beyond recovery, the provider diagnoses the root cause and works with the plan and PBM to correct the underlying configuration or contract interpretation so the error does not repeat on future claims. Both the financial recovery and the structural correction are tracked and reported to the plan.