Onerous Contracts under Ind AS 37: Identifying the Unavoidable Loss

A contract becomes onerous when the unavoidable costs of meeting the obligations under the contract exceed the economic benefits expected to be received. Ind AS 37 requires a present obligation under an onerous contract to be recognised and measured as a provision, after considering impairment of assets dedicated to the contract where applicable. 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. Loss-making economics and accounting onerousness are related but not always identical. A robust approach connects commercial substance, the Ind AS 37 decision criteria, measurement evidence and presentation consequences in one coherent file.

Identify the relevant contract boundary

The technical anchor. The assessment should reflect enforceable rights and obligations of the contract rather than a broad business unit's profitability. In application, finance should isolate the contract or group of rights that legally and economically create the unavoidable burden. A frequent failure mode is declaring an entire division onerous because expected margins have fallen. The working paper should identify the relevant facts, source data, judgement and conclusion so that an independent reviewer can reproduce the decision.

Measure unavoidable costs correctly

The accounting logic. Unavoidable costs reflect the lower of the cost of fulfilling the contract and any compensation or penalties arising from failure to fulfil it. Operationally, the fulfilment cost includes costs that relate directly to the contract under the current requirements. The main judgement risk is using only incremental cash costs when other directly related costs are required in the fulfilment-cost assessment. 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.

Compare with expected economic benefits

The decision point. Benefits should reflect consideration and other economic benefits expected from the contract, using supportable estimates. For implementation, revenue forecasts should be consistent with the contractual terms and realistic volume assumptions. Where errors often arise is using hoped-for future renegotiations that are not enforceable to avoid an onerous conclusion. A concise review note should state the trigger, the rule applied, the evidence considered and the financial-statement consequence.

Test related assets for impairment first

The core requirement. Before a separate onerous-contract provision is established, assets used in fulfilling the contract are tested for impairment under the applicable standards. In a controlled close process, finance should link contract-loss reviews with inventory, PPE and other asset-impairment processes. A common weakness is recognising both a full onerous provision and an unreduced impaired asset for the same economic loss. Evidence should be retained at the same level of detail as the accounting conclusion, with assumptions version-controlled and exceptions explicitly approved.

Update as contract economics change

The principle. The provision should be reassessed for actual performance, cost inflation, price changes, modifications and settlements. For a review-ready file, contract-management data should feed the accounting estimate rather than relying on the original budget. The risk to avoid is leaving the provision unchanged after the contract is renegotiated or partially fulfilled. The accounting result should reconcile to the underlying contract, valuation or subledger rather than rely on a standalone spreadsheet conclusion.

Practical illustration

Assume a fixed-price service contract will generate ₹100 of remaining revenue. The entity expects directly related fulfilment costs of ₹120, while cancelling the contract would require a ₹35 penalty. The unavoidable cost is analysed by comparing the cost of fulfilling with the cost of exiting, and any related asset impairment is considered before the provision is finalised. 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 contract identification; direct-cost methodology; benefit forecast; asset-impairment linkage; and provision refresh. 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

An onerous-contract provision measures the unavoidable burden of an existing contract, not a general reserve for a difficult market. 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.