How to Account for Cloud Computing Costs Under GAAP

Accounting for cloud computing costs under GAAP starts with classifying the arrangement, because the classification decides everything that follows. A contract that transfers a software license is capitalized as an asset under ASC 350-40. A contract that gives your company control over specific hardware may contain a lease under ASC 842. Everything else is a service contract: the subscription fees are expensed as the service is received, and only certain implementation costs can be capitalized under the three-stage model in ASU 2018-15. Get the classification right first, then the accounting entries fall into place.

Step One: Classify the Arrangement

Before booking any entries, work out which of three buckets the contract falls into. The label the vendor uses on the invoice does not decide this; the substance of what you receive does.

Does the Contract Transfer a Software License?

A hosting arrangement contains a software license only when both of these are true: your company has the contractual right to take possession of the software at any time during the hosting period without significant penalty, and it is feasible for your company to run the software on your own hardware or hire an unrelated third party to host it. “Without significant penalty” means you could take delivery without incurring significant cost and could use the software separately without a major reduction in its value or usefulness.

Most SaaS subscriptions fail both tests. You cannot download a typical multi-tenant application and run it on your own servers. Some customized enterprise platforms do meet the criteria, particularly when the vendor provides source code and self-hosting is realistic. When both criteria are met, treat the arrangement as a software license acquisition under ASC 350-40, capitalize the license cost, and amortize it over its useful life.

Does an IaaS or PaaS Contract Contain a Lease?

Infrastructure and platform arrangements need a second look, because they can give your company enough control over hardware to create an embedded lease under ASC 842. Two conditions must both be met. First, there must be an identified asset: the computing capacity is physically distinct or represents substantially all of an asset’s capacity, and the vendor lacks a substantive right to swap out the underlying hardware during the contract. Second, your company must have the right to direct how and for what purpose the computing resources are used and to obtain substantially all of the economic benefits from that use.

When both are met, recognize a right-of-use asset and lease liability, amortize the asset over the lease term, and reduce the liability as you pay. In practice, most IaaS and PaaS contracts are shared, multi-tenant environments where the vendor keeps substitution rights, so they fail the identified-asset test and are treated as service contracts.

Everything Else Is a Service Contract

If the arrangement transfers no license and contains no lease, it is a service contract. That is where most SaaS and cloud spending lands, and it is the case the rest of this article follows.

Step Two: Expense the Subscription Fees

Subscription fees under a service-contract hosting arrangement hit the income statement in the period the service is received. There is no asset to record for the subscription itself. Prepay a year and the prepayment sits in current assets, then moves to expense month by month as the service is delivered. That is the straightforward part. The complexity lives in the implementation work that surrounds the subscription.

Step Three: Apply the Three-Stage Model to Implementation Costs

FASB’s ASU 2018-15 aligned the accounting for implementation costs in a service-contract hosting arrangement with the rules for developing internal-use software. Every implementation project splits into three stages, and the stage determines whether a cost is capitalized or expensed.1Financial Accounting Standards Board. Accounting Standards Update 2018-15 – Customer’s Accounting for Implementation Costs Incurred in a Cloud Computing Arrangement That Is a Service Contract

Preliminary Project Stage: Expense Everything

All costs in this stage are expensed. This is the research and decision-making phase: evaluating vendors, comparing alternatives, deciding what functionality you need, and drafting initial plans. Employee time spent here is a period cost, even for people who later work on capitalizable tasks. Until you have committed to a specific project, the spending is exploratory.

Application Development Stage: The Only Capitalization Window

This is where capitalization is possible. Capitalizable costs include external fees paid to the vendor or consultants for configuration, coding, and testing the application, along with direct internal labor costs for employees working on those same activities. Internal labor has to be supported by detailed time tracking that ties specific hours to development-stage work.1Financial Accounting Standards Board. Accounting Standards Update 2018-15 – Customer’s Accounting for Implementation Costs Incurred in a Cloud Computing Arrangement That Is a Service Contract

Several categories are excluded from capitalization even during this stage. Training costs cannot be capitalized regardless of when they occur. Data conversion costs are generally expensed; the narrow exception is that if your company develops or purchases software specifically to perform the conversion, the cost of that conversion software can be capitalized. The underlying work of cleansing, reconciling, and migrating the data is always expensed. General and administrative overhead, including salaries of executive sponsors, indirect project managers, and other employees whose time is not directly tied to development activities, is also always expensed.

Post-Implementation Stage: Expense Again

