Accounting for Rebates: ASC 606, ASC 705-20, and Tax Treatment

Accounting for rebates requires two different frameworks depending on which side of the transaction you sit on. If you offer rebates to customers, ASC 606 treats the rebate as variable consideration: you estimate the future rebate at the time of sale and reduce recognized revenue by that estimate, parking the difference as a refund liability. If you receive rebates from a vendor, ASC 705-20 treats the payment as a reduction of the purchase price, which lands either on inventory (for goods still on hand) or on cost of goods sold (for goods already sold). Book and tax treatment can diverge on both sides, and uncashed rebate checks carry their own escheatment obligations.

Customer Rebates You Offer: ASC 606

A rebate tied to volume thresholds, prompt payment, or similar conditions is variable consideration under ASC 606. The standard lists rebates explicitly alongside discounts, refunds, credits, and price concessions.¹ You cannot book the full sticker price and sort the rebate out later. The estimate has to be built into the transaction price from the moment of sale.

Sell a product for $100 with an expected $10 rebate, and you recognize $90 of revenue. The remaining $10 goes on the balance sheet as a refund liability, representing cash you’ve collected but don’t expect to keep. ASC 606 requires recognizing a refund liability whenever you receive consideration from a customer and expect to return some of it.¹ That liability sits on the books until the rebate is paid or the conditions expire unmet.

The Constraint on Variable Consideration

Estimating the rebate is only half the job. ASC 606 adds a constraint: include variable consideration in the transaction price only to the extent it is probable that a significant reversal in cumulative recognized revenue will not occur when the uncertainty resolves.¹ Do not count revenue you might have to give back.

Several factors push toward constraining the estimate further:

The rebate amount depends heavily on market volatility, third-party actions, or weather conditions.
The uncertainty won’t be settled for an extended time.
You have little experience with similar contracts, or past experience is not a reliable guide.
Your company regularly offers price adjustments or changes payment terms on similar deals.
The contract allows for many possible rebate tiers or amounts.¹

A flat 2% rebate on purchases over $1 million takes less judgment than a multi-tier program tied to volatile purchasing behavior. Aggressive or uncertain programs typically need to be constrained downward, meaning you recognize less revenue upfront and pick up more later if the uncertainty resolves favorably.

Choosing an Estimation Method

ASC 606 offers two approaches, and you pick whichever better predicts the amount you’ll ultimately collect.¹

The expected value method calculates a probability-weighted average across all possible outcomes. It fits a large portfolio of similar contracts or situations where a wide range of outcomes is plausible. A 60% chance of a $5,000 rebate and a 40% chance of $10,000 gives you an expected value of $7,000, even though $7,000 is not an amount that will actually occur.

The most likely amount method picks the single most probable outcome. It fits binary situations or contracts with a small number of discrete tiers. Once you pick a method for a particular contract, you apply it consistently for that contract’s life. Different contracts can use different methods.

Updating the Estimate Each Period

Rebate estimates are not set-and-forget. At the end of each reporting period, you reassess based on the best available information. When the estimate changes, the adjustment hits the current period as a cumulative catch-up. If you initially estimated a $10,000 liability but now believe it will be $12,000, current-period revenue drops by the $2,000 difference. Prior periods are not restated. The same works in reverse: if the customer looks less likely to hit the threshold, you release part of the refund liability into current revenue.

Vendor Rebates You Receive: ASC 705-20

On the receiving side, the accounting flips. ASC 705-20 treats cash consideration from a vendor as a reduction of the purchase price, not as revenue. Where the reduction lands depends on what has happened to the related inventory:

Inventory still on hand: the rebate reduces the carrying cost of that inventory. Goods bought for $50,000 with a $3,000 volume rebate earned are carried at $47,000.
Goods already sold: the rebate reduces cost of goods sold in the period, improving reported gross margin.

You recognize the rebate as it is earned, not when cash arrives. For a volume-based program, that means allocating a portion of the expected rebate to each qualifying purchase throughout the period, provided you expect to meet the overall threshold. The entry debits a receivable from the vendor (or cash, if already paid) and credits inventory or COGS depending on whether the related goods are still on the shelves.

