When the invoice price and your expectation don't match, that's a compliance event
A buyer pulls an order report and finds a charge that doesn't match what the team expected for a 340B purchase. The conversation quickly drifts toward the wrong question: Is this close enough? In a 340B program that reached $100 billion in discounted purchases in 2025, that mindset is backward. Drug Channels reported that hospitals accounted for 87% of 340B purchases and described a shift from opacity and expansion toward transparency and accountability. For covered entities, ceiling price verification can't be a back-office courtesy check. It needs to be a controlled process connected to purchasing, exception handling, and record retention.
The topic sounds more technical than the underlying issue. Ceiling price verification isn't simply a matter of matching a number in one system to a number in another. Your organization needs to show, after the fact, why it bought at the price it paid, what happened when the data conflicted, and who had authority to decide what came next.
If the file only shows that someone noticed a discrepancy and sent an email, there is no verification process. Just an anecdote.
Compare sources by hierarchy, not by convenience
Most pricing disputes begin with organizations comparing whatever is easiest to export. That is poor discipline. A sound verification process first identifies the authoritative source for the specific question being asked. Are you validating the charged 340B acquisition price on an invoice, checking a wholesaler catalog entry before purchase, or reconciling a split-billing accumulator result to the replenishment order? These tasks relate to one another, but they are not the same control.
The safest approach is to establish a hierarchy of data sources and require staff to use it consistently. The exact hierarchy will vary by system design and purchasing model; the underlying logic should not. Documentation should identify the primary source, the source used for cross-checking, and the action required when the two disagree. Without that structure, staff bounce among wholesaler screens, account reports, internal spreadsheets, and screenshots from prior purchases. The result is an organization defending inconsistent decisions instead of a clear policy.
Drug Channels' 2026 coverage described 340B as entering a new era and highlighted ongoing rebate questions, including HRSA's revised 340B rebate model pilot. Even without getting ahead of guidance details that aren't in the source packet here, the message for covered entities is plain: pricing and discount accountability are under more scrutiny, not less. As the environment moves toward transparency, loose internal comparison methods become harder to defend.
A written procedure should answer several basic questions in plain language. Which fields are compared? Who can perform the review? What counts as a discrepancy? Can the team purchase while the discrepancy is under review? Which record serves as the final evidence that the decision was appropriate? None of this requires heroic system customization. It requires discipline.
What a real discrepancy workflow should look like
Consider a recognizable 340B scenario: pharmacy operations needs the product immediately, the wholesaler charge doesn't match the expected 340B price, and everyone feels pressure to release the order and sort it out later. The urgent purchase itself isn't what creates the problem. The problem is having no documented exception path.
A workable discrepancy workflow needs to do four things:
- capture the conflicting pricing data from the systems used at the time of purchase
- assign the issue to a named role for review
- record the decision to buy, hold, or reroute the purchase
- preserve the final resolution with the invoice and related purchasing records
What that list leaves out: improvisation. If a buyer calls the wholesaler, receives a verbal explanation, and moves on, that explanation needs to become a record the compliance team can retrieve later. If the organization proceeds because patient care operations can't wait, the file should say so. If it holds the order pending review, the file should say that instead. The purpose isn't paperwork for its own sake. It is evidence that the covered entity had a repeatable control, applied it, and retained the result.
Terminology causes trouble here, too. A price discrepancy does not automatically establish overcharging, undercharging, duplicate discount exposure, or diversion. It signals that the purchasing record needs further support. Labeling the issue before the relevant records have been compared creates avoidable compliance problems.
The resolution email is not the entire file. The complete record should connect the original expected price source, the actual transaction, the internal review, and the final disposition. When those pieces are stored in different places, the procedure should identify where each one belongs and how they are linked. Fragmentation, more than the initial discrepancy, often creates the audit problem.
Document the decision, not just the discrepancy
Covered entities often save evidence of the problem more reliably than evidence of the decision. That gets the emphasis backward. A screenshot showing a pricing mismatch is useful, but it doesn't explain why the organization proceeded with the purchase, reversed it, rebilled it through another channel, or escalated it for follow-up.
The purchasing decision is the real compliance artifact because it connects price verification to organizational authority. Who reviewed the issue? What did that person rely on? Was the matter treated as resolved or pending? Did the transaction stand? If the process doesn't require this level of documentation, staff default to informal workarounds. Those workarounds are difficult to defend when someone outside pharmacy asks why the record is incomplete.
Drug Channels' reporting on the program's scale matters for a straightforward reason. In a program with $100 billion in discounted purchases, casual controls are not a serious answer. The article also noted a gross-to-net difference of $79.5 billion, which it described as a proxy for funds available to covered entities. At that scale, attention follows how covered entities operationalize purchasing controls. Ceiling price verification is not a theoretical finance exercise. It is part of the credibility of the 340B purchasing record.
Good documentation protects operations as well. Staff turnover happens. Buyers go on leave. Systems change. A file that depends on one experienced employee's interpretation of a discrepancy is a weak process. A file that shows the organization's standard review path and final rationale lets another employee reconstruct what happened without guesswork.
Build a file that survives scrutiny after the people are gone
Use a simple test: if the buyer, analyst, and pharmacy director all left tomorrow, could someone else understand why the product was purchased at that price? If not, the documentation is unfinished.
That standard matters more as 340B oversight discussions continue moving toward accountability. Drug Channels described 340B in 2026 as part of broader market shifts and policy battles, and separately framed the program as moving from opacity and expansion to transparency and accountability. There is no need to overread those observations. Operationally, they point to greater interest in how purchasing decisions are supported, particularly when the data doesn't line up neatly.
Keep the control plain: define the comparison sources, set the discrepancy workflow, assign a named reviewer to the disposition, and store the evidence with the transaction record. A price mismatch is not just a purchasing nuisance. It is a documentation test.
Sources
- The 340B Program Hit $100 Billion in 2025: Has It Become Too Big to Reform?
- Drug Channels News Roundup, June 2026: PBM Shakeout Accelerates, 340B Enters a New Era, Rebate Questions Persist, Mark Cuban Wins Again, and Ge Bai’s HHS Nomination
- Drug Channels News Roundup, August 2026: 340B Rebate Model v2, Patients Feeling Drug Costs, Specialty Drug Spending Drivers, Impact on Coverage from the IRA, and a Drug Price Adventure
