The Business Model Test under Ind AS 109: Evidence over Intention

The business-model test is a portfolio-level assessment of how financial assets are actually managed to generate cash flows. It is not an instrument-by-instrument election and it is not established by a policy label alone; the conclusion should be supported by observable management behaviour. 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 business models can mask different management objectives and produce incorrect classification. A robust approach connects commercial substance, the Ind AS 109 decision criteria, measurement evidence and presentation consequences in one coherent file.

Assess at the right level of aggregation

The accounting logic. A business model is identified at the level at which groups of financial assets are managed together for a particular objective. Operationally, the entity may have more than one business model within a legal entity or treasury function and should segment portfolios accordingly. The main judgement risk is forcing all debt instruments into one business model because they sit in the same department. Evidence should be retained at the same level of detail as the accounting conclusion, with assumptions version-controlled and exceptions explicitly approved.

Use management reporting as evidence

The decision point. The information provided to key management personnel often reveals whether performance is evaluated on yield collection, fair value, liquidity sales or another objective. For implementation, accounting should compare stated policy with actual reports, KPIs and risk limits. Where errors often arise is documenting a hold-to-collect model while management is primarily compensated on short-term fair-value performance. The accounting result should reconcile to the underlying contract, valuation or subledger rather than rely on a standalone spreadsheet conclusion.

Analyse sales in context

The core requirement. Sales do not automatically disqualify a hold-to-collect model; their frequency, volume, timing and reasons must be considered in relation to the objective. In a controlled close process, sales because of credit deterioration, concentration management or infrequent liquidity events can have different implications from routine profit-taking. A common weakness is using a fixed numeric sales threshold without considering why the sales occurred. The working paper should identify the relevant facts, source data, judgement and conclusion so that an independent reviewer can reproduce the decision.

Distinguish hold-to-collect-and-sell

The principle. Some portfolios achieve their objective through both collecting contractual cash flows and selling assets, making both activities integral rather than incidental. For a review-ready file, liquidity portfolios managed to meet expected cash needs may provide evidence of this model when sales are part of the normal strategy. The risk to avoid is calling a portfolio hold-to-collect merely because interest income is important. 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.

Monitor without re-electing

The technical anchor. Business models should be monitored for consistency, but reclassification occurs only when the entity changes the way it manages financial assets in a manner that meets the standard's stringent criteria. In application, governance should distinguish a true strategic change from ordinary changes in market conditions or sales activity. A frequent failure mode is using reclassification as a response to temporary market volatility. A concise review note should state the trigger, the rule applied, the evidence considered and the financial-statement consequence.

Practical illustration

Suppose a treasury portfolio is described as 'liquidity reserves'. If management routinely forecasts liquidity needs, collects interest and sells securities to meet those needs, the evidence may support a collect-and-sell objective rather than hold-to-collect. The conclusion should follow how the portfolio creates value, not the wording used in the investment policy. 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 portfolio segmentation; management-report evidence; sales analytics; governance minutes; and periodic consistency 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

The most persuasive business-model memo reads like a description of how the portfolio is run, because that is precisely what the test is designed to capture. The most useful way to apply Ind AS 109 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.