
Once recognition criteria are met, Ind AS 37 requires the provision to represent the best estimate of the expenditure required to settle the present obligation at the reporting date. That estimate may involve one most likely outcome, probability-weighted outcomes or other techniques depending on the population and uncertainty. A professional application therefore needs more than the right journal entry: it needs a controlled decision path from contractual facts and management assumptions to measurement and disclosure. Provision measurement should reflect uncertainty without becoming an arbitrary conservatism buffer. A robust approach connects commercial substance, the Ind AS 37 decision criteria, measurement evidence and presentation consequences in one coherent file.
Choose a method suited to the obligation
The decision point. Large populations of similar items often lend themselves to expected-value techniques, while a single obligation may be informed by the most likely outcome together with other possible results. For implementation, the methodology should reflect the shape of the outcome distribution and the information available. Where errors often arise is using one calculation technique for warranties, litigation and decommissioning regardless of their different risk structures. Where the conclusion is sensitive to a contractual clause or estimate, the file should show the alternative outcome and why the selected treatment is more appropriate.
Use evidence available at the reporting date
The core requirement. Estimates should incorporate experience, expert input and events after the reporting period that provide evidence about conditions existing at period end. In a controlled close process, new information should be assessed for whether it confirms the year-end estimate or reflects a later event. A common weakness is using subsequent settlement information indiscriminately without considering what condition it relates to. A concise review note should state the trigger, the rule applied, the evidence considered and the financial-statement consequence.
Reflect risk without double counting
The principle. Uncertainty can affect the expected cash flows or the discount rate, but the same risk should not be loaded into both in a way that exaggerates the provision. For a review-ready file, valuation papers should state explicitly where risk adjustments are incorporated. The risk to avoid is adding a broad contingency percentage on top of already probability-weighted stressed outcomes. Evidence should be retained at the same level of detail as the accounting conclusion, with assumptions version-controlled and exceptions explicitly approved.
Exclude gains on expected disposal of assets
The technical anchor. Anticipated gains from disposal of assets are not taken into account when measuring a provision, even if the disposal is connected with the event giving rise to the obligation. In application, finance should separately account for asset disposals under the relevant standard. A frequent failure mode is netting an expected asset sale gain against a remediation obligation to reduce the provision. The accounting result should reconcile to the underlying contract, valuation or subledger rather than rely on a standalone spreadsheet conclusion.
Review estimates at every reporting date
The accounting logic. Provisions are revised to reflect the current best estimate and reversed when an outflow is no longer probable. Operationally, roll-forwards should separately identify utilisation, reversals, additions, changes in estimate and unwinding of discount. The main judgement risk is carrying forward last year's provision without reassessing probability, amount and timing. The working paper should identify the relevant facts, source data, judgement and conclusion so that an independent reviewer can reproduce the decision.
Practical illustration
Assume a company faces thousands of product warranty claims with outcomes ranging from minor repair to full replacement. Using only the single most common repair cost can understate the expected obligation. A probability-weighted estimate across the claim population may better capture the expected expenditure, provided the probabilities and cost assumptions are evidence-based. The illustration is deliberately simplified: its purpose is to show how the accounting conclusion follows the underlying facts rather than to prescribe a single mechanical answer for every entity. Before posting an entry, the preparer should reconcile contractual terms, management's commercial intent, relevant estimates and system data to the specific accounting requirement. Where the outcome is sensitive, the file should show the key judgement and explain why the selected assumption is reasonable at the reporting date.
Documentation and control points
Professional application depends as much on process quality as technical knowledge. For this topic, a minimum control set should cover measurement methodology; probability support; risk-adjustment location; subsequent-event review; and provision roll-forward. Ownership should be clear between the business, finance and any legal, tax, valuation, credit-risk or other specialists whose evidence is required. Source data should be dated and version-controlled; manual adjustments should show preparer, reviewer, rationale and approval. The final accounting memorandum should connect the conclusion to the general ledger or relevant subledger, presentation and disclosures. If facts or estimates change, the entity should reassess the conclusion when required and preserve an audit trail explaining the change.
Closing perspective
A best estimate is neither the optimistic case nor the most conservative case; it is the reporting-date amount that faithfully reflects the obligation and its uncertainty. The most useful way to apply Ind AS 37 is to treat the requirement as a decision framework rather than a compliance slogan. When the facts, accounting criteria, measurement evidence, controls and disclosure implications are considered together, the result is more consistent across reporting periods and easier to explain to management, auditors and users of the financial statements.
Continue learning on JUMOQ
Turn this guidance into practical capability
Explore focused courses, worked examples and activities related to this topic.
Explore related courses →References
- Ind AS 37, Provisions, Contingent Liabilities and Contingent Assets — ICAI Compendium of Indian Accounting Standards 2025-2026
