Can Product Development Costs Be Capitalised? A Finance Director's Guide to R&D Accounting

How to account for hardware and IoT development costs under IAS 38 — what must be expensed, what must be capitalised, and how to evidence it.

Your engineering team has spent nine months developing a connected medical monitoring device. The invoice total is $450,000. Now the CFO asks: do we expense this or capitalise it?
The answer changes your balance sheet, your tax position, and your EBITDA. Get it wrong and you risk an audit adjustment or restatement.
This post explains when product development costs can be capitalised, the specific criteria you must meet, and how to structure your R&D process to support compliant capitalisation. It is written for finance directors and CFOs managing hardware, embedded systems, and IoT product development.
R&D capitalisation is the accounting treatment of product development costs as intangible assets on the balance sheet rather than immediate expenses on the income statement, subject to meeting specific criteria under IAS 38 or equivalent national standards.
When Can Product Development Costs Be Capitalised?
Under IAS 38, development costs can be capitalised only from the point when technical feasibility is established and six specific criteria are met. All costs incurred before this point must be expensed as research.
This applies to companies reporting under IFRS — and in India under Ind AS 38, which mirrors IAS 38, or AS 26 for companies not on Ind AS. US GAAP is different: under ASC 730, research and development costs are generally expensed as incurred, with limited exceptions such as certain software development costs.
For hardware products, the transition point is typically the successful completion of a proof-of-concept or working prototype. Before that — market research, technology scouting, early experiments — is research and must hit the P&L.
After feasibility is proven, you can capitalise:
Engineering design and development labour
Software and firmware development
Testing and validation costs
Certification and regulatory compliance costs
Materials and components for development prototypes
Patent filing costs directly attributable to the product
Costs that remain expensed regardless of phase:
General administrative overheads
Sales and marketing expenses
Training costs
Costs of relocating operations
What Are the Six IAS 38 Criteria for Capitalisation?
All six criteria must be demonstrated before costs can be capitalised. Until all six are met, the costs are expensed. Under IAS 38 this is not a choice: once all six criteria are met, qualifying development costs must be capitalised.
Criterion | What It Means | Evidence Required |
1. Technical feasibility | The product can be built with available technology | Prototype test reports, technical reviews |
2. Intention to complete | The company intends to finish and deploy the asset | Board resolutions, project charters |
3. Ability to use or sell | The company has the market or internal need | Market analysis, customer letters of intent |
4. Adequate resources | Funding and technical capacity exist to complete | Approved budgets, resource plans |
5. Future economic benefits | The asset will generate revenue or cost savings | Financial projections, business case |
6. Reliable measurement | Costs can be traced to the specific asset | Time tracking, project accounting codes |
The most commonly challenged criterion is technical feasibility. For hardware, a working prototype with documented test results is the standard evidence. For software, a demonstrable build with core functionality working is typically sufficient.
How Do You Determine the Research-to-Development Transition Point?
The transition from research to development is the most critical judgment in R&D capitalisation. For hardware products, the transition typically occurs at one of these milestones:
Proof of concept complete: A prototype demonstrates that the core technology works. This is a common transition point for embedded and IoT products.
Alpha prototype validated: The first integrated prototype meets key performance specifications. This is a stronger transition point with clearer evidence.
Design freeze: The architecture is locked and development shifts to refinement. This is a later transition point that may reduce the amount capitalised.
The key is consistency. Apply the same transition criteria across all projects. Document the rationale for each project. Your auditor will compare your judgment against this documented policy.
The companies that get capitalisation right define their research-to-development transition in writing before the project starts. Retrofitting the boundary invites auditor challenge and potential restatement.
How Are Capitalised Development Costs Treated After Recognition?
Once capitalised, development costs are carried as intangible assets on the balance sheet. They are amortised over the useful life of the resulting product.
For hardware and IoT products, useful life is often estimated at three to five years, based on the product's expected market life. Amortisation begins when the asset is available for use — not when revenue starts. Straight-line amortisation is standard unless there is a clear basis for a different pattern.
If the product fails, becomes obsolete, or no longer has economic value, the capitalised amount must be impaired. This creates a one-time hit to the income statement. While the product is still in development, the capitalised amount must be tested for impairment at least once a year; once it is in use, it is tested whenever there is a sign of impairment.
Capitalised development costs are also subject to the same impairment indicators as other intangible assets: market decline, technological obsolescence, legal restrictions, or changes in business strategy.
What Documentation Do You Need to Support Capitalisation?
Auditors will challenge your capitalisation. Be prepared with:
Written policy: A documented R&D capitalisation policy defining the research-to-development boundary and the six IAS 38 criteria.
Project records: Evidence of technical feasibility achievement with dates and test results.
Time tracking: Clear attribution of staff costs to specific projects and phases.
Cost allocation: Methodology for splitting shared costs (facilities, software licenses) across projects.
Board evidence: Minutes or resolutions showing intent and resource commitment.
Market evidence: Documentation supporting future economic benefits.
Without this documentation, your auditor will likely require you to expense the costs. The burden of proof is on you.
Structuring your hardware R&D for compliant capitalisation?
Our product development team at Implantaire provides phased project structures with clear milestone documentation that supports your capitalisation policy. Talk to our team about structuring your next project with accounting compliance in mind.
What Are the Tax Implications of R&D Capitalisation?
Tax treatment of R&D costs often differs from accounting treatment. In India, expenditure on scientific research related to the business — revenue and capital (other than land) — is deductible under section 45 of the Income-tax Act, 2025, which replaced section 35 of the 1961 Act from 1 April 2026.
Tax rules on when development costs are deducted often differ from the accounting treatment. The gap creates temporary differences, recognised as deferred tax assets or liabilities.
Tax incentives for R&D vary by jurisdiction:
India: deduction for business-related scientific research (section 45, Income-tax Act, 2025)
USA: R&D tax credit (Section 41); domestic research costs are again deductible immediately (Section 174A, tax years beginning after 2024), while foreign research costs are amortised over 15 years
UK: merged R&D expenditure credit scheme from April 2024, with extra support (ERIS) for loss-making R&D-intensive SMEs
EU: national schemes vary widely — tax credits, super-deductions and payroll-tax reliefs
Consult a tax advisor familiar with your jurisdiction. The interaction of accounting standards and tax law is complex and changes regularly. This article is general information, not accounting or tax advice — confirm the treatment for your company with your auditor and tax advisor.
Capitalisation is not a way to make losses disappear. It is a faithful representation of economic reality. If your product has no clear path to market, expensing the cost is the right accounting treatment and the right business decision.
By Shanid A P, Director at Implantaire
Frequently Asked Questions
Can product development costs be capitalised under accounting standards?
Yes, product development costs can be capitalised under IAS 38 and equivalent accounting standards, but only from the point when technical feasibility is established and the entity can demonstrate future economic benefits. Costs incurred before this point — typically the research phase — must be expensed as incurred. For hardware products, this generally means costs after proof-of-concept validation can be capitalised, while early exploration and research are expensed.
What is the difference between research and development for accounting purposes?
Research is original investigation to gain new scientific or technical knowledge. Under IAS 38, all research costs must be expensed as incurred. Development is the application of research findings to produce new or improved products. Development costs can be capitalised if six criteria are met: technical feasibility, intention to complete, ability to use or sell, future economic benefits, adequate resources, and reliable measurement of costs.
What are the IAS 38 criteria for capitalising development costs?
IAS 38 requires all six criteria to be met before development costs can be capitalised: (1) technical feasibility of completing the asset, (2) intention to complete and use or sell it, (3) ability to use or sell the asset, (4) availability of adequate technical, financial and other resources, (5) demonstration of future economic benefits through market existence or internal use, and (6) reliable measurement of expenditure attributable to the asset during development.
When should hardware R&D costs be expensed versus capitalised?
Hardware R&D costs should be expensed during the research phase, which includes market research, technology exploration, and early feasibility studies. Once technical feasibility is demonstrated — typically after a working proof-of-concept or prototype — subsequent development costs can be capitalised. This includes engineering design, firmware development, testing, and certification costs. Manufacturing tooling is usually capitalised separately as property, plant and equipment; general production start-up costs are expensed.
How are capitalised development costs amortised?
Capitalised development costs are amortised over the useful life of the resulting asset, starting when the asset is available for use. For hardware products, useful life is often estimated at three to five years, based on the product's expected market life. Amortisation method should reflect the pattern of economic benefits — straight-line is commonly used when no better basis is available. If the product becomes obsolete or fails, the capitalised amount must be impaired.
What documentation is needed to support R&D capitalisation?
Documentation required includes: dated evidence of technical feasibility achievement (such as prototype test reports), board resolutions approving the project, project budgets showing adequate resources, market analysis demonstrating economic viability, timesheets and cost records attributing expenditure to specific development phases, and internal policies defining the research-to-development transition point. Without this documentation, auditors are likely to require the costs to be expensed.


