The deduction stack that defines specialty pharmacy economics
A specialty pharmacy invoices a payer or manufacturer for the full list price of a dispensed prescription. The cash that arrives is meaningfully less, sometimes 30 to 50 percent less, by the time every deduction works through the system. Commercial rebates. Medicaid rebates. 340B chargebacks. Prompt-pay discounts. Returns. Copay assistance. Hub and distribution service fees. The waterfall from gross to net is the operating reality.
Most ERP implementations treat deductions as period-end accruals. Gross revenue posts at invoice. A journal entry at quarter close estimates deductions in aggregate. The entry plugs to the cash collected. Variance becomes a black box. Finance cannot explain to the CFO, the auditor, or the board which deductions are running hot, which are mispriced, or which represent leakage.
NetSuite, configured for specialty pharmacy, posts each deduction at the transaction level with attribution to the originating prescription, payer, and manufacturer agreement. The waterfall is a query, not a reconstruction. Archer's specialty pharma configuration treats this as the foundational design principle.
Net revenue should be a reported number, queryable at the SKU, payer, manufacturer, or prescriber level. For most specialty pharmacies, it is a quarterly accrual exercise. The gap is configuration.
The 7 deduction categories that matter
01 Commercial rebates
Negotiated between the manufacturer and the PBM or payer. The specialty pharmacy is often an intermediary that accrues a portion of the rebate for itself based on its agreement structure. Rebate accrual rate is driven by the manufacturer agreement, captured in Contract Lifecycle Management, and applied automatically at point of dispense based on SKU, payer, and tier.
02 Medicaid rebates
Statutory rebates under the Medicaid Drug Rebate Program. CMS publishes Unit Rebate Amounts. The pharmacy or manufacturer pays the state directly. Configuration uses NDC-level rebate logic with state-specific overrides for supplemental rebates negotiated between states and manufacturers.
03 340B chargebacks
Manufacturers replenish 340B inventory at ceiling price; commercial inventory replenishes at WAC. The chargeback is the difference, claimed by the wholesaler against the manufacturer. For a pharmacy that operates as a contract pharmacy under a covered entity agreement, the configuration has to identify 340B-eligible dispenses at point of fulfillment and route them to the 340B inventory pool.
04 Prompt-pay discounts
Typically 2 percent for payment within a defined window. Posted automatically when the receipt clears within the discount period. Variance investigation focuses on customers who consistently take the discount outside the window.
05 Returns and reversals
Saleable returns flow back into inventory at the original lot. Non-saleable returns are destroyed and the loss is recognized. Reversals occur when a payer reprocesses a claim and recovers payment. Each has its own journal pattern.
06 Copay assistance
Manufacturer-funded programs that reduce patient patient out of pocket cost. The pharmacy bills the manufacturer's hub or copay card vendor for the assistance amount. From a financial statement perspective, copay assistance is a discount on gross revenue, not a payable.
07 Hub and distribution service fees
The pharmacy pays hub fees to the manufacturer's hub services vendor and may pay distribution fees to wholesalers. These are operating expenses, not contra-revenue, but they are part of the gross-to-net economics that determine product-level profitability.
The NetSuite configuration: 4 design decisions
Design decision 01: Contra-revenue account structure
Each deduction category posts to its own contra-revenue account. The chart of accounts looks like:
4000 Gross product revenue4100 Contra-revenue: commercial rebates4110 Contra-revenue: Medicaid rebates4120 Contra-revenue: 340B chargebacks4130 Contra-revenue: prompt-pay discounts4140 Contra-revenue: returns and reversals4150 Contra-revenue: copay assistance4900 Net product revenue (calculated)
Each contra-revenue account is reportable at the SKU, payer, manufacturer, and prescriber level through NetSuite class and department dimensions, plus custom fields on the transaction.
Design decision 02: Accrual rates driven by contract structure
Rebate accrual rates are stored on the contract record in Contract Lifecycle Management, not in static tables. When a manufacturer agreement is renegotiated, the new rate takes effect on the contract effective date. Historical transactions retain the rate that was in force when they posted.
Design decision 03: Reconciliation against actual
Accrued deductions reconcile against actual remittance or chargeback files on a monthly cadence. Variance between accrual and actual posts to a true-up account. Persistent variance triggers an investigation: rate is wrong, contract terms changed, or eligibility was misclassified.
Design decision 04: ASC 606 variable consideration treatment
ASC 606 requires that variable consideration be estimated and constrained to the amount where it is probable that a significant reversal will not occur. Each deduction category has its own methodology, documented in the contract record.
Commercial rebates: expected value method, based on historical accrual against actual variance.
Medicaid rebates: most likely amount based on the CMS-published URA.
340B chargebacks: most likely amount based on the chargeback contract terms.
Returns: expected value method, based on historical return rate by product.
Common configuration errors
Error 01: Single contra-revenue account for all deductions
Aggregating all deductions into a single account destroys the ability to investigate variance. When net revenue is 8 percent below expected, the CFO needs to know which deduction is driving it. A single account does not answer.
Error 02: Static rebate rates
Hardcoding rebate rates in a table rather than driving them from the contract record means contract changes require IT involvement. Every renegotiation creates a configuration debt. The cleaner approach drives rates from Contract Lifecycle Management with effective-dated rate tables.
Error 03: No transaction-level attribution
Posting deductions in aggregate against gross revenue means the system cannot answer questions like net revenue by prescriber, by payer, or by manufacturer. Every analysis becomes a spreadsheet project.
Error 04: No reconciliation between accrual and actual
If accrued deductions are never compared against the actual remittance files, the books never self-correct. Persistent over-accrual inflates reserves. Persistent under-accrual leaves liability off the balance sheet. Monthly reconciliation against the actual is the discipline that keeps the waterfall honest.
Error 05: ASC 606 applied as a single estimate
Applying a single variable consideration estimate to total gross revenue conceals the heterogeneity in the deduction stack. Each category has different variance characteristics. The methodology should reflect that.
What the configured waterfall looks like in operation
When the configuration is in place, the close runs differently. Gross revenue posts at fulfillment. Each deduction posts at the same transaction, driven by contract terms. Net revenue is a calculated balance, available at any dimension. At month end, the accruals reconcile against remittance files automatically. The CFO gets a net revenue report by product, by payer, by manufacturer, by prescriber, on the first business day of the close.
That is the operational difference between treating gross-to-net as a configuration problem versus an accrual problem. The companies that get it right operate on numbers their finance teams trust. The companies that get it wrong spend the close trying to reconcile.
Related on archerinsights.com
- Specialty pharma industry page. Archer's full configuration approach for specialty pharmaceutical operations.
- NetSuite for specialty pharmacies hub. Gross-to-net, 340B, and DSCSA compliance in one configuration.
- Drug stores and pharmacies industry page. Adjacent retail and regional pharmacy operating model.
- Contract Lifecycle Management module. Manufacturer agreement and rebate term tracking.
- Drug License App. Multi-state pharmacy licensure tracking.
- Case studies. Documented specialty pharmacy engagements.