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

Accounting for rebates splits along two sides of the transaction. If you offer the rebate to a customer, ASC 606 treats it as variable consideration: you estimate the rebate at the time of sale, reduce recognized revenue by that amount, and park the difference as a refund liability. If you receive the rebate from a vendor, ASC 705-20 treats it as a reduction to the cost of the goods you bought, which lands either in inventory or in cost of goods sold depending on whether you’ve already sold the related items. Federal tax rules add a timing wrinkle, especially for accrual-method sellers who can’t deduct a rebate liability until it’s paid (with one narrow exception).

Selling With a Rebate: ASC 606

A rebate tied to volume thresholds, prompt payment, or any other condition is variable consideration under ASC 606. The standard lists rebates alongside discounts, refunds, credits, and price concessions as forms of consideration that can vary based on future events.¹ You can’t book the full sticker price and deal with the rebate later. You estimate the rebate upfront and reduce recognized revenue by that amount at the time of sale.

Sell a product for $100 and expect the customer to earn a $10 rebate, and you recognize $90 of revenue. The remaining $10 goes to the balance sheet as a refund liability, representing cash collected that you 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.¹ The liability stays until the rebate is paid or the conditions expire unmet.

The estimate isn’t static. At the end of each reporting period, reassess the refund liability with the best available information. When the estimate changes, the adjustment hits the current period as a cumulative catch-up rather than a restatement of prior periods. A $10,000 estimate that grows to $12,000 reduces current-period revenue by the $2,000 difference. If conditions suggest the customer won’t hit the threshold you expected, release part of the liability and recognize additional revenue in the current period.

Expected Value or Most Likely Amount

ASC 606 gives you two estimation methods, 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 a single contract with a wide range of plausible outcomes. If there’s a 60% chance you’ll owe a $5,000 rebate and a 40% chance you’ll owe $10,000, the expected value is $7,000. That becomes your estimate even though $7,000 isn’t an amount that will actually occur.

The most likely amount method picks the single most probable outcome. It fits binary situations and contracts with a small number of discrete tiers. If a customer has an 85% chance of hitting the $5,000 rebate tier and a 15% chance of hitting nothing, the most likely amount is $5,000.

Once you pick a method for a contract, apply it consistently for the life of that contract. Different contracts can use different methods: a simple pass/fail program might use most likely amount while a complex tiered program uses expected value.

The Constraint

Estimating is only the first step. ASC 606 adds a limit on how much variable consideration you can include in the transaction price. Include it only to the extent it is probable that a significant reversal in cumulative recognized revenue won’t occur when the uncertainty resolves.¹ In plain terms: don’t count revenue you might have to give back.

Several factors push toward constraining the estimate further:

The rebate depends on market volatility, third-party actions, or weather.
The uncertainty won’t resolve for an extended period.
You have little history with similar contracts, or past experience isn’t a reliable guide.
Your company regularly offers price concessions or changes payment terms on similar deals.
The contract allows for many possible rebate tiers or amounts.¹

A flat 2% rebate on all purchases over $1 million needs less judgment than a multi-tier program with volatile customer behavior. The uncertain programs usually require constraining the estimate downward, so you recognize less revenue initially and pick up more later if the uncertainty resolves favorably.

Receiving a Rebate: ASC 705-20

When you’re the buyer, the accounting flips. ASC 705-20 treats cash consideration received from a vendor as a reduction of the purchase price of the goods, not as revenue. Where the reduction lands depends on whether the related inventory is still on hand.

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

Recognize the rebate as it’s earned, not when the cash arrives. For a volume-based rebate, allocate a portion of the estimated rebate to each qualifying purchase through the period, provided you expect to meet the overall threshold. The journal entry debits a receivable from the vendor (or cash, if already paid) and credits inventory or COGS depending on where the related goods sit.

When Vendor Consideration Is Revenue Instead

There’s one exception to the cost-reduction default. 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, you account for it as revenue. A retailer that provides dedicated shelf space, marketing displays, or promotional services to a manufacturer may be providing distinct services with standalone value, and the payments for those services are revenue to the retailer.

The burden of proof sits with the party receiving the money. If you can’t demonstrate that you’re providing something identifiable and distinct back to the vendor, the default applies and the full amount reduces your purchase cost.

Federal Income Tax Treatment

Book accounting and tax accounting for rebates don’t always line up, and the differences create temporary timing differences you have to track.

Buyer

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

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 in January, and the deduction generally falls in the payment year.

The recurring item exception under § 1.461-5 allows deducting a rebate liability in the year it accrues, provided the all-events test is met by year-end and payment occurs within 8½ months after the close of that taxable year.³ Miss that 8½-month window, and the deduction shifts to the later year. The rule applies to all rebates regardless of how they’re characterized on the books, whether as a deduction from gross income, an adjustment to gross receipts, or a change to cost of goods sold.

Uncashed Rebate Checks

Writing the check doesn’t retire the liability. If the payee never cashes it, the obligation stays on your books. Reversing the liability into income too early understates liabilities and overstates income, both of which cause audit problems.

After the check has been outstanding for a period set by state law (typically one to five years depending on the jurisdiction), the uncashed amount becomes unclaimed property subject to state escheatment rules. At that point the company turns the funds over to the appropriate state rather than reversing them into income. Most states require a good-faith effort to contact the payee before escheating, and virtually all states impose reporting obligations with penalties for noncompliance. Build a process for tracking outstanding checks, following up with payees, and filing unclaimed property reports when dormancy periods expire. Large consumer rebate programs can accumulate significant escheatment exposure if this tracking lapses.

Financial Statement Presentation and Disclosure

Customer rebates hit both statements at once. Revenue appears net of estimated variable consideration on the income statement, and the estimated future payments sit as a refund liability (sometimes labeled “contract liability”) on the balance sheet, generally classified as current. Vendor rebates flow through the balance sheet as a reduction to inventory values for goods still held and through the income statement as a reduction to COGS for goods already sold, with a receivable from the vendor on the balance sheet until cash arrives.

ASC 606 disclosure requirements are detailed. Companies 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 variable estimate is constrained.
The methods, inputs, and assumptions used to measure obligations for returns, refunds, and similar payments.
A reconciliation of beginning and ending balances for refund liabilities and vendor rebate receivables, so investors can see how much estimates shifted during the period.

Even entities that elect certain practical expedients under ASC 606 can’t skip the constraint-related disclosures. At minimum, a company must explain the methods, inputs, and assumptions used to assess whether an estimate of variable consideration 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