A customer buys a $1,200 refrigerator and adds a $150 three-year extended warranty at checkout. Your point-of-sale system rings up $1,350, deposits the cash, and — if your books mirror your cash register — records $1,350 in revenue that same day.
That's wrong, and it's wrong in a way that can misstate your financials for three years running.
Under ASC 606, the revenue recognition standard that governs how U.S. businesses report income, that $150 warranty fee doesn't belong to you yet. You haven't earned it. You've promised to be available for repairs over the next 36 months, and accounting rules say you recognize that promise's value only as you deliver on it — a little bit each month, for three years. Book the whole $150 today and your income statement lies to you: this month looks better than it is, and the next 35 months look worse than they are.
Small retailers selling anything with an attached service contract — appliances, electronics, furniture, vehicles, even high-end tools — run into this constantly. Here's how the rule actually works, why it exists, and how to build it into your bookkeeping instead of discovering it during a bank loan application or an accountant's year-end adjustment.
The Core Distinction: Two Kinds of Warranty, Two Kinds of Accounting
ASC 606 splits warranties into two categories, and which bucket yours falls into determines everything.
Assurance-type warranties simply promise that the product works as advertised — the manufacturer's standard 90-day or one-year warranty that comes free with the purchase. This isn't a separate thing you're selling; it's baked into the price of the product itself. You account for it under a different standard (ASC 460) by estimating your expected repair costs and accruing a liability for them upfront, the same day you record the sale. No revenue deferral involved — just a cost estimate sitting on your balance sheet.
Service-type warranties are different. These are warranties the customer pays extra for, that cover more than manufacturing defects — accidental damage, normal wear and tear, coverage that extends well beyond what's standard in the industry. Because the customer is buying an actual service (you standing ready to fix or replace the item over time), accounting treats it as a separate performance obligation — a distinct promise with its own price tag, its own revenue, and its own timeline.
That extended warranty on the refrigerator is a textbook service-type warranty. The customer paid extra, of their own choice, for coverage beyond the manufacturer's standard defect warranty. That $150 isn't sale revenue. It's a liability — specifically, deferred (or "unearned") revenue — until you actually deliver the service, month by month, over the life of the contract.
How to tell which one you're looking at
The standard gives three questions to ask:
- Is it required by law? A mandatory warranty is more likely assurance-type — you're not offering a choice, you're complying with a rule.
- How long does it last? The longer the coverage period stretches beyond what's typical for that product category, the more it looks like a paid-for service rather than a baked-in guarantee.
- What does it actually cover? If it's strictly "we'll fix defects in materials or workmanship," that's assurance-type. If it covers things a manufacturing defect warranty never would — spills, drops, general wear — that's a service.
The clearest signal of all: can the customer buy it separately, for an identifiable extra price? If yes — and your $150 add-on at the register is exactly that — you're looking at a service-type warranty, full stop.
Why the Rule Exists: Matching Revenue to Delivered Value
This isn't bureaucratic hairsplitting. The whole point of accrual accounting is matching — revenue should show up in the period you actually did the work that earned it, not just the period cash happened to change hands.
Think about what you're actually selling when you sell that warranty. You're not selling a repair today. You're selling standing readiness — the promise that if something breaks in month 14 of a 36-month contract, you'll be there. You deliver a little of that promise every single month the contract is active. Recognizing all $150 on day one would mean claiming you'd already delivered three years of service before you'd delivered any of it.
It also protects you from a distortion that's easy to fall into without noticing: a slow month in warranty sales makes your revenue line look artificially bad, and a strong push month (a Black Friday sale on extended coverage, say) makes it look artificially good — even though your actual repair obligations haven't changed at all. Deferring the revenue and recognizing it ratably smooths that noise out and gives you (and anyone reading your financials — a lender, an investor, your own future self) a much more honest picture of the business's real performance.
The Mechanics: Allocating the Price and Recognizing Revenue Over Time
Once you've identified a service-type warranty, two more steps follow.
Step 1: Split the transaction price
If the warranty is priced and sold separately (as in our refrigerator example — $1,200 for the appliance, $150 for the warranty, itemized on the receipt), this step is easy: the $150 is the warranty's price, done.
It gets more involved when a warranty is bundled into one all-in price — a "$1,300 refrigerator, warranty included" promotion, for instance. Now you have to estimate what each piece would have sold for on its own — its standalone selling price — and allocate the total price proportionally. ASC 606 gives you three ways to do this:
- Adjusted market assessment — look at what competitors charge for similar warranties and use that as your benchmark.
- Expected cost plus margin — estimate what it'll cost you to fulfill the warranty obligations, then add the margin you'd normally want on a service like this.
- Residual approach — if the product's price is well-established but the warranty's isn't, subtract the product's known standalone price from the bundle price; whatever's left is allocated to the warranty. This is a fallback, used only when the first two approaches don't produce a reliable number.
For most small retailers, warranties are priced and quoted separately at the register precisely because it sidesteps this allocation exercise. If you're bundling, talk to your accountant about which method fits — but know that the standard expects you to use real, observable data wherever it exists rather than a number you picked because it was convenient.
Step 2: Recognize revenue as you deliver the service
Once you know the warranty's price, that amount goes onto your balance sheet as a liability — unearned revenue — the moment the sale happens. Then, typically on a straight-line basis over the coverage period, you release a portion of it to actual revenue each month.
A $150, 36-month warranty means $150 ÷ 36 = $4.17 recognized as revenue each month. In plain-text bookkeeping terms, the sale itself might look like:
2026-07-20 * "Sale of refrigerator with extended warranty"
Assets:Cash 1,350.00 USD
Income:Sales:Appliances -1,200.00 USD
Liabilities:UnearnedRevenue:Warranty -150.00 USDAnd then, once a month for the next 36 months:
2026-08-20 * "Recognize one month of warranty coverage delivered"
Liabilities:UnearnedRevenue:Warranty 4.17 USD
Income:Sales:WarrantyRevenue -4.17 USDThe beauty of keeping your ledger in a format you can script against — rather than trusting a POS system's default "cash in, revenue out" logic — is that this kind of recurring, formulaic entry is trivial to automate. You're not manually typing 36 near-identical transactions per warranty sold; you're generating them from a template the moment the sale is recorded, and your monthly close just confirms the numbers.
Don't forget the cost side
None of this touches your actual repair costs, which still get expensed as incurred (parts, labor, third-party repair fees) — separately from the deferred revenue schedule. A well-run warranty program tracks both sides: revenue recognized ratably over the contract, and costs recognized as claims come in. Comparing the two over time tells you whether your warranty pricing is actually profitable — a number a surprising fraction of retailers who sell warranties have never actually calculated, because their books blur the timing of both sides together.
Common Mistakes Small Retailers Make
Booking it all as revenue on day one. This is the big one, and it's the natural default if your accounting is driven entirely by your point-of-sale system's cash reconciliation rather than a proper chart of accounts with a liability line for unearned revenue.
Treating every warranty as assurance-type by default. If you're selling an add-on for a separate, visible price at checkout, it's almost certainly service-type — don't assume it's "just part of the product warranty" because that's simpler to book.
Recognizing revenue on a schedule that doesn't match delivery. Straight-line (equal amounts each month) is the norm and is appropriate for most warranties, since the likelihood of a claim doesn't usually spike at a particular point in the coverage window. But if your product category genuinely has a predictable claims pattern — failures clustering late in a contract's life, say — a systematic method that reflects that pattern may be more accurate than a flat straight line. Get accounting advice before deviating from straight-line; it's the safer default.
Losing track of partially-earned balances when a customer cancels early or gets a refund. If a customer returns the product (and the warranty with it) in month 10 of a 36-month contract, you need to reverse the remaining unearned liability, not just stop recognizing revenue going forward — and if you'd been sloppy about tracking the balance, this reconciliation becomes a scramble.
Why This Matters Even If You're Small
You might be thinking: ASC 606 sounds like something for public companies with SEC filings, not a five-person appliance store. Two reasons it still matters to you:
First, if you ever seek a bank loan, apply for a line of credit, or bring on an investor, whoever's reviewing your financials will expect them to follow generally accepted accounting principles (GAAP) — and "we recognize all warranty revenue immediately" is a red flag that undermines confidence in the rest of your numbers.
Second, and more immediately useful: even if nobody outside your business ever looks at your books, getting this right means your monthly P&L actually reflects how the business is doing. A retailer that just had a huge warranty-selling month looks artificially profitable if all that revenue lands at once — right up until the following slow month makes it look like the business is struggling, when nothing about the underlying operation actually changed.
Keep Your Finances Organized from Day One
Deferred revenue schedules, liability accounts, and month-by-month recognition entries are exactly the kind of recurring, rule-based bookkeeping that benefits from records you can inspect, template, and audit — not a black-box ledger you have to trust blindly. Beancount.io offers plain-text accounting that gives you complete transparency and control over your financial data, with the flexibility to script recurring entries like warranty revenue recognition instead of tracking them by hand in a spreadsheet. Get started for free and see why developers and finance-minded business owners are switching to plain-text accounting.