Under U.S. GAAP, the costs to create intangible assets internally are expensed in the period incurred, with a handful of narrow exceptions. The exceptions that matter in practice are internal-use software, software developed to sell or license, implementation costs in a cloud hosting arrangement, and the legal fees paid to register a patent, trademark, or copyright. Everything else — the research that produced the idea, the brand you built through advertising, the customer relationships you cultivated — hits the income statement as you spend the money.
The reason for the default is measurement uncertainty. When a company generates an intangible internally, isolating which dollars produced value and which produced nothing is usually impossible, so the standards refuse to let those costs sit on the balance sheet as assets.
The Default: R&D Costs Are Expensed as Incurred
ASC 730 sets the baseline. Research and development costs go to expense in the period incurred, even when management is confident the project will succeed. The categories the rule sweeps in are broad:
- Materials and supplies consumed in the R&D process, whether pulled from inventory or bought for the project.
- 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.
- Equipment and facilities acquired solely for one R&D project with no other future use. Equipment with alternative future uses gets capitalized as tangible property, but its depreciation runs through R&D expense.
The equipment rule is where companies sometimes trip. A piece of lab equipment usable across projects is capitalized as property. A prototype built for a single project is not.
Intangibles That Can Never Be Capitalized When Built Internally
ASC 350-30 explicitly prohibits capitalizing the cost of developing certain intangibles internally. Goodwill, brand names, customer lists, and publishing titles cannot go on the balance sheet if you generated them through your own operations rather than acquired them in a purchase.
This produces a stark asymmetry. When Company A buys Company B for more than the fair value of its identifiable assets, the excess is recorded as goodwill on Company A’s books. But the goodwill Company A built organically over its own history never appears. The same treatment applies to customer relationships, proprietary processes, and trade names developed in-house. Real economic value, no recognized asset.
Internal-Use Software
Software developed for the company’s own internal use is the biggest exception to the expense-it-all default. ASC 350-40 governs the treatment, and through at least 2027 reporting periods it splits the development process into three stages.
Preliminary Project Stage
Costs during the initial planning phase are expensed. This covers deciding whether to build the software at all, evaluating technologies or vendors, and running feasibility studies. The stage ends when management formally commits to funding a specific project and authorizes the work.
Application Development Stage
Once management has committed, capitalization begins. Eligible costs 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 capitalizable under the general interest capitalization rules.
Two categories are always expensed even when incurred during this stage: employee training and data conversion from legacy systems. The line is whether the cost creates the software itself or merely supports its deployment.
Capitalization stops when the software is substantially complete and ready for its intended purpose.
Post-Implementation Stage
After go-live, costs go back to immediate expensing. Routine maintenance, bug fixes, and technical support are period costs. A major upgrade that adds significant new functionality can restart the capitalization cycle for those specific additions, running through the same three-stage analysis as a mini-project.
What ASU 2025-06 Changes
The three-stage model was built for linear waterfall development and fits agile methods poorly, where planning, coding, and testing overlap rather than proceed in sequence. In September 2025, FASB issued ASU 2025-06, which removes all references to development stages from ASC 350-40.
Under the new guidance, capitalization turns on two conditions instead of 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 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 change will likely push more costs to the income statement for software delivered through cloud arrangements, because the judgment-based probable-to-complete test is harder to satisfy than the old bright-line stage transitions.
Software Developed to Sell or License
Software built to be sold, leased, or marketed to external customers follows ASC 985-20, not the internal-use rules. The dividing line here is technological feasibility. All costs before technological feasibility are expensed as R&D. After that point, direct production costs, allocated indirect costs, and outside consultant fees are capitalized until the product is available for general release.
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 ends up in the income statement, with only the final push toward 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 implementing a cloud-based system they don’t own or license face a related question. ASU 2018-15 aligned the treatment of implementation costs in a hosting arrangement with the internal-use software model. If the arrangement is a service contract rather than a software license, the same framework applies: preliminary costs are expensed, application development costs are capitalized, and post-implementation costs are expensed.
What differs is where the capitalized amount sits. 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 fees, typically within operating expenses. The distinction matters for financial statement presentation and for any debt covenants that reference specific asset categories.
Training and data conversion costs are always expensed here too, just as with internal-use software.
Patents, Trademarks, and Copyrights
The R&D that produced an invention is expensed under ASC 730. The costs to legally protect that invention through registration are capitalized. Clean split: the research hits the income statement, the legal work to secure exclusive rights creates a balance sheet asset.
Capitalizable registration costs include government filing fees, attorney fees for preparing and prosecuting the application, and other direct costs of the registration process. These accumulate during the application period and become an intangible asset once the registration is secured. If the application is denied, the accumulated costs are written off immediately.
Legal defense works on the same logic. Costs of successfully defending a patent or trademark against infringement are added to the asset’s carrying value, because a successful defense confirms the exclusivity that gives the asset its worth. An unsuccessful defense signals that the 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, such as the USPTO’s periodic fees required to keep a patent in force, are expensed as incurred. They preserve an existing right rather than create additional value.
Amortization and Impairment After Capitalization
Once a cost is capitalized, it has to be allocated over time. The treatment depends on whether the resulting asset has a finite or indefinite useful life.
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. Straight-line is the default unless another pattern better reflects how the asset’s benefits are consumed. Finite-life assets are tested for impairment only when events or circumstances suggest the carrying amount may not be recoverable. If undiscounted future cash flows fall below carrying value, the company records an impairment loss.
Some intangibles, particularly certain trademarks acquired in a business combination, carry indefinite useful lives. These are not amortized. They are tested for impairment at least annually by comparing fair value to carrying amount. Once recognized, impairment losses on intangible assets cannot be reversed in later periods.
Book Treatment Is Not Tax Treatment
Getting the GAAP treatment right does not settle the tax return. The two frameworks have diverged. For tax years beginning after December 31, 2024, Section 174A permanently restored full expensing of domestic research and experimental expenditures, so domestic R&D can be deducted in the year incurred. Foreign research expenses still have to be capitalized and amortized over 15 years under Section 174, beginning at the midpoint of the year in which the expenses are paid or incurred.1Office of the Law Revision Counsel. 26 USC 174 – Amortization of Certain Research and Experimental Expenditures A separate Section 41 credit is available for qualifying research activities regardless of how the underlying costs are deducted.2Office of the Law Revision Counsel. 26 USC 41 – Credit for Increasing Research Activities
IFRS Reaches a Different Answer
Companies reporting under IFRS work from a different framework. IAS 38 separates research costs (always expensed, matching U.S. GAAP) from development costs (potentially capitalizable, unlike U.S. GAAP). Once a company can demonstrate technical feasibility, intent and ability to complete, probable future economic benefits, adequate resources, and reliable cost measurement, it must capitalize development costs.3IFRS Foundation. IAS 38 Intangible Assets
The practical result is that an IFRS reporter working on a new pharmaceutical compound, industrial process, or piece of software may begin capitalizing well before completion, while a U.S. GAAP company doing identical work expenses the same costs except in the specific scenarios above. When comparing companies across reporting frameworks, this difference has to be adjusted for or the comparison will be misleading.