Cloud-based software costs are accounted for differently depending on whether the costs meet the criteria to be treated like internal-use software. ASU 2018-15 by the Financial Accounting Standards Board requires companies to evaluate implementation costs in a hosting arrangement using the internal-use software model in ASC 350-40. Under that model, capitalization is permitted for costs incurred in the application development stage such as coding, configuration, and testing, while costs for the planning stage, training, and ongoing vendor subscription fees must be expensed.
Accounting criteria and eligible costs
Practical guidance from Deloitte explains that companies must document which activities belong to each development stage and apply consistent capitalization policies. Capitalization begins when management authorizes the project and expects it to be completed and used for its intended purpose. Costs capitalized are amortized over the useful life of the software. Not all cloud arrangements qualify because many are service contracts where the primary deliverable is access rather than a distinct software asset under the company’s control.
Practical consequences and cross-border considerations
Choosing capitalize versus expense affects reported profit, assets, and performance metrics. Capitalization increases assets and defers expense recognition, which can improve operating income and EBITDA in the near term but requires amortization over time. Tax treatment and regulatory disclosures vary by jurisdiction and may require different timing or classification, so multinational corporations must coordinate accounting policy across territories and consider local tax authorities. PwC commentary highlights that smaller companies and startups often prefer to expense to avoid capitalization administrative burden and uncertain useful-life estimates, while larger technology firms frequently capitalize significant customization to better reflect long-term investments.
Culturally, industries that view software as a strategic asset tend to capitalize more of their development costs, signaling investment to investors. Environmentally, decisions that encourage extensive cloud migration can have sustainability implications because centralized data centers concentrate energy use and emissions, even though accounting choices do not change actual consumption. The key is robust documentation, consistent application of ASC 350-40 and ASU 2018-15 guidance from the Financial Accounting Standards Board, and consultation with auditors and tax advisors to align reporting, governance, and stakeholder expectations.