Corporate Assets in Ind AS 36 Impairment Testing

Head-office buildings, shared technology platforms, research centres and other corporate assets often support multiple cash-generating units but do not generate independent cash inflows. Ind AS 36 requires these assets to be incorporated into impairment testing through reasonable and consistent allocation where possible or through higher-level testing when allocation is not possible. 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. Omitting corporate assets can overstate impairment headroom. A robust approach connects commercial substance, the Ind AS 36 decision criteria, measurement evidence and presentation consequences in one coherent file.

Identify corporate assets comprehensively

The accounting logic. Corporate assets contribute to future cash flows of more than one CGU and are not fully attributable to a single unit. Operationally, the fixed-asset register should flag shared assets and their beneficiary populations. The main judgement risk is assuming head-office assets are outside impairment testing because they do not earn revenue directly. Evidence should be retained at the same level of detail as the accounting conclusion, with assumptions version-controlled and exceptions explicitly approved.

Allocate when a reasonable basis exists

The decision point. The carrying amount should be allocated to CGUs on a reasonable and consistent basis when such allocation can be made. For implementation, drivers can reflect headcount, usage, capacity, floor area or another factor linked to economic benefit. Where errors often arise is allocating solely to profitable units or changing drivers year to year to influence headroom. The accounting result should reconcile to the underlying contract, valuation or subledger rather than rely on a standalone spreadsheet conclusion.

Use a bottom-up and top-down approach where needed

The core requirement. When a corporate asset cannot be reasonably allocated to individual CGUs, the entity tests affected units without it and then identifies the smallest group of CGUs to which a reasonable allocation can be made for a higher-level test. In a controlled close process, the testing hierarchy should be documented and avoid gaps. A common weakness is stopping after lower-level CGUs show headroom even though shared corporate assets remain untested. The working paper should identify the relevant facts, source data, judgement and conclusion so that an independent reviewer can reproduce the decision.

Coordinate with goodwill testing

The principle. Corporate assets and goodwill may sit at different allocation levels, requiring a coherent hierarchy so the same carrying amounts and cash flows are not duplicated or omitted. For a review-ready file, impairment models should map each shared asset and goodwill balance to its testing level. The risk to avoid is double counting head-office costs in cash flows while also omitting the corresponding asset. 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.

Revisit allocations after reorganisations

The technical anchor. Changes in business structure, shared-service usage or disposal of units can change which CGUs benefit from corporate assets. In application, allocation bases should be updated when economics change and reasons documented. A frequent failure mode is keeping historical allocations after the underlying business has been reorganised materially. A concise review note should state the trigger, the rule applied, the evidence considered and the financial-statement consequence.

Practical illustration

Assume a central data centre supports four operating CGUs and cannot generate independent cash inflows. If usage data provide a reasonable allocation basis, its carrying amount should be allocated consistently to those CGUs for testing. If no reasonable allocation exists at that level, the entity still needs a higher-level test that captures the shared asset rather than excluding it. 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 corporate-asset register; allocation-driver governance; testing hierarchy; goodwill coordination; and reorganisation review. 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

Corporate assets test whether impairment models include the full resource base supporting cash flows; convenience is not a basis for leaving shared assets out. 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.