Warranties come in two flavors, and the distinction has a direct impact on revenue recognition. Get this wrong and you either under-allocate revenue to a performance obligation you've committed to, or create unnecessary complexity by treating a simple assurance as a separate deliverable.
Assurance-Type Warranties
An assurance-type warranty provides the customer with assurance that the product will function as promised — it meets agreed-upon specifications. It does not provide any service or benefit beyond confirming that what was sold works as described.
Under both ASC 606 (606-10-55-30 through 55-35) and IFRS 15 (paragraphs 26–29 on performance obligations, and IFRS 15.B28–B33 specifically on warranties), assurance-type warranties are not separate performance obligations. You accrue the expected cost under ASC 450 (loss contingencies) or IAS 37 (provisions) — no revenue allocation needed.
Service-Type Warranties
A service-type warranty provides a service to the customer beyond confirming the product works. It might include proactive monitoring, priority support response times, guaranteed uptime with credits, or extended coverage periods that go beyond what the market expects for the product type.
Service-type warranties are separate performance obligations. You must allocate a portion of the transaction price to them and recognize that revenue over the warranty period.
How to Classify: Three Indicators
Ask these questions:
- Customer option to purchase separately? If the warranty is sold or could be sold separately, that's a strong indicator it's service-type.
- Duration significantly longer than standard? An unusually long warranty period suggests it provides a service, not just assurance.
- Coverage beyond defect repair? If the warranty covers enhancements, add-ons, proactive intervention, or service levels that go beyond "make it work as specified" — it's likely service-type.
Working Example: SaaS Support Tiers
A SaaS company offers two support options at contract signing:
Standard Warranty (included in all contracts): "We will fix bugs that prevent the software from functioning as documented within 5 business days." This covers defects only — it assures the product will work as specified. It cannot be purchased separately; every customer gets it. Duration mirrors the contract term, which is standard in the market.
→ Assurance-type. Not a separate performance obligation. Accrue the expected cost of providing warranty service under IAS 37 / ASC 450. No revenue split.
Premium Support Package (optional add-on, $500/month): "You receive a dedicated customer success manager, 99.9% uptime SLA with 10x credits for downtime, 4-hour response SLAs, and monthly business review calls."
→ Service-type. Separate performance obligation. The customer is buying ongoing service beyond defect assurance — proactive monitoring, dedicated resourcing, response-time commitments. Allocate $500/month of the total transaction price to this PO and recognize it over the service period.
Edge case — standard 99.9% uptime guarantee (SLA only, no other services): This requires judgment. If the market treats uptime SLAs as standard assurance (i.e., "the product should work"), and there are no separate services attached, it may qualify as assurance-type. If it includes credits or financial remedies for breach, the credit amount may be variable consideration rather than a warranty issue.