If you spend money on research and development, the accounting answer under U.S. GAAP is usually straightforward: expense it as incurred. ASC 730 sets the general rule that R&D costs go straight to the income statement in the period you spend them. You do not capitalize them as an asset on the balance sheet.
But "usually" is doing some heavy lifting in that sentence. There are important exceptions for software development costs (which fall under ASC 350-40), in-process R&D acquired in a business combination, and funded research arrangements where a third party is footing the bill. Each of these follows a different path, and getting the classification wrong can misstate both earnings and assets.
This guide covers the core rules of ASC 730, how to distinguish R&D from software capitalization, what happens with acquired R&D, and where funded research fits in.
Under ASC 730, research and development costs are expensed in the period they occur. The standard defines two categories:
Research is planned investigation aimed at discovering new knowledge that might be useful in developing a new product, service, process, or technique, or in significantly improving an existing one.
Development is the translation of research findings into a plan or design for a new or improved product or process, whether intended for sale or for internal use. This includes conceptual formulation, design, testing, and prototyping.
The costs that fall under ASC 730 include salaries of R&D personnel, materials and supplies consumed in R&D activities, depreciation on equipment used solely for R&D, contract services (payments to others for work performed on your behalf), and allocable overhead.
One thing that catches people: if you buy equipment that has no alternative future use outside of a specific R&D project, the full cost is expensed at the time of purchase. If the equipment has alternative future use in other R&D projects or elsewhere in the business, you capitalize it and depreciate it normally, charging the depreciation to R&D expense as appropriate.
The logic behind the expensing rule is uncertainty. At the research stage, it is not clear whether the work will produce anything commercially viable. GAAP takes the conservative position: do not put speculative future benefits on the balance sheet.
This is one of the most common areas of confusion. Software development does not live entirely under ASC 730. Depending on the nature of the software, different rules apply.
Software to be sold, leased, or marketed (ASC 985-20). Costs incurred before technological feasibility is established are expensed under ASC 730. Once technological feasibility is reached (typically when a detailed program design or working model is completed), costs can be capitalized. After general release, capitalization stops and amortization begins.
Internal-use software (ASC 350-40). Three stages apply: the preliminary project stage (expensed), the application development stage (capitalized), and the post-implementation stage (expensed). ASC 350-40 allows capitalization during the middle stage, which includes coding, testing, and installation. For cloud computing arrangements that are service contracts, ASC 350-40 also provides guidance on capitalizable implementation costs.
Where the line sits. Early-stage work (evaluating alternatives, determining needs) gets expensed. Once you commit and start building, capitalization begins. After the software is live, maintenance goes back to being expensed. The practical challenge is documenting the transition points clearly enough to withstand audit scrutiny.
When you acquire a business, you often pick up R&D projects that are not yet complete. Under ASC 805 (business combinations), in-process research and development that is acquired gets a different treatment than internally generated R&D.
Acquired in-process R&D is recognized as an intangible asset at fair value on the acquisition date. It is not expensed immediately. Instead, it sits on the balance sheet as an indefinite-lived intangible until the project is either completed or abandoned.
Once the project is completed, the asset becomes finite-lived and is amortized over its useful life. If the project is abandoned, the remaining asset is written off as impairment.
This is a meaningful difference from the general approach. If you had done the same R&D work internally, you would have expensed every dollar as incurred. But because you acquired it in a business combination, it lands on the balance sheet. The reasoning: in a purchase transaction, the buyer paid a real price that reflects the value of the in-process work, so it should be recognized as an asset.
For how impairment testing applies to these assets after acquisition, our guide on ASC 360 long-lived asset impairment covers the framework.
Sometimes a third party pays for R&D that your company performs. Under ASC 730-20, the accounting depends on whether the arrangement transfers risk to the funding party or whether your company retains the obligation to repay.
If the funding party bears the risk: The performing entity does not expense the costs. Instead, it recognizes revenue or a cost reduction as work is performed. This applies when the funder owns the results regardless of outcome.
If the performing entity retains the risk: If repayment is required regardless of outcome, the arrangement is essentially debt. You record a liability and expense the costs as incurred.
The key question is who bears the downside if the research fails. That determines whether you are doing contract work or borrowing money.
It is worth flagging one area that trips up a lot of teams: the difference between how R&D is treated for GAAP purposes versus for tax purposes.
Under GAAP (ASC 730), most R&D is expensed immediately. But under the Tax Cuts and Jobs Act, starting with tax years beginning after December 31, 2021, Section 174 requires companies to capitalize and amortize R&D expenditures over five years (15 years for foreign research). This means the same costs you expense on your books may need to be capitalized on your tax return and amortized over time.
This creates a book-tax difference that needs to be tracked for deferred tax purposes. Many companies were caught off guard by this change, and it remains one of the more discussed provisions in tax planning.
For context on how R&D tax credits interact with these rules, that guide covers the credit mechanics.
Capitalizing early-stage R&D. Under the standard, research and early development costs are expensed. Do not put these costs on the balance sheet just because you expect the project to succeed.
Misclassifying software stages. The transition from preliminary to development stage determines when capitalization starts under ASC 350-40. Unclear documentation leads to restatement risk.
Ignoring the funded research analysis. If someone else is paying for your R&D, do not automatically expense the costs. Analyze whether the arrangement is a true funding deal or a disguised loan.
Mixing up GAAP and tax treatment. The Section 174 capitalization requirement for tax does not change the GAAP treatment. You still expense under ASC 730 for financial reporting, even if you capitalize for tax.
1. What does ASC 730 require? It requires that research and development costs be expensed as incurred. You do not capitalize R&D as an asset under the general GAAP rule.
2. What costs qualify as R&D under ASC 730? Salaries of R&D staff, materials consumed in R&D, depreciation on R&D equipment, contract R&D services, and allocable overhead. Equipment with no alternative future use is expensed at purchase.
3. Can software development costs be capitalized? Yes, but not under ASC 730. Externally marketed software follows ASC 985-20 (capitalize after technological feasibility). Internal-use software follows ASC 350-40 (capitalize during the application development stage).
4. What is the difference between ASC 730 and ASC 350-40? ASC 730 covers general R&D and requires expensing. ASC 350-40 covers internal-use software and allows capitalization during the development stage. The two overlap during the early phases of software projects, where expensing applies until you move into active development.
5. How is in-process R&D treated in an acquisition? It is recognized as an intangible asset at fair value under ASC 805. It is not expensed at acquisition. Once the project is complete, it is amortized. If abandoned, it is impaired.
6. What is a funded research arrangement? An arrangement where a third party pays for R&D work. If the funder bears the risk of failure, the performing entity does not expense the R&D. If the performing entity must repay regardless of outcome, it is treated as a loan and the costs are expensed.
7. Does ASC 730 apply to tax reporting? No. ASC 730 is a GAAP standard. For tax purposes, Section 174 now requires capitalization and amortization of R&D costs over five years (or 15 for foreign research). This creates a book-tax difference.
8. Can R&D equipment be capitalized? Only if it has alternative future use beyond the current project. If the equipment is useful only for a single R&D effort, the full cost is expensed when purchased.
Need help with R&D accounting, ASC 730 compliance, or navigating the ASC 350-40 capitalization rules? Madras Accountancy works with CPA firms across the U.S. on complex financial reporting. Reach out to discuss your situation.
Section 127 lets employers give up to $5,250 in tax-free educational assistance, now including student loan repayment. See how the plan works.
Section 127 lets employers give up to $5,250 in tax-free educational assistance, now including student loan repayment. See how the plan works.
ASC 460 guidance on guarantee recognition and disclosure, fair value measurement, product warranties, and indemnification agreements.
