Research and development spending is one of the easiest areas to misclassify under AS 26, Intangible Assets. A project may be commercially promising, but that does not mean every rupee spent on it can be capitalised. The accounting turns on a disciplined distinction between the research phase, which is expensed, and the development phase, where capitalisation is permitted only after all recognition conditions are demonstrated.
ICAI’s AS 26 Intangible Assets publication page is a dedicated first-party reference. ICAI also lists AS 26 in its Accounting Standards compendium. Practical non-compliance examples are available in ICAI Financial Reporting Review Board’s Study on Compliance of Financial Reporting Requirements.
Start with the recognition question
AS 26 does not allow expenditure to become an asset merely because management expects future benefits. The item must satisfy the definition and recognition criteria for an intangible asset, including control of a resource, expected future economic benefits and reliable measurement of cost. If expenditure does not create or acquire a recognisable asset, it is charged to profit and loss when incurred.
Labels such as “product development”, “software project” or “new platform” are therefore not enough. Finance teams need evidence showing what stage the project has reached and, for development expenditure, why the recognition tests are satisfied from a particular date.
Research phase: expense the expenditure
No intangible asset arising from research, or from the research phase of an internal project, is recognised. Research expenditure is recognised as an expense when incurred because the enterprise cannot yet demonstrate that an intangible asset exists that will generate probable future economic benefits.
Research commonly involves obtaining new knowledge, searching for alternatives, evaluating technologies or processes, and investigating possible product or system solutions. The key feature is that the entity is still exploring whether a viable solution exists.
What if research and development cannot be separated?
If an enterprise cannot distinguish the research phase from the development phase of an internal project, AS 26 requires it to treat the project expenditure as if it were incurred in the research phase only. Weak project accounting can therefore prevent otherwise qualifying development expenditure from being supported as an asset.
Development phase: all six conditions matter
An intangible asset arising from development is recognised only when the enterprise 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 finish the asset and use or sell it.
- Ability to use or sell: the enterprise 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 its output or demonstrable internal usefulness.
- Adequate resources: sufficient technical, financial and other resources are available to complete the development and use or sell the asset.
- Reliable measurement: expenditure attributable to the asset during development can be measured reliably.
Capitalisation should therefore begin only when the evidence supports the recognition conditions. A financial-year start, board approval date or first coding date is not automatically the correct capitalisation date.
Worked example: internally developed software
Assume a company starts exploring a new billing platform on 1 April. From April to June it evaluates architectures, tests alternative technologies and assesses whether the project is viable. It incurs ₹9 lakh during this period. That amount is research expenditure and is expensed.
On 1 July, the company completes its feasibility assessment, approves the final design, commits funding, establishes that the platform can be completed and used internally, and starts reliably tracking attributable development costs. From July to December it incurs ₹24 lakh of qualifying development expenditure. Assuming all six conditions remain satisfied, the ₹24 lakh is capitalised while the earlier ₹9 lakh remains an expense.
Expenditure already recognised as an expense in previous financial statements is not reinstated later as part of the intangible asset merely because the project subsequently succeeds.
What belongs in the development asset?
Once recognition begins, the cost of an internally generated intangible asset comprises expenditure directly attributable to creating, producing and preparing the asset for its intended use. The working paper should therefore link qualifying employee time, external developer invoices, testing and other attributable costs to the recognised development period rather than capitalising a broad project-cost pool.
Software can also create a classification question. ICAI’s FRRB observations note that software integral to hardware may form part of the related tangible asset, while software that is not integral to the hardware is treated as an intangible asset. The substance of the arrangement matters more than the ledger description.
When does amortisation start?
After initial recognition, AS 26 carries an intangible asset at cost less accumulated amortisation and accumulated impairment losses. Amortisation begins when the asset is available for use, not simply when development spending stops or when the final invoice is paid.
The depreciable amount is allocated systematically over the best estimate of useful life. AS 26 contains a rebuttable presumption that useful life will not exceed ten years from the date the asset is available for use. If a longer life is justified, the reasons and significant factors supporting that conclusion require disclosure. Legal or contractual rights can also constrain useful life.
Common mistakes to avoid
- Capitalising all R&D expenditure without separating research from development.
- Using management optimism as evidence instead of documenting the six recognition conditions.
- Capitalising from project inception when the development conditions were demonstrated only later.
- Reviving earlier research costs after the project becomes successful.
- Using a deferred-revenue-expenditure bucket for costs that do not meet the definition of an asset.
- Failing to track project costs reliably, weakening support for development capitalisation.
- Starting amortisation at the wrong date instead of when the asset becomes available for use.
Year-end documentation checklist
- Prepare a project timeline separating research and development activities.
- Document the date on which all six development recognition conditions were first satisfied.
- Retain feasibility evidence, approvals, budgets, funding support and expected-benefit analysis.
- Reconcile capitalised costs to payroll records, vendor invoices and project ledgers.
- Identify and expense costs incurred before the recognition date or costs that are not directly attributable.
- Document the date the asset became available for use and begin amortisation from that point.
- Review useful life, amortisation, impairment and disclosures before closing the financial statements.
Practical takeaway
The safest AS 26 approach is to treat an internal project as a timeline rather than one accounting bucket. Expense the research phase, capitalise development expenditure only from the date all six recognition conditions are supported, retain reliable project-cost evidence, and start amortisation when the asset is available for use. The documentation around the transition from research to development is often what makes the accounting treatment defensible.
