Cash-Generating Units under Ind AS 36: Finding the Right Testing Level

A cash-generating unit is the smallest identifiable group of assets that generates cash inflows largely independent of other assets or groups. The CGU boundary determines which cash flows, assets and goodwill are compared in impairment testing and therefore has a major effect on whether losses are identified promptly. 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. Overly broad CGUs can shield weak assets with stronger businesses. A robust approach connects commercial substance, the Ind AS 36 decision criteria, measurement evidence and presentation consequences in one coherent file.

Start from independent cash inflows

The accounting logic. The key question is where cash inflows become largely independent, not where management prefers to report profit. Operationally, customer markets, pricing decisions, production interdependencies and internal transfer arrangements can all inform the boundary. The main judgement risk is using legal entities or operating segments automatically as CGUs. Evidence should be retained at the same level of detail as the accounting conclusion, with assumptions version-controlled and exceptions explicitly approved.

Consider how management monitors operations

The decision point. Internal management information and decisions about continuing or disposing of operations provide relevant evidence, but they do not override the independence criterion. For implementation, finance should reconcile CGUs with budgets, plant or store reporting and operational accountability. Where errors often arise is creating CGUs solely to match financial reporting note structures. The accounting result should reconcile to the underlying contract, valuation or subledger rather than rely on a standalone spreadsheet conclusion.

Address internal transfer pricing

The core requirement. When output is transferred internally, a unit can still be a CGU if an active market exists for the output, with cash-flow forecasts adjusted to market-based assumptions as required. In a controlled close process, the entity should document external market evidence and consistent pricing. A common weakness is concluding there is no CGU because all output is sold to another group division. The working paper should identify the relevant facts, source data, judgement and conclusion so that an independent reviewer can reproduce the decision.

Keep CGUs consistent unless change is justified

The principle. CGU identification should be consistent period to period unless a change is justified by altered operations or cash-flow generation. For a review-ready file, reorganisations should be documented with old-to-new mappings and implications for goodwill allocation. The risk to avoid is redrawing CGUs in a weak year to avoid impairment. 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.

Allocate shared assets thoughtfully

The technical anchor. Corporate assets that contribute to multiple CGUs should be allocated on a reasonable and consistent basis when possible, or tested through higher-level groupings when necessary. In application, the testing hierarchy should ensure shared assets are not omitted from carrying amounts. A frequent failure mode is excluding head-office or shared infrastructure because allocation is inconvenient. A concise review note should state the trigger, the rule applied, the evidence considered and the financial-statement consequence.

Practical illustration

Suppose three stores share a brand but each has its own customer base, pricing and cash inflows. The CGU may be at store level even though regional management reviews them together. If, however, stores cannot operate without a shared distribution asset whose contribution cannot be reasonably allocated, a higher-level testing step may also be required. 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 cash-inflow analysis; management-report mapping; internal-market evidence; CGU change approval; and corporate-asset allocation. 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

CGU design should reflect economic cash generation consistently; it is not a discretionary lever for changing impairment outcomes. 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.