You signed a contract promising 100% prescription drug rebate pass-through. Your CFO smiled. Your consultant nodded. And a few months later, the check arrived. But here’s what nobody told you: the biggest threat to actually keeping those savings isn’t the contract language, the PBM’s fine print, or even the pharmacy benefit manager themselves. It’s the software that sits between your employees and your claims data. Your benefits administration platform.
After spending over a decade auditing employer plans and the systems that support them, I’ve uncovered a pattern that rarely gets discussed in the benefits world. Rebate pass-through isn’t a pricing issue. It’s a data architecture problem. And if your HRIS, enrollment system, or third-party administrator wasn’t built to handle pharmacy rebate data at the individual employee level, you’re leaving savings on the table-often without any idea it’s happening.
Three Hidden System Traps That Kill Pass-Through
Trap 1: Your System Speaks a Different Language Than Your PBM
Most benefit administration platforms were designed for medical claims, premium billing, and eligibility files. They don’t natively ingest pharmacy rebate data. PBMs send rebate information in quarterly spreadsheets, PDFs, or flat-file extracts that no standard HRIS can automatically consume. So what happens in practice? The rebate check lands in your finance department. Someone manually applies it to the plan’s general fund. The link between that rebate and the specific prescriptions that generated it is broken forever. You never see which drugs drove the savings, which employees contributed most, or whether the PBM actually passed through the correct amount.
- The fix: Demand a structured, HIPAA-compliant data feed in your PBM contract-something like an 835 transaction with rebate extensions. If your vendor can’t ingest it, ask why.
- The reality: Most mid-market employers accept PDFs and never realize how much they’re losing.
Trap 2: You Can’t Allocate Savings Back to the Right Employee
True pass-through means that an employee on a $5,000-per-month specialty drug should directly benefit from the rebate that drug generates. But almost no benefits system can deliver that. Why?
- Pharmacy claims data stays in the PBM’s system, not your HRIS.
- Rebate calculations are pooled across hundreds of drugs and thousands of members.
- HIPAA creates a wall between medical data and pharmacy data unless you have explicit authorizations.
The result? Rebates get dumped into the plan’s general fund. That might look good on a trend report, but it silently subsidizes low-cost members at the expense of high-cost members. Your employees don’t see the impact, and neither do you-at least not at the individual level.
Trap 3: Compliance Risks Hiding in the Data Gap
ERISA requires plan fiduciaries to ensure all compensation-including rebates-is reasonable. If you can’t produce a pre-rebate and post-rebate drug cost per member on demand, you can’t prove you fulfilled that duty. Meanwhile, HIPAA adds another layer of risk: if you upload a rebate file with member-level NDC data into a system that doesn’t have a business associate agreement with your PBM, you’ve just violated privacy rules. And ACA affordability testing? Rebates affect the “share of premium” calculation. If your system doesn’t track rebates as a separate line item, you may miscalculate whether your plan meets minimum value requirements.
Three Systems Fixes That Actually Work
After working with employers who get pass-through right, I’ve seen what separates them from the pack. It’s not a better contract. It’s better system integration.
- 1. Require a machine-readable data feed in your PBM agreement. Not a quarterly PDF. Not a CSV you have to reformat. A standard, HIPAA-compliant file-like an 834 or 835 with rebate extensions-that your benefits administration platform can ingest automatically. PBMs can do this. They already do for their own internal analytics.
- 2. Build a rebate reconciliation module inside your HRIS or TPA system. Map the PBM’s rebate file to your enrollment data using employee IDs. Create a monthly dashboard that shows total rebates, per-member allocation, and net drug cost. Most modern platforms have API capabilities or report builders that can handle this. If your vendor says they can’t, ask them to explain why-and then consider switching.
- 3. Audit the allocation algorithm, not just the contract. Hire a pharmacy auditor who specializes in systems validation. They should review how the PBM’s system calculates rebate pools and how your benefits admin system processes that data downstream. Most leakage happens in the gap between two systems, not in the contract language.
The Bottom Line
Rebate pass-through is not a contract problem. It’s a systems integration problem. Your PBM can promise 100% pass-through all day long. But if your benefits administration platform cannot capture, allocate, and report that pass-through at the individual employee level, you’re operating on blind faith. The industry loves to talk about transparency. But real transparency requires systems that speak the same language. Until your enrollment platform, claims adjudicator, and PBM share a live data pipeline for rebates, pass-through will remain a marketing gimmick-and your prescription drug trend will keep mysteriously outrunning inflation.
Ask your benefit administration vendor this week: “Where do you store pharmacy rebate data in our system?” If they pause, you have your answer.