Warranty accounting under Ind AS is not a single-rule exercise. The accounting depends first on what the customer has actually been promised. Some warranties merely assure the customer that the product complies with agreed specifications when sold. Others give the customer an additional service for a period after the sale. That distinction changes both revenue recognition and the liability recorded at the reporting date.
The current ICAI Compendium of Indian Accounting Standards includes Ind AS 115 in Volume I and Ind AS 37 in Volume II. ICAI also provides dedicated educational material for Ind AS 115, Revenue from Contracts with Customers and Ind AS 37, Provisions, Contingent Liabilities and Contingent Assets.
The core question: assurance or additional service?
Ind AS 115 treats warranties differently depending on whether the warranty gives the customer a service in addition to assurance that the product complies with agreed specifications. The practical starting point is therefore not the label on the invoice. It is the substance of the promise.
- Assurance-type warranty: the warranty mainly protects the customer against defects or failure to comply with specifications that existed when the product was supplied. This is generally accounted for under Ind AS 37 as a provision for expected warranty obligations rather than as a separate revenue performance obligation.
- Service-type warranty: the warranty provides an additional service beyond basic assurance. That service is treated as a separate performance obligation under Ind AS 115, so part of the transaction price is allocated to it and recognised as revenue when the service is provided.
First test: can the customer buy the warranty separately?
A separately purchasable warranty is a strong and straightforward indicator of a distinct service. If the customer can choose whether to buy the warranty, the promise is not merely embedded quality assurance. The warranty is accounted for as a separate performance obligation.
In practice, this means the finance team should identify the stand-alone selling prices of the product and the warranty, allocate the transaction price between the performance obligations under the Ind AS 115 allocation model, and recognise the warranty-related amount as the promised service is delivered.
If the warranty is not sold separately, apply a substance test
A warranty that cannot be purchased separately is not automatically an assurance-only warranty. Ind AS 115 requires the entity to consider whether the warranty, or a part of it, still provides an additional service. Factors commonly relevant to that assessment include the legal requirement to provide the warranty, the length of the coverage period and the nature of the tasks promised.
A warranty required by law often supports an assurance conclusion because it may exist primarily to protect customers from defective products. A longer-than-normal coverage period may point toward additional service. The nature of promised work also matters: the more extensive the services beyond correcting defects that existed at sale, the stronger the case that the customer is receiving a separate service.
What happens when one warranty contains both components?
A single warranty arrangement can contain both assurance and service elements. If those components can be reasonably separated, the assurance portion is accounted for under Ind AS 37 and the service portion is accounted for as a performance obligation under Ind AS 115. If the entity cannot reasonably account for the components separately, Ind AS 115 requires the combined warranty to be accounted for as a single performance obligation.
This is why a warranty memo should describe exactly what the customer receives rather than relying only on marketing names such as standard, extended, premium or comprehensive warranty.
Accounting for an assurance-type warranty under Ind AS 37
For the assurance component, the seller evaluates the obligation under Ind AS 37. A provision is recognised when there is a present obligation from a past event, an outflow of resources is probable and a reliable estimate can be made. Product sales made with an assurance warranty can create that obligation because the seller has already made the covered sales and remains responsible for qualifying defects.
The provision should be based on the best estimate of the expenditure required to settle the obligation. For a large population of similar warranty claims, historical defect rates, repair patterns, parts and labour costs, product changes and other relevant evidence can support the estimate. The estimate should be reassessed at each reporting date rather than carried forward mechanically.
Accounting for a service-type warranty under Ind AS 115
For the service component, the seller does not record all of the allocated warranty consideration as revenue on the product delivery date. Instead, the amount allocated to the warranty performance obligation is recognised as the related service is provided. The pattern of recognition should reflect how the promised warranty service is transferred to the customer.
This creates an important distinction in the balance sheet. Assurance-related expected repair costs create a provision under Ind AS 37. Consideration allocated to an unperformed service warranty represents an Ind AS 115 contract liability until the related service is delivered.
Worked illustration
Assume a company sells equipment together with an optional two-year extended warranty for a combined price of ₹1,00,000. Assume the observable stand-alone selling prices are ₹90,000 for the equipment and ₹10,000 for the extended warranty. Because the customer can purchase the extended warranty separately, the warranty is a separate performance obligation.
On these simplified facts, ₹90,000 of the transaction price is allocated to the equipment and ₹10,000 to the warranty. Subject to the other Ind AS 115 requirements, the equipment amount is recognised when control of the equipment transfers. The ₹10,000 allocated to the warranty is recognised over the period in which the warranty service is provided, using the pattern that best depicts the transfer of that service.
Now change the facts. Suppose the seller provides only a non-optional standard warranty that promises to repair manufacturing defects and provides no additional service. That warranty is generally an assurance-type obligation. The product revenue is not split merely because warranty costs are expected; instead, the seller recognises an Ind AS 37 provision for the expected cost of satisfying qualifying warranty claims.
Month-end and year-end review checklist
- List every warranty programme by product, territory and customer contract.
- Identify whether customers can purchase the warranty separately.
- For non-separately sold warranties, document whether any part provides service beyond basic product assurance.
- Separate assurance and service components where they can be reasonably distinguished.
- For service warranties, support stand-alone selling prices and the transaction-price allocation.
- Reconcile the opening contract liability, new warranty sales, warranty revenue recognised and closing contract liability.
- For assurance warranties, update claim frequency, repair cost and other assumptions used in the Ind AS 37 provision.
- Reconcile actual warranty expenditure against the provision and investigate significant differences from estimates.
- Check presentation and disclosures under the reporting framework actually applied by the entity.
Common mistakes
- Treating every warranty as a provision without checking whether the customer is receiving a separate service.
- Deferring revenue for a basic assurance warranty merely because repair costs may arise later.
- Recognising the full price of a separately sold extended warranty immediately when the product is delivered.
- Using a fixed percentage provision year after year without updating evidence about claims and repair costs.
- Calling an extended warranty a service automatically without analysing its contractual substance.
- Failing to reconcile warranty contract liabilities and warranty provisions separately even though they arise from different accounting models.
Practical takeaway
Warranty accounting becomes much easier when the contract is split into promises before journal entries are considered. Ask whether the warranty merely assures product quality or provides an additional service. Account for assurance obligations under Ind AS 37, account for additional service as a performance obligation under Ind AS 115, and separate the two when a single warranty contains both components. A short written classification memo supported by contract terms, pricing evidence and claims data can prevent both premature revenue recognition and unsupported warranty provisions.
