For an internal R&D project, the accounting question is not simply whether the project is innovative or likely to succeed. Under Ind AS 38, the crucial issue is which phase the project is in and the date on which all recognition conditions are first demonstrated. Research expenditure is expensed as incurred. Development expenditure can become an intangible asset only after a strict recognition gate is crossed.
ICAI's Educational Material on Ind AS 38 announcement explains that the standard governs recognition and measurement of intangible assets and the treatment of costs incurred to generate them. The detailed material is available through the ICAI publication portal, while the current ICAI Ind AS Volume II index lists Ind AS 38 among the applicable standards.
Research and development are not the same accounting phase
The research phase is the exploratory stage: obtaining new knowledge, searching for alternatives and evaluating possible solutions. Ind AS 38 does not permit recognition of an intangible asset arising from research. Those costs are recognised as an expense when incurred because, at that stage, the entity cannot yet demonstrate that an identifiable intangible asset exists that will generate probable future economic benefits.
The development phase is later and more advanced. It involves applying research findings or other knowledge to a plan or design for producing new or substantially improved products, processes, systems or services before commercial production or use. Even then, development expenditure is not automatically capitalised. All six recognition conditions must be demonstrable.
If the entity cannot distinguish the research phase from the development phase of an internal project, Ind AS 38 requires the expenditure to be treated as if it were incurred in the research phase. Contemporaneous project documentation is therefore important.
The six conditions that must be met before development costs can be capitalised
An internally generated intangible asset arising from development is recognised only if the entity can demonstrate all of the following:
- Technical feasibility: the asset can be completed so that it will be available for use or sale.
- Intention to complete: management intends to complete the asset and use or sell it.
- Ability to use or sell: the entity is capable of putting the completed asset into use or selling it.
- Probable future economic benefits: there is support for how the asset will generate benefits, such as a market for the output or evidence of usefulness when the asset will be used internally.
- Adequate resources: sufficient technical, financial and other resources are available to complete development and use or sell the asset.
- Reliable measurement: expenditure attributable to the asset during development can be measured reliably.
These conditions operate as a single gate: capitalisation begins only when every condition is demonstrable.
Capitalisation starts on the recognition date, not at project launch
The cost of an internally generated intangible asset includes qualifying expenditure incurred from the date the asset first meets the recognition criteria. Expenditure already recognised as an expense cannot later be reinstated as part of the intangible asset merely because the project subsequently becomes viable.
Finance teams should therefore identify a supportable recognition date from evidence rather than choose a convenient accounting cut-off. The recognition date should be tied to the point at which technical feasibility, management intention, ability to use or sell, future benefits, resources and reliable cost measurement are all established.
Which development costs can form part of the intangible asset?
After the recognition gate is crossed, the asset's cost includes directly attributable expenditure necessary to create, produce and prepare it to operate in the manner intended by management. Ind AS 38 gives examples such as materials and services consumed in generating the asset, employee-benefit costs arising from generation of the asset, fees to register a legal right, and amortisation of patents or licences used to generate the asset.
Not every project cost belongs in the asset. Selling, administrative and other general overheads are excluded unless directly attributable to preparing the asset for use. Identified inefficiencies and initial operating losses are excluded, and expenditure on training staff to operate the asset is also excluded. A project code still needs a cost-classification review; charging an item to the project does not make it capitalisable.
Worked example: internal software development
Assume a company begins exploring a new internal workflow platform in January. From January to March it evaluates technologies, tests alternative architectures and builds early proof-of-concept prototypes. It spends ₹12 lakh during this exploratory phase. Those costs are research-phase expenditure and are expensed.
On 15 April, the company completes a feasibility assessment, approves the final architecture, commits the required budget and development team, documents the operational benefits expected from the platform, confirms that it intends and is able to complete and use the software, and begins reliable project-level cost tracking. Assume all six criteria are demonstrably met on that date.
From 15 April onward, directly attributable qualifying development expenditure can form part of the intangible asset. If ₹36 lakh of qualifying developer, external service and directly consumed project costs is incurred after that date, that amount may be capitalised. The earlier ₹12 lakh cannot be brought back onto the balance sheet. If the company separately incurs staff-training costs before launch, those training costs are expensed rather than included in the internally generated intangible asset.
Evidence checklist before recording a development asset
- Technical feasibility memo: evidence that the chosen design or solution can be completed.
- Approved intention: a dated management or project approval showing the decision to complete and use or sell the asset.
- Use or sale plan: documentation showing how the completed asset will actually be deployed or commercialised.
- Future-benefit support: a business case, market evidence or internal-use analysis linking the asset to expected economic benefits.
- Resource evidence: approved budgets, staffing plans, funding availability and access to required technical resources.
- Reliable cost records: project codes, time records, vendor invoices and other records that separate directly attributable development expenditure from research, overhead, training and other excluded costs.
- Recognition-date memo: a short conclusion identifying the exact date all six conditions became demonstrable and the evidence supporting that date.
Common mistakes to avoid
- Capitalising because management believes the project will succeed. Commercial optimism does not replace the six recognition conditions.
- Capitalising from day one. Early exploration and alternative evaluation normally belong to the research phase.
- Using an arbitrary cut-off date. The capitalisation date should follow evidence, not a convenient month-end.
- Reinstating previously expensed research costs. Once expenditure has been expensed before the recognition criteria are met, Ind AS 38 does not allow it to be reinstated as part of the asset.
- Capitalising every cost charged to the project. Only qualifying directly attributable costs after the recognition date belong in the internally generated intangible asset.
- Ignoring prohibited internally generated items. Internally generated brands, mastheads, publishing titles, customer lists and similar items are not recognised as intangible assets under Ind AS 38.
Practical takeaway
A defensible Ind AS 38 R&D policy is built around a documented phase change. Research is expensed. Development is capitalised only after all six conditions are demonstrated, and only qualifying expenditure incurred from that point is included in the asset. A strong control is a dated recognition memo supported by technical, commercial, funding and cost-tracking evidence. That approach makes the accounting conclusion easier to explain, reproduce and audit without retrospectively rewriting the history of the project.
