Extended Warranty Accounting Treatment: ASC 606 and IFRS 15

Under U.S. GAAP, the extended warranty accounting treatment depends on whether the coverage is an assurance that the product works as promised or a separate service the customer chose to buy. A service-type extended warranty is a distinct performance obligation under ASC 606: you allocate part of the transaction price to it, park that amount in a contract liability, and release it into revenue over the coverage period as you stand ready to perform. An assurance-type warranty stays on the old path, with an estimated liability accrued at the time of sale and the expense charged against that period’s revenue.

Assurance-Type or Service-Type

The classification question comes first because it decides every entry that follows. An assurance-type warranty is a promise that the product meets its agreed-upon specifications. It rides along with the sale, is often required by law or standard industry practice, and gives the customer nothing beyond confidence that the product isn’t defective. Because the customer cannot buy it separately and it delivers no distinct service, it is not a separate performance obligation. You estimate probable repair and replacement costs at the sale, accrue a warranty liability, and expense the amount against the period’s revenue.

A service-type warranty is different. When the customer can purchase the coverage separately, or when it goes beyond remedying defects in the original product, it is a distinct service. The seller treats it as its own performance obligation, allocates a portion of the transaction price to it, and defers that portion until earned.¹

ASC 606-10-55-33 gives three factors to weigh: whether the law requires the warranty (which points to assurance-type), how long the coverage runs (longer terms lean toward service-type), and the nature of the tasks promised (tasks that only ensure the product meets specifications don’t create a separate obligation).

Products often carry both. A manufacturer may include a one-year assurance warranty in the sale price and separately sell a three-year extended plan. In that case, account for each piece on its own path: accrue an estimated liability for the assurance portion, defer revenue for the service portion.¹

Recognizing Revenue Over the Coverage Period

When an extended warranty is sold on its own, the transaction price is what the customer pays for it. When it’s bundled with the product in a single transaction, allocate the total price across each performance obligation based on standalone selling prices. The product’s share follows product revenue rules; the warranty’s share goes to a contract liability (sometimes labeled deferred revenue) on the balance sheet.¹ Cash has arrived, but nothing hits the income statement yet, because you haven’t stood ready to service the coverage for any meaningful period.

Recognition happens over the warranty term. The default is straight-line: a $1,200 contract covering 24 months produces $50 of revenue each month. That method fits whenever you expect the effort and cost of performing to be roughly uniform across the term.

If historical claims data shows a different pattern, use a method that mirrors how the customer actually consumes the service. Coverage on aging equipment tends to generate more claims in later years as components wear, so recognizing less in the early months and more in the later months better reflects service delivery. Whatever method you pick has to depict the actual pattern, and you need the data to support it. When no reliable pattern exists, straight-line is the fallback.

Costs of Getting and Performing the Contract

Extended warranty costs split into two buckets that follow different rules.

Costs to Obtain the Contract

Sales commissions and other incremental costs of landing the deal get capitalized as an asset under ASC 340-40 when the entity expects to recover them and would not have incurred them without that specific contract.² Amortize that asset over the contract term, alongside the revenue you recognize each period. A $120 commission on a 24-month contract amortizes at $5 per month against the $50 of monthly revenue.

A practical expedient helps with shorter contracts: if the amortization period would be one year or less, you can expense the acquisition costs immediately. Retailers selling one-year protection plans commonly use this, and it’s fine as long as the election is applied consistently and disclosed.

Capitalized acquisition costs need periodic impairment review. If expected future cash flows from a contract drop below the unamortized balance of the asset, write it down.

Costs to Fulfill the Contract

Repair parts, technician labor, shipping, and other costs of servicing claims are expensed as incurred. They hit the income statement in the period the work happens. When claims arrive unevenly against straight-line revenue, period profitability will move around. That is expected. The matching here means matching costs to the period the service is performed, not smoothing them to align with revenue.

Balance Sheet Presentation

Deferred revenue from extended warranty sales sits on the balance sheet as a contract liability, split between current and non-current. The current portion is the amount expected to be recognized in the next 12 months; anything beyond that is non-current.³

Take the earlier example. A $1,200 warranty sold on January 1 with a 24-month term shows $600 current and $600 non-current on the initial balance sheet. At the end of month 12, the non-current portion reclassifies to current because the remaining $600 will be earned in the next 12 months.

