If you pay to configure and stand up a cloud-based application for your own business use, ASU 2018-15 lets you capitalize certain implementation costs of SaaS and cloud computing arrangements rather than expensing them as you go, provided the arrangement is a service contract and the costs were incurred during the application development stage. Everything else in the standard flows from those two gates.
Is Your Arrangement a Service Contract or a Software License
This classification decides your entire accounting treatment, so start here. A hosting arrangement is a service contract, and falls under ASU 2018-15, unless it clears a two-part test: you have the contractual right to take possession of the software at any point during the hosting period without a significant penalty, and it is feasible for you to run the software on your own infrastructure or through an unrelated third-party host.1Financial Accounting Standards Board. Accounting Standards Update 2018-15 Fail either prong and you have a service contract.
Most SaaS subscriptions fall on the service-contract side because the vendor keeps control of the software and you never receive the code. That matters because a software license would sit on your balance sheet as an intangible asset, while a service contract creates no software asset at all. The only balance sheet item you get from a service-contract implementation is the capitalized setup costs themselves. Read the vendor agreement for language about your right to take delivery of the code, and ask honestly whether your organization could host it independently.
One boundary worth flagging: ASU 2018-15 applies only when you are the customer. If your business builds a SaaS platform to sell, lease, or market to outside customers, those development costs follow Subtopic 985-20, not this standard.1Financial Accounting Standards Board. Accounting Standards Update 2018-15
Which Implementation Costs You Can Capitalize
Under the current standard, whether a cost gets capitalized or expensed depends on which of three project stages produced it. The stage boundaries are where most implementation accounting disputes originate, so document your project timeline carefully.
Preliminary Project Stage
This covers the early work of identifying business needs, evaluating vendors, defining performance requirements, and picking a direction. Every dollar spent here, whether on internal labor or outside consultants, is expensed as incurred.2Financial Accounting Standards Board. ASU 2025-06 – Intangibles Goodwill and Other Internal-Use Software You have not yet committed to a specific path, so nothing is being built.
Application Development Stage
Once management authorizes the project, commits funding, and it becomes probable the project will be completed, you enter the application development stage. Costs to configure the software, design interfaces, code customizations, install components on hardware, and test the system qualify for capitalization.2Financial Accounting Standards Board. ASU 2025-06 – Intangibles Goodwill and Other Internal-Use Software Both internal labor and third-party fees can be capitalized, but only for hours spent directly on qualifying activities. A developer splitting time between the new implementation and maintenance of an existing system needs an hour allocation. General overhead and administrative costs stay in expense regardless of timing.
Post-Implementation Stage
After the software is ready for its intended use, the capitalization window closes. Training, ongoing maintenance, and routine support are expensed as incurred.2Financial Accounting Standards Board. ASU 2025-06 – Intangibles Goodwill and Other Internal-Use Software The frequent mistake is capitalizing consultant fees for user training or go-live support because they feel like part of the implementation. Once the system works as intended, those costs belong on the income statement.
Data Migration Is Mostly an Expense
Moving records from a legacy system into a new cloud platform is often the single largest line in an implementation budget, and most of it cannot be capitalized. Data conversion costs, including cleansing records, reformatting files, and manually validating data, must be expensed as incurred.1Financial Accounting Standards Board. Accounting Standards Update 2018-15
There is one exception. If you develop or purchase software specifically to automate the transfer of old data into the new system’s format, the cost of creating that conversion software can be capitalized, even when the tool is temporary. When you hire a third party for data migration work, ask for an invoice that separates the components. The portion tied to building conversion software may qualify; the hands-on cleaning and validation does not.
Upgrades vs. Maintenance After Go-Live
You will keep spending money on the system after implementation. Whether those later costs get capitalized turns on one question: does the work give the software functionality it did not previously have? Modifications that let the system process a new transaction type, integrate with a new platform, or support a new business function qualify as upgrades and can be capitalized.
Bug fixes, security patches, performance tuning, and minor adjustments to keep existing features working are maintenance and go straight to expense. When a single project bundles both and you cannot reasonably separate the two, the safe answer is to expense the whole thing. Auditors will challenge capitalization that is not supported by documentation showing what new capability resulted.
Amortization and Impairment of the Capitalized Costs
Capitalized implementation costs are amortized on a straight-line basis over the term of the hosting arrangement, unless another pattern better reflects how you consume the benefit.1Financial Accounting Standards Board. Accounting Standards Update 2018-15 The term includes the initial fixed period plus any renewal periods you are reasonably certain to exercise, termination options you are reasonably certain not to exercise, and extension options controlled by the vendor.
What counts as “reasonably certain” requires judgment. The standard directs you to weigh factors including technology obsolescence, competitive dynamics, and the economic value of your own implementation costs when the renewal decision comes due.1Financial Accounting Standards Board. Accounting Standards Update 2018-15 A company that spent $2 million configuring a platform has a real incentive to renew, which can support including renewal periods in the amortization term. Reassess the term periodically, and treat changes as a change in accounting estimate.
Monitor the capitalized asset for impairment as well. If you abandon the arrangement before contract expiration, or the software stops delivering the value you expected, the remaining balance may need to be written down. The impairment framework is the same one used for other long-lived assets: if carrying amount exceeds future economic benefit, record a loss.
Where These Amounts Appear on the Financials
Presentation is designed to keep the capitalized costs traveling with the hosting service itself. On the balance sheet, capitalized implementation costs sit in the same line item where a prepayment for the hosting service would sit.1Financial Accounting Standards Board. Accounting Standards Update 2018-15 If that prepayment is a non-current asset, the capitalized costs are non-current too.
On the income statement, amortization of these costs goes into the same expense line as the hosting fees. If the SaaS subscription is in general and administrative expense, the amortization runs through G&A. Cash outflows are classified consistently with the hosting service payments, typically within operating activities.1Financial Accounting Standards Board. Accounting Standards Update 2018-15
For footnotes, describe the nature of your hosting arrangements that are service contracts, and treat the capitalized implementation costs as if they were a separate major class of depreciable asset. That means gross amount, accumulated amortization, and useful life information at the level you would give for property and equipment.1Financial Accounting Standards Board. Accounting Standards Update 2018-15 Companies with significant cloud investments sometimes bury these amounts in a prepaid expense footnote rather than giving them the standalone visibility the standard requires.
Book-Tax Differences to Track
The book treatment under ASU 2018-15 and the federal income tax treatment of software implementation costs do not line up. The tax question turns on whether the costs are specified research or experimental expenditures under Section 174.
For tax years 2022 through 2024, Section 174 as amended by the Tax Cuts and Jobs Act required taxpayers to capitalize and amortize all specified research and experimental expenditures, including software development costs, over five years for domestic work or fifteen years for foreign work, starting at the midpoint of the tax year.3Internal Revenue Service. Notice 2023-63 Legislation enacted in 2025 reversed course for domestic expenditures. For tax years beginning after December 31, 2024, domestic research and experimental costs, including software development, can be deducted in the year incurred, or the taxpayer can elect to capitalize and amortize them over at least sixty months. Taxpayers who capitalized these costs during the 2022 through 2024 period can claim catch-up deductions for the remaining unamortized balances.
Not every cloud implementation cost is a Section 174 expenditure to begin with. IRS Notice 2023-63 excludes several common SaaS implementation activities from the definition of software development: purchasing and installing pre-built software, configuring parameters to make it compatible with your business, reengineering business processes around the software, and related planning and testing.3Internal Revenue Service. Notice 2023-63 Training, routine maintenance, and most data conversion work are also excluded. In practice, much of what you capitalize on the books under ASU 2018-15 may be currently deductible for tax, while custom coding may follow a separate path. Track the differences for deferred taxes.
What Changes Under ASU 2025-06
FASB issued ASU 2025-06 in 2025, and it makes significant changes to the internal-use software guidance in Subtopic 350-40. The most notable shift is the elimination of the three-stage project model. In its place, a single capitalization threshold applies: costs can be capitalized only when management has authorized and committed to funding the project and it is probable the project will be completed and the software will perform as intended.2Financial Accounting Standards Board. ASU 2025-06 – Intangibles Goodwill and Other Internal-Use Software
The new standard also introduces “significant development uncertainty.” If the software involves novel or unproven functionality where technical feasibility has not been demonstrated through coding and testing, or if significant performance requirements have not been settled and keep changing substantially, the probable-completion threshold is not met and capitalization is deferred until that uncertainty resolves. FASB has acknowledged the change will likely result in more costs being expensed, particularly for complex or innovative implementations.2Financial Accounting Standards Board. ASU 2025-06 – Intangibles Goodwill and Other Internal-Use Software
ASU 2025-06 takes effect for fiscal years beginning after December 15, 2027, with early adoption permitted. Transition can be prospective, modified, or retrospective. For 2026 reporting the three-stage model under ASU 2018-15 still governs, but if you are in the middle of a multi-year cloud implementation, particularly one with uncertain scope or experimental features, start evaluating the impact of the new rules now.