PBM overpayment recovery: what happens after an error is identified

Pharmacy benefit manager (PBM) overpayment recovery is the process by which a health plan reclaims dollars paid on pharmacy claims that were adjudicated incorrectly, whether against the plan's benefit design, its PBM contract terms, or applicable regulatory requirements. Recovery is the plan's action: the plan brings documented findings to its PBM and pursues reconciliation, typically as a credit or repayment. What determines whether that process succeeds is everything that happens before it, which is the identification, validation, quantification, and documentation of the error.

Health plans already raise discrepancies with their PBMs. Pharmacy teams bring issues to operational meetings, open tickets, and push for answers. The constraint has never been willingness. A plan working manually can usually bring the PBM three example claims and ask the PBM to research the rest, which leaves the burden of proof with the plan and the scope of the issue in the PBM's hands. This article covers how the process changes when findings arrive complete, and why recovered dollars are only part of the financial outcome.

Identification and validation: establishing that an error is real

Recovery starts with a finding that can withstand scrutiny. In a continuous claims monitoring program, proprietary algorithms encoded from the plan's benefit design and contract terms evaluate 100% of post-adjudication claims, typically on a weekly or biweekly file cadence. When adjudication diverges from what the plan's rules say should have happened, the pattern is flagged.

A flagged claim is not yet a finding, because some variances have legitimate explanations rooted in override codes, timing, or benefit provisions that interact in non-obvious ways. Validation is the step where pharmacists review flagged patterns, separate true errors from explainable variances, and confirm the basis for each issue before it ever reaches the plan. This step protects the plan's credibility in the recovery conversation: a plan that brings validated findings to its PBM is never in the position of having raised a false alarm.

Quantification and documentation: building the case the PBM has to answer

Once an error is confirmed, the full population of affected claims is identified and the financial impact is calculated. This is where 100% claim review pays off. Instead of an extrapolated estimate from a sample, the plan receives the actual affected claims, the actual dollars, and the contractual or benefit design language that establishes why the adjudication was incorrect.

Documentation at that level changes the dynamic of the PBM conversation. Rather than the plan presenting a suspicion and asking the PBM to investigate itself, the PBM is responding to a complete, claim-level case. The burden of proof shifts: the PBM is now refuting specific evidence rather than scoping its own error. In Rivera's experience, that shift is what moves issues from open questions to resolved reconciliations.

The reconciliation pathway

Recovery itself belongs to the health plan. Rivera identifies, validates, quantifies, and documents overpayments, and provides the plan with everything needed to pursue recovery with its PBM, including recommended next steps based on what has worked across comparable findings. Each finding follows a somewhat different reconciliation pathway depending on its nature. A pricing logic error may resolve as a credit against future invoices. A misapplied benefit provision may require claims to be reprocessed. A guarantee shortfall may settle through the contract's existing true-up mechanics.

Two things are consistent across pathways. First, the resolution should include correction of the root cause, not just repayment, because an error that is repaid but not fixed simply accrues again. Second, the correction should be verified against subsequent claims until it demonstrably holds. Monitoring continues after resolution precisely because corrections can break again when something else in the PBM's environment changes.

It is worth saying plainly that this process is not adversarial by design. Pharmacy payment integrity is about getting claims right, and when issues are caught, documented, and corrected, the result is a PBM relationship operating on evidence rather than assertion. The current regulatory environment has also made PBMs less inclined to resist documented plan oversight than they once were.

Recovery versus cost avoidance: why the recovered dollar understates the value

Recovered dollars are the most visible outcome of this process, and for most plans they are sufficient on their own: across Rivera's client base, 100% of clients recover their investment in the first year of the contract. Recovery measures only the money already lost, though, while the larger financial outcome is usually the money that stops leaking once a root cause is corrected.

When a systemic error is corrected at the root cause, every future claim in the affected category adjudicates correctly for the life of that configuration. Those dollars never appear in a recovery total because they were never overpaid. Rivera's standardized terminology for this is cost avoidance, and in systemic findings it frequently exceeds the recovered amount, sometimes by a multiple. A plan evaluating this work on recovered dollars alone is reading half the financial statement.

The distinction also matters for how plans time their oversight. Recovery is retrospective by definition, and the longer an error persists, the more of its total cost is locked into the recovery bucket, where reclaiming it takes negotiation, and the less remains available as avoidance. An error caught in month two costs less in total than the same error caught in an audit finding delivered 18 months later, even if the eventual recovery succeeds in full.

Frequently asked questions

Who recovers pharmacy overpayments, the health plan or the payment integrity partner?

The health plan pursues recovery directly with its PBM. An independent payment integrity partner identifies, validates, quantifies, and documents the overpayment, then equips the plan with the affected claims, the contractual basis, the calculated impact, and recommended next steps. The plan owns the PBM relationship and the reconciliation, supported by evidence it did not have to assemble manually.

What is the difference between recovery and cost avoidance in pharmacy claims?

Recovery is money reclaimed on claims that were already paid incorrectly. Cost avoidance is money that is never overpaid because the root cause of an error was corrected, so subsequent claims adjudicate accurately. Recovery is visible in a reconciliation, while cost avoidance accrues quietly on every future claim in the corrected category, which is why systemic corrections often deliver more total value than the recoveries that prompted them.

How long does PBM overpayment recovery take?

Timelines vary with the nature of the finding and the reconciliation pathway it follows. Straightforward pricing corrections tied to clear contract language tend to resolve faster than issues requiring claims reprocessing or interpretation of benefit provisions. The strongest lever a plan has on timeline is documentation quality: complete, claim-level findings with a clear contractual basis give the PBM little to investigate and less to dispute.

Do PBMs resist overpayment recovery efforts?

Plans are often braced for more resistance than they encounter. Documented, claim-level findings are difficult to dispute, and the reconciliation mechanics usually already exist in the contract. The regulatory attention on PBM practices has also made cooperation with plan oversight the path of least resistance for PBMs. Where friction does occur, it tends to concentrate on findings that arrive as estimates or suspicions rather than as complete evidence.

Does pursuing recovery damage the relationship with the PBM?

Handled through documented findings and root-cause correction, recovery tends to put the relationship on firmer footing rather than weaker. The plan's discrepancy conversations already happen today; documentation changes their quality, not their existence. Both parties benefit when the benefit runs as designed, and a PBM responding to specific evidence resolves issues faster than one asked to investigate itself.