31 Aug Building a WAC Spend Recapture Workflow for Your 340B Program
Every covered entity running a replenishment model buys some drugs at wholesale acquisition cost that should have been replaced at 340B pricing. Not because anyone did anything wrong, but because an eligible dispense did not accumulate, a mapping was missing, or a package never triggered. The money is real and so is the fix, and it is almost entirely a workflow problem rather than a knowledge problem. Below is the sequence we build with pharmacy and finance teams, and the guardrails that keep it from turning into a compliance problem.
What WAC Spend Recapture Means Inside a 340B Program
In a replenishment model you dispense from existing inventory, the system accumulates eligible dispenses, and when accumulated units reach a package quantity a 340B replacement order is triggered. When accumulation works, your purchasing mix shifts toward 340B pricing over time. When it does not, the same drug gets replaced at wholesale acquisition cost instead.
Recapture is the disciplined identification of dispenses that were eligible and did not accumulate, followed by the correction that moves the associated purchasing back onto the right account going forward. It is not a way to reclassify past purchases at will. What is and is not correctable depends on your wholesaler terms, manufacturer policies, your third party administrator’s rules, and your own written policy, and those constraints have to be established before the workflow is designed rather than discovered halfway through.
Framed properly, this is a data completeness exercise with a purchasing consequence. Our other 340B services cover this alongside the adjacent financial operations work.
The Workflow Step by Step
Capture the full universe of dispenses
Start with everything, not with what already accumulated. Pull dispense records across every registered site, every dispensing system, and every contract pharmacy relationship for the period under review. Missing a data source at this step guarantees the gap survives the analysis, and mixed environments after an acquisition are where sources go missing.
Match dispenses to eligibility evidence
For each dispense, establish whether the entity has the record demonstrating the patient relationship, the qualifying provider relationship, and the registered site. This is the step that determines whether a gap is a recapture opportunity or an ineligible claim that should never accumulate. Getting this wrong in the permissive direction is the fastest way to convert a finance project into an audit finding.
Reconcile eligible dispenses against accumulation
Now compare eligible dispenses to what the accumulator actually recorded. The difference is your candidate pool. Group it by drug, by site, by pharmacy, and by date so the pattern is visible, because a scattered handful of unmatched claims is a data quality issue while a concentrated block is a configuration failure.
Diagnose the root cause before correcting anything
Candidates cluster into a small number of causes. Product mapping gaps where a national drug code was never linked. Package size and unit of measure mismatches that leave fractional accumulations stranded. Site or clinic identifiers absent from the feed. Prescriber records that failed the eligibility test because the source data was incomplete rather than because the prescriber was ineligible. Timing, where dispenses fell outside the accumulation window. And carve decisions applied inconsistently across payers. Our review of 340B TPA software behavior covers where these configuration failures usually hide.
Correct, replenish, and reconcile
Fix the underlying configuration first so the gap stops growing. Then process whatever correction your wholesaler, manufacturer, and administrator terms permit for the identified population, within your written policy. Finally reconcile the result end to end, meaning corrected accumulations, resulting orders, and the general ledger impact all agree and are documented. A recapture that finance cannot tie out is a recapture that will be questioned later.
Where Recapture Opportunities Leak Away
Five patterns account for most of the leakage we find.
New drugs and formulary changes that were never mapped, which quietly send an entire product’s volume to wholesale acquisition cost.
Clinic openings and relocations where the site identifier reached the pharmacy system before it reached the accumulator.
Contract pharmacy data feeds that fail partially rather than completely, since a feed that stops entirely gets noticed and one that drops a subset does not. Our overview of 340B contract pharmacy operations covers the oversight this requires.
Specialty and limited distribution products, where the ordering path differs enough from routine replenishment that it falls outside the standard workflow.
Mixed use areas where the outpatient and inpatient determination is made downstream of the dispense record, leaving eligible outpatient volume unclassified.
The Guardrails That Keep Recapture Compliant
This is the part that gets skipped when recapture is run as a savings initiative rather than a program function.
Eligibility is never relaxed to increase capture. If a dispense lacks the evidence, it is not a recapture candidate, and no financial target changes that.
Duplicate discount exposure gets checked at the same time. Recapturing volume that should have been carved out for Medicaid trades a purchasing gain for a serious finding, which is why our post on Medicaid duplicate discounts belongs on the desk of whoever runs this workflow.
Every correction leaves an audit trail. What was identified, on what basis, who approved it, what was corrected, and when. If the workflow cannot produce that record on demand, it is not ready to run.
Incentives stay aligned. Where an outside party is compensated on identified savings, the entity reviews the eligibility determinations independently rather than accepting them.
Written policy governs the whole thing, and it is reviewed when wholesaler terms, manufacturer policies, or administrator rules change. Those terms have been unusually fluid, and the rebate model developments we track in our 2026 rebate model briefing may change how purchasing, crediting, and reconciliation work in ways that a static policy will not survive.
Turning It Into a Standing Process
Most entities run recapture once, recover a meaningful amount, and never build the muscle. The version that pays repeatedly is a monthly exception review over the unmatched dispense pool, a quarterly root cause review that closes configuration causes rather than reprocessing symptoms, a mandatory recapture check triggered by any system, site, or vendor change, and a single named owner accountable for the pool shrinking over time rather than for the dollars recovered in any one cycle.
That last distinction matters. A recapture program measured on recovery is rewarded when the gap stays large. A recapture program measured on the size of the unmatched pool is rewarded when the underlying configuration gets fixed, which is the outcome you actually want. We keep working material for both views in the 340B resources library.
Three measures are enough to run it. The unmatched eligible dispense rate, tracked by site and by pharmacy, which should trend down. The time from a configuration change to its first recapture check, which should stay short. And the proportion of identified candidates that trace to a root cause already closed, which should approach zero if your quarterly reviews are working and tells you they are not if it does not.
Ownership is the other half. In most health systems this lands with the 340B program manager, with a finance partner who validates the ledger impact and a systems owner who executes the mapping fixes. Naming all three, and giving the program manager the standing to require the fixes, is what separates a workflow that runs quarterly from one that ran once. If your program has never had that trio in the same recurring meeting, start there rather than with the data pull. Our 340B services team usually spends the first engagement getting that meeting to exist.
Next Steps
If your unmatched dispense pool has never been quantified, that measurement is the whole first engagement and it usually pays for itself. Get help with WAC spend recapture and we will start by sizing the gap before anyone proposes a fix.