Costs incurred internally to create intangible assets are expensed as incurred under U.S. GAAP. The exceptions are narrow and specific: certain internal-use software development costs, certain costs of software built for sale, implementation costs in cloud hosting arrangements, and the legal costs of registering patents, trademarks, and copyrights. Everything else, including the research and development spending that produced the idea in the first place, hits the income statement in the period you spend the money.
The practical consequence is that two companies doing similar work can show very different balance sheets. A company that acquires an intangible asset in a purchase records it as an asset. A company that builds the same kind of asset internally generally cannot, even when the economic value is identical.
The Default Rule and What It Covers
ASC 730 sets the baseline for research and development: expense in the period incurred. The reasoning is that most R&D projects carry too much uncertainty about whether they will produce anything of value, so standards do not let companies park those costs on the balance sheet as assets. This holds even when management is confident the project will succeed.
The costs swept into immediate expense under this rule are broad:
- Materials and supplies consumed in the R&D process, whether pulled from inventory or purchased for the project.
- Equipment and facilities acquired solely for one R&D project with no alternative future use. Equipment with alternative future uses is capitalized as a tangible asset, but its depreciation is charged to R&D expense.
- Salaries, wages, and benefits of employees working on R&D activities.
- Payments to outside parties conducting research on the company’s behalf.
- A reasonable allocation of overhead related to R&D. General administrative costs unrelated to research stay out of the R&D bucket.
The equipment distinction is where companies sometimes slip. A piece of lab equipment usable across multiple projects is capitalized as property. A prototype built for a single project is not.
Beyond R&D, ASC 350-30 explicitly prohibits capitalizing the cost of developing certain intangible assets internally. You cannot capitalize costs spent building goodwill, brand names, customer lists, or publishing titles if they were generated through your own operations rather than acquired. The reasoning is that these assets lack the specificity needed for reliable measurement. A brand built over decades of advertising and customer experience has real economic value, but isolating the cost that created that value is effectively impossible.
This produces the stark asymmetry on the balance sheet. When Company A buys Company B for more than the fair value of its identifiable assets, the excess is recorded as goodwill. Company A’s own internally built goodwill never appears as an asset. The same goes for customer relationships, proprietary processes, and trade names developed organically.
Internal-Use Software
Software developed for a company’s own internal use is the most significant area where capitalization of internally created intangible costs is required. ASC 350-40 governs the treatment, and through at least 2027 reporting periods it divides the development process into three stages with different accounting for each.
Preliminary Project Stage
All costs during initial planning are expensed. This stage covers evaluating whether to build the software at all, assessing technologies or vendors, and conducting feasibility studies. The stage ends when management formally commits to funding a specific project and authorizes the work.
Application Development Stage
Once management commits, capitalization begins. Costs eligible for capitalization during this stage include coding, software configuration and design, testing of functionality, and fees paid to external consultants working directly on the build. Interest costs incurred during this stage are also capitalizable under the general interest capitalization rules.
Not every cost during this stage qualifies. Training employees to use the software and converting data from legacy systems are always expensed, even when they occur during application development. The distinction is whether the cost creates the software asset itself or merely supports its deployment. Capitalization stops when the software is substantially complete and ready for its intended purpose.
Post-Implementation Stage
After the software goes live, costs revert to immediate expensing. Routine maintenance, bug fixes, and technical support are all period expenses. A major upgrade that adds significant new functionality can restart the capitalization cycle for those specific additions, creating a new mini-project that runs through the same three-stage analysis.
Changes Coming Under ASU 2025-06
The three-stage framework was designed for traditional, linear software development and fits poorly with agile methods, where planning, coding, and testing overlap rather than run in clean sequence. FASB addressed this in September 2025 by issuing ASU 2025-06, which removes all references to development stages from ASC 350-40.
Under the updated guidance, capitalization hinges on two criteria rather than project stages. Management must have authorized and committed to funding the project, and it must be probable that the project will be completed and perform its intended function. If the software involves novel technology or unproven features where significant development uncertainty remains unresolved through coding and testing, the probable-to-complete threshold is not met, and costs continue to be expensed.
The new standard takes effect for annual reporting periods beginning after December 15, 2027. Early adoption is permitted in any interim or annual period where financial statements have not yet been issued. FASB has acknowledged that the revised guidance will likely result in more costs being expensed for software sold through cloud computing arrangements, because the judgment-based probable-to-complete test is harder to satisfy than the old stage transitions.
Software Built for Sale or Licensing
Software built to be sold, leased, or marketed to external customers follows a different standard, ASC 985-20. The dividing line for capitalization is technological feasibility. All costs incurred before the software reaches technological feasibility are expensed as R&D. After technological feasibility is established, direct production costs, allocated indirect costs, and outside consultant fees are capitalized until the product is available for general release.
In practice, most companies establish technological feasibility at a late stage of development, often when a working model or beta version is complete. The bulk of development spending still hits the income statement as R&D expense, with only the final push toward commercial release being capitalized. The threshold is intentionally high, reflecting the same uncertainty concerns that drive the general R&D expensing rule.
Cloud Computing Implementation Costs
Companies that implement a cloud-based system they do not own or license face a specific capitalization question. ASU 2018-15 aligned the treatment of implementation costs in a hosting arrangement with the internal-use software model. If the cloud arrangement is a service contract rather than a software license, the same three-stage framework applies: preliminary costs are expensed, application development costs are capitalized, and post-implementation costs are expensed.
The key difference is where the capitalized costs sit on the balance sheet. Implementation costs for a hosting arrangement are recorded as a prepaid asset and amortized over the term of the hosting contract, not as an intangible asset. The amortization runs through the same income statement line as the hosting service fees, typically within operating expenses. This matters for financial statement presentation and for debt covenants that reference specific asset categories.
Training costs and data conversion costs follow the same rule they do for internal-use software: always expensed, even during the application development stage.
Patents, Trademarks, and Copyrights
The R&D that produces an invention is expensed under ASC 730, but the costs to legally protect that invention through registration are capitalized. The research that generated the idea hits the income statement. The legal work to secure exclusive rights creates an asset on the balance sheet.
Capitalizable costs include government filing fees, attorney fees for preparing and prosecuting the application, and other direct costs of the registration process. These are accumulated during the application period and recognized as an intangible asset once registration is secured.
If the application is denied, all accumulated costs are written off immediately. The same logic governs legal defense. Costs spent successfully defending a patent or trademark against infringement are added to the asset’s carrying value, because the successful defense confirms the exclusivity that gives the asset its worth. An unsuccessful defense signals that the asset’s value has evaporated, and the litigation costs are expensed along with any remaining carrying value of the right itself.
Recurring maintenance fees paid after a patent is granted are expensed as incurred rather than added to the asset’s cost. The USPTO requires maintenance fee payments at intervals during a patent’s life to keep it in force, and these are treated as period costs to maintain the existing right.
What Happens After Capitalization
Once a cost is capitalized, the next question is how to allocate it over time. The answer depends on whether the asset has a finite or indefinite useful life.
Finite-Life Assets
Most internally created intangibles that qualify for capitalization have finite lives. Capitalized software is amortized over its expected useful life, often three to five years. A patent is amortized over the shorter of its legal life or its economic useful life. The straight-line method is the default unless another pattern better reflects how the asset’s economic benefits are consumed.
Finite-life assets are tested for impairment only when specific events or circumstances suggest the carrying amount may not be recoverable. A technology shift that renders capitalized software obsolete would trigger a recoverability test. If the undiscounted future cash flows from the asset fall below its carrying value, the company recognizes an impairment loss.
Indefinite-Life Assets
Some intangible assets, particularly certain trademarks acquired in a business combination, are assigned indefinite useful lives. These are not amortized. They are tested for impairment at least annually, comparing fair value to carrying amount. If the carrying amount exceeds fair value, the company records an impairment loss equal to the difference. Once recognized, impairment losses on intangible assets cannot be reversed in later periods.
The annual test is mandatory regardless of whether any triggering event has occurred. Companies can perform a qualitative assessment first to determine whether a full quantitative test is necessary, but the obligation to evaluate the asset at least once a year does not go away.
Tax Treatment Does Not Follow Book Treatment
The GAAP treatment of these costs and the tax treatment have diverged in recent years, so getting the book entries right does not mean the tax return matches. Section 174A, enacted as part of the One, Big, Beautiful Bill Act, permanently restored full expensing of domestic R&D costs for tax years beginning after December 31, 2024. Foreign research expenses still must be capitalized and amortized over 15 years under Section 174.1Office of the Law Revision Counsel. 26 USC 174 – Amortization of Certain Research and Experimental Expenditures A separate Section 41 credit for qualified research activities applies regardless of how the costs are deducted.2Office of the Law Revision Counsel. 26 USC 41 – Credit for Increasing Research Activities Companies that capitalized domestic R&D during the 2022–2024 window under the old Section 174 rules can elect to deduct the remaining unamortized balances immediately or ratably over 2025 and 2026.
IFRS Follows a Different Rule
Companies reporting under International Financial Reporting Standards operate under a different framework. IAS 38 splits research costs (always expensed, matching U.S. GAAP) from development costs (potentially capitalizable, unlike U.S. GAAP). Under IFRS, development costs must be capitalized once the company can demonstrate technical feasibility, intention and ability to complete and use or sell the asset, probable future economic benefits, adequate resources, and reliable measurement of costs.3IFRS Foundation. IAS 38 Intangible Assets
An IFRS-reporting company working on a new pharmaceutical compound, industrial process, or piece of software could begin capitalizing development costs well before the project is finished, provided it clears all six hurdles. Under U.S. GAAP, the same costs would be expensed except in the specific software scenarios above. IFRS reporters often show higher asset balances and higher reported earnings during heavy development periods compared with U.S. GAAP counterparts doing identical work. When comparing companies across reporting frameworks, that difference needs to be adjusted for, or the comparison will mislead.