Legal versus Constructive Obligations under Ind AS 37

Not every obligation is written into a contract or statute. Ind AS 37 also recognises constructive obligations when an entity's established pattern of past practice, published policies or sufficiently specific current statement creates a valid expectation in other parties that it will accept particular responsibilities. In practice, the accounting works best when commercial facts are separated from the technical assessment and every significant judgement can be traced to source evidence. Constructive obligations require careful evidence because informal intentions can easily be confused with enforceable expectations. A robust approach connects commercial substance, the Ind AS 37 decision criteria, measurement evidence and presentation consequences in one coherent file.

Identify legal obligations from external sources

The accounting logic. Legal obligations can arise from contracts, legislation or other operation of law and should be assessed using the terms and jurisdiction applicable at the reporting date. Operationally, finance should retain executed agreements, regulatory notices and legal interpretations that establish the duty to act. The main judgement risk is assuming a commercial expectation is legally enforceable without legal analysis. Evidence should be retained at the same level of detail as the accounting conclusion, with assumptions version-controlled and exceptions explicitly approved.

Test whether conduct creates a constructive obligation

The decision point. Past practice or public communication must be sufficiently specific and consistent to create a valid expectation in affected parties. For implementation, the entity should assess what it has actually communicated, to whom, and whether the recipient can reasonably rely on it. Where errors often arise is treating an internal management plan that has not been communicated as a constructive obligation. The accounting result should reconcile to the underlying contract, valuation or subledger rather than rely on a standalone spreadsheet conclusion.

Focus on valid expectation, not moral preference

The core requirement. A moral or reputational desire to act does not by itself create a present obligation unless the entity's conduct has removed a realistic alternative to performance. In a controlled close process, board intent should be distinguished from externally created expectations. A common weakness is recognising a provision simply because management believes settlement would be fair. The working paper should identify the relevant facts, source data, judgement and conclusion so that an independent reviewer can reproduce the decision.

Assess changes in policies carefully

The principle. A history of routinely honouring a customer remedy beyond contractual warranty can create an expectation even if the current written terms are narrower. For a review-ready file, operational data and customer communications should be considered when assessing whether past conduct has effectively expanded obligations. The risk to avoid is ignoring established practice because it is not written in the contract. 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.

Document the obligating event and affected parties

The technical anchor. Constructive obligations should be anchored to a specific past event and identifiable population rather than a broad statement of corporate values. In application, the accounting memo should explain the action that created the expectation and why the entity lacks a realistic alternative to settlement. A frequent failure mode is using generic sustainability or customer-service language as evidence of a specific obligation. A concise review note should state the trigger, the rule applied, the evidence considered and the financial-statement consequence.

Practical illustration

Assume a retailer has publicly and consistently refunded customers for a particular product defect even outside the legal warranty period and has communicated that policy broadly. If customers reasonably expect the retailer to continue that practice for products already sold, the historical conduct may create a constructive obligation even though the contract itself does not require the refund. 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 legal-source review; public-communication inventory; past-practice evidence; valid-expectation assessment; and obligating-event memo. 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

The distinction between intention and obligation is central to Ind AS 37; a constructive obligation exists because others can validly expect performance, not merely because management plans to act. 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.