Extended Warranties as Separate Performance Obligations in SAP

Almost every product company offers warranties. Many also sell extended coverage, either as a separately priced option or bundled into the sale. Under ASC 606, the accounting differs fundamentally depending on what kind of warranty it is. One type is a cost accrual; the other is deferred revenue.

Getting the classification right is an accounting judgment. Getting the SAP design right makes that judgment executable at scale.

Assurance-Type vs. Service-Type

ASC 606-10-55-30 distinguishes two kinds of warranties:

• Assurance-type warranty: gives the customer assurance that the product will function as the parties intended and complies with agreed specifications. It is not a performance obligation. Expected costs are accrued under ASC 460-10.

• Service-type warranty: provides a service in addition to that assurance. It is a performance obligation, and part of the transaction price is allocated to it.

The Decision Path

1. Can the customer purchase the warranty separately? If it is priced or negotiated separately, it is a distinct service and a performance obligation (ASC 606-10-55-31).

2. If not, does it provide a service beyond assurance? ASC 606-10-55-33 lists factors:

• Required by law: a legally required warranty indicates assurance, since such laws protect customers from defective products.

• Length of coverage: the longer the coverage, the more likely a service is provided. Duration is an indicator, not a bright line.

• Nature of tasks: tasks needed to provide assurance, such as return shipping for defective products, do not create a performance obligation.

3. Both elements present? If a warranty provides a service in addition to assurance, the service portion is a performance obligation (ASC 606-10-55-34). If the two cannot reasonably be accounted for separately, they are accounted for together as a single performance obligation.

Product liability for harm caused by products and indemnification against patent or trademark claims do not create performance obligations; they are loss contingencies under ASC 450-20 (ASC 606-10-55-35).

Under IFRS 15, the corresponding guidance is in the application guidance starting at paragraph B28, with IAS 37 for assurance-type warranty provisions.

What Changes When It Is a Performance Obligation

Once an extended warranty is a separate performance obligation:

• The transaction price is allocated based on relative standalone selling prices. A separately quoted warranty price is not automatically the allocated amount; discounts across the contract are allocated proportionately unless the ASC 606-10-32-37 criteria are met.

• Revenue is typically recognized over the coverage period. The measure of progress should reflect how the service is provided; a ratable pattern is common for stand-ready coverage, but it is a policy decision that needs support.

• The deferred amount is a contract liability and part of remaining performance obligation disclosures.

• Costs of servicing the service-type obligation follow a different path than the assurance-type portion, which stays in the ASC 460 accrual. Both need to be separable in reporting.

Modeling Extended Warranties in SAP

There are several design patterns. The right one depends on how the warranty is sold and serviced.

• Warranty as a separate sales order item. The extended warranty is sold as its own item, for example a service material, alongside the product. In SAP RAR, it becomes its own performance obligation with time-based fulfillment over the coverage period, and RAR performs the SSP-based allocation across product and warranty.

• Warranty as a service contract. If the coverage is administered as a service contract in SAP S/4HANA Service, the contract item can carry the coverage period and billing plan. Revenue can be recognized via SAP RAR, or via event-based revenue recognition, which recognizes service contract revenue over time following the billing plan. If the warranty was sold together with a product on a separate document, consider whether the contracts must be combined for ASC 606, which favors RAR.

• Implicit warranty without an order item. If a service-type element is embedded in the product price and not quoted separately, RAR can create a linked performance obligation attached to the leading POB of the product item, so that a portion of the price is allocated to the warranty.

Whatever the pattern, the coverage start date matters. Coverage usually begins at delivery or installation, not at order creation. Make sure the event that starts the warranty period is captured and passed to RAR.

Pitfalls

• Classifying by name. Calling a product "extended warranty" does not make it service-type; calling it "standard warranty" does not make it assurance-type. Apply the factors.

• Using the warranty list price as revenue. The allocated amount depends on SSPs of all items in the contract.

• Mixing claims costs. Keep claims attributable to the assurance accrual separate from costs of servicing the service-type obligation.

• Forgetting cancellations and refunds. Pro-rata refunds on cancelled coverage affect the transaction price and need a defined process in the order and in RAR.

• No documented policy. SOX auditors will expect a written warranty classification policy that maps to the SAP item categories and POB rules.

Related Articles

• Service Contracts and Service Orders: Revenue Recognition with RAR or Event-Based Revenue Recognition

• Standalone Selling Price (SSP): Methods and Common Mistakes

• The 5-Step Model of IFRS 15 / ASC 606 Explained for SAP Teams

The Bottom Line

Assurance-type warranties are a cost accrual under ASC 460; service-type warranties, including most separately sold extended warranties, are performance obligations under ASC 606 that defer revenue over the coverage period. In SAP, model the warranty as a separate item, a service contract, or a linked POB so that SAP RAR can allocate and recognize it correctly. Revident combines this with human-governed automation: rules classify and check, accountants decide the edge cases.

Reviewing your warranty accounting in SAP? Talk to our experts.