How do I set up a refund/returns reserve, and how does it affect revenue recognition?

Estimate expected returns from your own trailing return-rate history, then split every sale into two pieces: revenue for what you expect to keep, and a refund liability for what you expect to pay back. ASC 606 also requires a matching return-asset for goods you expect to get back — and constrains the whole estimate to what won't cause a significant revenue reversal later.

By Zuny Fester, Head of Operations and Marketing

Reviewed by Zuny Fester

Published September 14, 2026Last reviewed September 14, 2026Editorial policy

Part of the revenue recognition guide.

What gets recognized as revenue	Only the consideration expected to be kept after returns
What the refund liability represents	The amount expected to be paid back to customers for anticipated returns
What the return asset represents	The value of goods expected to come back — a separate balance, not netted against the liability
Estimation basis	Trailing-twelve-month return rates by product category, adjusted for known factors
The governing constraint	ASC 606-10-32-11 — only recognize variable consideration if a significant reversal isn't probable

Why a return isn't just a later journal entry

ASC 606 treats a right of return as variable consideration, which means the estimate has to be made at the point of sale, not deferred until an actual return happens. Recognizing full revenue on every sale and only adjusting when a return is actually processed overstates revenue in every period that has open, unreturned inventory sitting with customers — which is exactly the gap a refund reserve exists to close.

The three things to book, not just one

A sale with an expected return rate generates three separate items, not a single adjusted revenue number: revenue for the portion expected to be kept, a refund liability for the portion expected to be paid back, and an asset for the goods expected to be physically returned — the return asset. These have to be presented separately rather than netted against each other; a common early mistake is booking only the reduced revenue and the liability while leaving the return asset out entirely, which understates the balance sheet.

Building a defensible estimate

The strongest evidence for a return-rate estimate is the entity's own trailing-twelve-month history, broken out by product category rather than a single blended rate — categories with structurally different return behavior (apparel vs. electronics, for instance) shouldn't share one number. External factors (economic conditions affecting purchasing behavior) and internal factors (a new product launch, a known quality issue) both need to adjust that baseline. The whole estimate is bounded by the standard's own constraint: variable consideration can only be included in the transaction price to the extent a significant reversal isn't probable — an aggressive return-rate assumption that risks a big revenue reversal later isn't allowed just because it produces a better-looking number now.

Next step

Map the finance workflow with the most exposure and prove the automation path.

Bring the invoice, contract, payment reconciliation, or customer finance workflow you have to defend at audit. Loopfour can map the trigger, controls, integrations, and approval loop.

Book a workflow review

Worked example

A $500,000 month of sales with a 6% historical return rate

A retailer's apparel category has averaged a 6% return rate over the trailing twelve months, with no known factor this month that would move that number. On $500,000 of apparel sales, the entity recognizes $470,000 as revenue (the 94% expected to be kept), books a $30,000 refund liability for the expected returns, and records a return asset for the cost basis of the goods expected back — separately from the liability, not netted against it. If actual returns come in at 5.5% instead of 6% the following month, the reserve is adjusted forward rather than restated backward, since the original estimate was reasonable at the time it was made.

Frequently Asked Questions

No — ASC 606 requires them to be presented separately. The refund liability is what's owed back to the customer; the return asset is the value of the goods expected to come back, and they're evaluated as distinct balances even though they arise from the same estimate.

Use whatever real history exists, supplemented with industry benchmarks or comparable-product data, and disclose the estimation basis — the standard doesn't require twelve months specifically, it requires a reasonable estimate, but shorter history is inherently less reliable and worth flagging in the methodology.

The same variable-consideration logic applies to exchanges for a different product, since the entity is still giving something back rather than fully keeping the original consideration — the specific mechanics depend on whether the exchange is for a similar product (often not treated as a return) or a different one.

Sources

Topic

Revenue Recognition

Revenue recognition determines when — not just how much — revenue hits the books. Under ASC 606 (US GAAP) and its international counterpart IFRS 15, revenue is recorded as a company satisfies its perf…

How-to

How do you calculate a contract's transaction price under ASC 606?

Transaction price is the consideration a company expects in exchange for goods or services. Start with the stated contract price, add variable consideration using the expected-value or most-likely-amount method, constrained to amounts unlikely to reverse, adjust for any significant financing component, then subtract noncash consideration and amounts payable to the customer.

Role guide

How should a controller close revenue at month-end under ASC 606?

At month-end, a controller reconciles the deferred revenue roll-forward to the general ledger, reviews any contract modifications booked during the period, posts recognition journal entries by contract line rather than by invoice, and checks variable consideration estimates against actuals before closing the revenue sub-ledger for the period.

Definition

What's the difference between a contract asset and a contract liability under ASC 606?

It's about which side moved first. A contract asset is your right to payment for goods or services you've already delivered, when that right depends on something other than time passing — you performed, but haven't fully earned an unconditional bill yet. A contract liability is the opposite: the customer paid (or owes payment) before you've delivered what they're paying for.