Indefinite-Life Intangibles and Assets Not Yet Available for Use under Ind AS 36

Certain intangible assets require annual impairment testing even when there is no evidence of deterioration. Intangible assets with indefinite useful lives and those not yet available for use are tested annually because their recoverability cannot be protected by a finite amortisation pattern or current operating performance. The strongest accounting files make the reasoning visible, so that a reviewer can understand not only the conclusion but also why plausible alternatives were rejected. These assets are easy to lose from the annual testing population when projects, brands or systems move between teams. A robust approach connects commercial substance, the Ind AS 36 decision criteria, measurement evidence and presentation consequences in one coherent file.

Confirm indefinite-life classification separately

The core requirement. An indefinite useful life exists when there is no foreseeable limit to the period over which the asset is expected to generate net cash inflows, not merely because management expects a long life. In a controlled close process, Ind AS 38 useful-life assessments should be revisited and supported by legal, competitive, technological and demand factors. A common weakness is using 'indefinite' as a way to avoid amortisation without robust evidence. The accounting result should reconcile to the underlying contract, valuation or subledger rather than rely on a standalone spreadsheet conclusion.

Test annually irrespective of indicators

The principle. The annual impairment requirement applies even when performance is strong and can be performed at a consistent time each year. For a review-ready file, the impairment calendar should include every qualifying intangible and responsible owner. The risk to avoid is omitting testing because no external indicator was identified. The working paper should identify the relevant facts, source data, judgement and conclusion so that an independent reviewer can reproduce the decision.

Test not-yet-available assets before use

The technical anchor. Development projects and acquired intangibles not yet ready for intended use require annual testing because uncertainty about successful completion and benefits can be high. In application, project governance should reconcile capitalised balances with impairment testing status. A frequent failure mode is waiting until commissioning before considering recoverability. 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.

Determine the appropriate testing level

The accounting logic. When the intangible does not generate independent cash inflows, it is tested within the relevant CGU or group under the usual Ind AS 36 principles. Operationally, brand, licence or technology benefits should be mapped to the units that generate related cash flows. The main judgement risk is comparing a brand's carrying amount with total enterprise value without a supportable allocation. A concise review note should state the trigger, the rule applied, the evidence considered and the financial-statement consequence.

Reassess status when circumstances change

The decision point. An asset can move from not available for use to available, or an indefinite life can become finite, changing amortisation and testing requirements. For implementation, finance should link project commissioning and useful-life reassessment to the impairment register. Where errors often arise is continuing annual-only treatment after facts require finite-life amortisation and indicator-based testing. Evidence should be retained at the same level of detail as the accounting conclusion, with assumptions version-controlled and exceptions explicitly approved.

Practical illustration

Assume a company capitalises development expenditure for a platform that will not be ready for commercial use for another year. Even if the project remains on budget, the asset is not yet available for use and is subject to annual impairment testing. The test should consider the CGU or cash-flow benefits to which the platform will contribute, not just cumulative development cost. 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 intangible classification; annual test register; project-status reconciliation; CGU mapping; and useful-life reassessment. 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

Annual testing for these intangibles is a governance safeguard against carrying uncertain future benefits indefinitely without a recurring recoverability challenge. The most useful way to apply Ind AS 36 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.