Why Contract Pharmacies and TPAs Matter More Under the Rebate Model

From one loop to nine steps

Until now, the workflow for these drugs was one loop: accumulate, then replenish at the 340B price. For pilot NDCs, every claim now goes through nine steps: identify eligibility, choose the right pathway, submit within 45 days, track status, work denials, confirm payment, reconcile expected against paid, settle with the pharmacy and keep MFP separate. Most of that work lands with your TPA. For the basics of the pilot, see our explainer on HRSA's revised rebate model.

Catching every pilot claim

The rebate pathway only works if pilot claims are caught. That means flagging pilot NDC-11s, applying the usual 340B eligibility checks for patient, prescriber and location, and routing those claims to Beacon instead of the normal accumulator. Administered drugs count too, so your TPA needs medical claims data, not only pharmacy dispenses.

Why daily submission beats the 45-day deadline

Forty-five days is the deadline, not the target. Submitting daily helps for four reasons:

• Cash flow. The 10-day payment clock does not start until you submit.
• Time to fix errors. A claim sent on day 40 leaves little room to correct a rejection.
• Smaller batches. Rejections arrive a few at a time, not hundreds just before the deadline.
• Duplicates. If two covered entities submit the same prescription, the first valid claim is paid. This can happen when entities share patients and providers.

Clean data before it reaches Beacon

HRSA allows only approved data fields, and purchase or encounter data is not allowed. Patient information must be de-identified or hashed before it reaches Beacon. Quantity and unit of measure must follow Beacon's NDC list, for example Enbrel in 0.5 or 1 mL and Ibrance in multiples of 7. Removing duplicates before submission also prevents avoidable errors. Some entities learned that earlier this year, when 340B ESP stopped removing duplicates itself and started returning them as errors.

Confirming every payment

HRSA expects covered entities to have real-time rebate status for each claim, but a status alone is not enough. Rebates go straight to the covered entity's bank account through Beacon, not through the TPA. Someone still has to check that each payment arrived at the amount owed for that claim, and follow up on short pays.

Records that hold up in an audit

HRSA expects covered entities to keep auditable records of purchases and rebate requests, and it will include rebate-model compliance in audits. It may also use pilot data in routine audits. Your TPA should be able to show what was submitted, when, and how each correction was handled.

The contract pharmacy piece

Contract pharmacy claims follow the same rebate path, but the pharmacy is part of the reconciliation. When a manufacturer rejects a 340B rebate because the Medicare Maximum Fair Price is lower, the MFP refund goes to the pharmacy that filled the prescription, and that has to be settled. Read more in 340B contract pharmacy after the rebate pilot.

Where Aventi fits

Aventi identifies pilot claims, submits pharmacy and medical claims to Beacon daily, removes duplicates before sending, tracks every claim from submitted to paid, and checks each remittance against the amount owed. We can submit rebate claims for all of your pharmacies, and the rebate module works alongside your existing TPA, so you do not have to switch.