Loss Contracts

Sometimes the math turns against you. If estimated future costs to service a warranty contract exceed the remaining deferred revenue, you have a loss contract. This happens with product lines that develop unexpected defect patterns, or when input costs spike after contracts are already sold.

Once a loss contract is identified, the entire anticipated loss must be recognized immediately, even though the warranty still has months or years to run.⁴ Book a liability for the full expected loss and charge the expense to the current period. Losses are front-loaded while profits are spread over time.

Companies with large warranty portfolios should compare updated cost projections against remaining unearned balances on a regular cadence. Saving that analysis for year-end is a common source of surprises.

Book-Tax Differences Under Section 451

The gap between GAAP recognition and tax recognition for extended warranties is one of the more predictable book-tax differences. Under IRC Section 451(c), an accrual-method taxpayer that receives an advance payment (which warranty premiums typically are) can elect to defer part of it, but only briefly.⁵

The mechanics: in the year of receipt, include whatever portion your financial statements recognize that year under ASC 606. Include the remaining portion in gross income the very next tax year, no matter how long the warranty runs. There is no option to spread it further.⁵

The impact matters at longer terms. On a two-year warranty, book and tax roughly align. On a three-year or five-year warranty, GAAP might spread $1,200 across 36 or 60 months while tax law pulls all remaining income into Year 2. That mismatch produces a deferred tax asset in the early years that reverses as GAAP catches up.

Section 451(b) also requires that transaction price allocation across performance obligations for tax match the allocation used in your financial statements. You cannot split the price one way for the IRS and another way under ASC 606.⁵

Once made for a category of advance payments, the Section 451(c) election applies to all subsequent tax years unless the IRS consents to revocation. It is treated as an accounting method, so changing later requires permission.

Required Disclosures

ASC 606 imposes several disclosures tied to warranty contracts and their liabilities:

A description of the types of warranties offered and the nature of the related obligations (ASC 606-10-50-12).
Opening and closing balances of contract liabilities, plus the revenue recognized during the period that was included in the opening contract liability balance (ASC 606-10-50-8).
Qualitative and quantitative explanations of significant changes in contract liability balances, such as a change in expected timing for satisfying a performance obligation (ASC 606-10-50-10).
The aggregate transaction price allocated to unsatisfied performance obligations and when the entity expects to recognize that revenue, presented in time bands or with qualitative information (ASC 606-10-50-13).

Entities with warranty contracts of one year or less may elect to omit the remaining performance obligation disclosure, but must state that they applied the exemption.⁶

If You’re the Buyer, Not the Seller

Everything above sits on the seller’s books. If your company buys an extended warranty on equipment or other assets, record the cost as a prepaid expense at purchase and amortize it to expense on a straight-line basis over the coverage period. A $2,400 warranty covering 36 months produces roughly $67 of monthly expense. Split the prepaid asset between current and non-current based on how much will be consumed in the next 12 months versus later.

IFRS 15 vs. ASC 606

IFRS 15 and ASC 606 were developed jointly and treat warranties in substantially the same way. Both distinguish assurance-type from service-type coverage, and both require service-type warranties to be accounted for as separate performance obligations with deferred revenue.⁷ The main difference is the fallback: when a warranty is not a separate performance obligation, U.S. GAAP routes entities to ASC 460 on guarantees, while IFRS routes them to IAS 37 on provisions and contingent liabilities. Outcomes are similar in practice, but multinationals should expect the estimation methodology and disclosure language to differ.

1
Deloitte Accounting Research Tool. Deloitte’s Roadmap Revenue Recognition – 5.5 Warranties
2
Deloitte Accounting Research Tool. Deloitte’s Roadmap Revenue Recognition – Chapter 13.2 Costs of Obtaining a Contract
3
Deloitte Accounting Research Tool. Deloitte’s Roadmap Revenue Recognition – 14.6 Classification as Current or Noncurrent
4
PwC Viewpoint. 11.5 Onerous Contracts
5
Office of the Law Revision Counsel. 26 USC 451 – General Rule for Taxable Year of Inclusion
6
PwC Viewpoint. 33.4 Revenue Disclosures – ASC 606
7
IFRS Foundation. Warranties – Transition Resource Group for Revenue Recognition