Once the application is substantially ready for its intended use, the window closes. All costs from that point forward are expensed as incurred, internal or external. This covers end-user training, ongoing maintenance, minor configuration tweaks, and routine system administration.1Financial Accounting Standards Board. Accounting Standards Update 2018-15 – Customer’s Accounting for Implementation Costs Incurred in a Cloud Computing Arrangement That Is a Service Contract

One exception. If your company later undertakes a significant upgrade that adds new functionality or materially extends the system’s useful life, that project gets its own fresh three-stage analysis, and a new round of capitalizable development costs can result. Routine enhancements and bug fixes stay in expense.

Step Four: Split Bundled Contract Prices

Cloud contracts rarely arrive as one line item. A typical enterprise deal bundles the subscription, implementation services, training, data migration, and sometimes future upgrade rights into one price. Because each element follows different rules, the bundled fee has to be broken apart.

ASU 2018-15 requires allocation based on each element’s relative stand-alone selling price. If a vendor charges $400,000 as a lump sum for implementation that includes coding, data conversion, and training, you have to carve out each component’s fair value. Only the portion attributable to capitalizable development activities gets capitalized. The data conversion and training portions are expensed even though they were incurred during the development stage.1Financial Accounting Standards Board. Accounting Standards Update 2018-15 – Customer’s Accounting for Implementation Costs Incurred in a Cloud Computing Arrangement That Is a Service Contract

Without clear documentation of what each fee component covers, auditors will push back on any capitalization. Negotiate detailed statements of work that separate implementation elements before the contract is signed, not during the year-end close.

Step Five: Amortize the Capitalized Costs and Test for Impairment

Capitalized implementation costs are amortized over the term of the hosting arrangement on a straight-line basis, unless a different systematic method better reflects how your company benefits from access to the software. The term includes the fixed noncancelable contract period, plus any renewal option periods your company is reasonably certain to exercise, plus any periods where the vendor controls the renewal decision.1Financial Accounting Standards Board. Accounting Standards Update 2018-15 – Customer’s Accounting for Implementation Costs Incurred in a Cloud Computing Arrangement That Is a Service Contract

“Reasonably certain” is a judgment call. A company that has invested heavily in a platform, built workflows around it, and would face substantial switching costs is more likely to renew, so a longer amortization period is defensible. A short pilot with easy alternatives argues for using only the initial term.

Capitalized costs also have to be tested for impairment whenever indicators suggest the carrying amount may not be recoverable, using the framework for long-lived assets. Common triggers include a decision to abandon the platform, a significant change in how the system is used, or the vendor ceasing to provide the service. The unit of account is the asset group level, meaning the lowest level at which cash flows are identifiable and largely independent. If you terminate a cloud arrangement early, remaining unamortized costs must be evaluated for impairment and written off to the extent they are no longer recoverable. Early terminations happen more often than companies expect at signing, so build realistic terms into your amortization period from the start.

Step Six: Put the Numbers in the Right Places on the Financial Statements

This is the detail most commonly missed. ASU 2018-15 requires the capitalized implementation costs to follow the hosting arrangement’s own presentation, not the treatment used for owned software assets.

Because your company does not own the underlying software, FASB decided the capitalized implementation costs should not look like owned assets. They follow the hosting arrangement wherever it goes.

Disclosures

Companies capitalizing cloud implementation costs must disclose the nature of hosting arrangements that are service contracts. ASU 2018-15 requires disclosures about capitalized implementation costs as though they were a separate major class of depreciable asset, meaning the gross carrying amount, accumulated amortization, and the amortization period used.1Financial Accounting Standards Board. Accounting Standards Update 2018-15 – Customer’s Accounting for Implementation Costs Incurred in a Cloud Computing Arrangement That Is a Service Contract Footnotes should also describe the company’s accounting policy, making clear which costs are capitalized and which are expensed, and summarize the nature of material cloud arrangements and their classification.

A Note on Tax

Tax treatment does not necessarily follow the GAAP treatment. Software development costs, including cloud implementation work that qualifies as research or experimentation, are treated as research and experimental expenditures under the tax code. For domestic activities, Section 174A allows immediate deduction of qualifying costs in the year paid or incurred for tax years beginning after December 31, 2024. Research conducted outside the United States must still be capitalized and amortized ratably over 15 years, starting at the midpoint of the tax year in which the costs are incurred.2Office of the Law Revision Counsel. 26 U.S. Code 174 – Amortization of Research and Experimental Expenditures The mismatch between GAAP amortization over the contract term and immediate or 15-year tax treatment creates book-tax differences that generate deferred taxes. Handle those separately from the GAAP entries.