If your inventory flows through FIFO, LIFO, or weighted average, the rebate recognition should follow the same pattern so the cost reduction tracks logically.

When a Vendor Payment Counts as Revenue Instead

There is an exception. If you provide a distinct good or service to the vendor in exchange for the payment, something the vendor would otherwise buy from a third party, the payment is revenue rather than a cost reduction. A retailer that provides dedicated shelf space, marketing displays, or promotional services to a manufacturer may be earning revenue, if those services are genuinely separable from the purchase arrangement and have standalone value. The burden of proof sits with the company receiving the consideration. Without a clear case that something identifiable and distinct is being provided back, the default treatment applies and the whole amount reduces purchase cost.

Federal Income Tax Treatment

Book accounting and tax treatment do not always line up, and the differences create temporary timing differences worth tracking.

For the Buyer

The IRS generally treats a rebate received by a purchaser as a purchase price adjustment rather than taxable income. The rebate reduces the cost basis in the purchased property rather than generating gross income under Section 61. Buy equipment for $600 and later receive a $500 rebate, and your adjusted basis drops to $100.² A rebate received at the point of sale simply reduces the initial basis; one received later triggers a basis adjustment under Section 1016 when it arrives.

For the Seller

Accrual-method sellers face a stricter timing rule. Under 26 CFR § 1.461-4, economic performance for a rebate liability occurs when payment is actually made, not when the liability is estimated or accrued for book purposes.³ Accrue a $2,000 rebate liability in December but pay it in January, and the deduction generally falls in the payment year.

The recurring item exception under § 1.461-5 offers a narrow escape. It allows deducting the rebate liability in the accrual year if the all-events test is met by year-end and payment occurs within 8½ months after the close of that taxable year.³ Miss the 8½-month window and the deduction shifts to the later year. The rule applies whether the rebate is booked as a deduction from gross income, an adjustment to gross receipts, or a change to cost of goods sold.

Uncashed Rebate Checks

Issuing a check does not extinguish the liability. If a customer never cashes it, the obligation remains on the books. Writing off an uncashed rebate check early understates liabilities and overstates income, and both create audit exposure.

After the check has been outstanding for a period set by state law (typically one to five years depending on the jurisdiction), the unclaimed amount becomes unclaimed property subject to state escheatment. At that point, the funds must be turned over to the appropriate state rather than reversed into income. Most states require a good-faith effort to contact the payee before escheatment, and virtually all states impose reporting obligations and potential penalties for noncompliance. Companies with large consumer rebate programs can accumulate meaningful escheatment exposure if the tracking lapses.

Presentation and Disclosure

Customer rebates hit the income statement and balance sheet at the same time. Revenue appears net of estimated variable consideration; the estimated future payments sit as a refund liability, sometimes labeled a contract liability. The liability is generally classified as current, reflecting settlement within one year or the normal operating cycle.

Vendor rebates reduce inventory values for goods still held and reduce COGS for goods already sold. A receivable from the vendor appears on the balance sheet until the cash arrives.

ASC 606 disclosure requirements are detailed. Companies must disclose:

How the transaction price is determined, including the approach used to estimate variable consideration and assess whether estimates are constrained.¹
Significant payment terms, including whether consideration is variable and whether the estimate is constrained.
The methods, inputs, and assumptions used to measure obligations for refunds and similar payments.
A reconciliation of beginning and ending balances for refund liabilities and vendor rebate receivables.

Entities that elect certain practical expedients under ASC 606 still cannot skip constraint-related disclosures. At a minimum, a company must explain the methods, inputs, and assumptions it uses to assess whether a variable-consideration estimate is constrained.¹

1
FASB. Revenue from Contracts with Customers (Topic 606) – ASU 2014-09
2
Internal Revenue Service. Announcement 2024-19
3
eCFR. 26 CFR 1.461-4 – Economic Performance