Warranties under Ind AS 115 and Ind AS 37

Business fact first, accounting label second

This topic sits at the point where business decisions become accounting consequences. That makes disciplined fact finding as important as knowledge of the standard. Warranties under Ind AS 115 and Ind AS 37 matters because the finance team must separate assurance warranties from distinct service warranties using legal requirements, coverage period and nature of promised tasks. The same issue can affect several statement lines and reporting periods. Ind AS 115 seeks to depict the transfer of promised goods or services to customers in an amount reflecting consideration to which the entity expects to be entitled. A useful analysis asks not only what amount should be recorded, but also when the conclusion was reached, what evidence existed at that date and how the result will be explained to users.

Core Ind AS principles

Ind AS 115 should be read as a decision architecture. It governs contracts with customers, excluding leases, insurance contracts, financial instruments and specified non-monetary exchanges, and its measurement logic can be summarised as follows: The five-step model identifies contracts and performance obligations, determines and allocates transaction price, and recognises revenue when or as control transfers, with separate requirements for contract costs and presentation. The article’s focus—to separate assurance warranties from distinct service warranties using legal requirements, coverage period and nature of promised tasks—sits within that architecture. A conclusion is robust only when the same assumptions are used consistently in the general ledger, valuation or calculation model, primary statements, notes and management explanations.

How to build the analysis

A practical sequence keeps the analysis ordered and prevents a late disclosure review from uncovering a recognition error:

1. Frame the question. identify distinct promised goods, services and material rights. Record its effect on recognition, measurement or disclosure for warranties and ind as 37.
2. Build the evidence base. estimate fixed and variable consideration, financing effects and non-cash consideration. Give the conclusion on warranties and ind as 37 a date and an accountable owner.
3. Apply the accounting test. allocate transaction price using observable or estimated stand-alone selling prices. Retain the source supporting warranties and ind as 37.
4. Quantify and reconcile. recognise revenue over time or at a point in time and reconcile contract balances, costs and disclosures. Link it explicitly to warranties and ind as 37.

Illustrative scenario

Imagine that the year-end reviewer receives this fact pattern: A manufacturer offers a standard one-year defect warranty and sells three years of additional coverage. The matter involves a carrying amount, transaction value or exposure of approximately ₹100 crore. Rather than starting with a spreadsheet output, the reviewer asks management to identify enforceable customer contracts and combine or modify them where required and identify distinct promised goods, services and material rights. The answers should make clear how the entity intends to separate assurance warranties from distinct service warranties using legal requirements, coverage period and nature of promised tasks and which evidence supports that intention or conclusion.

For warranties and ind as 37, the likely source of misstatement is confusing a contract asset with an unconditional receivable. The strongest response is a calculation supported by executed contracts, approved order forms and side letters, together with a ledger-to-note reconciliation. Where judgement remains significant, the note should describe the entity-specific uncertainty and not simply reproduce the wording of Ind AS 115.

Questions a reviewer should ask

A technically sound conclusion should demonstrate that these shortcuts were avoided:

• Confusing a contract asset with an unconditional receivable. The risk increases when different teams own the contract, model, journal and note disclosure. For warranties and ind as 37, the working paper should show why the entity’s facts do or do not create this risk.
• Starting revenue analysis from invoice timing. This usually happens when the ledger label is accepted without tracing the underlying terms and timing. For warranties and ind as 37, the working paper should show why the entity’s facts do or do not create this risk.

Evidence and controls

The evidence pack should be proportionate to materiality but complete enough for another reviewer to reproduce the conclusion:

• Executed contracts, approved order forms and side letters, specifically cross-referenced to the conclusion on warranties and ind as 37 and the affected financial-statement line items.
• Performance-obligation and contract-combination memoranda, specifically cross-referenced to the conclusion on warranties and ind as 37 and the affected financial-statement line items.
• Variable-consideration, financing and selling-price models, specifically cross-referenced to the conclusion on warranties and ind as 37 and the affected financial-statement line items.

Connected-standard analysis is also necessary. Relevant interfaces include Ind AS 21, Ind AS 37 and Ind AS 38. The team should document whether these standards change recognition, measurement, tax, impairment, cash-flow classification or disclosure. For warranties and ind as 37, the final tie-out should align management reporting, the primary statements and the notes.

The durable lesson

The standard does not reward complexity for its own sake; it rewards faithful classification, consistent measurement and transparent communication. The practical objective is a conclusion that another competent reviewer can reproduce from the retained evidence. For warranties and ind as 37, consistency across contract review, model, ledger, primary statements and notes is the strongest sign that the accounting has been applied in substance. Building that discipline is central to mastering Ind AS 115, not merely passing a technical checklist.