The accumulator is only as accurate as the assumptions inside it.
Split billing decides which dispenses qualify for 340B pricing. When its logic drifts from how your pharmacy actually operates, you either lose savings you were entitled to or accumulate claims you were not — and only one of those shows up as a finding.
At a glance
- 01Common finding
- Duplicate discounts
- 02Review scope
- Logic + sample claims
- 03State rules covered
- All 50
- 04Deliverable
- Configuration report
Two failure modes, opposite directions
Split billing software separates 340B-eligible dispenses from everything else, accumulating eligible units into a virtual 340B inventory so replenishment can be ordered at 340B pricing. It is the operational heart of a hospital program.
It fails in two directions. Under-accumulation means eligible dispenses are not captured — you paid full price for drugs you could have bought at the ceiling price, and nobody notices because nothing is wrong on the compliance side. Over-accumulation means ineligible dispenses are captured — which is diversion, and which HRSA does notice.
Meanwhile the duplicate discount prohibition sits alongside it: a manufacturer cannot be required to provide both a 340B discount and a Medicaid rebate on the same unit. Preventing that requires your Medicaid Exclusion File status to match what you actually bill, in every state you operate in, for both fee-for-service and managed care.
Configuration, evidence, and the gap between them
01Accumulator logic
- What we test
- Location mapping, provider mapping, order and dispense location alignment, package size and unit conversion accuracy
- Typical finding
- Clinics mapped to the wrong cost center; providers absent from the eligible list after credentialing changes
02Eligibility rules
- What we test
- How the system decides an encounter is 340B-eligible, tested against your written patient definition
- Typical finding
- System logic and written policy describe different rules — auditors test practice against policy
03Medicaid Exclusion File
- What we test
- Carve-in or carve-out status per site and per state, checked against actual claims
- Typical finding
- MEF status set at registration and never revisited after billing practice changed
04Managed care handling
- What we test
- State-by-state MCO rules, identifiers, and whether 340B claims are flagged as required
- Typical finding
- A state adds an MCO flagging requirement and nothing in the workflow changes
05Replenishment integrity
- What we test
- Whether accumulation actually results in correct 340B ordering, and whether inventory reconciles
- Typical finding
- Accumulated units that never convert into 340B purchases — real savings lost silently
06Monitoring evidence
- What we test
- Whether anyone reviews the exception queue, and whether that review is documented
- Typical finding
- The queue is worked but never documented, so there is no evidence of oversight to show an auditor
There is no universally right answer
Carving Medicaid in means using 340B drugs for Medicaid patients and preventing the duplicate discount through the Medicaid Exclusion File and state-specific billing rules. Carving out means buying non-340B drugs for Medicaid patients entirely.
Which is better depends on your state, your fee-for-service versus managed care mix, your reimbursement methodology, and how much operational complexity you can genuinely sustain. Entities frequently inherit a decision made years ago that no longer reflects any of those factors.
- We model both options against your actual payer mix and state rules
- We document the reasoning so the decision is defensible at audit
- We test whether your current status matches your actual billing practice
- We re-check the decision when your state rules or payer mix change
Split billing — common questions
01What is a duplicate discount?
It occurs when a manufacturer is required to provide both the 340B discount and a Medicaid rebate on the same drug unit. The statute prohibits this. Preventing it is the covered entity's responsibility, primarily through the Medicaid Exclusion File and by following state-specific billing and identifier requirements.
02Does the Medicaid Exclusion File cover managed care?
Not by itself. The MEF addresses fee-for-service Medicaid. Managed care duplicate discount prevention is governed state by state, often through claim-level identifiers or modifiers, and the requirements differ meaningfully between states.
03Our TPA handles all of this. Why review it?
Your TPA executes the logic it was configured with. It does not independently verify that the configuration still reflects how your pharmacy operates, that your clinic mapping is current, or that your state rules have not changed.
04How would we know if we are under-accumulating?
You generally would not, because under-accumulation produces no error and no finding — just a smaller 340B purchase volume than you were entitled to. It surfaces only when someone tests eligible dispenses against actual accumulation, which is exactly what this review does.
Marked up with FAQPage schema for search and AI-answer eligibility.
Next step
When was your accumulator logic last tested against reality?
Not reviewed — tested, against real dispenses, by someone who does not administer it.