Provisions under Ind AS 37: Recognition before Measurement

Provision accounting begins with the existence of an obligation, not with management's desire to create a prudent reserve. A provision is recognised only when there is a present obligation from a past event, an outflow of resources embodying economic benefits is probable and a reliable estimate can be made. For finance teams, the practical challenge is to translate that principle into a repeatable conclusion supported by evidence, rather than treating the standard as a year-end checklist. Skipping the recognition test can turn provisions into discretionary earnings-management accounts. A robust approach connects commercial substance, the Ind AS 37 decision criteria, measurement evidence and presentation consequences in one coherent file.

Identify the obligating event

The technical anchor. The past event must leave the entity with no realistic alternative to settling the obligation, whether the obligation is legal or constructive. In application, finance should identify the event that created the obligation and distinguish it from future operating intentions. A frequent failure mode is accruing future expenditure merely because management expects or budgets to incur it. The working paper should identify the relevant facts, source data, judgement and conclusion so that an independent reviewer can reproduce the decision.

Establish a present obligation

The accounting logic. The obligation must exist at the reporting date and may arise from contract, legislation or valid expectations created by the entity's actions. Operationally, legal, operational and commercial evidence should be evaluated together when the existence of the obligation is uncertain. The main judgement risk is treating every business risk as a liability even when no counterparty or valid expectation creates an obligation. 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.

Assess probability of outflow

The decision point. Recognition requires that an outflow of resources be probable, with related cases assessed as a class when appropriate. For implementation, management should document the probability assessment using current facts, legal advice and experience with comparable obligations. Where errors often arise is using a fixed probability percentage divorced from the specific facts. A concise review note should state the trigger, the rule applied, the evidence considered and the financial-statement consequence.

Confirm reliable estimation

The core requirement. The inability to make a reliable estimate is expected to be rare because ranges, expected values and professional judgement can often provide a best estimate. In a controlled close process, finance should identify the range of outcomes and why the selected estimate represents the expenditure required to settle or transfer the obligation. A common weakness is avoiding recognition solely because the exact amount is uncertain. Evidence should be retained at the same level of detail as the accounting conclusion, with assumptions version-controlled and exceptions explicitly approved.

Separate provisions from accruals and contingencies

The principle. Provisions involve uncertainty of timing or amount, while ordinary accruals may involve less uncertainty and contingent liabilities are generally not recognised unless the relevant recognition conditions are met. For a review-ready file, the chart of accounts and close process should distinguish these populations. The risk to avoid is using the provision account as a catch-all for routine supplier accruals, possible claims and management buffers. The accounting result should reconcile to the underlying contract, valuation or subledger rather than rely on a standalone spreadsheet conclusion.

Practical illustration

Assume a manufacturer has breached an environmental regulation before year-end and remediation is required under law. The accounting question is not whether the company intends to remediate next year; the breach has already created a present legal obligation. If outflow is probable and the cost can be reliably estimated, provision recognition follows the obligation rather than the timing of cash payment. 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 obligating-event evidence; legal or constructive obligation assessment; probability approval; estimate support; and provision-to-ledger reconciliation. 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

Ind AS 37 is disciplined prudence: recognise obligations that exist, but do not use uncertainty as a reason to reserve for future business risks. 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.